# Executive Summary Pineapple is a decentralised exchange ecosystem built for a new generation of on-chain traders. At its core is the Pineapple DEX — a live, multi-chain exchange where users can swap tokens, bridge assets across chains, and trade through two distinct interfaces designed for very different levels of experience. What makes Pineapple different is not just the technology. It is the whole package: a clean and intuitive trading experience for newcomers, a deep and fully-featured environment for experienced traders, a staking programme that gives token holders a real share of ecosystem revenue, an education layer — including a weekly newsletter — that builds the next wave of DeFi participants, and a partner trading community in ATLAS. Each part of the ecosystem is designed to stand on its own and compound in value when used together. $PAPPLE is the native token of the ecosystem, staked on Ethereum. Staking gives holders a share of the 1% token tax revenue pool, access to tiered rewards, and entry to the Pineapple Mansion — the community's private governance and discussion space on Discord. TGE occurred over a year ago. All tokens are fully in circulation with no further inflation, and the team actively pursues burn initiatives to reduce supply over time. The product is live and operational. The team kept building through difficult market conditions. What ships next — P2P trading in early June, followed by Raffle — arrives into a working, established platform. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://pineappledex.gitbook.io/litepaper/executive-summary.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.