Whitepaper V4.1
Appendix E — Trust, Reputation and Adversarial Defense
Approved
IONON should assume that impersonation, phishing, fake pools, metadata hijacking, false reports and social-engineering attempts will occur. The response is not retaliation; it is a stronger, redundant trust graph.
E.1 Canonical trust roots
The canonical registry should reconcile five independent roots:
| Root | Evidence |
|---|---|
| Legal | MenteCrypto.AI INC records; IONON DAO LLC; registered IONON service mark |
| Web | ionon.ai; docs.ionon.ai; domain email; DNS security; security.txt |
| On-chain | IONON; gIONON; DAO; Safe/vaults; Genesis CCA; canonical Uniswap pool |
| Provenance | Team Finance Mint history; exact source/bytecode verification; signed releases |
| Independent | Etherscan, Blockaid/MetaMask status, audits, CoinGecko/CMC, GitHub verification, bug bounty |
The objective is zero identity contradictions.
E.2 Immediate public-surface reconciliation observed on 7 October 2026
The current public crawl contains several states that should be corrected before Genesis:
| Surface | Observed state | Required resolution |
|---|---|---|
| Homepage | Ethereum contract shown as “TBA at TGE” while token page publishes the canonical address | Publish one canonical address everywhere |
| Token page | Legacy gIONON address differs from management-confirmed canonical wrapper | Reconcile on-chain, then mark canonical vs deprecated explicitly |
| Token / presale pages | $1.25 / 850K distributed / bonus language remains | Remove or archive as unconsummated proposal before accepting new funds |
| DAO page | Describes direct IONON voting while token page describes gIONON governance | Publish actual Aragon wrapper/voting mechanics |
| Network page | Shows 955 active nodes and 0 chains while several connected chains are labeled Live | Bind metrics/statuses to reproducible telemetry or label them correctly |
| Docs page | Still points to GitBook and says last updated April 2026 | Replace with self-hosted docs.ionon.ai and versioned source-of-truth build |
| Security language | Legacy pages still use Dilithium/Falcon wording as if every path were final-standard conformant | Use current NIST terminology and scope claims to implemented components |
| IP language | Some pages say “created and patented” | Use “registered service mark” for the evidence currently supplied; patent claims require separate patent evidence |
E.3 Anti-impersonation controls
ionon.ai/verifyreturns the canonical registry in human and JSON form;- ENS text records mirror the canonical registry;
- GitHub organization verifies the IONON domain where the account plan permits the badge;
- Etherscan token profile, address ownership and public labels are maintained from
onchain@ionon.ai; - Team Finance provenance is linked without overstating template audit as a full-system audit;
- Blockaid and MetaMask false-positive cases are tracked to resolution;
- Certificate Transparency monitoring flags look-alike domains;
- SPF, DKIM and DMARC prevent unauthorized mail spoofing;
- official support never asks for seed phrases or private keys;
- canonical pool/auction addresses are announced simultaneously through website, ENS, Etherscan and signed release notes.
References
Last updated: October 16, 2026Version 1.0Maintainer: IONONSource: Whitepaper V4.1 canonical SHA-256 23b8e12be2fab3bcbaee6f5539964b2e299ae67be33e4d4d6962ccb57da0e01d