1062 sats \ 0 replies \ @ZezzebbulTheMysterious 13 Jan
use a new wordlist if you are adding a version field, to distinguish between BIP39.
Once the protocol is versioned the wordlist can be fixed and backward compatible. Version is very important for apis! If you are making an interface for something, version it for future compatibility.
reply
71 sats \ 3 replies \ @WeAreAllSatoshi 13 Jan
Versioning is a huge deal in general. Backwards compatibility is really hard over time. I don’t have a strong understanding of BIP39 from a technical perspective but it makes a ton of sense to support versioning for something so critical like seed phrase generation
reply
0 sats \ 2 replies \ @raw_avocado OP 13 Jan
Yup it does.
reply
0 sats \ 1 reply \ @WeAreAllSatoshi 13 Jan
Did you just zap me 22 times x 1 sat each? My phone was blowing up lol
reply
0 sats \ 0 replies \ @raw_avocado OP 13 Jan
Maybe?
reply
1 sat \ 0 replies \ @sirjanstha00 13 Jan
Yes....
reply
0 sats \ 1 reply \ @anon 13 Jan
Interesting. The electrum wallet is using a versioning system for their seeds since forever. They mention the exact same reason - backwards compatibility.
https://electrum.readthedocs.io/en/latest/seedphrase.html
reply
0 sats \ 0 replies \ @raw_avocado OP 13 Jan
Oh yeah, they were the 1st ever deterministic wallet, they also changed their dictionary and because of the versioning system this was fine.
Btw there was quite a bit of drama on the mailing list when BIP39 was being proposed between slush and Thosmas.
reply