ذرائع کی جانچ پر مبنی تحقیق: HOW TO USE Aerodrome

Decision Matrix

Source Map

• Aerodrome Finance: Aerodrome Finance Documentation (aerodrome-docs)
• Aerodrome Finance GitHub: Liquidity Pools (aerodrome-liquidity-docs)
• Aerodrome Finance GitHub: Contracts Specification (aerodrome-contracts-spec)

Control Notes

1. Official domain

Official domain is the decision point where public documentation must become an operating rule. In this package, it means a DEX tutorial starts by avoiding impostor domains and spoofed wallet prompts. The practical action is to open the official documentation and app path from a verified source. The unresolved edge is future domain, UI or merger-related changes, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

2. Wallet boundary

Wallet boundary is the decision point where public documentation must become an operating rule. In this package, it means wallet connection should not expose seed phrases, private keys or KYC files. The practical action is to connect only through the wallet's own signing interface and read the prompt. The unresolved edge is wallet extension compromise or malicious browser state, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

3. Pool type

Pool type is the decision point where public documentation must become an operating rule. In this package, it means stable, volatile and concentrated pools have different risk and maintenance profiles. The practical action is to identify the pool type before depositing. The unresolved edge is token correlation changing after deposit, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

4. Gauge eligibility

Gauge eligibility is the decision point where public documentation must become an operating rule. In this package, it means emissions depend on whether a pool has an eligible gauge and votes. The practical action is to verify gauge presence instead of assuming every pool earns emissions. The unresolved edge is future vote allocation and reward-rate changes, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

5. Fee versus emission

Fee versus emission is the decision point where public documentation must become an operating rule. In this package, it means unstaked fees and staked emissions are distinct reward paths. The practical action is to write down which path the position uses before signing. The unresolved edge is future APR display changes or incentive deposits, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

6. Approval hygiene

Approval hygiene is the decision point where public documentation must become an operating rule. In this package, it means token approvals can outlive a single deposit action. The practical action is to use minimal approvals and revoke stale permissions where appropriate. The unresolved edge is wallet support for granular allowances, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

7. Stop rule

Stop rule is the decision point where public documentation must become an operating rule. In this package, it means unclear pool, tick range, token contract or gauge state should stop onboarding. The practical action is to pause before signing and recheck source, contract and wallet prompt. The unresolved edge is whether a third-party UI shows the same state as official contracts, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

Known Unknowns

• future domain, UI or merger-related changes
• wallet extension compromise or malicious browser state
• token correlation changing after deposit
• future vote allocation and reward-rate changes
• future APR display changes or incentive deposits
• wallet support for granular allowances
• whether a third-party UI shows the same state as official contracts

Practical Takeaway

Aerodrome onboarding should be described as wallet-and-liquidity setup, not account registration. Aerodrome's official docs describe it as a decentralized exchange on Base with liquidity pools, gauges, AERO rewards and veAERO governance mechanics; its liquidity documentation separates pool types, concentrated liquidity, staking APRs and fee APRs. The safe tutorial outcome is to verify the official domain, connect a wallet with no seed disclosure, inspect token contracts, distinguish unstaked fees from staked emissions and stop before signing if the pool, gauge, tick range or approval is unclear. The article stops at the evidence boundary. It helps the reader decide what to inspect next without converting public documentation into a promise that a private account, wallet, callback, policy framework, settlement route or liquidity position will work under every future condition.