Your GPUs cut power.
Can you prove it?
When a grid operator, an auditor, or your own finance team asks what your GPUs actually did, a dashboard screenshot won't hold up. Spark-XC keeps a signed, hash-chained record of each GPU power-cap change: the limit before, the limit after, and when. Anyone with a copy can check it. Spark-XC keeps an attested, tamper-evident record of GPU power-cap changes, whoever makes them.
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.
Records anyone can check
Teams running GPUs are told their power is under control. Few can show it: not to the grid operator asking whether you curtailed, not to the auditor rebuilding what happened, not to finance.
Spark-XC closes that gap. It 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 and hash-chained when it's written, so anyone with a copy can check it. The claim stops being "trust us." It becomes "check it yourself."
Where Spark-XC sits
GPU power limits change for many reasons: schedulers, operators, facility tools, grid events. Spark-XC doesn't replace any of those tools.
It sits alongside them and keeps one record of the changes: which GPU, when, the limit before, and the limit after.
From a power-cap change to a record
Follow one change from request to GPU, and see what Spark-XC writes down along the way. Illustrative, not a real event.
GPU power limit
issued
another tool
applied
to the GPU
reaches GPU
when it changed
RECORDED
reported it
RECORDED
from the GPU
RECORDED
signature
ATTACHED
the previous record
SEALED · CHAINED
One change. One record.
Each record answers four questions: Which GPU, and when? What was the limit before? What did the GPU report after? Has the record been edited since?
Built to be checked
Asked to prove what your GPUs did? With just the public key, anyone holding your Power Event Records can check them themselves: the signatures are valid, the chain is unbroken, and no record is missing or out of order. Try it on the sample record →
Built for the people who get asked
What a record answers
A Power Event Record is a small, signed entry written when a GPU power cap changes. It answers the questions people ask later:
- ✓Which GPU, and when? The device and the time of the change
- ✓What was the limit before? As the GPU reported it
- ✓What did the GPU report after? The limit read back from the GPU itself
- ✓Has it been edited since? Recompute the SHA-256 chain and check the Ed25519 signature
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.
Send us one
power event
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.