> For the complete documentation index, see [llms.txt](https://docs.runealpha.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.runealpha.xyz/en/marketplace/what-is-psbts.md). # What is PSBTs ? Partially Signed Bitcoin Transactions (PSBTs) are a data format that allows wallets and other tools to exchange information about a Bitcoin transaction and the signatures necessary to complete it A PSBT can be created that identifies a set of Unspent Transaction Outputs (UTXOs) to spend and a set of outputs to receive that spent value. RuneAlpha’s marketplace is harnessing the power of PSBTs in some pretty rad ways: * **Multi-party Transactions**: PSBTs are perfect for getting multiple parties to sign off on the same transaction. We can mix and match signatures from buyers and sellers, then broadcast the result to the Bitcoin network. It’s secure and saves users a bundle. * **Offline Signing**: PSBTs come with handy metadata that helps devices check the addresses and amounts involved in a transaction they’re signing. This means sellers can list their items at a lower transaction cost, update anytime, and still keep their assets safe and sound. It’s all about that Bitcoin life, right? --- # 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.runealpha.xyz/en/marketplace/what-is-psbts.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.