> For the complete documentation index, see [llms.txt](https://docs.qiro.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.qiro.fi/qiro-marketplace-product-guide/for-borrowers/asset-tokenization/tokenized-asset-lifecycle.md). # Tokenized Asset Lifecycle ### Tokenized Asset Lifecycle Each asset on the platform goes through a set of stages. These help track where the asset is in its journey — from creation, to funding, to completion. Here's what each stage means: *** #### `Draft` The asset is being created. You can add or edit all the details here. It’s not yet submitted for approval. *** #### `MetadataValidated` All required financial details (like loan amount, tenure, and repayment terms) have been filled in correctly. The asset is now ready to be submitted for approval. *** #### `PendingApproval` The asset has been submitted and is waiting for approval from the relevant team. No changes can be made at this point. *** #### `Approved` The asset is approved and ready to be tokenized. It can now be added to a pool or prepared for funding. *** #### `Minted` An NFT (token) has been created to represent the asset on-chain. This makes it compatible with smart contracts and pools. *** #### `Underwritten` The asset has been underwritten — meaning a party (usually the originator) has committed to it or taken initial risk. This may be required before it joins a pool. *** #### `Locked` The asset is now locked into a pool. It starts generating repayments, and the capital is active. *** #### `Unlockable` The loan is fully repaid or has reached the end of its term. The asset is now eligible to be unlocked. *** #### `Unlocked` The asset is released from the pool. Any final actions (like fund returns or asset transfers) can be completed. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.qiro.fi/qiro-marketplace-product-guide/for-borrowers/asset-tokenization/tokenized-asset-lifecycle.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.