Skip to content

Commit

Permalink
Progress BIP173 to Proposed
Browse files Browse the repository at this point in the history
  • Loading branch information
@sipa
sipa committed Jan 3, 2018
1 parent 2166b78 commit 97a5587
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 3 deletions.
4 changes: 2 additions & 2 deletions README.mediawiki
View file
Original file line number Diff line number Diff line change
Expand Up @@ -749,13 +749,13 @@ Those proposing changes should consider that ultimately consent may rest with th
| Luke Dashjr
| Standard
| Draft
|-
|- style="background-color: #ffffcf"
| [[bip-0173.mediawiki|173]]
| Applications
| Base32 address format for native v0-16 witness outputs
| Pieter Wuille, Greg Maxwell
| Informational
| Draft
| Proposed
|-
| [[bip-0174.mediawiki|174]]
| Applications
Expand Down
2 changes: 1 addition & 1 deletion bip-0173.mediawiki
View file
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@
Greg Maxwell <greg@xiph.org>
Comments-Summary: No comments yet.
Comments-URI: https://github.com/bitcoin/bips/wiki/Comments:BIP-0173
Status: Draft
Status: Proposed
Type: Informational
Created: 2017-03-20
License: BSD-2-Clause
Expand Down

1 comment on commit 97a5587

@Dorson
Copy link

@Dorson Dorson commented on 97a5587 Jul 8, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am very happy about bech32.

As of now, I see a bit of confusion among the developers who coded for bech32 in a fast time. There is some confusion for how to generate the bech32 valid wallets.

I think there is a great potential for clarification AND examples for how to generate valid keys + addresses from start to finish. Like a step by step documentation. I know it already exists, but I see that some people got it wrong anyway.

Let's take a 12 word seed. Try to generate bech32 wallets with:

https://coinb.in/#newSegWit

AND

https://iancoleman.io/bip39/

AND
In the electrum wallet.

All of them generate a different thing for bech32. All of the coders are smart. Why do they get different results ?

I have no idea why. I only see that there is a great potential for clarification. What is exactly missing in the documentation is unclear.

The best thing would be to set up a very easy step-by-step guide for bech32 address + key generation and best practices guide. So that developers can follow the same thing.

Also the Q&A sessions with smart and silly questions about Bech32 generation would help to understand what the developers misunderstand about the Bech32. So that clarifications can be added to the documentation.

Thx for the bech32. Let's keep building a better world !

Please sign in to comment.