Open Source
Open where it earns trust,
closed where we compete
The Blitz platform is built so you can read it, prove it, and build on it. One block stays ours — the K1 engine that makes it fast. Everything that lets you check our work is in the open.
One socket, two cores
The Blitz card's design is an open platform around a swappable compute core. A single fixed interface joins the core to the platform — a tagged AXI-Stream pair carrying verification records through the throttle and auditor interposer. Everything else belongs to the open-source Blitz controller and its AXI-Lite bus, never to the core — so the open reference core and the K1 core drop into the same socket, on the same PCIe transport. Toggle between them.
Product build — the closed K1 core in the open platform.
Two blocks in the diagram have pages of their own: the K1 engine, and the RISC-V auditor — an independent processor that keeps putting K1 to the test against libsecp256k1 for as long as the card runs. The runtime auditor →
Copyleft on the machinery, permissive on the contracts
Two licenses, one principle. The machinery that moves and checks your signatures is GPL-2.0: read it, prove it, improve it — and if you build a product on it, your product is open too, or licensed from us. The interface contracts, the reference core, and the auditor SoC are MIT, so anything — closed cores included — can implement or embed them.
The platform — GPL-2.0
The controller that hosts the cores — valves, throttle, interposer, the fabric that enforces the audit — and the PCIe transport: DMA rings, doorbells, MSI. The same blocks the product runs, not a demo edition.
The host stack — GPL-2.0 + MIT
The kernel driver (GPL-2.0), the frozen two-file ABI, the GUI with its card daemon (MIT), and the virtual card that lets you develop and test with no hardware at all.
The software page →The reference core — MIT
A working verification core that drops into the same socket as K1. Run our published test vectors through it, study it, or use it as the starting point for a core of your own.
The auditor SoC — MIT
The card's resident second opinion — the RISC-V core, the firmware running libsecp256k1, the injection machinery. Not a black box auditing a black box.
How the auditor works →One closed block
The K1 engine — the optimized point-multiplier and modular-multiplier architectures that make it fast — is our competitive advantage: closed-source, licensable IP. The platform's seams exist precisely so the open and closed pieces can coexist — swap our core out, or build against it, without ever needing to see inside it. And the one block you can't read is the one block the card audits continuously, in your machine, with open code.
Browse our repositories on GitLab →