ericgas

Yeah, my library has Rust bindings, so you can use those directly.

Try this repo: https://github.com/shrec/UltrafastSecp256k1. Might have what you need.

Latest on UltrafastSecp256k1 v3.3: - Implemented GPU CABI across all languages - Added Ethereum ZK layer - 17-67x speedup for batch ops - OpenCL optimizations - Security updates and bug fixes.

You’re welcome! Glad I could help you achieve that 13x speedup.

UltrafastSecp256k1 v3.21 just dropped! Key updates include: - Constant-time SafeGCD scalar inverse - Quicker constant-time ECDSA signing - Stricter BIP-340 parsing - Improved audit infrastructure.

Hey, I checked your CUDA code, but it seems like you’re not using precomputed tables for ECMULT. With those, you could speed up the k.G process significantly. Just a thought.

Benchmark results against libsecp256k1 for BIP-352 pipeline are up.

This project sounds super intriguing! Just curious, what AI tools are you using to help speed up development?

Thanks for the heads up, I’ll keep that in mind.

I’ve been using the Milk-V Mars device for testing. I also plan to port it to the ESP32 RISC-V version I ordered. I’ve tested on various platforms like STM32 and Android too. It just works everywhere without extra…

Your repo looks solid! I noticed your block batch inversion is something I’ve never seen in public code before. Took me weeks to get something similar sorted out, and debugging those sync issues was a nightmare.

🔥 Here’s what UltrafastSecp256k1 is all about: A zero-dependency, multi-platform secp256k1 stack that covers everything in the Bitcoin and EVM space, from basic arithmetic to complex multi-party protocols.

Just added OpenCL support for ESP32 and optimized a few more parts.

Totally with you on that! Your take on Fermat-based inversion and side-channel risks is spot on. Right now, this library is all about performance research. Some of the optimization paths aim for speed, not constant-time…

Hey folks, I've been coding a super fast version of secp256k1 from scratch using C++ and CUDA. It’s got optional optimizations for x86-64 and RISC-V. Main goal? Max out performance and keep things efficient. Not about…