# Aero > The unified liquidity layer for all of Ethereum Aero is a cross-network decentralized exchange where users trade tokens, provide liquidity, and stake AERO to direct rewards. It unifies the former Aerodrome and Velodrome exchanges under one token. Aero is a decentralized exchange that runs across multiple blockchains as one liquidity network. Traders swap tokens through its pools, including swaps that settle across networks in a single transaction. Liquidity providers deposit tokens to earn AERO rewards or trading fees. Aero unifies the Aerodrome and Velodrome exchanges. Exchange rates come from automated market maker pools, either full-range basic pools or Slipstream concentrated liquidity pools. AERO holders stake their tokens as sAERO and allocate rewards to the pools they expect to be most productive. In return, they earn the exchange revenue those pools generate. Autopilot can manage allocation for holders who prefer a hands-off approach. Token issuers can create pools and bootstrap liquidity for new or existing tokens without approval. Aero is used by traders, liquidity providers, token operators, and token issuers. - Type: Protocol - Sector: DeFi - Status: Active - Founded: 2023-08-28 - Profile: https://thegrid.id/profiles/aero ## Products - [Aero](https://thegrid.id/profiles/aero): Aero is a cross-network decentralized exchange where users swap tokens through basic pools and Slipstream concentrated liquidity pools, including swaps that settle across networks in one transaction. Liquidity providers earn AERO rewards or trading fees, while sAERO holders allocate those rewards to pools and earn the exchange revenue they generate. Token issuers can create pools and bootstrap liquidity for new or existing tokens without approval. (Decentralised Exchange, Live, Main Product) - [Aero Launch](https://thegrid.id/profiles/aero): A permissionless token issuance and liquidity pool creation tool on Base. Project teams can launch tokens, create standard or concentrated liquidity pools, add single-sided or paired deposits, and lock liquidity natively to signal long-term commitment. All first-day trading fees go to liquidity providers with no platform fee. (Launch Pad, Live) ## Assets - [Aero (AERO)](https://thegrid.id/profiles/aero): AERO is the native token of Aero, formed by upgrading the former Aerodrome and Velodrome tokens into one. Holders stake it as sAERO to allocate rewards to liquidity pools, and it is paid out as rewards to liquidity providers. On other networks, rewards are paid in a receipt token redeemable for AERO on Base. (Utility) - [sAERO (sAERO)](https://thegrid.id/profiles/aero): sAERO is the staked form of AERO, held as an NFT that records the amount and the staking period. It gives holders the right to allocate AERO rewards to liquidity pools and to earn the exchange revenue those pools generate. Longer staking periods carry more allocation weight. (Governance) ## Links - [Documentation](https://app.aero.xyz/docs) - [Media Kit/branding](https://aero.xyz/brand) - [Terms of Service](https://aero.xyz/legal) - [Main](https://aero.xyz) - [Twitter / X](https://x.com/aeroxyz) - [Farcaster](https://warpcast.com/aerodrome) - [Discord](https://discord.gg/aerodrome) - [GitHub](https://github.com/aerodrome-finance) - [Medium](https://medium.com/@AerodromeFi) - [Twitter / X](https://x.com/dromoslabs) - [GitHub](https://github.com/dromos-labs) - [Farcaster](https://farcaster.xyz/dromos) - [Paragraph](https://blog.dromos.xyz) ## Legal This data is provided under two licensing models. Model 1 - open data. The open data core is licensed under the Open Database License (ODbL) — a copyleft/share-alike license allowing free use, modification, and sharing for any purpose. Attribution is required: include "Powered by The Grid" linking to https://thegrid.id wherever the data is used. Derivative databases must be shared under ODbL terms. Trademarks, logos, and brand names (marked "Special TPIP") are not covered by the ODbL. For ML/AI use: training datasets that substantially extract ODbL data are Derivative Databases and must be shared under ODbL if publicly used; models must be attributed in documentation. Model 2 - commercial licenses. The Grid Data Service (TGDS) is also available as a commercial license. See [Web Services Terms](https://about.thegrid.id/legal/web-services-terms) for commercial use that is not covered by the open data service. The following applies to both licensing models. - All data is provided AS IS with no guarantees of accuracy. - The Grid does not provide investment, legal, or tax advice, and - a project's presence in The Grid's data does not imply endorsement. - [Data Licensing & Disclaimers](https://about.thegrid.id/legal/data-licensing-and-disclaimers): Licensing models and disclaimers - [Open Data (ODbL)](https://about.thegrid.id/legal/open-data): Open Database License terms and scope for The Grid's open data service. - [Attribution Guidelines](https://about.thegrid.id/legal/open-data-attribution-guidelines): How to attribute The Grid's data when using the open data service. - [Web Services Terms](https://about.thegrid.id/legal/web-services-terms): commercial Terms for using data services. - [All Legal Documents](https://about.thegrid.id/legal): Full index of terms, policies, and disclosures ## Optional - [TGS Field Descriptions](https://github.com/The-Grid-Data/workspace-public/blob/main/references/tgs-field-descriptions.md): Schema field definitions for The Grid's data model - [TGS JSON Structure](https://github.com/The-Grid-Data/workspace-public/blob/main/references/tgs-json-structure.md): Data model structure and relationships - [Product Type Definitions](https://github.com/The-Grid-Data/workspace-public/blob/main/references/product-type-definitions.md): Definitions for each product type - [Product Type Classification](https://github.com/The-Grid-Data/workspace-public/blob/main/references/product-type-classification.md): Guide for classifying products into types - [Grid MCP Guide](https://github.com/The-Grid-Data/workspace-public/blob/main/grid-search/skills/grid-query/references/grid-mcp-guide.md): How to query The Grid programmatically via MCP