Proof
Check it yourself.
Recorded is a claim. Provable is a property. Here is what you can test about Grideōs and Ironwall without trusting us.
Grideōs makes claims about verification, so the evidence here is the kind you can check without taking our word for it. Where something is our own measurement or statement, it says so.
1. The live verifier
Ironwall's public verifier runs at edge.grideos.com. A #![no_std] Rust module compiled to WebAssembly checks Groth16 proofs over the BN254 curve inside a single Cloudflare Workers isolate. A valid proof receives a signed JWT; an invalid one is rejected.
| Measure | Value | Status |
|---|---|---|
| Groth16 verification time | 8.6 ms | self-measured |
| WebAssembly binary after wasm-opt | 381 KB | self-measured |
| Warm round trip | about 123 ms | self-measured |
| Cold-start round trip | about 298 ms | self-measured |
| Invalid proof rejected in | about 76 ms | self-measured |
How a request is checked
A request carries 256 bytes: a 128-byte compressed Groth16 proof followed by four 32-byte BN254 scalars: nonce, timestamp, attestation_hash and y. Proofs outside a 500 ms window are rejected, and so are nonces the verifier has already seen; in the current version that nonce check is kept in memory. Together the window and the nonce check limit replay of a captured proof.
Test it yourself
Send any 256 bytes that are not a valid proof and the verifier rejects them; only a valid, fresh proof receives a signed token. Outsiders cannot yet generate a valid proof, so the time window and nonce checks are stated, not publicly testable. For example:
head -c 256 /dev/urandom > not-a-proof.bin
curl -i -X POST https://edge.grideos.com --data-binary @not-a-proof.bin2. The source code
The verifier, its benchmark harness and the circuit challenge are public under the MIT licence:
- ironwall-verifier. The Groth16 ZK-SNARK verifier that runs at the edge: #![no_std] Rust compiled to WebAssembly, BN254 curve. MIT licence.
- ironwall-edge-bench. Benchmarking harness for Rust and WebAssembly latency on Cloudflare Workers. MIT licence.
- zk-circuit-challenge. An open challenge: review the zero-knowledge verification architecture and tell us what you would break. MIT licence.
3. Programs and results
- NRC IRAP client status, with an assigned Industrial Technology Advisor, as of 11 July 2026. Client status only; no funding agreement.
- Second place in the first Venture for Canada Responsible AI Adoption Challenge, for a student team with Grideōs as Project Partner.
4. A signed record of the claims on this site
The main factual claims on grideos.com, from the legal name to the verifier figures, are listed in the facts ledger: one entry per claim, each with its evidence and status, hash-chained and signed with an Ed25519 key published at /.well-known/jwks.json. You can verify the signature with a few lines of code.
What is not proven yet
- No independent third party has validated the verifier measurements.
- Grideōs does not publish client names or results without written permission, so none appear here.
- A signature proves that a claim came from Grideōs and has not changed since it was published. It does not prove that the claim is true; that is what the evidence links are for.
Bring us a problem.
Tell us about the work, where it gets stuck, and who has to trust the record afterwards. Grideōs reads every brief and replies by email. You can also write to info@grideos.com. How we handle what you send: privacy notice.