tgBTC Docs
  • Intro to TON Teleport BTC
  • USER GUIDES
    • Testnet in TON
    • Signet in BTC (for PC)
    • Signet in BTC (for Mobile)
    • Mint your first tgBTC
    • Burn your tgBTC for BTC
    • View transaction history
    • Common errors and solutions
    • How passwords keep you safe
  • DEVELOPMENT
    • Build first tgBTC dApp
    • tgBTC API by TONX
  • INFORMATION DESK
    • FAQ
    • Key resources
  • Whitepaper
    • Abstract
    • Declaration of Trustlessness
    • Overview
    • Key Concepts
      • Peg-in (BTC Deposit)
        • Bitcoin Simplified Payment Verification Client
        • Transaction Confirmation, Processing and tgBTC minting
      • Peg-out (tgBTC Withdraw)
        • Building of Withdrawal Transactions
        • DKG and FROST
        • Peg-out Timing and Optimizations
      • Additional Components and Security Mechanisms
        • Bitcoin Transaction Fees
        • Validator Rotation and Key Management
        • Refund Mechanism for Expired Deposits
        • Consensus-based System Updates
        • Inspectors
    • Expanding Possibilities and Value for TON
    • Conclusion
    • Papers
Powered by GitBook
On this page
  1. Whitepaper
  2. Key Concepts
  3. Additional Components and Security Mechanisms

Consensus-based System Updates

PreviousRefund Mechanism for Expired DepositsNextInspectors

Last updated 6 months ago

The TON Teleport BTC system is designed to be flexible and upgradable through validator consensus, ensuring seamless updates and modifications when necessary. This mechanism allows the system to evolve over time, adapt to changing conditions, and respond to new security requirements. Since the system operates within a validator-governed environment, updating contracts through validator consensus is a secure and natural process, aligning with the validators’ role in maintaining the network’s integrity.

Validators can make changes to both the code and state of core contracts by reaching a quorum. This capability allows them to address vulnerabilities, enhance functionality, and manage components such as Inspectors. Contracts in the system are divided into three groups based on their role and mutability:

The ability to update the system through validator consensus ensures long term reliability and integrity. Validators can coordinate to implement new logic, deploy updated utility contracts, and adjust components as needed without compromising the system’s core principles of decentralization and trustlessness.