Architecture · Retrospective
What stays off-chain in a blockchain game

People who meet Playermon through its NFTs and tokens often assume the game itself runs on a blockchain. Very little of it does. Almost everything the team built this February sits on our servers. That is a design choice, and it is worth explaining, because where the line falls decides what players can check for themselves and what they have to trust us with.
What February's work looked like
Our weekly development reports this month were mostly about data and servers:
- On 4 February, crafting Breeding Pod NFTs from Breeding Shards went live in SpaceDen.
- The team updated the database diagram for Playermons, enemies, the PvE maps and levels, and each player's progress through them.
- Configuration for the Playermon stat formulas was written, along with the API requirements for loading maps and levels.
- The game client was connected to updated server APIs for logging in, listing a player's Playermons, and creating teams.
- Enemies got their object structure in the game, and the designers began moving skill data into the spreadsheet that holds the game's data tables.
- Backend developers added an hourly limit on claims in the SpaceDen treasure hunt, tested it, and deployed it to production.
The 27 February update collects most of it. None of it touches a smart contract.
What the chain is for
On Polygon we keep what a player must be able to prove without asking us: which Playermons a wallet owns, the Breeding Pods crafted from shards, the PYM and SGEM a wallet holds, and sales on our marketplace. Any wallet or block explorer can read those records, and they do not depend on our database being correct. That is the promise an NFT game makes, and it is the part that needs a public ledger.
Crafting shows how the two sides meet. The player crafts inside SpaceDen, which is our game interface, but what comes out is an NFT in the player's wallet, not an entry in our database.
What the server is for
A game also has state that changes constantly: the layout of a level, an enemy's stats, how far a player has got through a map, which Playermons sit together in a team. Putting each of those changes on a chain would charge players a fee and a confirmation wait for ordinary clicks, and it would turn every balance change into a contract change. The stat formulas will be tuned many times before PvE is ready. They belong in configuration the team can adjust, not in code that is expensive to replace.
Teams are a good example of the split. The Playermons in a team are on-chain; the team itself is our record. Choosing a team moves no value, so it should be instant and free. The one thing the server must never do is let a team keep a Playermon that the wallet no longer owns. For ownership, the chain is the authority and our copy has to follow it.
The hard case: limits on claims
The treasure-hunt limit is where server logic touches value. Players find hidden SGEM in SpaceDen, and SGEM is an on-chain token, so the rate at which the game hands it out matters to everyone who holds it. The new rule gives each account a maximum number of claims per hour, and accounts with more Playermons, up to three, get more claims.
We put that rule on the server. A contract could enforce a limit too, but it sees only wallets and transactions, while the treasure hunt is a game mechanic the server already runs. The cost of that choice is trust: players have to believe the rule is applied the same way to every account. I do not think that cost can be removed, only reduced, and the way to reduce it is to publish the rule. That is why I want limits like this one stated in our public updates, as this one was, rather than adjusted quietly.
The test I use
My test for where something should live is two questions. Would a player need to prove it to someone else? Would a player lose something of value if we changed it without telling them? If either answer is yes, it goes on-chain or behind a rule we have published. If both are no, it stays on the server, where we can fix it the same day.
Moxie Marlinspike's essay on web3 in January pointed out how much of what is called decentralised still runs through ordinary servers. For a game I think that is acceptable, and mostly unavoidable. What is not acceptable is being vague about it. Players should know which parts of Playermon they own outright and which parts they are trusting us to run.