Back to collectionTHORChain Vault Rotation and Native-Swap Finality
Recurring custody changes require visible handoffs and clear finality.
THORChain's account of native swaps emphasizes churn: the nodes securing shared vaults rotate every few days and custody passes to a new set. Rotation reduces dependence on a permanent signer group, but creates a recurring handoff. The outgoing and incoming signer sets, transfer state and new quorum need to remain inspectable. Native exchange removes a wrapped-asset step; it does not remove the need to understand custody or recovery.
Permissionless execution adds a related limit: a user cannot assume that a central operator can pause, queue or reverse a completed trade. Finality must be understood before release, and a stalled display must not trigger an unsafe duplicate retry. Continuous market access also creates an out-of-hours support burden. Promotion and reach do not substitute for readable transaction state, limits and failure procedures.