This came up in Twitch chat tonight and I said I'd have a proper look at it afterwards, because I don't think "because blockchain" is really a useful answer to why EVE Frontier is built the way it is.The obvious question is why does Frontier need a blockchain at all? Couldn't Fenris Creations just have a normal database and build a much more capable version of ESI around it?The first answer is yes. They could.There isn't some capability where blockchain can write to a game and APIs can't. ESI itself has write endpoints. It is a REST API, authenticated access uses EVE SSO and OAuth 2.0, applications register with Fenris, request defined scopes and operate within whatever endpoints Fenris exposes. There are also rate limits, caching rules and all of the other things you'd expect from a centrally operated API.So I don't think "blockchain can do this but an API can't" is the right argument.In fact Frontier itself uses both.Fenris described this pretty clearly during the Sui hackathon earlier this year. Mods that actually exist inside the world can run through Smart Assemblies and Sui, while external applications such as maps, dashboards, coordination tools and analytics can use an official API to read and react to the live universe.That distinction is probably the easiest way I've found to explain why the blockchain is there.If I'm building something like EF-Map, I mostly want information. Give me objects, events, ownership, structures and whatever else Fenris chooses to expose and I'll do something useful with it. An API is excellent for that.If I'm changing the behaviour of a gate that physically exists inside the game world, that is a different problem.A Smart Gate might allow only members of a particular Tribe through. It could charge for access. It could check ownership of something else. A Smart Storage Unit could become a shop. Different pieces of infrastructure can interact with systems written by different developers. The important bit is that this isn't just an external website looking at the game. Player-written logic is becoming part of the shared game state and can produce an actual in-game effect.You could still build all of that with an API.But now the API needs to be a very powerful write API and Fenris needs to operate the authoritative execution environment behind it. They need to decide how third-party code is hosted, how it executes, how users authorise actions, how ownership works, how state is shared between applications, how one developer's system can interact with another developer's system, how history is recorded and how all of that is secured.Blockchain doesn't make those problems disappear, obviously. It does give them an existing architecture for a lot of it.Frontier migrated from Ethereum to Sui on 11 March 2026 with Cycle 5. Sui is an object-centric Layer 1 blockchain and I think the object-centric part is particularly relevant to Frontier.The Frontier whitepaper talks about eventually targeting 100,000 unique star systems containing huge numbers of player-built ships, bases and infrastructure. On Sui an object can have its own identity, ownership and history. Fenris specifically describes that as fitting its existing item-centric approach to building EVE games.So rather than one enormous contract containing the entire world state, a gate can be an object. A storage unit can be an object. An item can be an object. Those objects have defined rules and interfaces and player-written Move code can extend what they do within those boundaries.That also gives you composability.If I write a system against those objects, somebody else doesn't necessarily need Fenris to build a special endpoint so their system can interact with mine. They can build against the same state and the same contracts. One player's market, currency, access-control system or reputation system can potentially become an input to something another player has built.That's quite different from the normal ESI model.With ESI, Fenris decides what an application can ask for. They expose an endpoint, document it, maintain it and decide which scopes are required. If the data or action I want isn't exposed, I can't just invent the endpoint myself.That doesn't make ESI bad. I've built against it quite extensively recently and it does exactly what it is designed to do. But it is fundamentally an interface into a private game operated by Fenris.Sui is being used for selected parts of Frontier as part of the game itself.There's also the execution model. Independent transactions on Sui can be processed in parallel rather than every transaction having to wait behind unrelated transactions touching completely different objects. Fenris gives parallel execution, low latency and near-instant finality as some of the reasons it chose Sui.That matters if you're trying to put potentially billions of game objects and player interactions onto a chain without the whole thing behaving like the older mental image people understandably have of blockchain where you press a button and stare at a confirmation spinner for 30 seconds.It doesn't mean every calculation in Frontier is happening on Sui. It isn't.You're still playing a normal real-time MMO running on Fenris' Carbon engine. Your ship isn't submitting a blockchain transaction every frame because you've moved your mouse slightly to the left. The blockchain is being used where persistence, ownership, programmability and shared state actually matter.There is also the history and verification side.If the authoritative state of something is on-chain, I don't necessarily need to trust an API operator or somebody else's database when they tell me what happened to it. The transaction history exists independently and can be indexed by anybody.That has already been useful for tools. Rather than waiting for Fenris to build a historical endpoint for every possible question, you can index the underlying state yourself.There are obviously limits to how desirable that is in EVE. Information asymmetry matters. Knowing things other people don't know is part of the game.Fenris is aware of that and its Sui architecture also includes Walrus and Seal for data storage and access control. So "blockchain means everybody can see absolutely everything" isn't really the intended model either.Then there is the other reason that I don't think is worth trying to hide behind technical terminology.Money.Frontier is deliberately being built so value can cross the boundary of the game.Its whitepaper describes the Frontier economy as a participant in the global economy which can interact with virtual or real economies. $EVE is planned as an external token on Sui and has an actual game use, with the current design requiring it for the advanced Crude Mining Lenses used to extract Crude Matter.That's very different from EVE Online.EVE Online lets money travel quite a long way in one direction. I can buy PLEX for real money and sell it for ISK. What I cannot legitimately do is decide I've had enough of EVE, sell my 100 billion ISK and withdraw the proceeds into my bank account. Fenris' EVE Online RMT rules explicitly prohibit selling ISK or in-game items for real money.Frontier is intentionally opening that boundary.Whether that's a brilliant idea or a terrible idea is a completely separate discussion. I think there are perfectly reasonable arguments on both sides, especially once speculation starts affecting something that is supposed to be a game.But it absolutely belongs in the answer. Blockchain isn't just being used because somebody decided databases weren't fashionable enough. The external economic layer is part of Frontier's design.There are downsides to all of this as well.If I was building a game and didn't want these properties, I'd take the database and API every time.A database is simpler. It's under your control. Private information stays private. Updating something is straightforward. If somebody finds a catastrophic exploit you can stop the server, fix the data and carry on. You don't have an external consensus network, smart contracts, keys, transaction fees, chain infrastructure or another ecosystem to worry about.An API is also extremely good for things which don't need shared execution. I don't need a blockchain transaction to ask how many people are in Jita. I don't need cryptographic ownership to download a list of solar systems. There would be no benefit.There is also additional security risk when you're deliberately allowing other people to deploy code that affects your universe.Sui's Move language is designed around assets and ownership and removes or makes much harder some classes of smart-contract bug, but that isn't the same thing as saying player-written code can't contain bugs. It obviously can.Fenris still has to design the interface between player code and the game extremely carefully. The fact that my contract can control a gate does not mean it should be able to give my character a billion hit points. The underlying object defines what actions are available and the mod operates within that boundary.Scaling isn't free either.Sui's object model and parallel transaction execution are a much better fit for this than some older blockchain architectures, which is one of the reasons Fenris moved to it, but running a distributed blockchain is still more complicated than updating a row in PostgreSQL.And there is dependency risk. Fenris is deliberately building part of its universe on infrastructure it doesn't completely control. That's partly the point, but it's still a trade.So I don't think I would describe blockchain as "better than an API".I think that is asking the wrong question.Frontier already has an API, because APIs are very good at some things. It also has Sui because Fenris wants selected parts of the universe to have shared programmable state, object-level ownership and provenance, composability between things different people build, independently verifiable history and an economy that can interact with the world outside the game.Could Fenris build its own centralised version of all of that?I think so.But by the time you've built a globally accessible state layer, cryptographic ownership, signed transactions, a secure execution environment for arbitrary third-party code, permanent history, composability between applications, asset settlement and an external economic layer, you're starting to recreate quite a lot of the functionality the blockchain is providing anyway.Whether that trade eventually turns out to have been worth making is probably something we won't really know until Frontier is much further along.But yeah, that's my current understanding of why it's there rather than just being ESI 2.0. via /r/EVEFrontier https://ift.tt/8tdJekx
Social Media Icons