2. What Changed From the Legacy Whitepaper

The previous bilingual whitepaper was an important architecture draft, but it is now superseded. It described the project as an Agentic Settlement Network and captured enduring ideas such as the Order primitive, Agent OS, Policy Engine, Universal Router and post-quantum direction. It also contained economic and status assumptions that are no longer canonical: it used the token label ION, described a four-round 40% presale, included large token bonuses, treated future iUSD and AIX issuance as scheduled architecture, and described the sovereign chain as a later conditional phase.

This v4.0 consolidates the full project rewind and resets those items without erasing project history. It adopts the canonical token name IONON, treats the prior family-and-friends arrangement as an unfunded proposal rather than a completed sale, removes bonus-driven distribution, replaces generic bonding-curve rounds with a Uniswap CCA Genesis mechanism, adopts the current 40/30/10/7/6/5/2 allocation, treats 30M as a maximum phased-distribution program rather than scheduled circulation, and moves the now-tested IONON Network into the migration architecture while keeping Ethereum as the Genesis market and liquidity anchor.

The governing principle is simple: no public claim should outrun reproducible evidence. Where the project has internal implementation that is not yet externally verifiable, this document says so.

2.1 Deep rewind: how the architecture converged

The v4 canon is the result of a sequence of design corrections rather than a cosmetic rewrite. The following decisions are carried forward as binding architecture unless a future governance, legal, or engineering process changes them explicitly:

1. BCK/BCKMoney normalization. Earlier economic modeling under the working label BCK/BCKMoney is understood in this project context to have referred to IONON. V4 therefore maintains one Genesis economic asset: IONON.
2. Ethereum first. IONON begins market formation on Ethereum because the token, wallets, explorers, Uniswap v4 infrastructure and external liquidity already exist there.
3. IONON Network next. The sovereign network is not abandoned or subordinated. Management confirms a deployed testing environment that has completed initial tests successfully. Economic migration follows only after a public evidence package, bridge review and operational gates are satisfied.
4. Bridge as a conservation system. The bridge is not merely a UX feature. It is a monetary boundary. At no moment may canonical economic IONON across Ethereum and IONON Network exceed the fixed 100M supply.
5. CCA replaces the legacy presale/bonding-curve program. The old fixed-price/bonus structure is retired for Genesis. Uniswap's Continuous Clearing Auction is preferred because it provides explicit budget/max-price bidding, continuous price discovery and an integrated path into a v4 liquidity pool.
6. No completed family-and-friends sale. The earlier family support discussion was never funded. No proceeds were received. It is therefore not treated as a consummated external sale in the v4 economic history.
7. Allocation is not circulation. The 30M Phased Network Distribution bucket is a maximum program envelope, not a promise to sell 30M. Future tranches can remain dormant indefinitely.
8. Conditional reserve is not additive supply. Up to 10M of the Conditional Network Reserve sits inside the 40M DAO Treasury allocation; it is not an eighth tokenomics bucket.
9. gIONON is governance representation, not a second supply. Approximately 3M IONON have been described by management and the current public token page as wrapped for governance. The governance wrapper creates voting representation of deposited IONON; it does not increase the 100M economic cap.
10. Utility precedes financial narrative. Cards, agent identity, policy, wallet, routing, enterprise software, IONON Intelligence and operator services must create utility and revenue independently of speculative token demand.
11. The token is not the architecture. The system's primitive is an authorized economic action: identity, delegated authority, policy, simulation, approval, execution, settlement and evidence.
12. Future stable settlement and reputation are separate layers. USDC and regulated rails can serve stable settlement at Genesis. Any future IONON-native stable asset or reputation asset requires a separate governance, legal, reserve and security decision.
13. Public credibility is a graph, not a badge. Team Finance provenance, Ethereum, Etherscan, ENS, Aragon, Wyoming, USPTO, GitHub, security review, CoinGecko/CMC and wallet reputation should all resolve to the same canonical registry.
14. Docs are infrastructure. docs.ionon.ai becomes the self-hosted, versioned public source; docs@ionon.ai is an operational email identity, not the website hostname.

2.2 V4 truth hierarchy

When sources disagree, v4 applies the following priority rather than choosing whichever page sounds strongest:

On-chain state and signed legal instruments → verified deployment/source records → canonical registry → governance records → released documentation → public marketing surfaces.

A marketing page can never overrule a contract. A stale explorer profile can never overrule verified bytecode. A roadmap can never turn a test environment into production. Conversely, a project-internal implementation may be real without yet being public; in that case it remains MANAGEMENT-CONFIRMED or TEST until reproducible evidence is published.

2.3 Public-surface cleanup identified in the October 2026 crawl

A fresh crawl of ionon.ai identified several contradictions that must be treated as control defects before Genesis rather than repeated in v4:

• the token page still publishes the historical gIONON address 0x9913... while management identifies 0xbDde...8034 as the canonical wrapper;
• the token/presale pages still present 850K as distributed at $1.25 with bonus language even though the associated family arrangement was never funded;
• the homepage/identity surface still contains Contract 0x… (TBA at TGE) while the canonical Ethereum contract already exists;
• the DAO page says direct IONON holdings grant voting power while the token architecture uses gIONON as the governance representation;
• the network page shows 955 active nodes while simultaneously reporting zero chains and zero transactions, which requires telemetry-backed explanation or removal;
• some pages describe future network phases and bridge mechanisms as if final deployment choices were already production facts;
• some pages use legacy Dilithium/Falcon naming that must be reconciled with current NIST terminology and the exact implementation actually deployed;
• some pages say “created and patented,” while the documentary evidence supplied to this project proves a registered U.S. service mark; patent claims require separate patent evidence;
• blanket statements that ecosystem tokens are “utility tokens” should not substitute for jurisdiction-specific legal analysis of how a token or transaction is offered and used.

V4 therefore treats the website itself as an object that must be reconciled to the canonical registry before it can serve as evidence for third-party verification.

References

Whitepaper references