Make AI's power actions provable.
Spark Zero, Inc. builds Spark-XC, which keeps a tamper-evident record of GPU power-cap changes, whoever makes them. When the grid asks what your GPUs did, you can show it.
Your stack makes the change. Spark-XC keeps the signed record.
The grid asks for less power. Then someone asks you to prove it.
Utilities and grid operators ask large AI loads to cut back when the grid is tight. Cutting GPU power is the easy part. Weeks later, someone asks what your GPUs actually did, and all you have is a log anyone with access could have edited. That's hard to put in front of a grid counterparty, an auditor, or your finance team.
A request you can't trace
Which request led to which change, on which GPUs, at what time? Weeks later, it's hard to piece together.
A log anyone could edit
Plain logs and spreadsheets can't show whether someone changed them. It comes down to your word.
A number no one will stand behind
Without a record behind it, a power figure is just a claim. Finance and auditors know the difference.
Spark-XC: signed power records.
Spark-XC keeps a Power Event Record for each GPU power-cap change it records: which GPU, when, the limit before, and the limit after as the GPU reports it. It records changes made by other tools, not just its own.
Each record is signed with Ed25519 and hash-chained with SHA-256 when it's written, so anyone with a copy can check it. The claim stops being "trust us." It becomes "check it yourself."
Spark-XC records the GPU's own reported power limits and telemetry. It does not include facility or utility meter data.
With the operator's public key, supplied separately, and the full exported chain, an auditor can check the records.
You shouldn't have to ask anyone to take your word for what your GPUs did. With the operator's public key and the full exported chain, anyone can check the signature on each signed record and the order of the chain on their own machine, without access to your systems. Where chain heads are anchored off-box, a cut-off chain end is also detectable.
The signature is valid
Each record is signed with Ed25519. The public key shows whether a record still matches what was signed.
The chain is unbroken
Each record is SHA-256 hash-chained to the one before. Edit a stored record and the chain no longer checks out when it's recomputed.
Removals and reordering show
Recomputing the chain shows whether a record has been removed from the middle or moved out of order. Catching records cut from the end needs the chain head anchored off-box.
Changes from other tools, too
Spark-XC records power-limit changes made by other tools, not just its own, so the record covers what your stack did.
Anyone with a copy can recompute the chain. Anchors go to a local write-once directory by default, and can be sent to off-site storage you control.
Try it on the sample record →Records you can check, not claims to trust.
We'd rather hand you a record you can check than a number you have to trust.
Records over claims
We say what a record shows and nothing more. We don't publish savings figures.
Signed when written
The signature and the hash-chain link are added as each record is written, not pieced together afterward.
Tamper-evident
Change a stored record and the chain no longer checks out on recompute.
Plain about scope
Records hold the GPU's own reported limits and telemetry. We don't present them as facility or meter data.
Spark Zero, Inc.
Spark Zero, Inc. builds Spark-XC. We're a Delaware C-corporation, founded by Steven O'Neill.
We started Spark Zero because power has become the limit on AI, and the people running AI data centers deserve records they can stand behind when the grid asks what they did.
Running AI loads that answer the grid?
We're looking for design partners among AI sites and GPU clouds with grid or curtailment obligations. Send us one power event or curtailment scenario and we'll show you the record Spark-XC would keep for it.