Whitepaper V4.1
22. Trust, Provenance and Credibility Architecture
Credibility is a graph of consistent independent evidence.
Legal identity: MenteCrypto.AI INC, IONON DAO LLC and the IONON U.S. service-mark registration.
Web identity: ionon.ai, docs.ionon.ai, ionon.eth, official domain email and signed manifests.
On-chain identity: canonical IONON/gIONON/DAO/Safe/pool addresses.
Deployment provenance: Team Finance Mint history and associated audited token template.
Explorer identity: Etherscan source verification, ownership verification, token profile and public labels.
Security identity: Blockaid/MetaMask false-positive remediation, scanners, audits, monitoring and bug bounty.
Market identity: one canonical Uniswap pool, followed by CoinGecko/CMC and exchanges when criteria are met.
Software identity: verified GitHub organization/domain, signed tags/releases, SBOMs and security policy.
No single badge proves safety. The objective is that a third party can begin at any trusted surface and resolve to the same contracts, domains and legal entities.
22.1 Reputation ladder
The immediate reputation objective is not to purchase a cosmetic badge. It is to make independent systems converge on the same identity.
Level 0 — Canonical identity. ionon.ai, ionon.eth, signed registry and canonical contract addresses agree.
Level 1 — Explorer provenance. Source code verification, contract-address ownership, complete Etherscan Token Info, public labels/name tags and Team Finance Mint provenance are published.
Level 2 — Security normalization. MetaMask/Blockaid warning is investigated through their official false-classification path; scanners and auditors point to the same contract; critical findings are resolved or disclosed.
Level 3 — Market identity. One canonical CCA/pool is published, followed by CoinGecko/CMC and wallet metadata once real market criteria are met.
Level 4 — Institutional proof. Independent audits, financial/treasury reporting, security certifications where justified, bug bounty and recurring transparency reports.
Etherscan's own reputation model moves from Unknown toward Neutral/OK based on verified source, complete project information, public professional identities, active communications, aggregator listings and larger milestones. MetaMask separately notes that its Verified token signal generally depends on recognized trading availability and sufficient market activity, while Portfolio verification uses consensus from at least three third-party sources. These systems should be earned by consistency, not gamed.
22.2 Anti-impersonation root
ionon.ai/verify and ENS records should publish the only canonical token, governance wrapper, DAO, treasury, bridge, Genesis auction and Uniswap pool identifiers. Any address not present in the signed registry is unofficial by default. This gives wallets, exchanges, users and incident responders a simple resolution rule during a phishing or clone-token event.