> For the complete documentation index, see [llms.txt](https://bridge-docs.orbitchain.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bridge-docs.orbitchain.io/bridging-transaction/xrp.md). # XRP ## Vault ### LOCK * User submit `toChain` & `toAddress` in the [BRIDGE](https://bridge.orbitchain.io/) (or direct to orbitchain xrpaddressbook contract) and issued `TAG`. * The user requesting bridging sends Transfer Transaction with the `TAG` of the rule set in XRPVault * Bridge Operator catches the transaction and relays bridging data to Orbit Hub * Bridge Validator consensus on relayed bridging data * After the agreement is completed, `toChain` Minter's MINT Process ### RELEASE * Completes the BURN process of `fromChain` Minter * Bridge Operator proposes raw transaction for bridging data agreed by Bridge Validator * Bridge Validator proceeds to consensus on Raw Transaction * Each validator sign to Raw Transaction via own private key * Using XRP's public Ledger API to broadcast multi-signing transaction ### Reference * [multi-signing](https://xrpl.org/multi-signing.html) * [ledger-api](https://xrpl.org/get-started-with-the-rippled-api.html) --- # 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://bridge-docs.orbitchain.io/bridging-transaction/xrp.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.