Repository navigation
🧮 Add optional Soroban mainnet proof anchoring - #1
Merged
Merged
Conversation
… contract and an opt-in mainnet relayer flow that anchors a deterministic digest of the finalized SEP-53 proof while keeping document data off-chain.\n\nCo-authored-by: Codex Web <noreply@openai.com>
…n ArrayBuffer-backed view so TypeScript 5.9 accepts it as WebCrypto BufferSource input.\n\nCo-authored-by: Codex Web <noreply@openai.com>
…e authority-label expectation to match the existing shortKey helper's eight-character suffix.\n\nCo-authored-by: Codex Web <noreply@openai.com>
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.
Adds an opt-in Soroban mainnet anchor to the existing SEP-53 PDF signing flow without putting the PDF or signer identity on-chain.
proof-anchorSoroban contract that accepts a 32-byte digest, emits it with the ledger sequence/timestamp, and keeps no contract storageThe relayer key is separate from the document signer: users still sign only the SEP-53 message through their wallet, and the server never receives their wallet secret.