6 comments
Seems that an Elements rangeproof cache bug may've gotten exploited. A "fix" was committed last week and attackers could have just monitored the public commits and exploited the bug before fix was ever pushed? That's a leading theory anyhow.<p>fix: range proof cache bind to asset and scriptpubkey<p><a href="https://github.com/ElementsProject/elements/commit/c26d719c29" rel="nofollow">https://github.com/ElementsProject/elements/commit/c26d719c2...</a>
<a href="https://xcancel.com/Liquid_BTC/status/2096696272447218108#m" rel="nofollow">https://xcancel.com/Liquid_BTC/status/2096696272447218108#m</a>
Why do they say it's white hat hackers?
<i>Purported</i> white-hat hackers. The implication is that these people are presumably describing themselves as such, but it may not actually be true.
The same reason scam artists describe themselves as businessmen
Presumably to try and reduce the chance of a mass panic among their users.
It’s not "hackers". It’s an inside job, and a rug pull.
/r/buttcoin strikes again
[dead]