--- Day changed Wed Oct 14 2015
03:02 -!- jtimon [~quassel@18.31.134.37.dynamic.jazztel.es] has joined #secp256k1
03:34 -!- Guest58630 is now known as GAit
09:50 -!- Netsplit *.net <-> *.split quits: Guest4879, maaku, fkhan, TD-Linux
09:59 -!- maaku [~quassel@botbot.xen.prgmr.com] has joined #secp256k1
09:59 -!- fkhan [weechat@gateway/vpn/mullvad/x-axplirbccmseankd] has joined #secp256k1
09:59 -!- Guest4879 [~quassel@173-228-107-141.dsl.static.fusionbroadband.com] has joined #secp256k1
09:59 -!- TD-Linux [~Thomas@about/essy/indecisive/TD-Linux] has joined #secp256k1
10:07 -!- Netsplit *.net <-> *.split quits: fkhan, Guest4879, TD-Linux, maaku
10:10 -!- maaku [~quassel@botbot.xen.prgmr.com] has joined #secp256k1
10:10 -!- fkhan [weechat@gateway/vpn/mullvad/x-axplirbccmseankd] has joined #secp256k1
10:10 -!- Guest4879 [~quassel@173-228-107-141.dsl.static.fusionbroadband.com] has joined #secp256k1
10:10 -!- TD-Linux [~Thomas@about/essy/indecisive/TD-Linux] has joined #secp256k1
11:54 <@gmaxwell> sipa: thoughts on having some example users of the library in libsecp256k1?  Without them we risk people taking their examples from tests.c :P
11:54 <@gmaxwell> sipa: perhaps we could pull in matt's contracthashtool as an example?
11:54 <@gmaxwell> I'd like there to be a simple secure key generator available using our library; things other people are using are often really frightening.
12:27 < sipa> gmaxwell: sounds good!
12:29 <@gmaxwell> oh you merged the point test.
12:29 <@gmaxwell> Can we get github to log commits and prs to this channel?
12:32 <@gmaxwell> heh. contracthashtool is written in a mix of C and C++.
12:32 <@gmaxwell> (code stolen from bitcoin core is C++)
12:34 < sipa> yes, i know :)
12:37 <@gmaxwell> ERROREXIT("OH GOD WHAT DID YOU DO?\n");
12:37 <@gmaxwell> lol
15:13 <@andytoshi> i've been reading contracthashtool all day
15:13 <@andytoshi> it's funny in a lot of ways
15:14 <@andytoshi> i don't think we want to promote it as an example of anything tho in its current state unfortunately
15:19 <@gmaxwell> feel free to rewrite. :P contracthashtool itself is simple to redo, I don't really relish redoing all the base58 stuff.
15:20 <@andytoshi> oh, that's not a bad idea. i just finished adding all the requisite support to rust-bitcoin (which already does base58){
15:21 <@andytoshi> https://github.com/apoelstra/rust-bitcoin/commit/16e2a3519b8966dbce45bc9fcd28bf3c0321d5d3 commit 2 hours ago but i pushed 2 minutes ago..
15:21 <@gmaxwell> It needs base58 encode and decode, for private keys and addresses.
16:15 -!- lecusemb1e [~lecusembl@f9beb4d9.violates.me] has quit [Ping timeout: 264 seconds]
16:17 -!- lecusemble [~lecusembl@f9beb4d9.violates.me] has joined #secp256k1
16:25 -!- evoskuil [~evoskuil@c-73-225-134-208.hsd1.wa.comcast.net] has joined #secp256k1
16:47 -!- lecusemble [~lecusembl@f9beb4d9.violates.me] has quit [Ping timeout: 260 seconds]
17:08 -!- lecusemble [~lecusembl@f9beb4d9.violates.me] has joined #secp256k1
17:53 <@gmaxwell> andytoshi: you might hear from belcher (joinmarket) in that he asked what language I thought was best for bitcoin applications and I suggested rust may be a contender, and he found your library.
17:55 <@gmaxwell> sipa: were you going to make the change to make ecdsa verify require lows? and add a function that takes a signature and normalizes it? I think we should do that.
17:56 < sipa> yes
17:58 < sipa> i have a half-finished patch for that
18:03 <@gmaxwell> yea, well so did matt. :P (against an old version of the library, with a wonky api that verifies too. )
18:06 < sipa> oh really?
18:12 < sipa> andytoshi, gmaxwell: i think having example uses in the library should be C/C++ though, unless the wrapper for another language is in the repo too
18:27 <@andytoshi> sipa: agreed :/
18:30 <@gmaxwell> I think it should be C.
18:30 <@gmaxwell> Alas, otherwise we expand the toolset needed to build examples.
18:31 <@gmaxwell> I mean we could have additional examples in other languages too, but the main one should be some plain C thing.
18:31 <@gmaxwell> some bip32 keygen thing + some sign and verify thing.
18:34 <@gmaxwell> recently someone using pybitcointools (ugh) said they were doing so because their other options "didn't have bip32 support".
18:48 < sipa> gmaxwell: indeed, libsecp256k1 doesn't have sha512... :p
19:40 -!- wumpus [~quassel@pdpc/supporter/professional/wumpus] has quit [Ping timeout: 240 seconds]
21:12 <@andytoshi> port of contracthashtool in rust https://github.com/apoelstra/pacthash