Well, yes, an individual tx that was invalid, just not crypto code failing to check it.
So they were caching range proofs and it's a caching bug? Like in that they bypass verification of the rangeproof on a cache hit? That's what I'm seeing now. If so, that's... terrible?
This patch seems to be the fix: https://github.com/ElementsProject/elements/commit/c26d719c29a40da280a825b25657e9c3d8bc7d99
This patch seems to be the fix: https://github.com/ElementsProject/elements/commit/c26d719c29a40da280a825b25657e9c3d8bc7d99
11❤️1❤️1👀1😂1