UltrafastSecp256k1 v3.14.0

Implementation
,
1

Added — Language Bindings (12 languages, 41-function C API parity)

  • Java — 22 new JNI functions + 3 helper classes (RecoverableSignature, WifDecoded, TaprootOutputKeyResult): full coverage of ECDSA sign/verify, DER encoding, recovery, ECDH, Schnorr, BIP-32, BIP-39, taproot, WIF, address encoding, tagged hash

  • Swift — 20 new functions: DER encode/decode, recovery sign/recover, ECDH, tagged hash, BIP-32/39, taproot, WIF, address encoding

  • React Native — 15 new functions: DER, recovery, ECDH, Schnorr, BIP-32/39, taproot, WIF, address, tagged hash

  • Python — 3 new functions: ctx_clone(), last_error(), last_error_msg()

  • Rust — 2 new functions: last_error(), last_error_msg()

  • Dart — 1 new function: ctx_clone()

  • Go, Node.js, C#, Ruby, PHP — already complete (verified, no changes needed)

  • 9 new binding READMEs — c_api, dart, go, java, php, python, ruby, rust, swift

  • Selftest report API — SelftestReport and SelftestCase structs in selftest.hpp; tally() refactored for programmatic reporting

Fixed — Documentation & Packaging

  • Package naming corrected across all documentation — libsecp256k1-fast* → libufsecp* (apt, rpm, arch); CMake target secp256k1-fast-cpu → secp256k1::fast; linker flag -lsecp256k1-fast-cpu → -lfastsecp256k1; pkg-config Libs -lsecp256k1-fast-cpu → -lfastsecp256k1

  • RPM spec renamed — libsecp256k1-fast.spec → libufsecp.spec

  • Debian control — source libufsecp, binary packages libufsecp3/libufsecp-dev

  • Arch PKGBUILD — pkgname=libufsecp, provides=('libufsecp')

  • 3 existing binding READMEs fixed — Node.js, C#, React Native: removed inaccurate CT-layer claims (C API uses fast:: path only)

  • README dead link — INDUSTRIAL_ROADMAP_WORKING.md → ROADMAP.md

Fixed — CI / Build

  • -Werror=unused-function — added [[maybe_unused]] to get_platform_string() in selftest.cpp

  • Scorecard CI — pinned ubuntu:24.04 by SHA digest in Dockerfile.local-ci

1 Like
3

hello please join to our Discord channel and we can discuss all detail you are interested. yes i have many banchmarks on different devices and platforms you also can see them on git repo but i have more new improovments that not released yet will be today or max in 2 days working on self code auditing to check and test all edge cases

4

image
image505×306 4.82 KB

5

4.88 M ECDSA signs/s * 2.44 M ECDSA verifies/s * 3.66 M Schnorr signs/s * 2.82 M Schnorr verifies/s – single GPU (RTX 5060 Ti) this is GPU benchmark

1 Like
6

Clang 21.1.0, i7-11700, single core, pinned:

image
image736×497 12.5 KB

1 Like
7

I think it would be helpful and meaningful if you showed like-for-like comparative performance between your optimized library and the baseline libsecp256k1 implementation used by Bitcoin Core for instance. A useful metric would be number of ECDSA verifications per second, and then some discussion of where performance gains were made and where the remaining bottlenecks are for bandwidth.

8

Nice that you have both CPU and GPU versions. Is the GPU version using CUDA, OpenCL, or some other platform, and is it vendor-specific?