Most NFT projects are permanent only at the ownership layer.
The token exists on-chain, but the actual world around it often depends on servers, mutable metadata, admin keys, upgradeable contracts, and off-chain game logic.
That creates a strange contradiction.
The NFT is supposed to be permanent, but the experience around it can disappear as soon as the team stops maintaining the server.
I have been thinking about a different model:
an ownerless on-chain world protocol.
The Basic Idea
Instead of treating an NFT as a static collectible, the NFT becomes a stateful object inside a world.
The world does not depend on a backend server to decide what happened.
The contract defines the rules.
That means:
- no owner
- no upgrade admin
- no pause switch
- no rescue function
- no required server
- metadata generated from contract state
- traits and state stored on-chain
- evolution rules defined by contracts
- interactions such as fusion, hunting, rewards, or mutation handled on-chain
In this model, the contract is not only the ownership layer.
It becomes the rulebook.
Why This Matters
A lot of NFT projects say they are permanent because the token exists forever.
But if the art, metadata, game state, or evolution logic depends on an API, then the world is still fragile.
A fully on-chain world should be able to survive without the original team.
No official UI should be required.
No admin should be needed to keep the rules alive.
If a user can read contract state and reconstruct the world, the protocol has a much stronger claim to permanence.
The Hard Parts
This design is not easy.
Some obvious problems appear immediately:
- How do you keep evolution interesting without relying on off-chain randomness?
- How do you make metadata expressive enough while staying fully on-chain?
- How do you prevent interactions from becoming too expensive?
- How do you let creators define their own worlds without reintroducing admin trust?
- How do users understand the world if there is no official UI?
These are not just UX problems.
They are protocol design problems.
Creator-Defined Worlds
One direction I find interesting is letting creators provide seed images and parameters, then define the rules of their world through immutable contracts.
The first world is only one instance.
The more important idea is the interface:
- creator supplies seeds
- creator defines parameters
- contract defines traits
- contract defines state changes
- contract defines evolution
- users interact with the world directly
Different worlds can share the same protocol idea while having different rules.
An Early Example
One early experiment in this direction is Eternal Beings.
It describes itself as a fully on-chain, ownerless, non-upgradeable evolving world protocol.
The first instance seems to focus on beings that can evolve, fuse, hunt, mutate, and carry state over time.
Site:
I am less interested in whether this specific project succeeds, and more interested in the design question:
Should NFT worlds be designed to survive without servers, admins, or upgrade keys?
Or is that too much complexity for most users to care about?
Top comments (0)