1 2015-08-27 00:23:07 <petertodd> btcdrak: by auto-HS I mean, automatically setup a hidden service if tor is available
 2 2015-08-27 00:25:51 <wumpus> petertodd: did you see https://github.com/laanwj/bitcoin/blob/2015_08_tor_hs ?
 3 2015-08-27 00:26:05 <petertodd> wumpus: broken link
 4 2015-08-27 00:26:50 <wumpus> https://github.com/laanwj/bitcoin/tree/2015_08_tor_hs
 5 2015-08-27 00:32:24 <petertodd> wumpus: ha, nice
 6 2015-08-27 00:32:30 <petertodd> wumpus: we'll go debug and test that then :)
 7 2015-08-27 00:34:38 <wumpus> thanks :)
 8 2015-08-27 02:22:33 <StephenM347> Does bitcoin core expose the address-to-scriptPubKey functionality in any straightforward way?
 9 2015-08-27 02:23:02 <StephenM347> I can do a createrawtransaction with no inputs and one dummy output, and then decode the result the get the scriptPubKey->hex, but it's a bit hacky
10 2015-08-27 02:27:39 <Luke-Jr> StephenM347: libblkmaker has it
11 2015-08-27 03:14:24 <isis> wumpus: i know you've got the sha256 hash in the gitian descriptor for libevent https://github.com/laanwj/bitcoin/blob/2015_08_tor_hs/depends/packages/libevent.mk#L3 but if you're concerned for any reason to fetch from sourceforge, then nickm also has a github mirror for libevent: https://github.com/libevent/libevent
12 2015-08-27 03:25:56 <isis> wumpus: uh… also you maybe forgot to checkin torcontrol.h :)
13 2015-08-27 03:37:10 <petertodd> isis: http://0bin.net/paste/bNDyIrQjyfs5ImFL#rYXW1+yaKVpzIJQYny0p-9PMLVlunGgXBto7ssFP3Xp this works
14 2015-08-27 03:37:32 <petertodd> isis: against git commit 817d9e68f27dde1d11f0926d4baeb542f7e18d8c from wumpus's tree
15 2015-08-27 03:38:53 <isis> ack
16 2015-08-27 04:50:30 <petertodd> wumpus: minor error message fix here, and that missing header: https://github.com/petertodd/bitcoin/tree/2015_08_tor_hs
17 2015-08-27 06:06:30 <jouke> j/win 21
18 2015-08-27 06:30:13 <dcousens> https://github.com/kristovatlas/bips/pull/1#issuecomment-135306343 -  sigh, I'm not even sure if there is a right answer to the transactions hashes being little/big endian confusion :S
19 2015-08-27 06:31:14 <dcousens> Is the underlying assumption that the SHA256 output is big-endian?  Why is the transaction id (hex string) shown in little endian then if typically big-endian strings are used for human readability?
20 2015-08-27 06:35:27 <jtimon> rebased and reopened: https://github.com/bitcoin/bitcoin/pull/5970
21 2015-08-27 06:36:16 <jtimon> jonasschnelli: btcdrak may be interested ?
22 2015-08-27 06:53:28 <wumpus> isis: oops! checked in torcontrol.h, had indeed forgotten to
23 2015-08-27 06:57:23 <jtimon> cool you can have PRs with several steps ala org-mode [6/12]
24 2015-08-27 06:57:36 <jtimon> hi isis
25 2015-08-27 06:58:34 <wumpus> petertodd: pulled, thanks
26 2015-08-27 06:58:48 <wumpus> jtimon: yes I saw that on the bips repository; quite nice