lukechilds/bips - bips - Gitea: Git with a cup of tea

Commit Graph

Author	SHA1	Message	Date
Manuel Aráoz	2a7e5a00a7	Update BIP32 to add bitcore as implementation	10 years ago
Nicolas Pouillard	987323e36b	Add a link to my CLI interface in Haskell	10 years ago
Jonathan Brown	d201d139cd	Mention that "Unsecure money receiver" use-case prevents theft	10 years ago
Jonas Schnelli	f44f68b939	Bip32, fix missing parenthesis reported by fenn on #bitcoin-dev [02:59:57]	10 years ago
Micah Winkelspecht	4a44d1c748	Short one digit in BIP32 doc notes.	10 years ago
Micah Winkelspecht	b369978bab	Update bip32 wiki, repo moved	10 years ago
Jonas Schnelli	852bf26494	fix secg.org secp256k1 docs link	10 years ago
Andrew Poelstra	a2029e165b	Clarify identifier serialization I had a tough time interpreting "serialization of the public key", which is hashed to get the extended key identifier. Since the very next section is "Serialization format [for extended keys]" I thought that I was supposed to use the serialization of the /extended/ public key. Then I noticed "ignoring the chain code", so I tried skipping that part of the extended key serialization. Then I realized that what was meant was "the `K` half of `(K, c)`".	10 years ago
jurov	3000cd5738	Added Haskell implemetation. Tested it and confirm it's functional.	10 years ago
Dave Collins	25a55ed60f	Add BIP0032 Go implementation.	10 years ago
Timothy Hobbs	224faeaa2a	Spelling bip 32	10 years ago
David A. Harding	5be4021fa1	Disambiguate Which Key Is Compromised When Ext. PubKey + PrivKey Are Leaked I mistakenly inferred from the following clause that a parent extended public key plus a child private key would be equivalent to knowing the extended child private key---meaning that the parent private key was still secure: > knowledge of the extended public key + any non-hardened private key > descending from it is equivalent to knowing the extended private key This patch's addition of the word "parent" (twice) removes the ambiguity and may help other readers draw the correct inference that the parent private key is no longer secure in this case. I also changed "+" to "plus" to avoid confusion with the actual mathematical operations used in this BIP.	11 years ago
Nicolas Dorier	fe4685a73c	C# implementation Github link to a C# implementation	11 years ago
Olivier Lalonde	be336d352d	Update bip-0032.mediawiki	11 years ago
Wladimir J. van der Laan	1647c7e6d3	Change date format to ISO 8601 This came up on the mailing list. yyyy-mm-dd (ISO 8601) is the internationally accepted format for numeric dates. This commit changes all BIPs to use that instead of dd-mm-yyyy. It also updates BIP 0001 to prescribe the new format.	11 years ago
afk11	0b83886040	Link to PHP implementation of BIP32- Passes test vectors.	11 years ago
Johnathan Corgan	de71fc1d15	Added bip32utils Python implementation reference	11 years ago
Oleg Andreev	868bd622ed	added link to Objective-C implementation of BIP32	11 years ago
Pieter Wuille	6a418689f3	Update BIP32: 'hardened' terminology + explicit conversions	11 years ago
Chuck	9ffdda8070	Link to Sarchar's JavaScript BIP32 implementation.	11 years ago
Cayman	2ca1e6229c	Adding link to Go implementation	11 years ago
Micah Winkelspecht	152cc283a2	Adding link to Ruby implementation I had added this link on the wiki, but when the page got moved over to GitHub, the link disappeared.	11 years ago
Peter Todd	d9e890a8f2	Fix formatting	11 years ago
Peter Todd	d0ae273977	Archive Revision as of 16:12, 18 October 2013 https://en.bitcoin.it/w/index.php?title=BIP_0032&oldid=41827	11 years ago
Peter Todd	1f64d2b06d	Rename to mediawiki extension	11 years ago
genjix	be17417866	BIP 32 by sipa	13 years ago
genjix	8079281cff	rename 32 to 31	13 years ago
genjix	f048fea5eb	BIP 32 - pong messages.	13 years ago

32 Commits (fd189fdccd7e3c3caef01313df9c36f621af6d04)