# Bitcoin Settlement Flow and One-Step Transactions One of Helios’s architectural breakthroughs is enabling **one-step deposit and withdrawal operations** despite Bitcoin’s slower, UTXO-based transaction model. On DLC-based lending platforms, users need to sign multiple times and involve waiting for each to confirm. Helios can bundle actions to take place within a single Bitcoin block for a seamless user experience: * **One-Step Deposit & Borrow:** A user can send a single transaction that simultaneously deposits BTC as collateral and executes a borrow. The Bitcoin transaction output goes into a TSS vault, while the embedded MIDL instruction triggers the protocol to credit the user a loan. By the time one block confirmation occurs, the user’s BTC is locked and the borrowed amount is reflected in their account – all from one on-chain operation. * **One-Step Repay & Withdraw:** Similarly, paying back a loan and withdrawing collateral can happen in one atomic transaction. The user sends the owed amount (plus interest) in BTC to the vault with an instruction to repay, and the same transaction (or a subsequent automatic one in the same block) releases their BTC collateral back to their address. There is no need for the user to manually perform multiple steps; the protocol orchestrates the sequence under the hood. * **Benefits:** Users get a banking-like experience: deposit and withdrawal feel like singular actions rather than a series of technical steps. It also **reduces transaction fees and UTXO clutter** – fewer on-chain transactions are needed overall. By reducing intermediate steps, Helios minimizes the potential points of failure or user error. --- # Agent Instructions: 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: ``` GET https://helios-finance.gitbook.io/helios-finance/architecture/publish-your-docs-1.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.