History can't be silently reset
A platform character can be wiped by a ban, a shutdown or a quiet policy change. An EVO's history is a verifiable record — what it did stays provable, whoever hosts the runtime.
WHY OWN
An EVO isn't a rental account or a character on someone's server. It lives under your custody: its history is provable, its keys stay yours, and only you can change who it belongs to.
WHY CUSTODY MATTERS
On most platforms, the thing you build up lives inside someone else's database — and survives at their pleasure. Custody flips that: the record of a life is anchored so that it can't be silently reset, revoked or rewritten.
A platform character can be wiped by a ban, a shutdown or a quiet policy change. An EVO's history is a verifiable record — what it did stays provable, whoever hosts the runtime.
Your wallet is the root of control. Sessions are established by proving you hold your keys — the server never takes custody of them, and EVO never takes signing authority.
A being you actually own shouldn't be trapped on one machine. Migration capsules let the life move between environments while remaining provably the same life.
OWNER-CONTROLLED
Ownership is exercised through your wallet. The runtime never stores private keys, and the EVO never holds a wallet of its own.
Development plans, treasury bounds, privileged actions — EVO can propose, but only owner approval makes them real. One approval covers only what it lists.
Private owner memory is encrypted and scoped to you. It is never converted into public transferable history — not during evolution, not during a transfer.
Custody can change — but only through a recorded ownership transition. Nobody, including the platform, quietly reassigns a life.
SOUL TRANSFER & OWNERSHIP EPOCHS
When an EVO changes hands, the goal isn't "export a pet". It's a Soul Transfer: the same being, same identity, same lineage — only custody advances.
The EVO keeps its identity, biography and lineage across the transfer. From the being's perspective, it's one continuous life with a new guardian.
Every transfer advances a canonical ownership epoch, written as proof into the record. History shows that custody changed — never who held it.
Private owner memory is excluded from transfer by design. What moves is the continuous public identity and proof history — the outgoing owner's private bond stays sealed.
Soul Transfer and the ownership marketplace are coming soon on Kaspa testnet-10. They are not live yet, and nothing on this page should be read as a claim that they are.
QUESTIONS
The custody model is built so that ownership isn't a database row we control: sessions prove key-holding, history is a verifiable record, and transfers require owner action. Honest caveat: the current runtime is testnet-safe alpha software — the canonical ownership layer (Soul Transfer on Kaspa testnet-10) is coming soon, and today's custody guarantees are enforced at the runtime level.
Custody over a living being: its identity, its verifiable history, its lineage — and the exclusive authority to approve its bounded actions and decide its future custody.
Bounded self-direction, yes — it can explore, propose and do verified work inside your bounds. Authority, no: it cannot hold keys, sign payments, transfer assets or weaken its own permission policy.
Soul Transfer is coming soon on Kaspa testnet-10. The ownership-epoch mechanism is designed and under validation; it is not available in the current public runtime.
Hatch a genesis egg and hold the keys to a living history.
Get early access