# How Helios Differs from Other Protocols Bitcoin’s base layer doesn’t offer native smart contracts, so Helios anchors its logic on an EVM-compatible execution layer that sits directly on top of **Bitcoin mainnet**(MIDL). Every loan, repayment, and liquidation is executed in Solidity yet ultimately settled in **raw BTC** within **1 BTC block**, so users keep **self-custody** and never leave the Bitcoin security envelope. Beyond the core architecture, Helios is built to satisfy the operational, security, and compliance checklists that professional capital demands: * **Audit-ready transparency** – All positions are provably solvent via on-chain proof-of-reserves and real-time Merkle-tree attestations, making third-party audits and regulatory reporting frictionless. * **Dynamic risk controls** – An adaptive model tunes LTVs and liquidation buffers block-by-block, reacting to mempool congestion, fee spikes, and spot-market volatility instead of waiting for governance votes. * **Compliance hooks** – Native event feeds export KYC/KYB flags, travel-rule metadata, and transaction analytics, streamlining integration with custodians, fund administrators, and auditors. Taken together, these choices make Helios a Bitcoin-first lending market that is secure, transparent, and ready for regulated capital—without the bridge risks or governance lag that characterize many Ethereum-based alternatives. --- # 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/readme/how-helios-differs-from-other-protocols.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.