Repository navigation
docs(specs): make the profile version fix the protocol parameters - #65
Merged
Merged
Conversation
The Canonical Runtime derives a proof's expiry from the profile it ran, so a lifetime governance can change lets that expiry disagree with a Consumer Chain, or shift under a verifier upgrade. Each Platform Profile now fixes proofLifetime and maxFutureAttestationSkew per (platform, version); a new value takes a new Platform Ceremony Version. Governance keeps the Supported Version Set and the trust roots. Spec side of libid-org/libID-contracts#65. Assisted-by: Claude Opus 5.5 Signed-off-by: Green Baneling <XgreenX9999@gmail.com>
🚀 Deploying Preview to Cloudflare 🚀Preview Deployments by commit
|
Wondertan
approved these changes
Sep 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Canonical Runtime derives a proof's expiry from the profile version it ran, so one version must mean one value on every chain and through every verifier upgrade. Spec side of libid-org/libID-contracts#65; the contracts implementation lands in a separate libID-contracts PR.
Changes
libid.md): per-profile table;("x", 1)and("github", 1)fixproofLifetime3600 andmaxFutureAttestationSkew300,("google", 1)names neither.Verified
lint_spec.py: the same findings on main and on this branch; 0 errors and 7 warnings over the three specs, 80 and 93 over all five.Not verified / known issues