# Interoperability with Bitcoin: The Role of Relayers

A core innovation of Torram’s decentralized oracle network is its Bitcoin-native settlement mechanism, which ensures that all price data is finalized directly on the Bitcoin blockchain.&#x20;

Relayers are an integral part of Torram’s peer-to-peer (P2P) network and are responsible for packaging aggregated price data, verifying it with Merkle proofs, and committing it to Bitcoin for finality. Every validator runs a relayer as part of their node, ensuring a tamper-proof and trustless data layer that applications can depend on.&#x20;

The relayer process works as follows:&#x20;

\- Validator Submission: Validators retrieve data from multiple trusted sources, reach consensus on pricing, and submit aggregated price updates to Torram every 1 to 60 seconds.&#x20;

\- Relayer Finalization on Bitcoin: Every 10 minutes, relayers submit a cryptographically verified Merkle-proof-backed transaction containing finalized price data onto the Bitcoin blockchain, ensuring permanent and verifiable settlement.&#x20;

\- Immutable Records: Bitcoin’s open ledger guarantees that once data is committed, it cannot be altered, providing a high-integrity source of truth for applications.&#x20;

<figure><img src="/files/oueKxxWCaQWLZA0DmsrC" alt=""><figcaption></figcaption></figure>


---

# 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://torram.gitbook.io/torram-documentation/torrams-bitcoin-native-solutions/interoperability-with-bitcoin-the-role-of-relayers.md?ask=<question>
```

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.
