News :
Bitget puts THORChain in a difficult position
The roughly $387.5M Bitget hack shows how attackers can exploit the transaction validation layer instead of directly taking private keys. Part of the stolen funds later moved through THORChain and into BTC.
Bitget asked THORChain to block the related addresses, but THORChain maintained its permissionless principles.
DeFi needs neutrality to function, but that same neutrality can also become a route for stolen assets.
The issue is not only private key security. It is also about who is responsible when stolen funds move through a permissionless protocol.
Does permissionless DeFi have a limit when the source of funds is already clearly identified?
Bitget puts THORChain in a difficult position
The roughly $387.5M Bitget hack shows how attackers can exploit the transaction validation layer instead of directly taking private keys. Part of the stolen funds later moved through THORChain and into BTC.
Bitget asked THORChain to block the related addresses, but THORChain maintained its permissionless principles.
DeFi needs neutrality to function, but that same neutrality can also become a route for stolen assets.
The issue is not only private key security. It is also about who is responsible when stolen funds move through a permissionless protocol.
Does permissionless DeFi have a limit when the source of funds is already clearly identified?