-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 10/20/2014 12:50 PM, Mike Hearn wrote: > One thing this brings up is the never-resolved issue of whether > BIPs should document how we'd *like* things to work, or how things > *actually do* work. BIP32 is an example of the former - it was new > technology and the spec was finalised before any wallets actually > implemented it. BIP 44 is an example of the latter, it basically > documents how myTREZOR works and as such there was minimal or no > scope for changes to it. Of course both kinds of document are > valuable.
You also have things like BIP43 that encourage people to reserve BIP numbers to avoid namespace collisions even if their work does not affect any other project. There should be an efficient process for informational BIPs of this type. - -- Justus Ranvier | Monetas <http://monetas.net/> <mailto:jus...@monetas.net> | Public key ID : C3F7BB2638450DB5 | BM-2cTepVtZ6AyJAs2Y8LpcvZB8KbdaWLwKqc -----BEGIN PGP SIGNATURE----- iQEcBAEBCAAGBQJUR9T1AAoJEMP3uyY4RQ21ADgH/0JUnkrAzKiBrtFcoXNTEkNl 7npCPY90zQDXk0RN0sV49ralMg/j71azHKmdeH3XHPF2BG3mC4+7TejhJkDEoCoB fzVyQ/a7MSz3Hnxh0iwx/4p+8A3v6oI6h3yDJeCrwdMudGYA2OfyQuFdrSuchHp6 j0yJpdxxEwtc9A/7SKk5R7yrLqeeLs4OCk2Ep8mZfCQyWssXvlJzd0IDvYZiUHrM jwLgDCAUNIotEqF4sPzxUMCUkQH3okeVhND/WvoDh8EIrE6l48I19CfDax3gJUU+ 4eI5Ooba3SRu5a8cf3V/lgtdbpJJ4i1UdpcjeWNAz1w/P1NVrWN4uJgzUilh6zU= =OWdW -----END PGP SIGNATURE-----
0x38450DB5.asc
Description: application/pgp-keys
------------------------------------------------------------------------------
_______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
