TBTC
tBTC is a Bitcoin-backed token and bridging protocol associated with Threshold Network. It is designed to represent deposited bitcoin in smart-contract applications. The design uses groups of operators and threshold signing to control Bitcoin wallets, distributing custody functions rather than assigning them to one conventional custodian.[1]
Bridge design
In the tBTC v2 design, selected operators jointly manage wallets holding deposited BTC. A sufficient signing threshold is required to authorize wallet actions. The documentation explicitly describes an honest-majority assumption: the protocol’s security depends on the operator set and implementation, as well as Bitcoin’s own consensus. Threshold cryptography changes the custody arrangement; it does not remove every trust assumption.[1]
Deposits, minting and redemption
A deposit is recorded on Bitcoin and processed by the bridge before the corresponding token balance is issued or credited on a supported network. Redemption reverses that relationship, returning native bitcoin through the protocol’s wallet operations. The project describes one-to-one backing as the intended accounting relationship. Minting and redemption fees, processing and service availability are separate from that backing ratio.[2][1]
Tokens can circulate in smart-contract applications while the underlying bitcoin remains in bridge wallets. A token transfer or a loan using tBTC is therefore distinct from redeeming it for BTC. Additional applications bring their own contract, liquidity and liquidation arrangements; the bridge documentation’s backing claim is not an audit of those applications.[2]
Availability and risk
On 31 October 2026, an Aave risk notice reported a pause in tBTC minting and redemption, alongside a pre-emptive freeze of its Ethereum Core reserve. A T Network Labs contributor reported in the same discussion on 10 November that minting and redemption were live through the user interface. These dated reports describe separate bridge and lending-market actions.[3]
Distributed signing relies on participating operators, working software and the procedures that coordinate deposits and redemptions. Operational pauses can affect conversion between native BTC and its token representation. A statement that a bridge has resumed does not establish the operating state of every market using the token.[1][3]