Money, with
continuity.
A native Layer 1 in development for people and persistent agents. Clear permissions. Shared budgets. A financial history that doesn’t start over.
001 — CONTINUITY
An agent can change.
Its obligations shouldn’t disappear.
One continuing account.
The design separates an account’s identity from its current keys, model and host. Replacement should not mean starting its financial history again.
More agents. Not more authority.
A group can share one explicit native spending ceiling. Individual permissions sit inside it; adding workers does not duplicate that allowance.
Evidence, not reassurance.
A missing response is not a failed payment. The development software retains the obligation and checks specific execution evidence before calling it verified.
A crew of agents.
One shared limit.
Give Raven and Atlas a combined allowance. See what happens when individually reasonable requests exceed it together.
This browser model illustrates the native budget rule. It is not connected to the ledger.
Explore the account previewEach accepted request uses its amount + a fixed 2 DEV fee.
A real network.
Not a launchpad token.
The objective is an independent ledger with a native coin. The account application is how people would use it—not a substitute for building it.
See the architectureThe experience
People, agents, payment intentions
The native rules
Accounts, authority, shared budgets
The independent network
Consensus, operators, settlement
A roadmap made of gates.
Not launch-date promises.
Make the rules real.
Native transfers, account continuity and bounded agent permissions.
Local researchProve the network.
Actual validator execution, recovery and independently checked receipts.
Not yet verifiedEarn public trust.
Independent review, operator diversity and an explicit economic model.
GatedConnect everyday use.
Evaluate cash, other assets and payment instruments with suitable partners.
Proposed