Release v1.1.0#230
Merged
Merged
Conversation
Ashex
approved these changes
Jul 6, 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
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@hypercerts-org/lexicon@1.1.0
Minor Changes
#219
39d7547Thanks @aspiers! - Add optional cryptographic signature support to all 21 record lexicons.Non-breaking: signatures are optional on every record.
app.certified.signature.defswith#list(open union of inline signatures andcom.atproto.repo.strongRefreferences) and#inline(raw ECDSA(r,s)bytes plus a DID verification method reference; signing curve derived from the verification method's multicodec prefix).app.certified.signature.proofrecord for remote attestations.signaturesproperty referencing#list.README.md,SCHEMAS.md, and thebuilding-with-hypercerts-lexiconsagent skill all gain a "Cryptographic Signatures" section with a worked end-to-end signing example.On-the-wire shape, signing procedure, and verification procedure all conform to Nick Gerakines' ATProtocol Attestation Specification (see also the accompanying blog post).
On
app.certified.link.evmthe existing EIP-712prooffield (wallet consent) and the newsignaturesarray (record provenance) are complementary and do not conflict.