Bitcoin Simplified Payment Verification Client

Within the TON Teleport BTC system, a Bitcoin Simplified Payment Verification client (hereinafter referred to as the Bitcoin Client) is implemented as a smart contract. This client plays a critical role in maintaining the connection between the Bitcoin and TON networks, enabling the verification of Bitcoin block states directly on the TON blockchain.

Any network participant can submit blocks to the Bitcoin Client, whether they are specialized relays or ordinary users. This is a key point for decentralization and system security. The submission of blocks is not restricted to a narrow group of nodes, which prevents centralization and the possibility of manipulation.

This openness ensures that the system does not depend on a single data source, and thanks to the block verification mechanisms within the smart contract, the submission of incorrect data is practically impossible. Even if incorrect data is transmitted, it will fail the verification process and not affect the system’s operation.

Once a block is sent to the Bitcoin Client, it undergoes a series of checks:

Blocks in the Bitcoin Client are classified as either confirmed or candidate blocks. For a candidate block to transition to confirmed status, it must be followed by six more candidate blocks. This requirement protects the system from potential reorganizations of the Bitcoin blockchain, which could occur if miners, for various reasons, begin to form alternative chains.

Using six confirmations is a widely accepted standard in the cryptocurrency industry, ensuring a sufficient security level for transactions to be considered final. Depending on the context and security requirements, the number of confirmations can be adjusted.

The Bitcoin Client in TON not only synchronizes with the state of the Bitcoin blockchain, but also acts as an authoritative source of truth for the Peg-in process.

If a block is present in the Bitcoin Client, it can be assumed that it also exists on the Bitcoin blockchain. This enables further proofs to be built on top of the confirmed blocks, proving that a specific transaction has indeed occurred on Bitcoin. This foundational aspect of the Peg-in process ensures the secure interaction between the Bitcoin and TON blockchains, reinforcing the trustless nature of the system and making it resistant to manipulation or false data submissions.