> 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/feature-guides/reference-and-support/40-glossary.md). # 40. Glossary Plain-language definitions for the terms used across SPAWN. | Term | Meaning in this guide | | ---------------------- | ------------------------------------------------------------------------------------------------------- | | Account | Your SPAWN login identity for account-based projects and tools | | Wallet | The application/account used to hold assets and sign Solana actions | | Public address | An address others can use to identify a wallet or on-chain record | | Mint address | The unique on-chain identifier of a fungible token; different from its ticker | | Token account | An account holding one wallet's balance of one token | | SOL | Solana's native asset, used for fees and many SPAWN payments | | Wrapped SOL / WSOL | SOL represented through a token account for compatible program operations | | Message signature | Proof of wallet control; by itself, not an on-chain asset transfer | | Transaction | An on-chain operation or group of instructions approved by the required signers | | Transaction signature | The identifier used to inspect a submitted transaction | | Confirmed | The chain has confirmed a transaction at the observed commitment level; a website can still be updating | | RPC | A service through which the app reads or submits Solana data | | Account rent | SOL held to support an on-chain account, sometimes recoverable when eligible accounts close | | Quote | An estimated/current offer for a trade or service; it can expire or change | | Slippage | The allowed difference between the quoted and executable trade outcome | | Minimum received | The lowest output permitted by the prepared trade's current limits | | Price impact | The effect an order can have on execution price given available liquidity | | Liquidity | Assets available in a trading pool; not the same as market capitalization | | Market cap (estimated) | A price-and-supply estimate, not cash available for all holders to exit | | Bonding curve | The configured pool pricing progression used before migration/graduation | | Graduation | Migration from the initial curve to the next pool stage under its actual on-chain rules | | Creator position | The launch wallet's eligible post-graduation pool position; fee claims do not unlock its liquidity | | Classic / Token-2022 | Different Solana token programs; support differs across tools | | Metadata | A token/NFT's associated name, description, image and other details | | Immutable | Not changeable through the relevant authority or supported flow after it is locked | | Metaplex Core | The NFT standard used by SPAWN collection and NFT tools | | Collection | An on-chain record grouping related NFTs | | Trait | A descriptive NFT attribute with a name and value | | Public mint | A configured sale/distribution allowing eligible visitors to mint under its rules | | Arweave | The permanent storage network used for supported NFT files and metadata | | Royalty | A resale payment rule whose effect depends on marketplace support/enforcement | | Whitelist | The wallet list from which participating creators draw airdrop recipients | | Buy Bot | The Telegram alert tool for supported confirmed token buys | | Organic Trending | Activity-based ranking of qualifying supported connected tokens | | Promoted | A paid sponsored entry, separate from organic rank | | Boost | Paid, time-limited website discovery visibility | | Order memo/reference | Information attached to a service payment so it can be matched to the intended order | | Indexing | A service discovering and processing chain records for search, stats or display | | Draft | Saved work that may still need publishing or an on-chain transaction | | UTC | The timezone used for quest check-in days and the campaign times in this manual | If a term appears in an error, keep the exact message and use [Troubleshooting](/spawnmeme-docs/feature-guides/reference-and-support/38-troubleshooting.md) to connect it to the correct recovery step. ## New feature terms | Term | Meaning | | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------ | | Limit order | A conditional SOL/token order at a chosen dollar price, subject to expiry, liquidity and slippage. A fill is not guaranteed. | | Jupiter vault | The connected wallet’s deposit location at Jupiter for limit-order funds; it is separate from the wallet balance and is not held by SPAWN. | | Curve milestone | A supported token’s 25%, 50%, 75% or graduation alert threshold. | | Share link | A page-specific link that supplies that page’s title, description and artwork for social previews. | | Top holders | The token-page view of the largest holders, creator holdings and top-ten concentration excluding the bonding pool from that aggregate. | ## Creator fee terms | Term | Meaning | | -------------------- | --------------------------------------------------------------------------------------------------------------------------------- | | Creator curve fees | The launch wallet’s share of eligible curve trading fees; about 0.25% of trade value under the current creator-fee configuration. | | Claim curve fees | The wallet-signed action collecting accrued creator curve fees, including any remaining after graduation. | | Legacy pool settings | Permanent settings of an earlier launch; a 0% creator curve share cannot be changed retroactively. | *** [Guide home](/spawnmeme-docs/feature-guides.md) · [Troubleshooting](/spawnmeme-docs/feature-guides/reference-and-support/38-troubleshooting.md) · [Get help](/spawnmeme-docs/feature-guides/reference-and-support/39-support-and-safety.md) --- # 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/feature-guides/reference-and-support/40-glossary.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.