schnorr-verify VS noble-secp256k1

Would it maybe be better to incorporate web3 tools into the existing network? Constructing an entirely separate parallel set of servers and software, and getting enough people to use them, seems pretty costly and difficult. What about instead using the metadata events to publish web3 addresses in association with a npub address, similar concept to https://github.com/nostr-protocol/nips/blob/master/05.md, and including an additional web3 generated signature as a tag for events you want to be verifiably associated with your Eth wallet? The features you describe like using ens and direct NFT ownership checking would be possible this way, only needs a client that supports them. The dns based identity does enable some workarounds for using eth addresses. The problem is those events are still signed shnorr sigs of sha256 hashes. That is something that can be worked around and there already is existing solutions in sol (https://github.com/noot/schnorr-verify)

I noticed in July of 2022 that Go did exactly the vulnerable example and reported it to the security team.

https://github.com/golang/go/issues/53849

It was fixed as of Go 1.21 https://go.dev/doc/go1.21

---

The article cites JavaScript, which is not constant time. There's no sure way to do constant time operations in JavaScript and thus no secure way to do crypto directly in Javascript. Browsers like Firefox depend on low level calls which should be implemented in languages that are constant time capable.

JavaScript needs something like constant time WASM in order to do crypto securely, but seeing the only constant time WASM project on GitHub has only 16 stars and the last commit was 2 years ago, it doesn't appear to have much interest. https://github.com/WebAssembly/constant-time

However, for JavaScript, I recommend Paul's library Noble which is "hardened to be algorithmically constant time". It is by far the best library available for JavaScript. https://github.com/paulmillr/noble-secp256k1