
Adventure Gold (AGLD)
Documentary contract0x32353a6c91143bfd6c7d363b546e62a9a2489a20
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.
Promise
This dossier examines the documented purpose and mechanisms of Adventure Gold (AGLD) on the Ethereum network. The goal is to explain the stated aims of the token as recorded in community-maintained registries, without implying that an independent audit has occurred or that operational safety has been verified.
Established facts
The pinned Trust Wallet Ethereum integration record identifies Adventure Gold with the symbol AGLD and contract address 0x32353a6c91143bfd6c7d363b546e62a9a2489a20. The record specifies 18 decimal places for amount representation. This label does not measure supply or value. The registry entry describes Adventure Gold as the native ERC-20 token of the Loot non-fungible token project. Loot is defined as a text-based, randomized adventure gear generated and stored on-chain. The creator is identified as Dom Hofmann, co-founder of Vine. These descriptions are attributed registry claims from a community-maintained source. They are not independently established issuer statements or operational observations. The general ERC-20 specification defines a standard interface for fungible tokens in smart contracts. It includes functions for reading total supply and balances, executing transfers, and managing allowances. An allowance permits a named spender to use a specified amount of tokens. Repeated approvals overwrite previous amounts. The specification also outlines Transfer and Approval events. Name, symbol, and decimal metadata are optional within this standard. The wallet project labels this entry as active, but this is a metadata label with no live-network validation. No deployed bytecode, controller permissions, or security audits have been checked.
Unknowns
Present independent control, beneficial ownership, actual usage, client adoption, supply distribution, concentration, liquidity, and complete incident history remain unverified. The registry excludes brand-new tokens from submissions, meaning this source cannot provide an exhaustive inventory of recent launches. No live network observation was performed to confirm current operation.
Consequences
Documentary mechanisms alone cannot establish actual network behavior or investment outcomes. The active status label provides no assurance of ongoing functionality or security. Users relying solely on registry descriptions may lack visibility into current controllers or potential risks.
Verdict
Operational strength remains unproven. The asset is unrated with 0% scoring coverage. Missing essential criteria include identity verification beyond registry labels, supply data, and control structures. The dossier serves as a documentary explanation of stated aims, not an independent operational verification.
What would change it
Reproduced identity checks, independent dated network observations, and criterion-specific evidence would be required to update the status. Calibration and editorial review would follow the submission of such proof. Without these, the unrated status persists.
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 Ethereum record for Adventure Gold
The pinned Trust Wallet Ethereum integration record names Adventure Gold with symbol AGLD, contract 0x32353a6c91143bfd6c7d363b546e62a9a2489a20 and 18 decimal places. Decimal places concern amount representation and do not measure supply or value. The record labels the entry ERC20 and active. Its community-maintained description states: "Adventure Gold is the native ERC-20 token of the Loot non-fungible token (NFT) project. Loot is a text-based, randomized adventure gear generated and stored on-chain, created by social media network Vine co-founder Dom Hofmann." 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. This dossier may explain those stated aims with that attribution. No deployed implementation, rights, ownership, safety, supply, use or investment outcome was checked. The general ERC-20 specification is separate from this token implementation. Treat the generic application family as a documentary contract subject; its economic niche and scoring criteria remain unclassified and unknown.
Inspect the primary source ↗Trust Wallet Assets: blockchains/ethereum/info/info.json (bbe582d25a22)
The pinned wallet blockchain-information file names the network Ethereum, symbol ETH, and lists its project website and explorer. That named network context accompanies token records in the repository's Ethereum subtree. This identifies the documented integration network without reproducing its operation. 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 ↗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.