Safeguarding native assets across different blockchains is made possible on THORChain through a decentralized network of autonomous node operators. To ensure complete alignment and security, these nodes are required to stake RUNE as bonded collateral, facing slashing penalties if they act maliciously or show negligence. Thanks to this cooperative architecture, cross-chain transactions can be completed safely, ensuring neither a solo developer nor a single node ever holds unchecked power over the protocol assets.
Managing incoming activity relies on a specialized service called Bifrost, which nodes run to track events on connected external networks. Before the system proceeds with processing any received deposit, consensus is mandatory: at least two-thirds of the active nodes must confirm and validate the transaction.
Stored assets remain protected in decentralized vaults powered by Threshold Signature Scheme (TSS) cryptographic technology. During vault setup, participants generate individual cryptographic key shares simultaneously, ensuring an entire private key is never assembled in one place. Whenever an outgoing transfer is initiated, a supermajority of the vault nodes must work together to sign the transaction, preventing any single participant from executing a withdrawal alone.
Security is refreshed continuously through a process called churning, occurring typically around every 3 days. In this cycle, the roster of active nodes shifts, prompting the deployment of fresh vaults and the automatic migration of balances from outgoing vaults to the newly established ones.
Managing incoming activity relies on a specialized service called Bifrost, which nodes run to track events on connected external networks. Before the system proceeds with processing any received deposit, consensus is mandatory: at least two-thirds of the active nodes must confirm and validate the transaction.
Stored assets remain protected in decentralized vaults powered by Threshold Signature Scheme (TSS) cryptographic technology. During vault setup, participants generate individual cryptographic key shares simultaneously, ensuring an entire private key is never assembled in one place. Whenever an outgoing transfer is initiated, a supermajority of the vault nodes must work together to sign the transaction, preventing any single participant from executing a withdrawal alone.
Security is refreshed continuously through a process called churning, occurring typically around every 3 days. In this cycle, the roster of active nodes shifts, prompting the deployment of fresh vaults and the automatic migration of balances from outgoing vaults to the newly established ones.