tgBTC Fi

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:

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.

TON teaches its smart contracts to “read Bitcoin” so they do not have to trust a person, an exchange, a bridge, or a custodian.
Before, it worked like this:

“Send BTC to a company. The company says: yes, we received your BTC, here is your wrapped BTC.”

But the idea of BTC Teleport is different:

“Send BTC to Bitcoin. Then bring cryptographic proof to TON. TON itself verifies that the BTC really arrived, and then TON itself mints tgBTC.”

That is the genius of it.
Imagine a border between two countries
There is the country of Bitcoin.
And there is the country of TON.
Usually, you need an intermediary between them: a bank, an exchange, a bridge, or a custodian. This intermediary says:

“I checked that the BTC arrived. Trust me.”

BTC Teleport removes this intermediary.
It creates something like a mini Bitcoin border officer inside TON — a smart contract that can verify Bitcoin blocks and Bitcoin transactions.
In the whitepaper, this is called a Bitcoin SPV client, implemented as a smart contract. It is needed to verify the state of Bitcoin blocks directly inside TON.
How BTC → tgBTC works
Let’s say you want to bring 1 BTC into TON.
Step 1. The system gives you a Bitcoin address
You receive a special Bitcoin address. This address is connected to your TON address. So the system knows in advance: if BTC arrives at this address, tgBTC must be minted to this TON wallet.
Step 2. You send BTC
You send BTC through the Bitcoin network. This is a normal Bitcoin transaction.
Step 3. Bitcoin miners include it in a block
The transaction gets included in a Bitcoin block. Then the system waits for confirmations, usually 6 blocks, to reduce the risk of a Bitcoin chain reorganization.
Step 4. Anyone can bring Bitcoin blocks to TON
This is an important part: it does not have to be only an official server. According to the whitepaper, any network participant can submit blocks to the Bitcoin Client: a relayer, an ordinary user, or anyone else. This reduces centralization.
Step 5. The TON smart contract verifies the Bitcoin block
It checks that:
the block was really mined through Proof-of-Work;
the block is connected to previous valid blocks;
the parameters match Bitcoin SPV rules.
So TON does not simply “believe” that the block is real.
It verifies it mathematically.
Step 6. You bring proof of your transaction
When the block is confirmed, you or any other participant sends to TON the Bitcoin transaction itself plus proof that it was included in that block. Usually, this is a Merkle proof. The smart contracts verify that the transaction was really inside a confirmed Bitcoin block.
Step 7. The smart contract mints tgBTC
If everything is correct, the TON smart contract reads the Bitcoin transaction, extracts the BTC amount and the receiver’s TON address, and then mints the equivalent amount of tgBTC on TON.
That is it.
A person did not decide.
An exchange did not decide.
A “bridge admin” did not decide.
The proof decided.
This is where the genius is
A normal bridge says:

“Trust me, I hold your BTC.”

BTC Teleport says:

“Do not trust me. Show proof of the Bitcoin transaction, and the smart contract will verify everything itself.”

If Durov launches tgbtc as part of one of the seven points, I’ll track him down and ask him to be the godfather of my future children

Here is the English version, keeping the tone strategic, calm, and professional:

Why Did TON Integrate BTC Teleport Into the Core?

This is one of the most important questions.
If custodial solutions already exist, why build a complex trustless architecture?

Let’s break it down.

Why TON Validators Need It

Teleport is not controlled by a single company.
It operates through TON validators — via consensus.

This means:
— security is distributed
— there is no single point of failure
— control is not concentrated in one entity

For validators, this expands the role of the network:
TON becomes not just a blockchain,
but infrastructure for external assets.

Why This Is Not Just an Experiment

Teleport includes:
— on-chain SPV
— DKG
— FROST
— key rotation
— open-source code

You don’t build an architecture like this “just to test.”
It is expensive, complex, and requires coordination.

Infrastructure at this level only appears
when there is a long-term strategy behind it.

Why Infrastructure Is Built in Advance

Critical infrastructure is not created during a crisis.
It is built before one.

Most of the time, a trustless architecture may seem excessive.
But if an ecosystem wants to be resilient,
alternative mechanisms must exist in advance.

Teleport is not a product designed for traffic.
It is a security layer for the future.

@tgbtcfi

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

Two Trust Models: cbBTC and tgBTC

After BTC was added to TON Wallet, many started comparing cbBTC and tgBTC.
But this is not a direct competition. It’s about two different trust models.

cbBTC — Trust in an Issuer
cbBTC is issued by Coinbase and backed 1:1 by Bitcoin.
Users trust the company that holds the BTC reserves.
It is convenient, liquid, and easy to use.
However, security ultimately depends on a centralized entity.

tgBTC (TON Teleport BTC) — Trust in Code
tgBTC operates through on-chain Bitcoin verification (SPV),
threshold signatures (DKG + FROST),
and TON validators.
There is no single custodian.
Trust is placed in the protocol, not a company.

Both models have their place.
One is optimized for mass-market UX.
The other is optimized for long-term resilience and sovereignty.

An ecosystem becomes stronger when users have a choice.

The key is understanding the difference —
not positioning one against the other.

@tgbtcfi

Is tgBTC dead? Let’s clarify calmly.
After BTC was added to TON Wallet, many assumed: “tgBTC is no longer relevant.” Let’s remove emotions and focus on facts.
WHAT ACTUALLY HAPPENED
TON Wallet added cbBTC (issued by Coinbase, backed 1:1 by BTC) and wETH. These are custodial assets. They are convenient, liquid, and designed for mass users. That makes sense for a large-scale wallet product.
BUT THIS IS NOT TON TELEPORT BTC
tgBTC is a different architecture: on-chain Bitcoin verification (SPV), DKG + FROST threshold signatures, no single custodian, validator-based governance. It is not a company wrapper. It is infrastructure.
WHY THE WALLET CHOSE THIS MODEL
A wallet is a UX product. It optimizes for simplicity, speed, and liquidity. Teleport is a protocol. It optimizes for sovereignty and long-term resilience. These are different layers of the system.
DOES THIS MAKE tgBTC IRRELEVANT
No. It means: cbBTC is about convenience. tgBTC is about trustless infrastructure. Mass markets always choose simplicity first.
WHY tgBTC STILL MATTERS
It does not depend on a single company. It cannot be frozen by one decision. It cannot be minted arbitrarily. It operates through blockchain verification. It is a foundation, not just a product.
THE KEY POINT
tgBTC does not need to be the most popular option today to become the most important one tomorrow. No hype. No promises. Only architecture and on-chain facts.

@tgbtcfi

Traditional bridges —
“a translator you trust.”

TON BTC Teleport —
“a translator who must prove every word with documents in court.”

SPV = the documents.
FROST / DKG = the court’s collective signature.
Key rotation = regular seal replacement.

@tgbtcfi

tgBTC is a “cryptographic check” for real BTC.