
Aerodrome (AERO)
Documentary contract0x940181a94a35a4569e4529a3cdfb74e38fd98631
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 Aerodrome (AERO) on the Base network. The objective is to evaluate the project based on available registry data and technical standards, without assuming operational safety or investment viability.
Established facts
The pinned Trust Wallet integration record identifies Aerodrome with symbol AERO and documentary address 0x940181a94a35a4569e4529a3cdfb74e38fd98631 on the Base blockchain. The record specifies 18 decimal places, a metadata value for amount representation that does not measure supply or value. The community-maintained description labels Aerodrome Finance as a next-generation automated market maker designed to serve as Base's central liquidity hub. This description also cites a liquidity incentive engine, vote-lock governance model, and user experience focus. These are attributed registry claims, not independently established issuer statements. The Trust Wallet Assets README confirms this is a community-maintained registry where inclusion does not imply partnership. The ERC-20 specification defines the standard interface for fungible tokens, including totalSupply, balanceOf, transfers, and allowances. An allowance permits a named spender to use funds up to a set limit. The generic application family identifies only a documentary token subject; its economic niche remains unclassified.
Unknowns
Present independent control, beneficial ownership, usage, client adoption, supply, concentration, liquidity, and complete incident history remain unverified. No deployed implementation, rights, ownership, safety, or investment outcome was checked. The active status is a metadata label with no live-network validation. No token transaction was performed in this review. Documentary mechanisms alone cannot establish actual network behavior.
Consequences
Documentary mechanisms alone cannot establish actual network behavior or investment outcomes. The absence of independent verification means the stated aims regarding liquidity hubs and governance models are unproven. Operational strength remains unproven. The dossier may explain those stated aims with attribution, but no current program behavior, deployed control, or safety is confirmed by the provided evidence.
Verdict
Operational strength remains unproven; unrated with 0% scoring coverage. No public admission of operational status exists. The calculated score reflects missing essential criteria for identity, supply, and control. The project is classified as unrated due to the lack of independent criterion observations.
What would change it
Reproduced identity checks, independent dated network observations, and criterion-specific evidence would be required. Calibration and editorial review must follow any new evidence. Current market, return, supply, performance, adoption, or ownership claims are excluded from this assessment. Concrete research questions include verifying the deployed bytecode against the documentary address and observing actual liquidity flows on the Base network.
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 Base record for Aerodrome
The pinned Trust Wallet Base integration record names Aerodrome with symbol AERO, documentary address 0x940181a94a35a4569e4529a3cdfb74e38fd98631 and 18 decimal places. Decimal places concern amount representation and do not measure supply or value. The record labels the entry BASE and active. Its community-maintained description states: "Aerodrome Finance is a next-generation AMM designed to serve as Base's central liquidity hub, combining a powerful liquidity incentive engine, vote-lock governance model, and friendly user experience." 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 Base directory context
The pinned Trust Wallet base network-context record identifies the community registry directory for Base. 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.