BIP draft: Standardization of On-Chain Identity Publication #2038
+129
−0
Conversation
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
edyth933
changed the title
jonatack
reviewed
Nov 20, 2025
Member
jonatack
left a comment
jonatack
left a comment
There was a problem hiding this comment.
Thank you for your proposal, but this PR appears to have been opened prematurely:
- No dedicated prior ML post to present your draft proposal and have prior discussion of concept, technical merit, or soundness before opening this PR (https://groups.google.com/g/bitcoindev/c/MvfU6i67CDg only links directly to this PR)
- LLM-generated ("92% – Highly likely LLM-generated.")
- Author's GitHub (https://github.com/edyth933) has little-to-no previous proof of work in this space and its sole action recently has been to open this PR.
It would be best to propose a branch of your original proof of work on your own fork of this repository via a dedicated ML post, and discuss/refine it there first.
Please see the "BIP workflow" section of BIP 2 for more information.
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.
The draft defines canonical CBOR message formats and domain-separated prefixes for publishing identity attestations on Bitcoin (personal
v0idenand corporatev0corp), specifies Poseidon-basednullifier_hashderivation, and documents an optional Ed25519 signature wrapper and recommended canonicalization rules.