pull down to refresh
Big Phil Scolari Oof!!
Such a simple flaw to exploit, once the door has been unlocked 🔓
The zcash had an inflation bug that was unknown because of obvious reasons, but this is more visible on liquid, albeit it's more private than on chain
So whose buckets do these 4 hunny billy sats get taken from?
Or is it able to be cancelled as the federation is a centralised entity, can they unapprove this?
I think the problem here, and imho this is really nasty, is:
- The problem was spotted a while ago and it was fixed, but not treated as a security incident.
- The fix commit was sitting in a release candidate
- The attacker raced the release / deployment of the fix
So that is a nightmare scenario for open collaboration on FOSS, which is something we have to think about how to counter. I might make a post about it, because this is pretty bad.
Or is it able to be cancelled
No. The swap already paid on L1 in BTC.
So whose buckets do these 4 hunny billy sats get taken from?
It's 95% of all sats on Liquid - basically the backing of that entire network.
Dayum 😲😯😲😯😲😲😯 that is bad 😞 is Adam gonna replenish the sats lol
No.
It sounds pretty much like a recently introduced or recently fixed consensus bug, which is why mempool's node would stop processing blocks right before the tx happened. It rejected the chain from that block onward.
Also, since the source seems to be confidential txs, it sounds very much like an inflation bug a la zcash.
"Fake L2".. I wasn't aware that they called their sidechain an L2?
Maybe mempool was running this patch and blockstream wasn't?
https://github.com/ElementsProject/elements/commit/c26d719c29a40da280a825b25657e9c3d8bc7d99
Do we know what actually happened with the liquid thing?
I've read through Scoresby's post and I still don't get it
It's a fake L2 and not a surprise I guess