Repository navigation
Conversation
REQ-COMMON-18 has a profile with attestations fix their format, but the X and GitHub profiles only named "the pinned attestation format". The bytes lived in four implementations that agree by fixture alone. Section 4.1 now fixes the 48-byte header, the direction blocks, the SHA-256 range commitment and the EIP-191 notary signature, as the contracts verify them. Assisted-by: Claude Opus 5.5 Signed-off-by: xgreenx <xgreenx9999@gmail.com>
The X token-session text called every unrevealed byte charset-constrained. The circuit opens and constrains only the bearer range (REQ-PLAT-30); the status line, headers, scope and token_type stay behind commitments that nothing opens. Assisted-by: Claude Opus 5.5 Signed-off-by: xgreenx <xgreenx9999@gmail.com>
The direction-block table listed fields once, so an encoder could read it as one array per field. State that each range and each commitment is written whole, count times. Split REQ-PLAT-65's last sentence into one requirement each, and drop a sentence that restated "opens only the bearer range". Assisted-by: Claude Opus 5.5 Signed-off-by: xgreenx <xgreenx9999@gmail.com>
🚀 Deploying Preview to Cloudflare 🚀Preview URL: https://specs-attested-data-format.previews.lib.id, https://specs-attested-data-format-libid.grounded-systems.workers.dev (commit 809c042)This URL reflects your latest Preview deploymentPreview Deployments by commit
|
This was referenced Oct 5, 2026
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.
REQ-COMMON-18 requires a profile with attestations to fix its attestation format. The X and GitHub profiles only named "the pinned attestation format".
Changes
specs/platform-ceremonies.md:458): the 48-byte header, the direction-block encoding, theSHA-256(plaintext || 16-byte blinder)commitment and the EIP-191 secp256k1 signature, all asCeremonyAttestation.solandNotaryService.solverify them.:536-590): encoding, field values, commitment construction, signing, recovery, and shape rejection.:1590): a 246-byte conformance vector with its digest, plus negative cases.Verified
CeremonyAttestation.sol:117-124, 510-547. The shape checks match:567-603.cast keccakreproduces the digest (0x48162f05…95936) andkeccak256("api.x.com").sign_claimand TSdecode.ts.Not verified / known issues
authority_id_oflowercases the host but keeps a trailing dot. It fails TEST-PLAT-23'sapi.x.com.case, but it fails closed.NotaryService.sol:129does. Common REQ-COMMON-33 names only the signature check.🤖 Generated with Claude Code