Conversation
Revealing a range does not reject a form delimiter inside it, so X's soundness argument rested on X's parser (ASM-PROV-07). REQ-PLAT-63 mirrors REQ-PLAT-61: Prover and Platform Verifier hold the whole body to the canonical serialization of the five X fields, in order, each once. No launch profile cites ASM-PROV-07; the assumption stays defined for a future profile that reads a form it does not hold whole. TEST-PLAT-09C carries the form vectors TEST-PLAT-12 lists for GitHub. Assisted-by: Claude Fable 5.1 Signed-off-by: xgreenx <xgreenx9999@gmail.com>
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ❌ Deployment failed View logs |
libid | 7ff7f72 | Sep 20 2026, 09:47 AM |
…alues decode to A value in the serializer's alphabet cannot become another field, which is all the verifier needs; `code`, `redirect_uri` and `client_secret` are read by no contract, so a UTF-8 or printable-ASCII rule on chain protects nothing and costs a decoder. REQ-PLAT-61 and REQ-PLAT-63 now put those values with the party that compares them. Assisted-by: Claude Fable 5.1 Signed-off-by: xgreenx <xgreenx9999@gmail.com>
Assisted-by: Claude Fable 5.1 Signed-off-by: xgreenx <xgreenx9999@gmail.com>
This branch has not been deployed
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
1 participant
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.
Stacked on #35. libid-contracts#47 holds every token body to its profile's field list on chain, X's included. #35 gives GitHub that rule as REQ-PLAT-61 and leaves X on ASM-PROV-07; this makes the specification say what the verifier does for X, and trims one clause of REQ-PLAT-61.
Changes
platform-ceremonies.md: REQ-PLAT-63 (upholds SP-EXCHANGE-01, SP-BIND-01, SP-CLIENT-01), REQ-PLAT-61's counterpart for X: the complete body is the canonical serialization of exactlygrant_type, client_id, code, redirect_uri, code_verifier, in that order, once each, nonempty; malformed encoding, noncanonical spelling, extra or duplicate fields and bytes outside are rejected;client_idper REQ-COMMON-16B,code_verifierper §7,grant_typeexactlyauthorization_code; acceptance does not depend on X rejecting malformed or duplicate forms. The paragraph under the X table says the table fixes field order.code,redirect_uriandclient_secretare nonempty values with no further constraint; their comparisons stay with the Prover. The UTF-8 and printable-ASCII clauses go, with their TEST-PLAT-09C and TEST-PLAT-12 vectors: a value in the alphabet cannot become another field, and no contract reads those three.Verified
lint_spec.pyover the three documents: base 0 errors / 7 warnings, branch 0 / 7, delta zero. No ids renumbered, no links changed, only the two ceremony documents in the diff.Not verified / known issues
🤖 Generated with Claude Code