1 2014-02-03 00:00:34 <dkog> What I mean is in https://en.bitcoin.it/wiki/Technical_background_of_Bitcoin_addresses step 1: "Take the corresponding public key generated with it (65 bytes, 1 byte 0x04, 32 bytes corresponding to X coordinate, 32 bytes corresponding to Y coordinate)" -- if the X or Y coord is e.g. < 2^254.
 2 2014-02-03 00:01:34 <dkog> And P.S. that page should probably be updated with an explanation of compressed address construction too - at minimum a mention of it!
 3 2014-02-03 00:02:16 <dkog> If I had a better handle on this, I would contribute that, but I'm still wrapping my head around the details.
 4 2014-02-03 00:16:37 <dkog> Hmm, ok.  Found one brute force.  1943E4DEE8BCFBD2479D501816D4C63FAD67CB1F8A57D03498957764AAA8A844 yields shorter public pair values.
 5 2014-02-03 00:26:20 <jcorgan> dkog: yes, the x or y point might require zero padding when converting from an integer to a string or hex encoded string, and yes, the lack of mention of compressed keys on that page bit me in the ass too
 6 2014-02-03 00:50:52 <jcorgan> i've put up an initial, experimental release of bip32utils, still working on the documentation
 7 2014-02-03 00:51:06 <jcorgan> https://github.com/jmcorgan/bip32utils
 8 2014-02-03 00:51:57 <jcorgan> only depends on the pypi ecdsa package
 9 2014-02-03 03:16:14 <Luke-Jr> anyone know of a tool to parse C code and figure out what headers are needed? would save a lot of time :/
10 2014-02-03 03:18:31 <jcorgan> gcc -M
11 2014-02-03 03:18:36 <jcorgan> or do you need something different
12 2014-02-03 03:22:51 <Luke-Jr> jcorgan: I want it to figure it out from symbols used ;)
13 2014-02-03 03:23:55 <jcorgan> it's still gcc, you just comment out all the includes and iterate adding them back until it succeeds :)
14 2014-02-03 03:26:01 <Luke-Jr> jcorgan: that's not a good method; often you get symbols by accident