Seems that an Elements rangeproof cache bug may've gotten exploited. Fix for suspicious issue was committed just last week and attackers could've monitored the public commits and exploited the bug before fix was ever pushed?

Sort of self-fulfilling prophecy if true, that's a leading theory anyhow.

fix: range proof cache bind to asset and scriptpubkey

https://github.com/ElementsProject/elements/commit/c26d719c2...

lmao, PR description says:

> Fixes a number of small issues picked up during LLM scans