Episode Summary
Executive Summary: The episode centers on a heated debate over whether ThorChain can and should take action to block laundering of hacked funds, especially DPRK-related flows. Chad argues the protocol is too decentralized and slow to censor specific transactions, while Taylor counters that ThorChain has repeatedly shown it can act, has operational controls, and benefits from illicit volume. The discussion expands into decentralization, custody, governance coercion, regulatory risk, and whether ThorChain should emulate more interventionist systems like Near Intents.
Main Topics: Can ThorChain block illicit transactions? (Priority: 5/5): Chad says ThorChain cannot practically censor individual wallets or transactions fast enough without becoming more centralized; Taylor argues the protocol has used or could use pause/halt mechanisms to interfere with laundering. ThorChain’s decentralization and control model (Priority: 5/5): The conversation debates whether ThorChain is comparable to Bitcoin/Ethereum or functions more like an intermediary because bonded validators collectively control vaults and protocol decisions. Admin key, pause functions, and protocol governance (Priority: 4/5): They dispute what the historical admin key and various halt/pause mechanisms could do, whether they were used for configuration only, and whether they imply ThorChain could intervene in laundering cases. Validator incentives, coercion, and node departures (Priority: 4/5): Taylor argues some operators may have left after Bybit due to fear of social or financial punishment; Chad denies any such culture exists and says departures were voluntary and driven by sticker shock. Regulatory and custody implications (Priority: 4/5): The discussion examines money-transmitter style custody/control tests, Tornado Cash comparisons, and whether ThorChain’s TSS/vault structure could expose it to legal risk. Profits from illicit volume and ethical responsibility (Priority: 4/5): Taylor argues ThorChain benefits financially from laundering routes and should return or block stolen funds when possible; Chad says illicit volume is a tiny part of long-term protocol revenue and that all protocols earn fees from questionable flows. Comparison to other chains and systems (Priority: 3/5): They compare ThorChain to Bitcoin, Ethereum, Shapeshift, Wasabi, and Near Intents to argue over whether permissionlessness or active interdiction is the better norm.
Key Arguments: Chad argues ThorChain cannot censor individual transactions or wallets in time because protocol actions require broad consensus and can take days to two weeks. Taylor argues ThorChain has repeatedly had operational levers—pause/halt functions, admin controls, and validator coordination—that could have slowed or stopped laundering routes. Chad says the admin key was only for configuration and never used to reallocate funds; Taylor presses on past incidents where protocol actions changed behavior during crises. Taylor argues the protocol’s social dynamics discourage dissent and may have driven node operators to leave after contentious events like Bybit. Chad rejects the claim that node operators were punished for disagreement, saying no one has ever floated the idea of seizing funds over opinion. Taylor argues ThorChain’s vault/TSS architecture means it is not equivalent to Bitcoin or Ethereum because bonded validators jointly custody assets. Chad argues that if enough validators wanted to change ThorChain’s behavior, they could do so through consensus, but that would amount to a deliberate move toward centralization. Taylor argues that even partial interdiction matters because it makes life harder for thieves and signals ethical refusal to profit from stolen funds. Chad argues illicit volume is a small fraction of ThorChain’s overall activity over time, and that other protocols also benefit from tainted flows. Taylor argues that because ThorChain earned large fees during hacks, it should return or divert some protocol revenue back to victims when possible.
Data Points: Consensus time for protocol action: 3 days on average, up to 2 weeks - Chad says ThorChain needs this long to reach two-thirds consensus for major actions. ThorChain pause duration: 5 weeks - Chad references a past protocol pause unrelated to North Korea to show ThorChain can halt itself for extended periods. Thorify incident: lending feature paused - Chad says the admin key was used to pause a feature, not to reallocate funds. Bybit hack size: $1.4 billion - Discussed as a major theft that triggered controversy and validator departures. ThorChain hack size: $10 million - Chad says the bond-slashing case involved an attacker who mathematically stole $10 million from the protocol. ThorChain active validators: 115 validators (including standby) - Chad cites current network size when discussing decentralization. Distinct operator addresses: ~54 - Raised to show that multiple nodes may be controlled by fewer operators. Nodes run by four operators: 39 nodes - Used to argue coordination thresholds could be reached more easily than it appears. One-third threshold: 39 of 100+ nodes - Taylor argues this concentration could allow blocking consensus or coordination. Thornode operators leaving after Bybit: ~20 validators (approx.) - Chad says a chunk of validators left after the Bybit episode. ThorChain trading halt function: 720 blocks - Taylor mentions a make-pause function that can halt chains for about an hour. Illicit-share estimate of volume: 1%-2% - Chad claims only a small portion of total historical volume is illicit. Protocol historical volume: $125 billion - Chad cites cumulative volume over several years. Bybit-related fees: $10 million to $12 million - Taylor cites estimates of fees generated during the Bybit episode. Risk score response: 99.9% / 99% illicit on some routes - Chad says certain routes were overwhelmingly DPRK-related during specific windows. Operation threshold types: 3-node operational limit; 2/3 economic limit - Chad distinguishes operational versus economic memirs/limits.
Pivotal Quotes: "The protocol itself is. And so the UI is controlled by the treasury. It's not controlled by the protocol." — Chad Bereford: Explaining why the front end can screen addresses while the base protocol cannot be treated as the same entity. "If you get consensus behind any change, you could change anything, right? That's true with every protocol, no matter how centralized or decentralized it is." — Chad Bereford: Summarizing his position that ThorChain can only act through broad consensus, which would equally apply to other chains. "I think that when people support and help thieves, that's bad because it hurts people and it incentivizes harm." — Taylor Monaghan: Stating her ethical objection to ThorChain benefiting from illicit laundering flows.
Implications: The debate highlights a core crypto dilemma: whether decentralized systems should stay neutral or use available controls to stop theft. For ThorChain, the issue may affect user trust, validator behavior, and regulatory scrutiny.