How TON Teleport BTC Works in Practice
Many people see tgBTC as “just another wrapped token.”
But it’s not just a token.
It’s a mechanism for verifying Bitcoin inside TON.
Let’s break it down step by step.
SPV — Bitcoin verification inside TON
When a user sends BTC,
TON smart contracts verify Bitcoin block headers using SPV (Simplified Payment Verification).
What is verified:
— Proof-of-Work
— chain continuity
— transaction inclusion in a block (Merkle proof)
This happens on-chain.
No oracles. No manual confirmation.
Peg-in (BTC → tgBTC minting)
After the required number of confirmations on the Bitcoin network,
the contract automatically mints tgBTC 1:1 on TON.
No one mints anything manually.
The code makes the decision.
DKG — distributed key generation
To redeem BTC, the system uses a shared group key
created by validators via DKG (Distributed Key Generation).
This key never exists in full with any single party.
FROST — threshold signatures
When a user burns tgBTC (peg-out),
validators produce a single Bitcoin transaction signature via FROST —
a modern threshold signature scheme.
No single validator can withdraw funds alone.
Key rotation
Keys are regularly regenerated.
This reduces long-term risk and improves system resilience.
Why this matters:
• No single custodian
• No single private key
• No “admin” who can mint tokens at will
• Verification is enforced by cryptography
tgBTC is not just a wrapper.
It’s infrastructure — a bridge built on Bitcoin verification inside TON.
Only mechanics and architecture.
@tgbtcfi
Many people see tgBTC as “just another wrapped token.”
But it’s not just a token.
It’s a mechanism for verifying Bitcoin inside TON.
Let’s break it down step by step.
SPV — Bitcoin verification inside TON
When a user sends BTC,
TON smart contracts verify Bitcoin block headers using SPV (Simplified Payment Verification).
What is verified:
— Proof-of-Work
— chain continuity
— transaction inclusion in a block (Merkle proof)
This happens on-chain.
No oracles. No manual confirmation.
Peg-in (BTC → tgBTC minting)
After the required number of confirmations on the Bitcoin network,
the contract automatically mints tgBTC 1:1 on TON.
No one mints anything manually.
The code makes the decision.
DKG — distributed key generation
To redeem BTC, the system uses a shared group key
created by validators via DKG (Distributed Key Generation).
This key never exists in full with any single party.
FROST — threshold signatures
When a user burns tgBTC (peg-out),
validators produce a single Bitcoin transaction signature via FROST —
a modern threshold signature scheme.
No single validator can withdraw funds alone.
Key rotation
Keys are regularly regenerated.
This reduces long-term risk and improves system resilience.
Why this matters:
• No single custodian
• No single private key
• No “admin” who can mint tokens at will
• Verification is enforced by cryptography
tgBTC is not just a wrapper.
It’s infrastructure — a bridge built on Bitcoin verification inside TON.
Only mechanics and architecture.
@tgbtcfi