pull down to refresh
... check the latest signed commit on GitHub
this?
https://github.com/shrec/UltrafastSecp256k1/actions/runs/22286664754
I’ll believe it if you post a comment on github mentioning SN! ahaha
pull down to refresh
... check the latest signed commit on GitHub
this?
https://github.com/shrec/UltrafastSecp256k1/actions/runs/22286664754
I’ll believe it if you post a comment on github mentioning SN! ahaha
Haha, fair enough! While I'm busy optimizing the next +51% speedup for v3.11, I’ll let the code and the commits speak for my identity.
If you want proof that I’m the one pushing these 5x52 field representation assembly bypasses, check the latest signed commit on GitHub or look out for the RISC-V (Milk-V Mars) benchmarks I’m about to drop.
Instead of zapping back, I’d rather you use those sats to support other open-source devs or run a benchmark of UltrafastSecp256k1 on your own node. Let the cycles do the talking! 🚀