The biggest issue here is a critical vulnerability in Zebra’s script parser, which is apparently the part of the software responsible for figuring out if a block of transactions is actually allowed to exist, kind of like the bouncer at a pub who checks your ID but occasionally forgets how old 21 is. The flaw made Zebra undercount signature operations against the 20,000-sigop block limit-yes, that’s a real, hard-coded limit that the Zcash team apparently pulled out of a hat during a very long, very boring meeting and decided was “good enough,” no takebacks, despite the fact that crypto moves faster than a British summer holiday weather forecast. This undercounting meant Zebra would cheerfully accept blocks that every other Zcash node implementation would look at, squint, and declare completely invalid, like a tourist who tries to pay for fish and chips with a Monopoly banknote. If this had gone on long enough, it could have split the entire network into two competing versions, which is the kind of drama that makes a family Thanksgiving argument over politics look like a polite chat about the weather, except no one can throw a dry roast potato at the other side to settle it. The flaw was found by researcher Samsulselfut, who I assume is currently very glad they didn’t just scroll past this bug while scrolling through TikTok, and is probably owed a very large pint (or several) by the entire Zcash community.