$ODAI Holder Transparency:
Reproducible Base Snapshot
A block-pinned reconstruction of the $ODAI ERC-20 ledger on Base, with raw address concentration, a neutral evidence-based taxonomy, treasury verification, movement files, and explicit limits on what on-chain data can establish.
$ODAI is a non-security utility and access token. Holder-distribution evidence does not create holder rights to revenue, profit, yield, liquidity, or managerial effort. Activity-specific legal requirements remain separate.
This is a technical transparency publication, not investment, legal, tax, or accounting advice. It reports addresses and Transfer events—not people, beneficial owners, transaction purpose, revenue, or operating expense.
At Base block 49,875,807, the reconstructed ledger contains 3,685 positive-balance addresses across 348,446 Transfer events and sums to the token's 100,000,000,000 ODAI supply. The report publishes the raw ledger and its evidence trail. It does not convert address properties into claims about unique people or “real” holders.
II. Pinned Snapshot
The snapshot is fixed to one canonical Base block. Pinning the block number, block hash, and timestamp makes later comparisons meaningful and prevents “latest” state from silently changing the result.
| Field | Pinned value |
|---|---|
| Network | Base |
| Token contract | 0x0086cff0c1e5d17b19f5bcd4c8840a5b4251d959 |
| Snapshot block | 49,875,807 |
| Block hash | 0xa0868633ad4f1ea487177caf7aad09788239ed31ae025ca850776ede67552154 |
| Block timestamp | 2026-08-12 13:22:41 UTC |
| Transfer events processed | 348,446 |
| Positive-balance addresses | 3,685 |
| Reconstructed ledger sum | 100,000,000,000 ODAI |
totalSupply() at the pinned block | 100,000,000,000 ODAI |
| Ledger invariant | Reconstructed balances equal the on-chain total supply |
The unit counted is an address—not a person.
III. Address Taxonomy
Every positive-balance address remains in the raw ledger. Classification adds context; it does not erase balances or create an adjusted holder count.
| Category | Evidence threshold | Interpretive limit |
|---|---|---|
| Verified market contracts | Address matched to an official market-protocol deployment and has code at the pinned block | Describes the address surface, not each party whose assets may be routed through it |
| Verified protocol contracts | Contract call or verified protocol evidence identifies the role | A protocol balance is still a token balance; control and economic entitlement can require deeper tracing |
| Burn address | Conventional burn destination represented in the Transfer ledger | The label describes the destination convention, not a general circulating-supply calculation |
| Declared ODEI addresses | Address attribution published by ODEI | Attribution alone does not establish the purpose of every transfer or identify counterparties |
| Other code-bearing addresses | eth_getCode is non-empty at the pinned block | May be protocol infrastructure, a smart account, or an EIP-7702 user-controlled account; bytecode alone cannot decide |
| Non-contract addresses | eth_getCode is empty at the pinned block | May still be custodial, shared, automated, or controlled by the same person as another address |
Bytecode is an address property, not proof that an address is protocol-controlled or non-human. Smart-contract wallets and EIP-7702 accounts can be user-controlled. Conversely, an address without bytecode can represent an exchange, custodian, service, multisystem workflow, or multiple end users.
The published taxonomy is therefore address-level and evidence-level. It does not estimate unique owners, users, investors, wallets per person, or beneficial control.
IV. Raw Address Concentration
Concentration below is the cumulative balance of the highest-ranked raw addresses divided by the observed total supply at the pinned block. No category is removed and no balance is reassigned.
| Raw rank cutoff | Cumulative share of supply |
|---|---|
| Top 1 address | 18.5611117535% |
| Top 5 addresses | 32.4976553919% |
| Top 10 addresses | 41.1962033990% |
| Top 20 addresses | 51.1500281447% |
| Top 50 addresses | 67.3396505195% |
| Top 100 addresses | 79.2530247532% |
These are mathematically reproducible address shares. They are not a distribution of people: a contract can aggregate many users, one controller can operate many addresses, and custodial balances can represent third parties.
V. Treasury Verification
At the pinned block, the token's treasury() call resolves to 0x14926224168492cdc06461713b3011cd25d8c901. The address is classified as a verified Flaunch protocol treasury contract. Its balance represents 4.9016453883% of total supply at this snapshot.
| Check | Result |
|---|---|
| Token-reported treasury | 0x14926224168492cdc06461713b3011cd25d8c901 |
| Classification | Verified protocol contract |
| Share of observed total supply | 4.9016453883% |
| Verification boundary | Pinned eth_call, balance call, bytecode check, and declared protocol evidence |
This classification prevents the contract from being casually described as a founder or team wallet. It does not claim that protocol custody has no economic relevance; treasury flows and contractual control remain separate questions.
VI. Declared ODEI Operations Address
ODEI declares 0x510a08954fd7096f67b58ed210703b323a5f405e as an operations address. At the pinned block it holds 112,491,100.661182 ODAI, equal to 0.1124911007% of observed total supply. Across 11 Transfer events, gross flow was 192,042,600.443326 ODAI: 152,266,850.552254 inbound and 39,775,749.891072 outbound. The balance is a net ledger position, not an expense or revenue measure.
The number is Transfer-event volume. It is not operating expense, revenue, profit, cash flow, token sale proceeds, or net disposition. Direction, counterparties, transaction traces, pricing, internal routing, and accounting records are required before assigning economic purpose.
The complete address-touching event file is published so readers can examine direction and transaction hashes without relying on the narrative summary.
VII. Movement Windows
The 24-hour, 7-day, and 30-day files contain Transfer events of at least 100,000,000 ODAI (0.1% of observed total supply) inside windows ending at the pinned block timestamp. A qualifying event is not automatically a trade or sale.
Transfers can reflect liquidity routing, protocol accounting, custody changes, smart-account execution, internal consolidation, burns, transfers between related addresses, or market activity. The CSVs report event facts and address categories; economic interpretation requires transaction-level traces and independent evidence.
VIII. Reproduction & Methodological Limits
The public generator is scripts/generate-odai-holder-snapshot.mjs. From the repository root, run:
node scripts/generate-odai-holder-snapshot.mjs- Verify block
49,875,807resolves to the pinned hash before processing. - Read $ODAI
Transferlogs from start block42,057,936through the pinned block. - Apply mint, transfer, and burn deltas to a local address ledger in chain order.
- Remove zero balances and reject any negative-balance reconstruction.
- Compare the ledger sum with pinned-block
totalSupply(). - Query pinned-block bytecode, token treasury state, and treasury balance.
- Write CSV/JSON artifacts and a SHA-256 manifest into the dated snapshot directory.
What the snapshot does not prove
- Addresses are not identities. The data cannot determine the number of people or beneficial owners.
- Code is not control. EIP-7702 and smart accounts mean code-bearing addresses can be user-controlled.
- Transfers are not intent. ERC-20 events do not by themselves establish a purchase, sale, expense, revenue, compensation, or related-party transaction.
- Labels are evidence-scoped. Only independently verified or project-declared roles receive specific labels; other addresses remain mechanically classified.
- The report is not real time. State after the pinned block is intentionally excluded.
- RPC access matters. Reproduction requires a Base endpoint that serves the complete historical log range and pinned-block state.
The block hash fixes chain state; the raw CSV exposes every positive balance; the classification CSV exposes every rule; and the manifest binds the published files by SHA-256. Interpretation remains explicitly separate from reconstruction.
IX. Public Artifacts
All report artifacts are versioned under the 2026-08-12 snapshot. The manifest records file sizes and SHA-256 digests.
Sources
- Base JSON-RPC documentation. docs.base.org
- BaseScan $ODAI token and event surface. basescan.org
- Pinned Base block
49,875,807. basescan.org - Uniswap v4 deployment records. docs.uniswap.org
- EIP-7702: Set EOA account code. eips.ethereum.org
- Verified treasury address. basescan.org