Access Layer
Access And Progeny
This page explains how access, creation, and routing connect. The practical rule is simple: source profiles create assets, and approved routes preserve benefits where supported.
Vanguard is the legacy access tier. Benefits carry forward as new Access Token variants launch.
Characters, children, gear, creatures, and project assets can inherit traceable source qualities.
Royalty benefits depend on approved marketplace routes that honor the collection's royalty flow.
Developers can choose a Progeny structure or request a project-specific attribute tree.
User Summary
Why This Page Exists
Users should understand what carries forward, what can be generated from their profile, and where support matters. This is the short version before reading the full policy layer.
Future Progeny Flow
One Genesis. Many Future Builds.
Early users should think of as the origin deed, not the entire Engine. is planned to become the layer where characters, gear, vehicles, creatures, and project-specific assets can be generated from that origin.
The Soul Deed is intended as the one-person entry point. It anchors the profile layer before later Engine branches open.
Future is planned as the repeatable creation layer. Eligible users, especially Vanguards, may be able to generate and sell multiple assets over time.
A developer game character can be strict if the game needs one active character per player. Weapons, armor, transport, companions, and similar assets can stay more flexible.
01
Legacy Access
wallets keep their access tier as the Engine expands. New variants may introduce new benefits, but eligibility is designed to carry forward by default.
02
Progeny Model
includes children and material assets: clothing, armor, weapons, creatures, adversarial constructs, transport, and project objects. Each Project can draw from 479,001,600 user-specific possibilities, with supply rules shaped by the asset type and published project terms.
03
Royalty Routing
When the contract and route support it, the originating is written into a NFT as a receiver. Approved marketplaces, including OpenSea when creator earnings are supported, help preserve that route.
04
Developer Access
Developers can choose which structure fits their game or request a specific character for users to generate from or purchase through a collection.
05
Marketplace Limits
Some marketplaces do not honor routing. Users should use approved marketplaces for and sales so contract-level attribution has the best chance to work as intended.