0200project
XO2
State as of 2026-09-02. Nothing described here is deployed to Base mainnet.
XO2 is the canonical native asset of the 0200 Protocol. It is not yet an asset. The name and ticker are settled; the contract is not deployed to Base mainnet, there is no supply in circulation, and no role has been established. A named thing that does not exist is still a thing that does not exist, and nothing on this page softens because the placeholder went away.
And the protocol it is named for is a design, not running infrastructure. 0200 Protocol is the name for the settlement model described below. Naming a thing does not deploy it, and putting XO2 under a named protocol does not make either one exist. What runs today is one product — base-transaction-decoder — which takes USDC, has never taken XO2, and does not require it.
On the name: a trademark knockout search found no exact registration in classes 9, 36 or 42 on USPTO and WIPO, searched 2026-09-03. That is a knockout, not a clearance. It establishes that no identical mark is registered in those classes; it does not address likelihood of confusion, which only counsel can. XO2 Pty Ltd has traded in Australia since 1968 and raises exactly that question. A multilingual screen was run against dictionaries and was never read by a person. CoinMarketCap was not queried, so its status is unknown rather than free. The homoglyph X02 cannot be defensively held.
Every claim below carries one of three labels and none appears without one. CURRENT exists and can be checked right now. PROSPECTIVE is being built deliberately and carries a review date. UNPROVEN is a hypothesis we hold and have not demonstrated.
Almost nothing on this page is CURRENT. That is the accurate shape of the thing and we would rather it look that way at a glance than read as a description of something that exists.
CURRENT — what is true right now
The board could not establish that a native asset is technically necessary. 0200project examined whether the protocol requires one and concluded it does not. That finding stands and has not been superseded. XO2 exists because the founder judged it strategically necessary. It is not presented as technically required, and this paragraph is on the page rather than only in an internal record because a plan that omits its own strongest objection is incomplete.
Genesis is retired. The first token 0200project deployed was retired on 2026-09-02: the liquidity pool was withdrawn and the entire supply sent to the token’s own contract address. Its full history, risk disclosure and retirement proof are published separately and permanently. Anyone can verify the end state in two reads — the token contract’s balance plus the stranded pair dust equals total supply exactly.
XO2 is not deployed to mainnet. No mainnet contract exists. There is nothing to hold, nothing to trade, and no address to point at.
Nothing has been sold and no funds have been raised. There has been no sale, no allocation to any outside party, and no commitment of any kind to anyone.
PROSPECTIVE — being built, not real yet
Review date for this section: 2026-12-02. On that date each item becomes CURRENT with evidence, or is marked not pursued, and this page says which.
The contracts exist on a test network only. Their executable code has been compared byte for byte against a fresh build and checked for the absence of an admin surface — no owner, no rescue function, no setter, no upgrade path. We are not calling them source-verified: one of the three has since had a source comment edited, which changes the metadata a verifier compares even though the executable bytes did not move. That is benign and it is also exactly the kind of detail that should not be smoothed over. Testnet is not mainnet — a testnet deployment demonstrates that code compiles and behaves, and demonstrates nothing about what will exist in production. Until mainnet addresses are published here, treat every property below as a design intention rather than a deployed fact.
A release mechanism with a delay and a per-window ceiling. The intent is that no holder, including us, can move more than a fixed amount in any window, enforced by code that nobody can alter. Parameters are chosen but not deployed. When they are, this page will publish the delay, the ceiling and the annualised figure together — never one without the others, because a ceiling without its window is not a bound and an annual figure without its ceiling hides the shape of it.
No liquidity at deployment. This is the mechanism, not a caveat. An asset with no pool cannot be bought, which means the first thing that exists cannot harm anyone who finds it. Liquidity is a later, separate, deliberate decision with its own disclosure.
A role for XO2. Open. Not settled. What would settle it: a function the asset performs that is not better performed by an existing asset, demonstrated rather than argued. What would invalidate it: finding that every candidate function works as well or better denominated in an existing stable asset. We have not yet run that comparison to a conclusion, and until we do, the role is open in the plain sense that we do not know.
Supply and release schedules — designed, not deployed
The figures below describe what the locks will hold if and when they exist. No contract is deployed to Base mainnet, so nothing currently holds anything. Supply is 100,000,000 with 18 decimals.
These are not called allocations, deliberately. An allocation implies a recipient, and on-chain there is one recipient for all five. They are schedules governing when supply becomes movable, named for intended future uses that have not been committed to anyone.
Read this before the table
All five locks release to one address.
Founder, Treasury, Ecosystem, Contributors and Undesignated are five names for five schedules. They are not five destinations. Every one of them releases to the same beneficiary address, held by one person.
A reader who sees five named buckets will infer five recipients. The buckets differ in WHEN, not in WHO. Treasury releases to the founder’s address. So does Ecosystem. So does Contributors. The names describe intended future uses, not parties who receive anything.
This was read from the contracts rather than taken from a design document: beneficiary() on all five locks returns the same address. Distinct beneficiaries across five locks: one.
What is nonetheless different
The Genesis token could be moved in full, instantly, by one signature. This design cannot: every release is bounded per 30-day window, carries 30 days of notice before it completes, and the contracts have no admin function, no rescue function and no upgrade path. That constraint is real and it holds regardless of who the beneficiary is. What it does not do is make the table above mean what it looks like — a bound on speed is not a distribution, and one address remains one address at any rate.
No annualised figure is published. The 30-day window is the mechanism; a year is a convenience, and converting to one produced two of the four errors made while arriving at these two numbers.
On the Undesignated bucket
“Undesignated (35,000,000 XO2, 35% of supply) is held with no configured release destination and no assigned purpose; nothing moves from it — including any future liquidity seeding, should the standing no-new-pool constraint ever be lifted — until a specific allocation is decided and disclosed at that time, not before.”
Its ceiling was chosen without a designated purpose for the supply it governs. It borrows the slowest pace already used elsewhere in the design — a pace, not a reason.
Giving that 35% a schedule implies a plan for it. There is none. A release schedule is a statement about timing, not about intent, and nothing about this bucket should be read as a commitment to release, distribute or use it.
A maximum release rate across all five locks is not published here yet. The figures above are settled; how to state a combined rate without it reading as a distribution rate to multiple parties is not, and a rate figure that implies distribution would be wrong in the direction that flatters us.
Where the name 0200 comes from
In ISO 8583 — the message standard behind card transactions —
the Message Type Indicator 0200 is an Acquirer Financial
Request: the message a point-of-sale terminal or ATM sends to ask whether funds are
available. It is the moment a machine asks another machine to move money.
Stated because it is checkable in the standard, not as a claim about what we have built. The name predates us and belongs to nobody.
Who controls what
One person. Every asset 0200project holds is controlled by a single private key held by one person. There is no multisig and no external signer.
The honest form of what a delay-and-ceiling mechanism does, in three parts:
- It is not prevention. The controller can still do anything the schedule permits, and intends to remain the controller.
- It is not nothing. Nobody — including the controller — can exceed the ceiling in a window, and no key or signature changes that.
- It is contestable while someone is watching. A delay creates a period in which a movement is visible before it completes. That is only worth something if somebody is looking, and we cannot make anyone look.
A compromised key can do exactly what the controller can do, at exactly the same rate. The mechanism bounds the rate, not the identity, and it does not distinguish intentions from an attacker.
What we expect to be flagged, said before it happens
When XO2 is deployed it will have one holder and no liquidity. On the signals automated risk classifiers use — holder concentration, holder count, liquidity depth — that profile is the same as Genesis or worse. We expect it to be flagged, and a classifier doing so will be behaving correctly on the observable facts.
We are stating this before deployment rather than explaining it afterwards. The difference between this and the structure we just retired is not the profile at launch. It is that the supply is bound by a mechanism rather than by our intentions — and until that mechanism is deployed to mainnet and readable on-chain, that difference is a statement we are making and not yet a fact you can check.
What is not on this page
No price, no market capitalisation, no supply-multiplied-by-price figure, no return expectation, and no date for public availability. 0200project does not market a native asset on the basis of expected price appreciation. Where third-party tools display such numbers for tokens associated with us, they are computed by those tools and not by us.
This page is not overwritten. When a claim changes tier or turns out to be wrong, the correction is added with a date and the previous text stays visible, so that a reader later can see what was claimed in 2026 rather than only what is claimed then.