Conversation
Preserve original transcript offsets and bearer-only commitments while accepting JSON whitespace around colons and before integer terminators. Assisted-by: GPT-6 Signed-off-by: Wondertan <hlibwondertan@gmail.com>
This was referenced Sep 10, 2026
Contributor
|
Closed in favor of #37 for more general coverage. Tests from here were used in the PR above |
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
2 participants
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.
GitHub’s real identity response can contain whitespace after JSON colons. Accept that formatting in the shared JSON readers and token bearer framing while retaining duplicate detection across whitespace spellings and reveal seams, contiguous reads, and canonical integer validation.
Validation: all 318 ceremony contract tests pass, including pretty-printed identity, token framing, mixed-spelling duplicates, and disjoint-range rejection. Matching browser/Rust readers are required; existing bearer proof circuits and verification keys are unchanged.
Specification: libid #32. Standalone Bridge fix: libid-server-rs #11, based only on the token-exchange prerequisite (#8).