Introduction
Most cryptographic libraries rely on a simple model:
- write code
- get audited once
- ship a PDF
But modern systems don’t stand still.
They evolve daily.
So I asked a different question:
What if audit was not a document, but a continuous process?
The Idea
UltrafastSecp256k1 was designed around two principles:
- High-performance cryptographic execution (CPU + GPU)
- Continuous, self-evolving audit system
Instead of relying on one-time audits, the system:
- runs ~1M+ checks per audit
- performs nightly differential validation
- converts every discovered exploit into a permanent test
- uses AI-assisted adversarial analysis
- enforces correctness through CI
Security is not declared — it is continuously verified.
Real-World Adoption: Frigate
Recently, Sparrow Wallet’s Frigate integrated UltrafastSecp256k1 as its core compute layer.
Frigate is an experimental Silent Payments (BIP352) server that performs high-throughput blockchain scanning using DuckDB.
Instead of treating cryptography as a separate layer, Frigate embeds it directly into the database via a custom extension:
- ufsecp.duckdb_extension
- ufsecp_scan(...)
This extension is powered by UltrafastSecp256k1.
Independent benchmarks from Frigate show:
- ~40 million operations/sec on 2 RTX 5090
This is not a synthetic benchmark —
it’s a real-world scanning pipeline.
Source:
https://github.com/sparrowwallet/frigate/blob/master/README.md
Why This Matters
This is not about “fastest library” claims.
This is about:
- independent integration
- real-world validation
- reproducible performance
- continuous verification
No contracts.
No paid audits.
No marketing.
Just:
clone → build → run → verify
Rethinking Audit
Traditional model:
- audit = event
- output = PDF
- trust = assumption
This model:
- audit = process
- output = evidence
- trust = reproducibility
Final Thought
If a system cannot be verified continuously,
it is only temporarily trusted.
UltrafastSecp256k1 is an attempt to change that.