> For the complete documentation index, see [llms.txt](https://spawnmeme.gitbook.io/spawnmeme-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://spawnmeme.gitbook.io/spawnmeme-docs/whitepaper/05-markets-wallet.md). # 5. Markets, trading and wallet tools ### Discovery inside and beyond SPAWN Spawn Feed focuses on projects launched through the platform. Markets expands discovery to wider Solana activity, including trending tokens, gainers, losers, volume leaders and new pools. These views help users find assets, but their scope and data sources differ. A market rank is a data signal. A listing or verification label does not establish investment quality, suitability or the credibility of every claim made by an issuer. Data can lag, and new or thinly traded assets may have incomplete information. ### Inspecting an asset A token page connects available market information with the token's full mint and relevant actions. Users should compare the full mint against an official source and use explorer links for on-chain inspection. Charts depend on coverage and supported pools. A missing chart is not proof that an asset is safe or unsafe; it indicates that the interface does not currently provide that view. A visible chart also does not guarantee an executable swap. Where tokenized assets appear, their issuer terms, access conditions and underlying rights require separate review. Displaying a tokenized stock instrument does not establish ordinary shareholder rights for its holder. ### Spawn Swap Spawn Swap uses Jupiter routing across available supported liquidity, including Meteora and Raydium routes where available. Quotes depend on the asset, amount, liquidity and current conditions. Before approval, the user should review the input and output assets, expected output, slippage, minimum received and fees. Routes can change or become unavailable. Comparing available routes does not guarantee the best price across every venue at every moment. SPAWN token-page bonding-curve trades and wider-market swaps are separate flows. Their fees, referral treatment and current support should not be conflated. ### My Wallet, Explorer and Incinerator My Wallet brings balances, searchable holdings, recent activity and receive or trading shortcuts into the same interface. It is a view of the connected wallet and supported actions, not a transfer of control over that wallet. Explorer supports token, wallet and transaction lookup. Incinerator supports burning unwanted tokens and closing eligible token accounts to reclaim rent. Burning destroys the selected tokens; recovering account rent does not recover their purchase price. These tools reduce navigation between services while leaving transaction review with the wallet owner. ### Limit orders and holder inspection A swap uses a current quote, with funds in the wallet until the transaction executes. A limit order waits for the selected dollar price with funds deposited in your own Jupiter vault. SPAWN does not hold the deposit. Expired orders require withdrawal; cancellation also requires completing the withdrawal. Only the connected owner wallet can deposit or withdraw. Limit orders have a $10 minimum, a maximum 30-day expiry and no SPAWN fee; network and Jupiter fees may apply. Top holders adds creator holdings and top-ten concentration to token-page inspection. Wallet count is not a count of independent people. ### Expanded token inspection Token pages now combine available RugCheck findings, supported token-lock schedules, DEX paid status and creator records with existing holder and trading information. Data availability varies by provider. Paid profiles and activity badges are not verification of safety, and a missing report is not a passed check. The holder-map embed is conditional. The Blink sharing control remains disabled in the reviewed build. *** Previous: 4. Token launches and graduation ยท Next: 6. NFT collections and public mints --- # 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://spawnmeme.gitbook.io/spawnmeme-docs/whitepaper/05-markets-wallet.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.