This is the difference between trusting a person and trusting mathematics + Bitcoin + TON.
Where is the BTC physically?
BTC does not magically fly anywhere.
It stays in the Bitcoin network, on special Bitcoin addresses controlled by the system.
And inside TON, tgBTC appears — a token representation of that BTC.
That is why it is called “teleport” not because the coin physically jumps from Bitcoin to TON, but because the proof of BTC ownership is transferred through cryptographic evidence.
BTC is locked in Bitcoin.
tgBTC lives in TON.
How tgBTC → BTC works
Now let’s say you want to get your BTC back.
Step 1. You burn tgBTC
You send tgBTC to a special TON smart contract that burns it. This is necessary to prevent double spending: you cannot keep tgBTC and withdraw BTC at the same time.
Step 2. TON creates a Bitcoin transaction
The smart contract gathers the data: which BTC were previously locked, where to send the BTC, the amount, inputs, and outputs.
Step 3. TON validators sign the Bitcoin transaction
But not one person signs it. The system uses DKG + FROST.
The simple meaning is this: the private key is not stored by one owner. Validators jointly create one public key and their own secret shares. Then they collectively produce one aggregated signature for the Bitcoin transaction.
Step 4. Anyone can broadcast the final Bitcoin transaction
When the signature is ready, the final Bitcoin transaction is already formed. Any participant can send it to the Bitcoin network. This is also important: there is no single “main server” holding the withdrawal button.
The simplest scheme
BTC → tgBTC:
You send BTC
↓
Bitcoin includes the transaction in a block
↓
TON receives Bitcoin blocks
↓
TON verifies Proof-of-Work and Merkle proof
↓
TON understands: yes, the BTC really arrived
↓
TON mints tgBTC
tgBTC → BTC:
You burn tgBTC
↓
TON understands: the user wants BTC back
↓
The smart contract builds a Bitcoin transaction
↓
Validators sign it through FROST/DKG
↓
The transaction is sent to Bitcoin
↓
You receive BTC
Why this can be the “best bridge”
Because it tries to remove the weakest points of ordinary bridges.
No centralized issuer.
The whitepaper directly says that tgBTC should not depend on a centralized issuer or custodian.
No single oracle that must be trusted.
Bitcoin blocks can be submitted by any participant, while the smart contract checks their correctness itself.
No single private key controlled by a company.
For withdrawals, the system uses a collective validator signature through DKG/FROST instead of one owner’s private key.
tgBTC becomes useful inside TON.
After minting, tgBTC can be used in DeFi, DEXs, lending, liquidity, mini apps, and other TON services.
The most important idea
The genius of BTC Teleport is not that “BTC became a token.”
There are already many wrapped BTC tokens.
The genius is that:
It is as if TON received built-in “eyes” that can see Bitcoin.
Where is the BTC physically?
BTC does not magically fly anywhere.
It stays in the Bitcoin network, on special Bitcoin addresses controlled by the system.
And inside TON, tgBTC appears — a token representation of that BTC.
That is why it is called “teleport” not because the coin physically jumps from Bitcoin to TON, but because the proof of BTC ownership is transferred through cryptographic evidence.
BTC is locked in Bitcoin.
tgBTC lives in TON.
How tgBTC → BTC works
Now let’s say you want to get your BTC back.
Step 1. You burn tgBTC
You send tgBTC to a special TON smart contract that burns it. This is necessary to prevent double spending: you cannot keep tgBTC and withdraw BTC at the same time.
Step 2. TON creates a Bitcoin transaction
The smart contract gathers the data: which BTC were previously locked, where to send the BTC, the amount, inputs, and outputs.
Step 3. TON validators sign the Bitcoin transaction
But not one person signs it. The system uses DKG + FROST.
The simple meaning is this: the private key is not stored by one owner. Validators jointly create one public key and their own secret shares. Then they collectively produce one aggregated signature for the Bitcoin transaction.
Step 4. Anyone can broadcast the final Bitcoin transaction
When the signature is ready, the final Bitcoin transaction is already formed. Any participant can send it to the Bitcoin network. This is also important: there is no single “main server” holding the withdrawal button.
The simplest scheme
BTC → tgBTC:
You send BTC
↓
Bitcoin includes the transaction in a block
↓
TON receives Bitcoin blocks
↓
TON verifies Proof-of-Work and Merkle proof
↓
TON understands: yes, the BTC really arrived
↓
TON mints tgBTC
tgBTC → BTC:
You burn tgBTC
↓
TON understands: the user wants BTC back
↓
The smart contract builds a Bitcoin transaction
↓
Validators sign it through FROST/DKG
↓
The transaction is sent to Bitcoin
↓
You receive BTC
Why this can be the “best bridge”
Because it tries to remove the weakest points of ordinary bridges.
No centralized issuer.
The whitepaper directly says that tgBTC should not depend on a centralized issuer or custodian.
No single oracle that must be trusted.
Bitcoin blocks can be submitted by any participant, while the smart contract checks their correctness itself.
No single private key controlled by a company.
For withdrawals, the system uses a collective validator signature through DKG/FROST instead of one owner’s private key.
tgBTC becomes useful inside TON.
After minting, tgBTC can be used in DeFi, DEXs, lending, liquidity, mini apps, and other TON services.
The most important idea
The genius of BTC Teleport is not that “BTC became a token.”
There are already many wrapped BTC tokens.
The genius is that:
TON can verify a Bitcoin fact inside a smart contract and make its own decision: whether to mint tgBTC or not.
It is as if TON received built-in “eyes” that can see Bitcoin.