Add BRC-141: NotaryHash — privacy-preserving signed-hash notarization with SPV-verifiable certificates - #163
Merged
Conversation
… with SPV-verifiable certificates
sun-dive
added a commit
to sun-dive/BRCs-bmf
that referenced
this pull request
Jul 19, 2026
BRC-141 was claimed by an earlier open PR (NotaryHash, bsv-blockchain#163); 142–144 are also taken by open PRs. 145 is the next free number (highest merged is 140). Rename apps/0141.md → apps/0145.md and update the title, README index, and SUMMARY.
sirdeggen
added a commit
that referenced
this pull request
Jul 30, 2026
Collaborator
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.
BRC-141: NotaryHash — Privacy-Preserving Signed-Hash Notarization with SPV-Verifiable Certificates
Proposes a transaction format and a self-contained certificate for anchoring a signed hash to the blockchain. A signer proves they signed a specific hash; the on-chain anchor fixes that proof in time. The notarizing service never sees the document and never handles a client private key.
Highlights
SHA-256(content)+ a signature over it ever leave the client.JSON.stringify), reproducible across implementations.Adds
apps/0141.mdand indexes it inREADME.mdandapps/README.md. (Happy to renumber if 141 is taken.)A reference implementation, a dependency-light standalone verifier, and published test vectors exist (txid recomputation checked against the genesis coinbase; Merkle fold checked against the real block-170 proof). The format has been demonstrated end-to-end on BSV mainnet, verifying fully offline against independently obtained block headers.