1 2017-03-28 01:45:58	0|jcorgan|does anyone know if the digital garage presentation will be live streamed?
  2 2017-03-28 02:00:45	0|phantomcircuit|jcorgan, you mean the bitcoin dev meetup happening nowish?
  3 2017-03-28 02:01:15	0|jcorgan|yes. i had planned to attend but had something come up at the last minute.
  4 2017-03-28 02:02:10	0|jcorgan|well, i'm sure it will be recorded in any case
  5 2017-03-28 02:07:24	0|phantomcircuit|jcorgan, they're usually not
  6 2017-03-28 02:07:32	0|phantomcircuit|i doubt this will be
  7 2017-03-28 02:08:24	0|jcorgan|ah well.
  8 2017-03-28 02:09:29	0|jcorgan|i'll just have to do what they did in the pre-Interet age and use my *imagination* when reading sipa's documentation
  9 2017-03-28 02:25:36	0|sipa|jcorgan: or you could ask questions here :)
 10 2017-03-28 02:25:40	0|sipa|it will be recorded, yes
 11 2017-03-28 02:25:46	0|sipa|not streamed i believe
 12 2017-03-28 04:09:51	0|achow101|I'm attempting to run the linearize scripts but it keeps timing out? anyone have any ideas?
 13 2017-03-28 04:15:35	0|achow101|nvm. it magically resolved itself
 14 2017-03-28 04:21:33	0|bitcoin-git|[13bitcoin] 15achow101 opened pull request #10104: linearize script: Option to use RPC cookie (06master...06linearize-use-cookie) 02https://github.com/bitcoin/bitcoin/pull/10104
 15 2017-03-28 04:46:07	0|testando|test
 16 2017-03-28 06:30:42	0|kallewoof|There were cameras pointed at sipa so presumably there are recordings
 17 2017-03-28 09:27:05	0|bitcoin-git|[13bitcoin] 15MarcoFalke pushed 4 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/5114f8113627...c412fd805ddf
 18 2017-03-28 09:27:06	0|bitcoin-git|13bitcoin/06master 1455992f1 15John Newbery: Add --quiet option to suppress rpc-tests.py output...
 19 2017-03-28 09:27:06	0|bitcoin-git|13bitcoin/06master 146d780b1 15John Newbery: Update travis config to run rpc-tests.py in quiet mode
 20 2017-03-28 09:27:07	0|bitcoin-git|13bitcoin/06master 148c7288c 15John Newbery: Print out the final 1000 lines of test_framework.log if test fails
 21 2017-03-28 09:27:30	0|bitcoin-git|[13bitcoin] 15MarcoFalke closed pull request #9780: Suppress noisy output from qa tests in Travis (06master...06travislogging) 02https://github.com/bitcoin/bitcoin/pull/9780
 22 2017-03-28 09:38:51	0|bitcoin-git|13bitcoin/06master 1429d6634 15John Newbery: Check that all test scripts in test/functional are being run...
 23 2017-03-28 09:38:51	0|bitcoin-git|[13bitcoin] 15MarcoFalke pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/c412fd805ddf...79af9fbd8c3c
 24 2017-03-28 09:38:52	0|bitcoin-git|13bitcoin/06master 1479af9fb 15MarcoFalke: Merge #10096: Check that all test scripts in test/functional are being run...
 25 2017-03-28 09:39:11	0|bitcoin-git|[13bitcoin] 15MarcoFalke closed pull request #10096: Check that all test scripts in test/functional are being run (06master...06check_all_tests_run) 02https://github.com/bitcoin/bitcoin/pull/10096
 26 2017-03-28 10:16:36	0|brg444|has someone undertaken more research into BFD/committed bloom filters since it was proposed on the ml?
 27 2017-03-28 12:47:14	0|bitcoin-git|[13bitcoin] 15MarcoFalke pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/79af9fbd8c3c...5b029aaedb5f
 28 2017-03-28 12:47:15	0|bitcoin-git|13bitcoin/06master 145b029aa 15MarcoFalke: Merge #10076: [qa] combine_logs: Use ordered list for logfiles...
 29 2017-03-28 12:47:15	0|bitcoin-git|13bitcoin/06master 14fa4535d 15MarcoFalke: [qa] combine_logs: Use ordered list for logfiles
 30 2017-03-28 12:47:39	0|bitcoin-git|[13bitcoin] 15MarcoFalke closed pull request #10076: [qa] combine_logs: Use ordered list for logfiles (06master...06Mf1703-orderedLog) 02https://github.com/bitcoin/bitcoin/pull/10076
 31 2017-03-28 12:49:37	0|bitcoin-git|[13bitcoin] 15jnewbery opened pull request #10105: [tests] fixup - make all Travis test runs quiet, non just cron job runs (06master...06fixup_travis_logging) 02https://github.com/bitcoin/bitcoin/pull/10105
 32 2017-03-28 12:57:41	0|bitcoin-git|[13bitcoin] 15awemany opened pull request #10106: bitcoin-tx: Fix missing range check (06master...06bitcointx-addoutaddr) 02https://github.com/bitcoin/bitcoin/pull/10106
 33 2017-03-28 13:11:37	0|bitcoin-git|13bitcoin/06master 140b9fb68 15MarcoFalke: Merge #10105: [tests] fixup - make all Travis test runs quiet, non just cron job runs...
 34 2017-03-28 13:11:37	0|bitcoin-git|13bitcoin/06master 1491f1f19 15John Newbery: Make all Travis test runs quiet, non just cron job runs
 35 2017-03-28 13:11:37	0|bitcoin-git|[13bitcoin] 15MarcoFalke pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/5b029aaedb5f...0b9fb682890b
 36 2017-03-28 13:12:02	0|bitcoin-git|[13bitcoin] 15MarcoFalke closed pull request #10105: [tests] fixup - make all Travis test runs quiet, non just cron job runs (06master...06fixup_travis_logging) 02https://github.com/bitcoin/bitcoin/pull/10105
 37 2017-03-28 13:13:47	0|luke-jr|hmm. I wonder if, when there are two equal-work tips, we ought to be treating the last common block as the real tip until the contention resolves.
 38 2017-03-28 13:23:13	0|bitcoin-git|[13bitcoin] 15practicalswift opened pull request #10107: Remove unused variable. Fix accidental trailing semicolons in Python code (06master...06recent-python-style-regressions) 02https://github.com/bitcoin/bitcoin/pull/10107
 39 2017-03-28 15:57:28	0|BlueMatt|wumpus: hmm, would be good to get a rebase on #7729
 40 2017-03-28 15:57:30	0|gribble|https://github.com/bitcoin/bitcoin/issues/7729 | An error has occurred and has been logged. Please contact this bot's administrator for more information.
 41 2017-03-28 15:57:34	0|BlueMatt|so i can review :)
 42 2017-03-28 17:11:42	0|spudowiar|Does Bitcoin Core use any IPC?
 43 2017-03-28 17:12:14	0|spudowiar|For signing, we could have a signer process (which could talk to a hardware wallet, a remote computer, etc.) which communicates with the wallet over IPC
 44 2017-03-28 17:20:14	0|TD-Linux|spudowiar, it only has the RPC interface and zeromq
 45 2017-03-28 17:20:33	0|spudowiar|TD-Linux: I was thinking about the RPC interface, but I don't think running a server would be a good idea
 46 2017-03-28 17:20:45	0|spudowiar|TD-Linux: What does it use ZMQ for?
 47 2017-03-28 17:20:55	0|TD-Linux|there was a previous BIP proposal for a URL-style communication for hw wallets: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2016-August/013008.html
 48 2017-03-28 17:21:19	0|spudowiar|If that's jonasschnelli's proposal, I've read that :)
 49 2017-03-28 17:21:42	0|TD-Linux|spudowiar, it's for "push notifications" of events
 50 2017-03-28 17:21:53	0|spudowiar|I see
 51 2017-03-28 17:22:36	0|TD-Linux|spudowiar, yeah. I'm personally not a huge fan of the URL style communication method...
 52 2017-03-28 17:22:43	0|spudowiar|Me neither
 53 2017-03-28 17:23:10	0|spudowiar|I want a separate process (I don't want any hardware wallet stuff in Bitcoin Core)
 54 2017-03-28 17:23:25	0|spudowiar|We could have something like bitcoin-trezor-signd
 55 2017-03-28 17:23:44	0|TD-Linux|I think it'd actually be really neat if bitcoin core supported hw wallets out of the box
 56 2017-03-28 17:24:08	0|spudowiar|Of course, but it should be a separate process
 57 2017-03-28 17:24:27	0|spudowiar|e.g. Core starts `bitcoin-trezor-signd`, communicates over IPC
 58 2017-03-28 17:24:48	0|TD-Linux|what's the main purpose of the separate process?
 59 2017-03-28 17:25:06	0|spudowiar|I don't think it's a good idea to have the actual code in Core
 60 2017-03-28 17:25:23	0|spudowiar|gmaxwell: Since you're on GitHub RIGHT NOW talking about IPC, what IPC method do you suggest :)
 61 2017-03-28 17:25:23	0|TD-Linux|for security reasons?
 62 2017-03-28 17:25:43	0|spudowiar|For a number of reasons, security being one of them
 63 2017-03-28 17:25:56	0|TD-Linux|if you want to do IPC for security, you also need sandboxing or some sort of isolation between the two processes
 64 2017-03-28 17:25:58	0|spudowiar|You'd have to add dependencies on software like hidapi, etc.
 65 2017-03-28 17:26:02	0|luke-jr|TD-Linux: it'd be nice if hw wallets could just distribute plugins
 66 2017-03-28 17:26:11	0|spudowiar|luke-jr: That would work with my method
 67 2017-03-28 17:26:13	0|spudowiar|Ooh
 68 2017-03-28 17:26:20	0|spudowiar|Doesn't Bitcoin Core use Protocol Buffers for payment requests?
 69 2017-03-28 17:26:26	0|spudowiar|We could use Protocol Buffers?
 70 2017-03-28 17:26:28	0|gmaxwell|DO NOT USE PROTOBUF
 71 2017-03-28 17:26:47	0|spudowiar|Ok :)
 72 2017-03-28 17:26:49	0|spudowiar|Why?
 73 2017-03-28 17:26:57	0|spudowiar|I feel like I've been told off ;)
 74 2017-03-28 17:27:03	0|gmaxwell|As you should.
 75 2017-03-28 17:27:04	0|gmaxwell|:P
 76 2017-03-28 17:27:10	0|luke-jr|use Perl and put a Perl interpreter in Core
 77 2017-03-28 17:27:11	0|luke-jr|/s
 78 2017-03-28 17:27:29	0|spudowiar|luke-jr: I kind of think Java would be better? Know any Perl JVM implementations? /s :)
 79 2017-03-28 17:27:34	0|gmaxwell|spudowiar: what you're discussing has been discussed a few times in the past. You don't need a freeking seralization library to send a simple 'sign this'
 80 2017-03-28 17:27:35	0|TD-Linux|luke-jr, yes, though that's an extra step that would be nice to have automated
 81 2017-03-28 17:27:49	0|spudowiar|gmaxwell: Well, you can't send the transaction, you need a data format
 82 2017-03-28 17:28:10	0|spudowiar|The hardware wallet needs to know the key path and other metadata it will store with the wallet (like account number, etc.)
 83 2017-03-28 17:28:56	0|spudowiar|And UTXO ids
 84 2017-03-28 17:29:38	0|gmaxwell|spudowiar: yes, so just seralize it. this isn't rocket science. We manage to run the whole network without any wonky seralization libraries.
 85 2017-03-28 17:30:09	0|TD-Linux|I'd really love to have a standard USB protocol, maybe I am overreaching :)
 86 2017-03-28 17:30:20	0|gmaxwell|die.
 87 2017-03-28 17:31:29	0|gmaxwell|somewhere I wrote some requiremets for a suggestion that you be able to add to the configuration a path to an executable to run for signing, and it would just invoke it and communicate over stdin, to tell it what to sign.  Said executable could do whatever it wanted, pop up confirmation dialogs to get passwords and decrypt keys, connect out over usb using whatever protocol you want, etc.
 88 2017-03-28 17:32:49	0|gmaxwell|this keeps the implementation of whatever weird interface you want to use outside of bitcoin.
 89 2017-03-28 17:32:50	0|spudowiar|gmaxwell: Serialize it with... what? That's all I'm asking you :)
 90 2017-03-28 17:33:03	0|spudowiar|gmaxwell: That's the sort of thing I was thinking of
 91 2017-03-28 17:33:11	0|spudowiar|I meant serialization earlier, not IPC when I asked you :)
 92 2017-03-28 17:33:33	0|gmaxwell|spudowiar: the serialization code already in the software.
 93 2017-03-28 17:33:47	0|spudowiar|So, the C* family of classes?
 94 2017-03-28 17:34:21	0|spudowiar|Well, base_blob
 95 2017-03-28 17:36:08	0|gmaxwell|spudowiar: this is like ... programming 101 stuff. Define a structure for what you need to communicate and then make a seralizer for it. This is simplified by the fact that we already have seralizers for most or all of the fields you need to send (like a transaction).
 96 2017-03-28 17:36:34	0|spudowiar|gmaxwell: I know how to serialize, but this is more of a "this is your codebase, how do you do stuff around here"
 97 2017-03-28 17:37:23	0|gmaxwell|spudowiar: look at the codebase to answer that! we don't do things by pulling in gigantic libraries that barely do what we need and only inefficiently in other to replace what is probably 5 lines of code. :P
 98 2017-03-28 17:37:53	0|spudowiar|Anyway, sorry for being annoying, it takes me a bit of time to get familiar with large codebases
 99 2017-03-28 17:38:23	0|spudowiar|Grrr, CExtKey and CExtPubKey share no interface :( This means there's a ton of repeated code :(
100 2017-03-28 17:44:45	0|bsm117532|bitcoin.sipa.be appears to be down.  I can't check my daily segwit activation stats!
101 2017-03-28 17:46:27	0|sipa|spudowiar: look at the Serialize and Unserialize methods that some classes have
102 2017-03-28 17:46:47	0|spudowiar|sipa: Ah, so it's all the base_blob stuff, gotcha! :)
103 2017-03-28 17:47:30	0|spudowiar|I should just be able to create something like an ExternalSignatureCreator : BaseSignatureCreator
104 2017-03-28 17:47:58	0|sipa|eh, maybe
105 2017-03-28 17:48:05	0|sipa|i dodn't read the conversation above
106 2017-03-28 17:48:57	0|spudowiar|sipa: Basically, execute other program, feed it serialized transaction data, (external program talks to HW wallet), verify signature
107 2017-03-28 17:49:52	0|spudowiar|Probably : TransactionSignatureCreator, rather than Base
108 2017-03-28 17:56:05	0|spudowiar|Thanks sipa & gmaxwell for all the help :)
109 2017-03-28 17:56:22	0|spudowiar|Now I know what to grep for, I can infer the rest :)
110 2017-03-28 18:10:32	0|sipa|bsm117532: my vps provider claims it was running a bitcoin miner and turned it off
111 2017-03-28 18:10:47	0|sipa|bsm117532: thankfully i'm in the middle of migrating elsewhere
112 2017-03-28 18:11:51	0|bsm117532|Sounds like they need to be hit with a cluestick.  Moving sounds like a good plan...
113 2017-03-28 18:12:33	0|sipa|it is not even the first time they claim this
114 2017-03-28 18:12:57	0|sipa|though in previous occasions they at least asked for an explanation instead of just turning it off
115 2017-03-28 18:13:37	0|bitcoin-git|[13bitcoin] 15RHavar opened pull request #10108: ApproximateBestSubset should take inputs by reference, not value (06master...06trivial) 02https://github.com/bitcoin/bitcoin/pull/10108
116 2017-03-28 18:22:12	0|bitcoin-git|[13bitcoin] 15jnewbery opened pull request #10109: Remove SingleNodeConnCB (06master...06remove_single_node_conn_cb) 02https://github.com/bitcoin/bitcoin/pull/10109
117 2017-03-28 18:29:10	0|bitcoinreminder_|sipa: it looks like your segwit stats are offline?
118 2017-03-28 18:33:14	0|sipa|bitcoinreminder_: read a few lines up
119 2017-03-28 18:33:42	0|bitcoinreminder_|oh right, I see, sorry! :)
120 2017-03-28 19:30:09	0|instagibbs|what's the fastest way to run a python test with an additional debug log param?
121 2017-03-28 19:31:08	0|jnewbery|./test_runner.py -l debug
122 2017-03-28 19:32:19	0|jnewbery|Sorry. To be clearer: bitcoind instances being tested now always have debug logging enabled. the -l debug enables debug logging for the test framework
123 2017-03-28 19:33:22	0|jnewbery|instagibbs: ^
124 2017-03-28 19:41:17	0|instagibbs|jnewbery, ah thanks.
125 2017-03-28 19:42:17	0|jnewbery|#10017 may also be helpful if you're trying to fix failing testcases
126 2017-03-28 19:42:18	0|gribble|https://github.com/bitcoin/bitcoin/issues/10017 | combine_logs.py - aggregates log files from multiple bitcoinds during functional tests. by jnewbery · Pull Request #10017 · bitcoin/bitcoin · GitHub
127 2017-03-28 19:51:43	0|sipa|bsm117532: it's moved, but DNS will take 12 hours to propagate
128 2017-03-28 19:51:54	0|sipa|s/propagate/timeout/
129 2017-03-28 19:52:11	0|bsm117532|But...what if segwit activates in the next 12 hours?!?!?!  How will we know?!?!?!
130 2017-03-28 19:52:42	0|bsm117532|I kid...I kid...but thanks for making that service.
131 2017-03-28 19:53:09	0|sipa|the only way you should find out: you run a segwit-enabled full node :)
132 2017-03-28 19:53:13	0|bsm117532|Oh I do. :-P
133 2017-03-28 19:54:09	0|Cobra|so this is where the magic happens :P
134 2017-03-28 19:54:47	0|BlueMatt|sipa: I rndc flush'd and i still cant access it
135 2017-03-28 19:55:56	0|BlueMatt|sipa: looks like ns*.ulyssis.org are still returning the old values
136 2017-03-28 19:58:50	0|sipa|BlueMatt: that's possible
137 2017-03-28 20:01:50	0|bitcoin-git|[13bitcoin] 15jnewbery opened pull request #10111: Remove NetworkThread from individual test cases (06master...06remove_network_thread_from_test_scripts) 02https://github.com/bitcoin/bitcoin/pull/10111
138 2017-03-28 21:17:04	0|bitcoin-git|[13bitcoin] 15ryanofsky opened pull request #10113: Fix test_bitcoin-qt when DISPLAY is unset (06master...06pr/nodisp) 02https://github.com/bitcoin/bitcoin/pull/10113