This misunderstands what Verifiable Compute actually does. VC isn't about restricting execution, it's about proving properties of computation. The key difference is that VC lets you verify what happened, not control what can happen.
Think SSH keys, not DRM. SSH lets you verify you're talking to the right server without restricting which servers exist. Similarly, VC lets you verify properties of AI models (like training data lineage or inference characteristics) without restricting which models can run.
The regional censorship concern isn't relevant here since VC doesn't enable content restriction. It's a mathematical verification tool, not an enforcement mechanism.
Comments
This misunderstands what Verifiable Compute actually does. VC isn't about restricting execution, it's about proving properties of computation. The key difference is that VC lets you verify what happened, not control what can happen.
Think SSH keys, not DRM. SSH lets you verify you're talking to the right server without restricting which servers exist. Similarly, VC lets you verify properties of AI models (like training data lineage or inference characteristics) without restricting which models can run.
The regional censorship concern isn't relevant here since VC doesn't enable content restriction. It's a mathematical verification tool, not an enforcement mechanism.
enforcement comes from the rubber hose. The maths is what makes the enforcement possible.
Unless you are able to prevent attestations from being made with your machine (presumably against your will).
The attestations in this case are completely determined by you.