Create SLIP-0137: Like BIP 137 but it defines the sign/verify procedure for all address types. #1555
Conversation
This file contains 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
|
Some further questions:
Ideally I don't want there to be any "extensions", and those existing ones to either be requirements or dropped altogether. |
|
Really guys? No comments? |
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.
This was a BIP I created to somewhat standardize the procedure for generating signed messages for post-P2PKH address types. You can see it here on the mailing list. It was unceremoniously rejected with the reason being that more effort should be directed to BIP 322.
None of the recent efforts on BIP 322 came into any fruition on the BIPs repo.
Some companies such as Coinkite (the coldcard makers) are already using this BIP so it's best for all parties to officially publish this document in some capacity so that people don't have to rely on the source of the document being on my website, which can go down at any time.
Only superficial modifications such as changing "BIP" to "SLIP" have been made to the original BIP. I'm also open to deleting some of the optional modules if it means the core parts of the document get merged.