The best I can gather is that this captures telemetry while you're running some computationally-expensive job, and checks that the resource usage roughly matches what it's supposed to be. But what does "Tamper-evident" mean? I assume you sign with your own private key? What exactly prevents the data from being faked?
https://kveritas.org/docs/benchmarks - What a verifier learns:
> "A run of committed code, on attested hardware at time T, reading a model with hash m and a dataset with hash d, produced score S.” If d is a public benchmark, they also confirm it is the real benchmark, without you exposing it. The score is also cross-checked by the compute-cost certificate, which confirms the evaluation consumed the compute a real forward pass over the data requires.
They should really put that front and center. Still not a complete enough description, but something at least.
But this seems to just be collecting evidence and signing it?
Punchy phrase. It does A, never B. It Xs, Ys and Zs.
These are the simple tells but the general tell is what you describe - a lot of words that say nothing.
What are the scopes of this project?
Definitely needs to people test it out for improvements.
Have you tested it on clusters? Most experiments are ran on distributed systems I have tested it with c++, it had few problems when I combined the compile and execution commands. but it worked when i specify sh -c.
i might have more questions after testing it more