> For the complete documentation index, see [llms.txt](https://devlab-machines.gitbook.io/devlab-machines-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://devlab-machines.gitbook.io/devlab-machines-docs/funding.md). # Tokens & funding Optional machine tokens use Meteora with wallet-approved creation, simulation, signing, and confirmation. The chain is verified before token publication. Tokens launch on Meteora's dynamic bonding curve with DAMM v2 migration; the historical BIO mint is unchanged. ## Deposits Owner-authorized confirmed SOL deposits require: * an exact machine memo (`devlab:`), * a verified signing sender and recipient, * the selected network, * exact integer lamports. Network + signature uniqueness prevents double counting. Deposits are owner-controlled receipts, **not** managed hosted credits. ## Separation of funds Received deposits, claimed creator fees, and liquidity reserves remain separate. Confirmed fee transfers deposited this way remain received deposits; no fee-origin claim is made without a separate verified fee receipt. There are no automatic wallet debits, no invented provider prices, and no automated fee-to-compute routing — so runway is unavailable until those integrations exist. Historical tokens stay separate from machine registry entries. --- # 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://devlab-machines.gitbook.io/devlab-machines-docs/funding.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.