--- Day changed Sun Dec 11 2016 00:11 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection] 00:12 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev 00:25 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection] 00:26 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev 00:33 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-nkbyamsttgmvejgy] has joined #bitcoin-core-dev 01:19 -!- MarcoFalke [~marco@2a02:778:100:ea01:2225:64ff:fe3b:d4ca] has joined #bitcoin-core-dev 01:46 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection] 01:47 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev 03:00 -!- gluytium_ [U2FsdGVkX1@ma.sdf.org] has joined #bitcoin-core-dev 03:03 -!- gluytium [~g@45.63.76.107] has quit [Quit: IRC (Quit: Not that there is anything wrong with that)] 03:54 -!- CubicEarth [~cubiceart@c-50-159-126-21.hsd1.wa.comcast.net] has quit [Remote host closed the connection] 03:56 -!- CubicEarth [~cubiceart@c-50-159-126-21.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 04:49 -!- nickler [~nickler@185.12.46.130] has quit [Ping timeout: 245 seconds] 04:54 -!- CubicEarth [~cubiceart@c-50-159-126-21.hsd1.wa.comcast.net] has quit [Remote host closed the connection] 05:00 -!- CubicEarth [~cubiceart@c-50-159-126-21.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 05:14 -!- CubicEarth [~cubiceart@c-50-159-126-21.hsd1.wa.comcast.net] has quit [Remote host closed the connection] 05:15 -!- CubicEarth [~cubiceart@c-50-159-126-21.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 05:18 -!- LeMiner [~LeMiner@5ED1AFBF.cm-7-2c.dynamic.ziggo.nl] has quit [Read error: Connection reset by peer] 05:19 < bitcoin-git> [bitcoin] MarcoFalke opened pull request #9322: [qa] Don't set unknown rpcserialversion (master...Mf1612-qaSerial) https://github.com/bitcoin/bitcoin/pull/9322 05:20 -!- CubicEarth [~cubiceart@c-50-159-126-21.hsd1.wa.comcast.net] has quit [Ping timeout: 248 seconds] 05:23 -!- alpalp [~allen@cpe-24-27-58-209.austin.res.rr.com] has joined #bitcoin-core-dev 05:23 -!- alpalp [~allen@cpe-24-27-58-209.austin.res.rr.com] has quit [Changing host] 05:23 -!- alpalp [~allen@unaffiliated/alpalp] has joined #bitcoin-core-dev 06:27 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-nkbyamsttgmvejgy] has quit [Quit: Connection closed for inactivity] 06:30 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [] 06:33 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Remote host closed the connection] 06:33 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #bitcoin-core-dev 06:43 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 06:58 -!- MarcoFalke [~marco@2a02:778:100:ea01:2225:64ff:fe3b:d4ca] has left #bitcoin-core-dev [] 07:00 -!- d9b4bef9 [~d9b4bef9@web419.webfaction.com] has quit [Remote host closed the connection] 07:00 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-core-dev 07:01 -!- d9b4bef9 [~d9b4bef9@web419.webfaction.com] has joined #bitcoin-core-dev 07:09 -!- AaronvanW [~ewout@207pc74.sshunet.nl] has joined #bitcoin-core-dev 07:09 -!- AaronvanW [~ewout@207pc74.sshunet.nl] has quit [Changing host] 07:09 -!- AaronvanW [~ewout@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 07:27 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 07:29 -!- shesek [~shesek@bzq-84-110-57-45.red.bezeqint.net] has quit [Ping timeout: 260 seconds] 07:36 -!- Giszmo [~leo@pc-40-227-45-190.cm.vtr.net] has joined #bitcoin-core-dev 07:40 -!- Sosumi [~Leon@bl10-113-190.dsl.telepac.pt] has joined #bitcoin-core-dev 07:43 < paveljanik> sipa_, restarting bitcoind, it was started at 13:17:26 and Import mempool run at 13:18:40, ie. more than one minute after the new start. Is this as designed? I was even able to getmempoolinfo in between... 07:47 -!- shesek [~shesek@bzq-84-110-57-94.red.bezeqint.net] has joined #bitcoin-core-dev 07:58 -!- nickler [~nickler@185.12.46.130] has joined #bitcoin-core-dev 08:10 < sipa_> paveljanik: it runs after connecting blocks on disk 08:10 < paveljanik> sipa_, yes. 08:11 < paveljanik> I have added some debugging 08:11 < paveljanik> load speed here is 1000 tx per 10seconds... 08:11 < paveljanik> or even more: 08:11 < paveljanik> 2016-12-11 16:10:49 Loadmempool tx 3000 08:11 < paveljanik> 2016-12-11 16:11:09 Loadmempool tx 4000 08:13 < paveljanik> 2016-12-11 16:11:27 Loadmempool tx 5000 08:13 < paveljanik> 2016-12-11 16:11:51 Loadmempool tx 6000 08:13 < paveljanik> 2016-12-11 16:11:59 Loadmempool tx 7000 08:13 < sipa_> transaction validation is not that fast 08:16 < paveljanik> I was a bit surprised that it took more than minute (67MB mempool.dat) 08:31 -!- laurentmt [~Thunderbi@176.158.157.202] has joined #bitcoin-core-dev 08:40 -!- laurentmt [~Thunderbi@176.158.157.202] has quit [Quit: laurentmt] 09:04 < bitcoin-git> [bitcoin] rebroad closed pull request #9055: Skip processing of cmpctblocks we have previously downloaded. (master...SkipCmpctblocksPreviouslyDownloaded) https://github.com/bitcoin/bitcoin/pull/9055 09:11 < bitcoin-git> [bitcoin] rebroad closed pull request #9300: Check for oversized getblocktxn message. (master...CheckOversizedGetblocktxns) https://github.com/bitcoin/bitcoin/pull/9300 09:12 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-fbjjhbsxmvzzhqzy] has joined #bitcoin-core-dev 09:59 -!- nickler [~nickler@185.12.46.130] has quit [Ping timeout: 256 seconds] 09:59 -!- nickler [~nickler@185.12.46.130] has joined #bitcoin-core-dev 10:13 -!- protomar [~protomar@91.214.169.69] has joined #bitcoin-core-dev 10:18 -!- wkohlenberg [4da693e4@gateway/web/freenode/ip.77.166.147.228] has joined #bitcoin-core-dev 10:40 -!- CubicEarth [~cubiceart@2002:329f:7e15:0:cc7f:1bb:d934:205] has joined #bitcoin-core-dev 10:43 -!- CubicEarth [~cubiceart@2002:329f:7e15:0:cc7f:1bb:d934:205] has quit [Remote host closed the connection] 10:44 -!- CubicEarth [~cubiceart@c-50-159-126-21.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 10:50 -!- wkohlenberg [4da693e4@gateway/web/freenode/ip.77.166.147.228] has quit [Quit: Page closed] 10:57 -!- vorksholk [ae1cac5c@gateway/web/freenode/ip.174.28.172.92] has quit [Ping timeout: 260 seconds] 10:59 -!- laurentmt [~Thunderbi@176.158.157.202] has joined #bitcoin-core-dev 10:59 -!- laurentmt [~Thunderbi@176.158.157.202] has quit [Client Quit] 11:19 -!- JackH [~laptop@79-73-186-159.dynamic.dsl.as9105.com] has joined #bitcoin-core-dev 11:43 < Chris_Stewart_5> How is OP_0 handled inside of a witness, because it is an empty byte vector when actually placed onto the stack? Is it replaced some where in the serialization code from 0x00 -> []? 11:48 -!- JackH [~laptop@79-73-186-159.dynamic.dsl.as9105.com] has quit [Remote host closed the connection] 11:51 -!- CubicEarth [~cubiceart@c-50-159-126-21.hsd1.wa.comcast.net] has quit [Remote host closed the connection] 11:52 -!- CubicEarth [~cubiceart@2002:329f:7e15:0:cc7f:1bb:d934:205] has joined #bitcoin-core-dev 11:57 < luke-jr> 0x00 has always been [] 11:59 < sipa_> OP_0 produces [] on the stack 11:59 -!- sipa_ is now known as sipa 11:59 < sipa> in the witness stack, we just bypass the opcode, and use [] directly 12:02 < Chris_Stewart_5> So that is done the witness serialization code? the 'bypass the opcode'? 12:02 < luke-jr> oh, hm. I guess small numbers take 2x the bytes in segwit then 12:02 < luke-jr> Chris_Stewart_5: segwit witnesses aren't scripts, so it's just automatic 12:03 < luke-jr> although AFAIK OP_0 is just serialized as 0 which is also the length of [] so I'm not sure why that specific case would appear any different? 12:05 < sipa> Chris_Stewart_5: scriptSigs being a script is just a legacy, probably intended to support delegation 12:05 < sipa> the script witness stack is just encoded as a vector of vectors of bytes 12:06 < Chris_Stewart_5> Maybe this is what I'm getting confused about, when a vector is '00' it is indicating that the length of the vector is zero in the witness, correct? 12:06 < sipa> yes 12:06 < Chris_Stewart_5> yeah, doh! Thanks guys. 12:07 < luke-jr> ☺ 12:07 < Chris_Stewart_5> luke-jr: What did you mean by 2x the bytes in segwit? 12:07 < Chris_Stewart_5> because they require a pushop to be encoded before the actual number if it is only a number in a byte vector? 12:07 < luke-jr> Chris_Stewart_5: OP_1 would be a single byte (0x81) in Script, but in segwit it is 0x01 (length) 0x01 (data) 12:08 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 250 seconds] 12:08 < Chris_Stewart_5> Yeah, I think that is what was confusing me. A small but important difference 12:09 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev 12:10 < luke-jr> of course, it rarely makes sense to have a small integer in a witness by itself I think 12:10 < luke-jr> usually it'd be part of the program 12:10 < Chris_Stewart_5> Yeah I agree, I can't think of anything off of the top of my head 12:11 < sipa> luke-jr: i recently generated a histogram of the sizes of pushes in scriptSigs 12:11 < sipa> there are 48M 1-byte pushes 12:11 < sipa> sorry, 23.5M 1-byte pushes 12:12 < luke-jr> sipa: exclude OP_1 and scriptSigs which are only OP_TRUE? 12:12 -!- MarcoFalke [~marco@2a02:778:100:ea01:2225:64ff:fe3b:d4ca] has joined #bitcoin-core-dev 12:12 < luke-jr> OP_0* 12:12 < sipa> 408M signatures 12:12 < sipa> 359M pubkeys 12:12 < sipa> 15.3M 107-byte pushes 12:13 < sipa> 7.7M 72-byte pushes (= mostly non-DER signatures, as those aren't counted under the signatures field) 12:15 < sipa> 0.5M 138-byte pushes 12:15 < sipa> all the rest is less than 0.2M 12:17 < luke-jr> 1-byte pushes besides OP_0 and entire-scriptSig-is-OP_TRUE seem like they wouldn't be used much, but I have no real data measuring it 12:25 < sipa> i agree, i don't know what they're for 12:27 < gmaxwell> hm? checkmultisig paramters 12:27 < gmaxwell> oh in signatures. hm 12:28 < gmaxwell> well used to activate if branches. 12:32 < sipa> i would be surprised if there are 23M spends of outputs with branches in the chain 12:33 < sipa> (but i don't know) 12:35 < gmaxwell> Oh I missed the number, that is a lot 12:37 < gmaxwell> sipa: would you like me to give a crack at writing a release note for 9302? 12:37 < sipa> gmaxwell: sure 12:49 < gmaxwell> sipa: https://0bin.net/paste/49XqHf2k61I38lxn#pMcwMTsRWlKraOsU+dk93V-rv/if0qV+IRlrwTwil3f 13:03 -!- Sosumi [~Leon@bl10-113-190.dsl.telepac.pt] has quit [Quit: Bye] 13:03 < MarcoFalke> gmaxwell: ACK 13:06 < gmaxwell> How do we deal with release notes for backports for features that are initially going into master? 13:08 -!- alpalp [~allen@unaffiliated/alpalp] has quit [Ping timeout: 240 seconds] 13:08 < sipa> backport the release notes as well? 13:09 < MarcoFalke> Only create a pull against 0.13 13:10 < MarcoFalke> We don't need the release notes in 0.14, as the feature was already released 13:21 < bitcoin-git> [bitcoin] gmaxwell opened pull request #9323: [0.13] Add release notes for wallet/mempool rejections. (PR #9302 and #9290) (0.13...mempool_relnote) https://github.com/bitcoin/bitcoin/pull/9323 13:37 -!- CubicEarth [~cubiceart@2002:329f:7e15:0:cc7f:1bb:d934:205] has quit [Remote host closed the connection] 13:45 -!- CubicEarth [~cubiceart@c-50-159-126-21.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 13:54 -!- CubicEarth [~cubiceart@c-50-159-126-21.hsd1.wa.comcast.net] has quit [Remote host closed the connection] 13:54 -!- CubicEarth [~cubiceart@2002:329f:7e15:0:cc7f:1bb:d934:205] has joined #bitcoin-core-dev 13:56 -!- CubicEar_ [~cubiceart@c-50-159-126-21.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 13:56 -!- CubicEar_ [~cubiceart@c-50-159-126-21.hsd1.wa.comcast.net] has quit [Read error: Connection reset by peer] 13:58 -!- CubicEarth [~cubiceart@2002:329f:7e15:0:cc7f:1bb:d934:205] has quit [Ping timeout: 258 seconds] 14:10 -!- CubicEarth [~cubiceart@c-50-159-126-21.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 14:10 -!- CubicEarth [~cubiceart@c-50-159-126-21.hsd1.wa.comcast.net] has quit [Remote host closed the connection] 14:10 -!- CubicEarth [~cubiceart@c-50-159-126-21.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 14:13 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has quit [Quit: :)] 14:19 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 260 seconds] 14:22 -!- MarcoFalke [~marco@2a02:778:100:ea01:2225:64ff:fe3b:d4ca] has left #bitcoin-core-dev [] 14:23 -!- CubicEarth [~cubiceart@c-50-159-126-21.hsd1.wa.comcast.net] has quit [Remote host closed the connection] 14:40 -!- d9b4bef9 [~d9b4bef9@web419.webfaction.com] has quit [Remote host closed the connection] 14:40 -!- belcher [~belcher@unaffiliated/belcher] has joined #bitcoin-core-dev 14:41 -!- d9b4bef9 [~d9b4bef9@web419.webfaction.com] has joined #bitcoin-core-dev 14:41 -!- CubicEarth [~cubiceart@c-50-159-126-21.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 14:51 -!- AaronvanW [~ewout@unaffiliated/aaronvanw] has quit [Quit: Ex-Chat] 14:54 -!- CubicEarth [~cubiceart@c-50-159-126-21.hsd1.wa.comcast.net] has quit [Remote host closed the connection] 14:59 -!- alpalp [~allen@unaffiliated/alpalp] has joined #bitcoin-core-dev 14:59 -!- CubicEarth [~cubiceart@c-50-159-126-21.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 15:15 -!- owowo [ovovo@gateway/vpn/mullvad/x-jbiuuwqlgrfvarjv] has quit [Ping timeout: 244 seconds] 15:18 -!- protomar [~protomar@91.214.169.69] has quit [Quit: Leaving] 15:52 -!- owowo [ovovo@unaffiliated/ovovo] has joined #bitcoin-core-dev 15:52 -!- owowo [ovovo@unaffiliated/ovovo] has quit [Changing host] 15:52 -!- owowo [ovovo@gateway/vpn/mullvad/x-myxoyexrhwztqgca] has joined #bitcoin-core-dev 16:19 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 265 seconds] 16:28 -!- belcher [~belcher@unaffiliated/belcher] has joined #bitcoin-core-dev 16:59 -!- CubicEarth [~cubiceart@c-50-159-126-21.hsd1.wa.comcast.net] has quit [] 17:07 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-fbjjhbsxmvzzhqzy] has quit [Quit: Connection closed for inactivity] 17:11 -!- [Author] [~Author]@2401:a400:3200:5600:bad:d09:15:90d] has quit [Ping timeout: 268 seconds] 17:12 -!- [Author] [~Author]@2401:a400:3200:5600:bad:d09:15:90d] has joined #bitcoin-core-dev 17:43 -!- PaulCapestany [~PaulCapes@2604:5500:17:2ea:80ba:b743:538a:b5ae] has joined #bitcoin-core-dev 18:07 -!- tadasv [ttttt@gateway/shell/panicbnc/x-spkxovlcbhzhkkgj] has quit [Quit: PanicBNC - http://PanicBNC.net] 18:34 < bitcoin-git> [bitcoin] goku1997 opened pull request #9324: Increase block size to 8MB for Bitcoin Ocho. Bitcoin Ocho is the future. (master...master) https://github.com/bitcoin/bitcoin/pull/9324 18:41 -!- dgenr8 [~dgenr8@unaffiliated/dgenr8] has joined #bitcoin-core-dev 18:48 < bitcoin-git> [bitcoin] sipa closed pull request #9324: Increase block size to 8MB for Bitcoin Ocho. Bitcoin Ocho is the future. (master...master) https://github.com/bitcoin/bitcoin/pull/9324 18:52 < gmaxwell> oh no sipa closed /the future/ 19:02 < BlueMatt> https://github.com/bitcoin/bitcoin/blob/master/src/addrman.cpp#L38 its not the first time he's blocked things from the future 19:02 < luke-jr> if only all our trolls were this ridiculous 19:06 -!- tadasv [ttttt@gateway/shell/panicbnc/x-wpbnavqaqjbwhsio] has joined #bitcoin-core-dev 19:58 -!- alpalp [~allen@unaffiliated/alpalp] has quit [Ping timeout: 264 seconds] 20:24 -!- kadoban [~mud@unaffiliated/kadoban] has quit [Quit: bye] 20:29 -!- Madars [~null@unaffiliated/madars] has joined #bitcoin-core-dev 20:54 -!- wasi [~wasi@gateway/tor-sasl/wasi] has quit [Ping timeout: 245 seconds] 21:15 -!- thechronicode [48c2dce2@gateway/web/freenode/ip.72.194.220.226] has joined #bitcoin-core-dev 21:17 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection] 21:17 -!- wasi [~wasi@gateway/tor-sasl/wasi] has joined #bitcoin-core-dev 21:18 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev 21:42 -!- windsok [~windsok@45.63.59.8] has quit [Ping timeout: 250 seconds] 21:45 -!- wasi [~wasi@gateway/tor-sasl/wasi] has quit [Ping timeout: 245 seconds] 22:00 -!- wasi [~wasi@gateway/tor-sasl/wasi] has joined #bitcoin-core-dev 22:21 -!- Giszmo [~leo@pc-40-227-45-190.cm.vtr.net] has quit [Quit: Leaving.] 22:30 -!- windsok [~windsok@45.63.59.8] has joined #bitcoin-core-dev 22:56 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 250 seconds] 23:00 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-jmntxozuayuobkqa] has joined #bitcoin-core-dev 23:00 -!- thechronicode [48c2dce2@gateway/web/freenode/ip.72.194.220.226] has quit [Ping timeout: 260 seconds] 23:05 < owowo> the future was yesterday. 23:10 < bitcoin-git> [bitcoin] rebroad opened pull request #9325: Allow first cmpctblock/blocktxn received to be processed (rather than first requested) (master...ProcessFirstCmpct) https://github.com/bitcoin/bitcoin/pull/9325 23:12 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 23:24 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 252 seconds] 23:27 < jonasschnelli> This looks like an openssl incompatibility? http://bitcoin.stackexchange.com/questions/50125/failing-to-build-bitcoin-core-v0-13-1-on-debian-stretch 23:31 < sipa> jonasschnelli: yup 23:32 < gmaxwell> jonasschnelli: openssl 1.1 made a breaking change to their API. AFAICT there is no fix for the libsecp256k1 tests except fixing the configure script to not try to build them-- they removed functionality the tests were using. I opened an issue, it's a trivial thing to address-- but without an impacted machine a bit of a pain to know if the test is right 23:32 * gmaxwell goes to update his debian testing system to see if it breaks. 23:33 < jonasschnelli> But I guess we also need fixing in crypto_tests.cpp (OldEncrypt()) in the non-libsecp256k1 part of the code 23:33 < gmaxwell> Or we just drop those tests. 23:33 < jonasschnelli> Yeah 23:33 < luke-jr> Shouldn't --enable-openssl-tests=no still work if passed to Core's configure, even if it shows a warning? 23:34 < gmaxwell> at least that one can be fixed though, the struct is made opaque and can be constructed on the heap with EVP_MD_CTX_create. 23:34 < luke-jr> (I agree it makes sense to remove them, but as a stop-gap fix for users until the new version) 23:36 < gmaxwell> well we should fix this now for 0.13.2 too. 23:36 < gmaxwell> I find it a bit absurd that debian continually ships massively out of date software but then just changes openssl's API in a stable release willynilly. 23:41 < TD-Linux> gmaxwell, well it looks like that affects stretch and jessie is the one with out of date software.... 23:42 < gmaxwell> welp. doesn't reproduce on streach for me. :-/ 23:45 < gmaxwell> (not in bitcoind compile, nor libsecp256k1 compile.) 23:45 < aj> gmaxwell: libssl1.1-dev installed? 23:47 < gmaxwell> aj: thanks, that broke it! interesting that update/upgrade didn't pull that in. 23:53 < aj> gmaxwell: or apparently just libssl-dev now. there's openssl1.0 and libssl1.0-dev for testing now by the looks so it might have helpfully upgraded to let you keep developing against the 1.0 api... 23:54 < gmaxwell> explains why we've only had ~two reports so far. 23:59 < gmaxwell> https://github.com/bitcoin-core/secp256k1/pull/433 okay thats the libsecp256k1 part, I'll go do the bitcoin-core part.