RE: LeoThread 2026-04-24 16-34

You are viewing a single comment's thread:

Adding censorship to THORChain is a fool's errand

  1. If fewer than 33 nodes attempt to censor, they get slashed and churned out
  2. If more than 33 but fewer than 67 censor, the funds are irretrievably lost and cannot be intercepted


0
0
0.000
6 comments
avatar

as a bare minimum, 67 nodes must collude to censor from the start

How could that be achieved?

0
0
0.000
avatar
  1. 67 nodes each complete KYB and buy 67 API subscriptions at 67× the cost (impractical)
  2. One node completes KYB and exposes address screening on a free API for 66 other nodes to query
0
0
0.000
avatar

How would auditing work? A single node hosting the screening API could turn hostile and intercept funds, so the service would need to be publicly exposed

0
0
0.000
avatar

then anyone could query the service beforehand to see if an address will be screened, letting users game the system

0
0
0.000
avatar

Ultimately it fails — malicious actors will rotate addresses and protocols faster than screening services can tag them, which is what typically happens. Wallets and API providers add screening, yet bad actors still get through.

0
0
0.000
avatar

Instead: 1) be meaningfully decentralised and 2) provide easy tracking tools — which is what THORChain does

0
0
0.000