cryptosnif
AI Doge (AIDOGE)
Documentary contract0x09e18590e8f76b6cf471b3cd75fe1a1a9d2b2c2b
Unrated · 0% Evidence coverage
Operational strength remains unproven; unrated with 0% scoring coverage.
Documentary mechanisms alone cannot establish actual network behavior or investment outcomes.
Inspect the evidenceThe source review explains documented mechanisms. Independent network checks remain pending.
The documented promise
AI Doge (AIDOGE) is presented as a community-owned asset on the Arbitrum network. The pinned registry entry attributes specific aims to the project, stating it is created by AI and that all tokens belong to the community. It explicitly rejects classification as a meme token. These statements define the intended identity of the asset within the wallet ecosystem. They represent the project's self-description rather than an independently verified operational fact.
Established documentary facts
The Trust Wallet Arbitrum integration record identifies AIDOGE with the symbol AIDOGE and the documentary address 0x09e18590e8f76b6cf471b3cd75fe1a1a9d2b2c2b. The record specifies six decimal places for amount representation. This metadata does not measure supply or value. The entry is labeled active within the ARBITRUM directory. The ERC-20 specification defines a standard interface for fungible tokens, including functions for total supply, balance checks, transfers, and allowances. An allowance permits a named spender to use a specified amount. Repeated approvals overwrite previous allowances. The specification requires handling false transfer results and describes Transfer and Approval events. Name, symbol, and decimal metadata are optional in this standard. The Trust Wallet Assets README describes a community-maintained registry used by the wallet and other projects. Inclusion does not imply a direct partnership with listed projects. The registry excludes brand-new tokens from submissions. Promotional statements and network performance claims in the registry are not verified issuer statements.
Unknowns and verification gaps
No live network observation was performed. Independent control, beneficial ownership, usage patterns, client adoption, supply distribution, concentration, liquidity, and complete incident history remain unverified. Documentary address matching establishes no current program behavior, deployed control, or safety. The generic application family identifies only a documentary token subject. Its economic niche and scoring criteria remain unclassified. No deployed implementation, rights, ownership, safety, supply, use, or investment outcome was checked. The active status is a metadata label without live-network validation. No token transaction was performed in this review.
Consequences of limited evidence
Documentary mechanisms alone cannot establish actual network behavior or investment outcomes. The absence of independent verification means the stated community ownership and AI creation claims lack operational proof. Users relying on the registry entry face uncertainty regarding contract functionality and controller permissions. The distinction between the ERC-20 standard requirements and the specific token implementation remains untested. Without independent dated network observations, the dossier cannot confirm if the contract behaves according to its documentation.
Verdict
Operational strength remains unproven. The asset is unrated with zero percent scoring coverage. Critical missing elements include identity verification, supply confirmation, and control analysis. The dossier reflects a preliminary examination of documentary records only. It does not constitute an audit or independent operational verification. The unrated status persists until criterion-specific evidence is provided and calibrated.
Evidence that would change the verdict
Reproduced identity checks, independent dated network observations, and criterion-specific evidence would alter the assessment. Verification of deployed bytecode against the documented address would confirm implementation. Observation of actual token transfers and allowance mechanics would validate ERC-20 compliance. Disclosure of controller keys and ownership structures would clarify control risks. Complete incident history and liquidity data would assess resilience. Editorial review following such calibration would be required to assign a score.
Each check earns its result.
| Check | Weight | Result |
|---|---|---|
| Exact asset identityEssential | 3% | Verification pending |
| Observable use | 15% | Verification pending |
| Economic role of the token | 10% | Verification pending |
| Supply mechanismsEssential | 10% | Verification pending |
| Ownership concentration | 8% | Verification pending |
| Value capture | 7% | Verification pending |
| Control powersEssential | 10% | Verification pending |
| Security verification | 7% | Verification pending |
| Decision process | 8% | Verification pending |
| Accountability | 7% | Verification pending |
| Incident history | 6% | Verification pending |
| Operational continuity | 4% | Verification pending |
| Execution conditions | 5% | Verification pending |
Family-specific checks: Observable usage, token necessity and dependencies.
Inspect the evidence
Sources behind this analysis
Trust Wallet: captured Arbitrum record for AIDOGE
The pinned Trust Wallet Arbitrum integration record names AIDOGE with symbol AIDOGE, documentary address 0x09e18590e8f76b6cf471b3cd75fe1a1a9d2b2c2b and 6 decimal places. Decimal places concern amount representation and do not measure supply or value. The record labels the entry ARBITRUM and active. Its community-maintained description states: "ArbDogeAI is created by AI. 100% of the tokens belong to the community. Never consider AIDOGE as a MEME." Every project, economic, partnership, performance, supply, date and adoption statement within this quoted description is an attributed registry claim, not an independently established issuer statement or operational observation. The dossier may explain those stated aims with that attribution. No deployed implementation, rights, ownership, safety, supply, use or investment outcome was checked. The generic application family identifies only a documentary token subject; its economic niche and scoring criteria remain unclassified and unknown. The general ERC-20 specification is separate from this token implementation.
Inspect the primary source ↗Trust Wallet: pinned Arbitrum directory context
The pinned Trust Wallet arbitrum network-context record identifies the community registry directory for Arbitrum. This supplies documentary network context for entries in the same pinned directory. Promotional statements, network performance, consensus behavior, current deployment and control are not verified or admitted from this context.
Inspect the primary source ↗Trust Wallet Assets: README.md (bbe582d25a22)
The Trust Wallet Assets README describes a community-maintained registry of token information and logos across blockchains, used by the wallet and other projects. It says additional token information is optional and unavailable on-chain. Anyone can submit assets, and inclusion does not imply a direct partnership with the listed projects. It also explicitly excludes brand-new tokens from submissions, so this source cannot provide an exhaustive inventory of recent launches. The README states that its scripts and documentation use the MIT license. This source is the wallet project's own integration registry, maintained with community submissions. Its project descriptions are documentary claims from that registry, not independently verified issuer statements or operational observations. The active status is a metadata label, with no live-network validation. No deployment bytecode, controller, supply, reserve, use, concentration, liquidity, security audit, incident completeness or investment return has been established.
Inspect the primary source ↗Ethereum ERC-20: pinned token interface specification
The pinned ERC-20 specification describes a standard interface for fungible tokens in smart contracts. It defines totalSupply and balanceOf reads, transfers, third-party transfers after authorization, approval and remaining allowance. An allowance is the amount a named spender may use; a repeated approval overwrites that amount. The specification says callers must handle a false transfer result and describes Transfer and Approval events. Name, symbol and decimal-place metadata are optional in the standard. These interface requirements describe what a conforming implementation should do. A wallet ERC20 label establishes no independently checked compliance, actual deployed implementation, controller permissions, token use, supply or security. No token transaction was performed in this review. Copyright and related rights are waived under CC0.
Inspect the primary source ↗Only original summaries are distributed. Licensed raw market data stays private.