> For the complete documentation index, see [llms.txt](https://stackset.gitbook.io/stackset/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stackset.gitbook.io/stackset/summary.md). # Summary A great place to start your journey! This page serves as a high-level summary of Stackset. Hey there! Welcome to Stackset, our exciting gamified on-chain memecoin project crafted with love for all the memecoin, card game, and NFT lovers out there (yeah, we have an enticing blend for you!) ### Playbook 1. Trade Stackset memecoins to join the game. 2. Get NFTs with personalized attributes, giving you the opportunity to add your creative touch. 3. Sell these NFTs for profit or build NFT stacks. 4. Compete for the grand prize in ETH. Stackset isn't just your run-of-the-mill memecoin printer; it's a whole lot more than just flipping coins for potential gains. When you trade our monthly-released memecoins, you're not just making transactions – you're diving into a game where there are even more opportunities to profit. Some might say NFTs have are dead, but not in the case of Stackset where they're a key part of generating yield. Every memecoin launched by Stackset kicks off a new game. Trade our memecoins or join in our community events, and you'll snag an NFT airdrop, personalized with your own attributes. These NFTs come in 10 different rarity tiers. You get to choose: sell them right away for a quick profit, or gather NFTs of the same rarity to compete for a much bigger prize. So, what's this grand prize? It's funded by a 3% buy/sell tax on each new memecoin. We swap these taxes for ETH, doing it smartly to maximize returns for users while keeping the token price unaffected. Half of the total trading taxes collected over time goes into the prize pool. To grab a share of this pool, you just need to collect at least 2 NFTs from the same rarity tier!
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://stackset.gitbook.io/stackset/summary.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.