The addition of the comment about LLMs isn't really helping.
The spec itself made mistakes:
• Silent account hijack via “Connect this provider.”
• Redirect leaks of code (via Referrer) or access_token (via #hash).
• CSRF because state was optional and often ignored.
The point is: these aren’t obscure edge cases, they’re structural issues baked into the protocol.
Something claiming over 20-30 tps onchain is usually a big blocker. Big blocker design is well recognized as insecure: no end user is able to run a full node locally, only datacenters are able to keep up with 100k tps load. Which diminishes entire purpose of creating a blockchain. Could have been a database with 100k tps or 3-of-4 validator multisig like Hyperledger, wouldn't matter.