--- Day changed Fri Sep 22 2017 00:11 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 00:15 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 00:16 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 00:17 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 00:17 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 00:17 -!- ThomasV [~thomasv@unaffiliated/thomasv] has joined #bitcoin-core-dev 00:18 -!- paveljanik [~paveljani@unaffiliated/paveljanik] has quit [Quit: Leaving] 00:19 -!- Ruben [~RubenSoms@1.217.138.142] has joined #bitcoin-core-dev 00:21 -!- RubenSomsen [~RubenSoms@1.217.138.142] has quit [Ping timeout: 248 seconds] 00:22 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 00:22 -!- JackH [~laptop@46.231.18.66] has joined #bitcoin-core-dev 00:25 -!- timothy [~tredaelli@redhat/timothy] has joined #bitcoin-core-dev 00:34 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 00:35 -!- Ruben [~RubenSoms@1.217.138.142] has quit [Ping timeout: 240 seconds] 00:42 -!- pbase [~pbase@unaffiliated/pbase] has joined #bitcoin-core-dev 00:43 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has joined #bitcoin-core-dev 00:52 -!- dcousens [~anon@c110-22-219-15.sunsh4.vic.optusnet.com.au] has quit [Ping timeout: 240 seconds] 00:59 -!- laurentmt [~Thunderbi@92.154.68.134] has joined #bitcoin-core-dev 00:59 < sipa> question: how to deal with existing tests that use getnewaddress/sendtoaddress? they often don't work without modification, as spends from segwit outputs don't work before segwit activates (in block 432 on regtest) 00:59 < sipa> 1) force all tests to stick with legacy addresses 01:00 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Read error: Connection reset by peer] 01:00 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Read error: Connection reset by peer] 01:00 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has quit [Read error: Connection reset by peer] 01:00 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Write error: Connection reset by peer] 01:01 < sipa> 2) make getnewaddress etc fall back to legacy addresses before segwit activation (but that's not something you want on mainnet, as it could lead to accidentally creating a legacy address if you're too fast 01:02 < sipa> 3) have an cmdline argument to make segwit activate from genesis in regtest (which would be on by default, excepr for tests that actually test the transition) 01:04 < sipa> 4) use -prematurewitness liberally, for cases where it's only wallet logic that is being tested (not validation/consensus) 01:04 -!- tripleslash [~triplesla@unaffiliated/imsaguy] has quit [Read error: Connection reset by peer] 01:04 -!- asoltys [~adam@115.96.198.104.bc.googleusercontent.com] has quit [Ping timeout: 240 seconds] 01:04 -!- [b__b] [~b__b]@ec2-54-85-45-223.compute-1.amazonaws.com] has quit [Remote host closed the connection] 01:04 -!- timothy [~tredaelli@redhat/timothy] has quit [Remote host closed the connection] 01:05 -!- spinza [~spin@196.212.164.26] has quit [Ping timeout: 240 seconds] 01:05 -!- eck [~eck@fsf/member/eck] has quit [Ping timeout: 240 seconds] 01:05 -!- [b__b] [~b__b]@ec2-54-85-45-223.compute-1.amazonaws.com] has joined #bitcoin-core-dev 01:05 -!- timothy [~tredaelli@redhat/timothy] has joined #bitcoin-core-dev 01:05 -!- tripleslash [~triplesla@unaffiliated/imsaguy] has joined #bitcoin-core-dev 01:06 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has joined #bitcoin-core-dev 01:06 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-dev 01:06 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 01:06 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #bitcoin-core-dev 01:07 -!- asoltys [~adam@115.96.198.104.bc.googleusercontent.com] has joined #bitcoin-core-dev 01:07 < sipa> 5) adapt all tests to mine enough blocks up front (but that's a lot of changes... getbalance calls everywhere) 01:08 -!- phantomcircuit [~phantomci@192.241.205.97] has quit [Ping timeout: 255 seconds] 01:09 -!- victorSN [~victorSN@ec2-52-14-222-162.us-east-2.compute.amazonaws.com] has quit [Ping timeout: 240 seconds] 01:10 -!- eck [~eck@fsf/member/eck] has joined #bitcoin-core-dev 01:11 -!- spinza [~spin@196.212.164.26] has joined #bitcoin-core-dev 01:12 -!- phantomcircuit [~phantomci@192.241.205.97] has joined #bitcoin-core-dev 01:13 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has quit [Ping timeout: 248 seconds] 01:16 -!- JackH [~laptop@46.231.18.66] has quit [Read error: Connection reset by peer] 01:17 -!- JackH [~laptop@46.231.18.66] has joined #bitcoin-core-dev 01:19 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has joined #bitcoin-core-dev 01:22 -!- victorSN [~victorSN@ec2-52-14-222-162.us-east-2.compute.amazonaws.com] has joined #bitcoin-core-dev 01:34 -!- vicenteH [~user@195.235.96.150] has joined #bitcoin-core-dev 01:35 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has quit [Ping timeout: 248 seconds] 01:47 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-vtzjkywyzxbosxpa] has quit [Quit: Connection closed for inactivity] 01:53 -!- Evel-Knievel [~Evel-Knie@178-119-237-211.access.telenet.be] has quit [] 02:02 < jl2012> sipa: I think 3) is the best, as it could also show all existing tests pass with the segwit getnewaddress 02:03 < bitcoin-git> [bitcoin] MarcoFalke closed pull request #11343: added `-walletallowsymboliclink` (default false) (0.15...wallet-allow-symbolic-link) https://github.com/bitcoin/bitcoin/pull/11343 02:04 < meshcollider> I agree, 2 is quite nice in theory but I think 3 is best practically 02:06 -!- Evel-Knievel [~Evel-Knie@178-119-237-211.access.telenet.be] has joined #bitcoin-core-dev 02:07 < MarcoFalke> 5 is an ugly workaround, lets not do that. 02:19 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has quit [] 02:19 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has joined #bitcoin-core-dev 02:26 -!- Geoffy [~Geo@178-119-187-213.access.telenet.be] has joined #bitcoin-core-dev 02:35 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has joined #bitcoin-core-dev 02:46 < gmaxwell> 5 is strictly worse than 3. I like 3. technically we could make mainnet activate segwit at the same time as p2sh, which would also result in regtest being born-segwit... but it would break transistion tests. 02:47 < gmaxwell> I don't really think we need transition tests anymore, but they're probably also incidentally testing other useful things so probably not great to just drop them. 02:53 -!- niska [~niska@68.ip-149-56-14.net] has quit [Quit: Leaving] 02:57 -!- jtimon [~quassel@199.31.134.37.dynamic.jazztel.es] has joined #bitcoin-core-dev 02:57 -!- niska [~niska@68.ip-149-56-14.net] has joined #bitcoin-core-dev 02:58 -!- ThomasV [~thomasv@unaffiliated/thomasv] has quit [Ping timeout: 248 seconds] 03:12 -!- StopAndDecrypt_ [~StopAndDe@142.75.255.199] has quit [] 03:16 -!- StopAndDecrypt_ [~StopAndDe@142.75.255.199] has joined #bitcoin-core-dev 03:24 -!- ThomasV [~thomasv@unaffiliated/thomasv] has joined #bitcoin-core-dev 03:28 -!- Sentineo [~Undefined@unaffiliated/sentineo] has quit [Ping timeout: 240 seconds] 03:29 -!- Shaun3811 [~shaun@93.109.214.154] has joined #bitcoin-core-dev 03:35 -!- Sentineo [~Undefined@node.ispol.sk] has joined #bitcoin-core-dev 04:04 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 04:07 -!- ThomasV [~thomasv@unaffiliated/thomasv] has quit [Ping timeout: 264 seconds] 04:16 -!- Sentineo [~Undefined@node.ispol.sk] has quit [Changing host] 04:16 -!- Sentineo [~Undefined@unaffiliated/sentineo] has joined #bitcoin-core-dev 04:18 -!- adiabat [~adiabat@45.63.20.152] has quit [Ping timeout: 240 seconds] 04:26 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 04:30 -!- ThomasV [~thomasv@unaffiliated/thomasv] has joined #bitcoin-core-dev 04:30 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 04:32 < bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/6c4fecfaf7be...390771be6276 04:32 < bitcoin-git> bitcoin/master 6951a1c MeshCollider: Remove extremely outdated share/certs dir 04:32 < bitcoin-git> bitcoin/master 390771b Wladimir J. van der Laan: Merge #11380: Remove outdated share/certs/ directory... 04:32 < bitcoin-git> [bitcoin] laanwj closed pull request #11380: Remove outdated share/certs/ directory (master...201709_remove_old_certs) https://github.com/bitcoin/bitcoin/pull/11380 04:34 < bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/390771be6276...94c9015bca86 04:34 < bitcoin-git> bitcoin/master 46c9043 Pieter Wuille: Remove some unused functions and methods... 04:34 < bitcoin-git> bitcoin/master 94c9015 Wladimir J. van der Laan: Merge #11385: Remove some unused functions and methods... 04:34 < bitcoin-git> [bitcoin] laanwj closed pull request #11385: Remove some unused functions and methods (master...201709_misc_cleanups) https://github.com/bitcoin/bitcoin/pull/11385 04:39 < wumpus> it's kind of sad that we never merged #9937 and no one followed up on it 04:39 < gribble> https://github.com/bitcoin/bitcoin/issues/9937 | rpc: Prevent `dumpwallet` from overwriting files by laanwj · Pull Request #9937 · bitcoin/bitcoin · GitHub 04:40 < wumpus> thinking about it, I don't really think "The change as written now allows to test the existence of any file." is a concern that should have prevented it from being merged, it's much better than being able to overwrite every file 04:44 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 04:45 < bitcoin-git> [bitcoin] laanwj reopened pull request #9937: rpc: Prevent `dumpwallet` from overwriting files (master...2017_03_walletdump_nooverwrite) https://github.com/bitcoin/bitcoin/pull/9937 04:45 -!- dcousens [~anon@c110-22-219-15.sunsh4.vic.optusnet.com.au] has joined #bitcoin-core-dev 04:54 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 05:07 -!- pbase [~pbase@unaffiliated/pbase] has quit [Read error: Connection reset by peer] 05:08 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 05:10 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 05:11 < morcos> sipa: i'm in favor of 3 or even just dumping transition tests entirely. i know sdaftuar was looking at these for his attempts to have segwit active earlier, we should get his opinion 05:12 -!- ThomasV [~thomasv@unaffiliated/thomasv] has quit [Ping timeout: 240 seconds] 05:15 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Ping timeout: 260 seconds] 05:20 -!- dcousens [~anon@c110-22-219-15.sunsh4.vic.optusnet.com.au] has quit [Ping timeout: 260 seconds] 05:21 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 05:23 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has quit [Remote host closed the connection] 05:24 -!- Miezel [~Miezel@64-83-208-26.static.stcd.mn.charter.com] has joined #bitcoin-core-dev 05:24 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has joined #bitcoin-core-dev 05:28 < sdaftuar> sipa: i agree with 3) as the best idea for now. 05:29 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has quit [Remote host closed the connection] 05:30 < sdaftuar> gmaxwell: sipa: i was experimenting with moving segwit activation back to p2sh activation for mainnet, to see how much code simplification we could get 05:30 < sdaftuar> it ended up being a lot messier than i thought and i got a little stuck on that project-- 05:31 < sdaftuar> moving SCRIPT_VERIFY_WITNESS enforcement back is a straightforward change, but the rules around witness commitments in the coinbase are not really changeable, as far as i can tell 05:31 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has joined #bitcoin-core-dev 05:32 < sdaftuar> the simplest example -- pre-segwit, someone mines a block with a witness commitment that commits to the transactions all not having a witness -- doesn't validate, because checking the commitment 05:33 < sdaftuar> requires checking the witness nonce, which is not present 05:33 < sdaftuar> never mind if there are blocks which have an incorrect commitment (pre-activation) -- i assume those exist too 05:34 < sdaftuar> so i was left wondering if it was worth splitting segwit activation into two parts -- one where witness commitments are only checked at some height, but SCRIPT_VERIFY_WITNESS is enforced eg from genesis 05:34 < sdaftuar> and my instinct was that was only complicating things, and not simplifying 05:34 < sdaftuar> but i'd be interested in others' opinions 05:35 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has quit [Remote host closed the connection] 05:37 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has joined #bitcoin-core-dev 05:37 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has quit [Remote host closed the connection] 05:38 -!- veleiro [~sleeper@fsf/member/veleiro] has joined #bitcoin-core-dev 05:38 -!- veleiro [~sleeper@fsf/member/veleiro] has left #bitcoin-core-dev [] 05:54 -!- veleiro [~sleeper@fsf/member/veleiro] has joined #bitcoin-core-dev 05:55 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 06:07 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has joined #bitcoin-core-dev 06:39 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has quit [] 06:43 -!- sdfgsdfg [~sdfgsdfg@unaffiliated/sdfgsdfg] has quit [Ping timeout: 248 seconds] 06:45 -!- Miezel [~Miezel@64-83-208-26.static.stcd.mn.charter.com] has quit [Quit: This computer has gone to sleep] 06:48 -!- veleiro [~sleeper@fsf/member/veleiro] has quit [Quit: Leaving.] 06:55 < jnewbery> sdaftuar: I think it's still worthwhile, even if you need to split SCRIPT_VERIFY_WITNESS enforcement from witness commitment verification. We could then change SCRIPT_VERIFY_WITNES activation height on regtest to 0 and remove all the transition tests (except one test for verifying that witness commitment verification is not enforced before witness commitment verification height) 06:56 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-zpyebmccyobsxhbm] has quit [Quit: Connection closed for inactivity] 06:57 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 06:58 -!- ThomasV [~thomasv@unaffiliated/thomasv] has joined #bitcoin-core-dev 06:58 < jnewbery> sipa: (3) is best for now. It'd be nice to eventually dump most transition tests if possible 06:58 -!- promag [~promag@bl6-24-70.dsl.telepac.pt] has joined #bitcoin-core-dev 07:02 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 264 seconds] 07:07 -!- lifeofguenter [~lifeofgue@bnc.pro.to.co.ls] has quit [Ping timeout: 258 seconds] 07:13 -!- lifeofguenter [~lifeofgue@bnc.pro.to.co.ls] has joined #bitcoin-core-dev 07:20 -!- jtimon [~quassel@199.31.134.37.dynamic.jazztel.es] has quit [Ping timeout: 240 seconds] 07:30 -!- promag [~promag@bl6-24-70.dsl.telepac.pt] has quit [Remote host closed the connection] 07:30 -!- alreadylate [~textual@m77-218-242-44.cust.tele2.se] has joined #bitcoin-core-dev 07:30 -!- promag [~promag@bl6-24-70.dsl.telepac.pt] has joined #bitcoin-core-dev 07:32 -!- veleiro [~sleeper@fsf/member/veleiro] has joined #bitcoin-core-dev 07:36 -!- veleiro [~sleeper@fsf/member/veleiro] has quit [Ping timeout: 240 seconds] 07:38 -!- promag [~promag@bl6-24-70.dsl.telepac.pt] has quit [Remote host closed the connection] 07:42 -!- promag [~promag@bl6-24-70.dsl.telepac.pt] has joined #bitcoin-core-dev 07:44 -!- promag [~promag@bl6-24-70.dsl.telepac.pt] has quit [Remote host closed the connection] 07:47 -!- promag [~promag@bl6-24-70.dsl.telepac.pt] has joined #bitcoin-core-dev 07:57 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 08:13 -!- newbie is now known as newbie-- 08:15 < instagibbs> how would people feel about removing mempoolreplacement arg? There's no tests, and I have yet to hear a reason to not allow it.(or people setting it to off) 08:23 -!- JackH [~laptop@46.231.18.66] has quit [Quit: Leaving] 08:27 -!- promag [~promag@bl6-24-70.dsl.telepac.pt] has quit [Remote host closed the connection] 08:29 < jonasschnelli> wumpus: Oh. I completely forgot #9937. We should have merged it, yes. 08:29 < gribble> https://github.com/bitcoin/bitcoin/issues/9937 | rpc: Prevent `dumpwallet` from overwriting files by laanwj · Pull Request #9937 · bitcoin/bitcoin · GitHub 08:30 < Sentineo> /window 3 08:33 -!- RubenSomsen [~RubenSoms@1.217.138.142] has joined #bitcoin-core-dev 08:38 < jnewbery> luke-jr: I'm looking at #11383 (nice work btw!). I don't understand the comment about it requiring #10615. It looks like they're basically orthogonal (except a bit of overlap in the RPC console). I think it'll probably aid review if you separate them out so there's no cross-dependency. 08:38 < gribble> https://github.com/bitcoin/bitcoin/issues/11383 | Basic Multiwallet GUI support by luke-jr · Pull Request #11383 · bitcoin/bitcoin · GitHub 08:38 < gribble> https://github.com/bitcoin/bitcoin/issues/10615 | RPC: Allow rpcauth configs to specify a 4th parameter naming a specific wallet (multiwallet RPC support) by luke-jr · Pull Request #10615 · bitcoin/bitcoin · GitHub 08:41 -!- promag [~promag@bl6-24-70.dsl.telepac.pt] has joined #bitcoin-core-dev 08:47 -!- adiabat [~adiabat@45.63.20.152] has joined #bitcoin-core-dev 08:48 -!- Murch [~murch@96-82-80-28-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev 08:51 -!- promag [~promag@bl6-24-70.dsl.telepac.pt] has quit [Remote host closed the connection] 09:00 -!- alreadylate [~textual@m77-218-242-44.cust.tele2.se] has quit [] 09:02 -!- ThomasV [~thomasv@unaffiliated/thomasv] has quit [Ping timeout: 246 seconds] 09:07 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Remote host closed the connection] 09:10 -!- ThomasV [~thomasv@unaffiliated/thomasv] has joined #bitcoin-core-dev 09:18 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Ping timeout: 252 seconds] 09:21 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #bitcoin-core-dev 09:31 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 09:43 < luke-jr> jnewbery: 10615 has the commit resolving the wallet for RPC earlier, so GUI can assign it 09:48 -!- laurentmt [~Thunderbi@92.154.68.134] has quit [Quit: laurentmt] 09:50 -!- ThomasV [~thomasv@unaffiliated/thomasv] has quit [Ping timeout: 260 seconds] 09:52 -!- ThomasV [~thomasv@unaffiliated/thomasv] has joined #bitcoin-core-dev 09:56 -!- abpa [~abpa@96-82-80-28-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev 09:59 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 246 seconds] 10:07 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 10:10 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-wsbbxjnvwkxnbpkr] has joined #bitcoin-core-dev 10:12 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 10:17 -!- timothy [~tredaelli@redhat/timothy] has quit [Quit: Konversation terminated!] 10:17 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 10:20 -!- Giszmo [~leo@pc-204-28-214-201.cm.vtr.net] has quit [Ping timeout: 248 seconds] 10:20 -!- Alina-malina [~Alina-mal@unaffiliated/alina-malina] has quit [Ping timeout: 240 seconds] 10:21 -!- Giszmo [~leo@pc-204-28-214-201.cm.vtr.net] has joined #bitcoin-core-dev 10:21 < jnewbery> luke-jr : That's only used for the RPC console. If I just cherry-pick all the commits apart from that, then it works fine without 10615. There are still several outstanding concerns in 10615, so I think it makes sense to separate the two PRs and allow them to be reviewed separately 10:30 -!- Alina-malina [~Alina-mal@37.157.223.81] has joined #bitcoin-core-dev 10:32 -!- ThomasV [~thomasv@unaffiliated/thomasv] has quit [Ping timeout: 252 seconds] 10:34 -!- Alina-malina [~Alina-mal@37.157.223.81] has quit [Changing host] 10:34 -!- Alina-malina [~Alina-mal@unaffiliated/alina-malina] has joined #bitcoin-core-dev 10:35 -!- ula [~kvirc@b2b-78-94-9-226.unitymedia.biz] has joined #bitcoin-core-dev 10:38 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 10:38 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 10:38 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 10:40 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has joined #bitcoin-core-dev 10:40 -!- laurentmt [~Thunderbi@176.158.157.202] has joined #bitcoin-core-dev 10:43 -!- Emcy [~MC@unaffiliated/emcy] has joined #bitcoin-core-dev 10:45 -!- Emcy_ [~MC@unaffiliated/emcy] has quit [Ping timeout: 248 seconds] 10:55 -!- abpa [~abpa@96-82-80-28-static.hfc.comcastbusiness.net] has quit [Read error: Connection reset by peer] 10:59 -!- vicenteH [~user@195.235.96.150] has quit [Ping timeout: 255 seconds] 11:04 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has quit [] 11:12 -!- Emcy_ [~MC@unaffiliated/emcy] has joined #bitcoin-core-dev 11:14 -!- Emcy [~MC@unaffiliated/emcy] has quit [Ping timeout: 240 seconds] 11:15 -!- Emcy [~MC@unaffiliated/emcy] has joined #bitcoin-core-dev 11:17 -!- Emcy_ [~MC@unaffiliated/emcy] has quit [Ping timeout: 264 seconds] 11:23 < luke-jr> jnewbery: it should be used by WalletModel too (although maybe it isn't yet) 11:23 < luke-jr> (pretty sure it is tho) 11:35 -!- Emcy_ [~MC@unaffiliated/emcy] has joined #bitcoin-core-dev 11:37 -!- Emcy [~MC@unaffiliated/emcy] has quit [Ping timeout: 240 seconds] 11:46 -!- Emcy [~MC@unaffiliated/emcy] has joined #bitcoin-core-dev 11:48 < achow101> .... wow. I managed to get bitcoin 0.1.0 to start syncing off of Core 0.15.99 11:48 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has joined #bitcoin-core-dev 11:49 -!- Emcy_ [~MC@unaffiliated/emcy] has quit [Ping timeout: 240 seconds] 11:49 < sipa> achow101: i assume you needed to patch 0.1.0 a bit? 11:50 < achow101> sipa: I patched Core to speak 0.1.0 11:50 < achow101> and apparently bitcoin.org's docs are wrong 11:50 < sipa> fix them! 11:50 < achow101> I will 11:53 -!- ThomasV [~thomasv@unaffiliated/thomasv] has joined #bitcoin-core-dev 11:53 < sipa> morcos: perhaps you can answer https://bitcoin.stackexchange.com/questions/59854/where-are-the-new-smart-fee-estimate-data-saved-can-the-file-be-re-used 11:59 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 12:06 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Ping timeout: 255 seconds] 12:07 -!- jtimon [~quassel@199.31.134.37.dynamic.jazztel.es] has joined #bitcoin-core-dev 12:08 < morcos> sipa: ok done 12:08 < achow101> are coinbase transactions supposed to have witnesses? 12:09 < achow101> I'm seeing coinbase transactions with witness fields of 32 bytes of 0's 12:09 < achow101> *1 stack item of 32 bytes of 0's 12:09 < sipa> achow101: yes 12:09 < sipa> achow101: they're a field intended for extensibility 12:10 < achow101> sipa: oh, ok. I don't see that in the BIPs though.. 12:10 < achow101> oh, nvm. found it in bip 141 12:10 -!- RubenSomsen [~RubenSoms@1.217.138.142] has quit [Ping timeout: 252 seconds] 12:10 < sipa> it's called 'witness reserved value' in the bip 12:11 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has quit [] 12:18 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has quit [Remote host closed the connection] 12:18 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has joined #bitcoin-core-dev 12:22 -!- Emcy_ [~MC@unaffiliated/emcy] has joined #bitcoin-core-dev 12:22 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #bitcoin-core-dev 12:24 -!- Emcy [~MC@unaffiliated/emcy] has quit [Ping timeout: 248 seconds] 12:26 -!- thomas__ [4d99f87f@gateway/web/freenode/ip.77.153.248.127] has joined #bitcoin-core-dev 12:27 < thomas__> Hey guys, new here. Does someone have to work on windows and has a good workflow set up ? 12:28 < sipa> a good workflow for what? 12:28 < thomas__> to dev 12:30 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 12:31 < thomas__> I'll be rebuilding a lot this weekend to see how things work, if someone has a way to make it less painful I'd like to hear from him ^^ 12:32 < achow101> thomas__: use linux and read the Bitcoin Core docs 12:33 < thomas__> damit, everyone has the same answer. I have an ubuntu set up on my computer, but I also have to do stuff on windows. I don't see myself switching 3 times a day between both. 12:33 < achow101> thomas__: then use a VM 12:33 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 264 seconds] 12:33 < achow101> developing things is infintely easier to do in a *nix environment than windows 12:33 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 12:33 < sipa> how well does bash-on-windows work these days? 12:34 < achow101> sipa: pretty well, but AFAIK, no gui support 12:34 < thomas__> the wsl works if you keep all your file on the linux side 12:34 < achow101> i.e. can't run bitcoin-qt 12:35 < thomas__> I'm cross compiling right now, I'll know after that 12:35 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has joined #bitcoin-core-dev 12:35 < achow101> thomas__: I suppose you could use wsl and cross compile. note that cross compiling with ubuntu 15.10+ (wsl uses ubuntu 16.04) is a bit flaky 12:35 -!- Emcy [~MC@unaffiliated/emcy] has joined #bitcoin-core-dev 12:37 < thomas__> Apparently mine uses: Description: Ubuntu 14.04.5 LTS 12:37 < thomas__> So should be ok then 12:38 < bitcoin-git> [bitcoin] runn1ng opened pull request #11386: RPC: Consistently use UniValue.pushKV instead of push_back(Pair()) (master...univalue_bikeshed) https://github.com/bitcoin/bitcoin/pull/11386 12:38 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Ping timeout: 240 seconds] 12:38 -!- Emcy_ [~MC@unaffiliated/emcy] has quit [Ping timeout: 252 seconds] 12:42 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #bitcoin-core-dev 12:53 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Ping timeout: 248 seconds] 12:55 -!- Emcy_ [~MC@unaffiliated/emcy] has joined #bitcoin-core-dev 12:57 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #bitcoin-core-dev 12:57 -!- Emcy [~MC@unaffiliated/emcy] has quit [Ping timeout: 240 seconds] 13:03 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Ping timeout: 252 seconds] 13:07 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has quit [] 13:12 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has joined #bitcoin-core-dev 13:12 < achow101> with old versions of bitcoin (e.g. 0.1.0), what happens if they receive blocks out of order? 13:14 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has quit [Client Quit] 13:16 -!- vicenteH [~user@93.104.135.37.dynamic.jazztel.es] has joined #bitcoin-core-dev 13:17 < sipa> achow101: stored as orphans in memory until the parent is fetched 13:18 < sipa> at some point we limited the size of the orphan block pool, which resulted in the same blocks being fetched over and over again 13:18 -!- Emcy [~MC@unaffiliated/emcy] has joined #bitcoin-core-dev 13:18 < sipa> until headers-sync in 0.10 13:21 -!- Emcy_ [~MC@unaffiliated/emcy] has quit [Ping timeout: 240 seconds] 13:25 -!- laurentmt [~Thunderbi@176.158.157.202] has quit [Quit: laurentmt] 13:26 -!- ossifrage [~ossifrage@unaffiliated/ossifrage] has quit [Ping timeout: 246 seconds] 13:27 -!- Emcy_ [~MC@unaffiliated/emcy] has joined #bitcoin-core-dev 13:30 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #bitcoin-core-dev 13:30 -!- Emcy [~MC@unaffiliated/emcy] has quit [Ping timeout: 240 seconds] 13:32 < esotericnonsense> thomas__: if you haven't spent much time working in VM's I'd really recommend it. on modern hardware it's a treat. 13:32 < thomas__> A few years ago a lot of people were bitching about it and so I never took the time to really try 13:32 * esotericnonsense is pleased to see virgl slowly working its way into kvm 13:34 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 13:35 -!- darkROL [~Mutter@181.33.6.176] has joined #bitcoin-core-dev 13:35 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Ping timeout: 240 seconds] 13:38 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Ping timeout: 240 seconds] 13:38 -!- Emcy [~MC@unaffiliated/emcy] has joined #bitcoin-core-dev 13:41 -!- Emcy_ [~MC@unaffiliated/emcy] has quit [Ping timeout: 255 seconds] 13:47 -!- abpa [~abpa@96-82-80-28-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev 13:48 -!- darkROL [~Mutter@181.33.6.176] has quit [Quit: Mutter: www.mutterirc.com] 13:50 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #bitcoin-core-dev 13:50 < jonasschnelli> Should we tolerate lost GUI window positions in 0.16 (the window will recenter in 0.16 when merging #11335) 13:50 < gribble> https://github.com/bitcoin/bitcoin/issues/11335 | Replace save|restoreWindowGeometry with Qt functions by MeshCollider · Pull Request #11335 · bitcoin/bitcoin · GitHub 13:52 -!- laurentmt [~Thunderbi@176.158.157.202] has joined #bitcoin-core-dev 13:56 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Ping timeout: 260 seconds] 13:57 -!- danra [0566c489@gateway/web/freenode/ip.5.102.196.137] has joined #bitcoin-core-dev 13:58 -!- laurentmt [~Thunderbi@176.158.157.202] has quit [Quit: laurentmt] 14:03 -!- Emcy_ [~MC@unaffiliated/emcy] has joined #bitcoin-core-dev 14:05 -!- Emcy [~MC@unaffiliated/emcy] has quit [Ping timeout: 240 seconds] 14:05 -!- ThomasV [~thomasv@unaffiliated/thomasv] has quit [Ping timeout: 252 seconds] 14:10 -!- Sinclair6 [~sinclair6@gateway/vpn/privateinternetaccess/sinclair6] has joined #bitcoin-core-dev 14:12 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has quit [Quit: Going offline, see ya! (www.adiirc.com)] 14:22 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 14:22 * luke-jr ponders if BIP editor should be enabled to fix spelling/grammar without going through the author 14:26 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 14:27 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #bitcoin-core-dev 14:33 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Ping timeout: 240 seconds] 14:42 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 240 seconds] 14:43 -!- Emcy [~MC@unaffiliated/emcy] has joined #bitcoin-core-dev 14:45 -!- Emcy_ [~MC@unaffiliated/emcy] has quit [Ping timeout: 252 seconds] 14:50 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #bitcoin-core-dev 14:56 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 14:59 -!- danra [0566c489@gateway/web/freenode/ip.5.102.196.137] has quit [Quit: Page closed] 15:02 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 15:02 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection] 15:02 -!- Emcy_ [~MC@unaffiliated/emcy] has joined #bitcoin-core-dev 15:02 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 15:04 -!- Emcy [~MC@unaffiliated/emcy] has quit [Ping timeout: 260 seconds] 15:05 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 252 seconds] 15:07 -!- Miezel [~Miezel@64-83-208-26.static.stcd.mn.charter.com] has joined #bitcoin-core-dev 15:09 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Ping timeout: 240 seconds] 15:15 -!- thomas__ [4d99f87f@gateway/web/freenode/ip.77.153.248.127] has quit [Ping timeout: 260 seconds] 15:18 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 15:23 -!- fengling_ [~fengling@2400:8901::f03c:91ff:fe61:b65c] has quit [Ping timeout: 240 seconds] 15:24 -!- fengling_ [~fengling@2400:8901::f03c:91ff:fe61:b65c] has joined #bitcoin-core-dev 15:25 -!- chjj [~chjj@unaffiliated/chjj] has joined #bitcoin-core-dev 15:27 -!- ossifrage [~ossifrage@pool-98-114-91-222.phlapa.fios.verizon.net] has joined #bitcoin-core-dev 15:27 -!- ossifrage [~ossifrage@pool-98-114-91-222.phlapa.fios.verizon.net] has quit [Changing host] 15:27 -!- ossifrage [~ossifrage@unaffiliated/ossifrage] has joined #bitcoin-core-dev 15:27 < ossifrage> That is really annoying chrome decided to eat up all the memory, but the oom killer took out bitcoin (while doing a reindex) and somehow the progress went from 99ish% to 85%, that is quite a bit of rollback 15:31 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 240 seconds] 15:31 < esotericnonsense> ossifrage: how long does the entire reindex take? if it's the same mechanism as during IBD then with a high dbcache value it's just every N minutes/hours (don't remember the figure) 15:32 < esotericnonsense> (sorry, that's a flush happening every N minutes/hours) 15:33 < gmaxwell> ossifrage: it'll rollback to the last flush. In the future we'll hopefully switch to more incremental flushing which will roll back less far in the event of a crash during initial sync. 15:34 < ossifrage> gmaxwell, I had a 4G dbcache which was part of the reason the oom killer picked on bitcoin 15:34 < esotericnonsense> static const unsigned int DATABASE_FLUSH_INTERVAL = 24 * 60 * 60; 15:34 < esotericnonsense> O_o 15:34 < gmaxwell> I wish linux mem handling had a "shrink now or you're gonna get killed" signal. 15:35 < gmaxwell> esotericnonsense: that means it'll force a flush once a day if it hasn't been triggered by the cache filling. 15:35 < gmaxwell> during IBD cache filling triggers the flushes. 15:35 -!- To7 [~theo@2604:2000:1382:b7:5d67:ff32:8632:e814] has joined #bitcoin-core-dev 15:36 < ossifrage> esotericnonsense, I am generating the full tx index (txindex=1) and it is taking a very long time [I'm not sure when I started it, the debug.log got truncated] 15:36 < ossifrage> >24 hours ago 15:37 < gmaxwell> >24 hours with a 4gb dbcache. damn txindex. 15:37 < esotericnonsense> think my laptop was sub 24hours when I did it and it's not super-fast or anything. though that was syncing over LAN rather than reindex. 15:38 < esotericnonsense> (with txindex on). 15:38 < esotericnonsense> is that on a HDD? 15:38 < ossifrage> gmaxwell, it doesn't seem to be IO or CPU bound, but I am using spinning rust, it seemed wasteful to eat up a large % of my ssd on bitcoin 15:38 < esotericnonsense> ah yeah. 15:40 < gmaxwell> ossifrage: with a large dbcache it doesn't matter if you're on a SSD or rust when txindex is not in use, alas... 15:40 < ossifrage> If I turn txindex off, do I have to start over again when I turn it back on? 15:43 < ossifrage> The last log entry was 96% with a 2446MB dbcache and it rolled back to 84% (my memory of almost done was faulty) 15:46 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 15:50 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Ping timeout: 240 seconds] 16:06 < bitcoin-git> [bitcoin] sipa pushed 3 new commits to master: https://github.com/bitcoin/bitcoin/compare/94c9015bca86...877678710800 16:06 < bitcoin-git> bitcoin/master 6059182 Marko Bencun: add m_added_nodes to connman options 16:06 < bitcoin-git> bitcoin/master 35e5c22 Marko Bencun: remove unused IsArgSet check... 16:06 < bitcoin-git> bitcoin/master 8776787 Pieter Wuille: Merge #11301: add m_added_nodes to connman options... 16:07 < bitcoin-git> [bitcoin] sipa closed pull request #11301: add m_added_nodes to connman options (master...addnode) https://github.com/bitcoin/bitcoin/pull/11301 16:07 < esotericnonsense> ossifrage: if you have enough log, you can go back and find the time when dbcache reset, that will be the last flush probably at 84%. 16:09 < bitcoin-git> [bitcoin] sipa pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/877678710800...c6223b3daab0 16:09 < bitcoin-git> bitcoin/master 22fd04b Gregory Maxwell: Remove nBlockMaxSize from miner opt struct as it is no longer used. 16:09 < bitcoin-git> bitcoin/master c6223b3 Pieter Wuille: Merge #11362: Remove nBlockMaxSize from miner opt struct as it is no longer used.... 16:10 < bitcoin-git> [bitcoin] sipa closed pull request #11362: Remove nBlockMaxSize from miner opt struct as it is no longer used. (master...2017_09_rm_nBlockMaxSize) https://github.com/bitcoin/bitcoin/pull/11362 16:10 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-qzomvszelqprirlz] has joined #bitcoin-core-dev 16:12 -!- dcousens [~anon@c110-22-219-15.sunsh4.vic.optusnet.com.au] has joined #bitcoin-core-dev 16:16 < bitcoin-git> [bitcoin] theuni opened pull request #11387: net: remove more CConnman globals (master...more-connman-params) https://github.com/bitcoin/bitcoin/pull/11387 16:18 < bitcoin-git> [bitcoin] sipa pushed 3 new commits to master: https://github.com/bitcoin/bitcoin/compare/c6223b3daab0...aeed345c9bad 16:18 < bitcoin-git> bitcoin/master e912118 Johnson Lau: [Refactor] Combine scriptPubKey and amount as CTxOut in CScriptCheck 16:18 < bitcoin-git> bitcoin/master 3a131b7 Johnson Lau: Rename out to m_tx_out in CScriptCheck 16:18 < bitcoin-git> bitcoin/master aeed345 Pieter Wuille: Merge #10953: [Refactor] Combine scriptPubKey and amount as CTxOut in CScriptCheck... 16:18 < bitcoin-git> [bitcoin] sipa closed pull request #10953: [Refactor] Combine scriptPubKey and amount as CTxOut in CScriptCheck (master...combine_script_amount) https://github.com/bitcoin/bitcoin/pull/10953 16:35 -!- dcousens [~anon@c110-22-219-15.sunsh4.vic.optusnet.com.au] has quit [Ping timeout: 252 seconds] 16:41 -!- Emcy [~MC@unaffiliated/emcy] has joined #bitcoin-core-dev 16:43 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 16:43 -!- Miezel [~Miezel@64-83-208-26.static.stcd.mn.charter.com] has quit [Quit: This computer has gone to sleep] 16:44 -!- Emcy_ [~MC@unaffiliated/emcy] has quit [Ping timeout: 252 seconds] 16:46 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Read error: Connection reset by peer] 16:46 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 16:50 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Ping timeout: 248 seconds] 16:51 -!- Emcy_ [~MC@unaffiliated/emcy] has joined #bitcoin-core-dev 16:52 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev 16:52 -!- Emcy [~MC@unaffiliated/emcy] has quit [Ping timeout: 240 seconds] 17:00 -!- abpa [~abpa@96-82-80-28-static.hfc.comcastbusiness.net] has quit [Quit: Textual IRC Client: www.textualapp.com] 17:10 -!- Emcy [~MC@unaffiliated/emcy] has joined #bitcoin-core-dev 17:12 -!- Emcy_ [~MC@unaffiliated/emcy] has quit [Ping timeout: 248 seconds] 17:33 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 252 seconds] 17:39 < ossifrage> To my local 0.15.0, I added a command line option to specify the max upload timeframe to try and more evenly spread out the data spent serving old blocks. The 24 hour default results in overly spikey network traffic. 17:46 -!- Emcy_ [~MC@unaffiliated/emcy] has joined #bitcoin-core-dev 17:49 -!- Emcy [~MC@unaffiliated/emcy] has quit [Ping timeout: 240 seconds] 17:54 -!- Emcy [~MC@unaffiliated/emcy] has joined #bitcoin-core-dev 17:56 -!- Emcy_ [~MC@unaffiliated/emcy] has quit [Ping timeout: 252 seconds] 18:00 -!- Emcy_ [~MC@unaffiliated/emcy] has joined #bitcoin-core-dev 18:02 -!- Emcy [~MC@unaffiliated/emcy] has quit [Ping timeout: 240 seconds] 18:03 -!- Murch [~murch@96-82-80-28-static.hfc.comcastbusiness.net] has quit [Quit: Snoozing.] 18:03 -!- ShaunR [~ShaunR@freenode/sponsor/NDChost.com] has quit [Read error: Connection reset by peer] 18:08 -!- Emcy [~MC@unaffiliated/emcy] has joined #bitcoin-core-dev 18:10 -!- ThomasV [~thomasv@unaffiliated/thomasv] has joined #bitcoin-core-dev 18:10 -!- Emcy_ [~MC@unaffiliated/emcy] has quit [Ping timeout: 240 seconds] 18:16 -!- Emcy_ [~MC@unaffiliated/emcy] has joined #bitcoin-core-dev 18:19 -!- Emcy [~MC@unaffiliated/emcy] has quit [Ping timeout: 240 seconds] 18:20 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-qzomvszelqprirlz] has quit [Quit: Connection closed for inactivity] 18:20 -!- Aaronvan_ is now known as AaronvanW 18:50 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-wsbbxjnvwkxnbpkr] has quit [Quit: Connection closed for inactivity] 18:53 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection] 18:53 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 18:55 -!- RubenSomsen [~RubenSoms@1.217.138.142] has joined #bitcoin-core-dev 18:58 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 248 seconds] 18:59 -!- Emcy [~MC@unaffiliated/emcy] has joined #bitcoin-core-dev 19:00 -!- Geoffy [~Geo@178-119-187-213.access.telenet.be] has quit [] 19:00 -!- ThomasV_ [~thomasv@unaffiliated/thomasv] has joined #bitcoin-core-dev 19:01 -!- Emcy_ [~MC@unaffiliated/emcy] has quit [Ping timeout: 248 seconds] 19:04 -!- ThomasV [~thomasv@unaffiliated/thomasv] has quit [Ping timeout: 240 seconds] 19:08 -!- Emcy_ [~MC@unaffiliated/emcy] has joined #bitcoin-core-dev 19:11 -!- Emcy [~MC@unaffiliated/emcy] has quit [Ping timeout: 248 seconds] 19:21 -!- LUNA_ [519a3e67@gateway/web/freenode/ip.81.154.62.103] has joined #bitcoin-core-dev 19:22 -!- Miezel [~Miezel@64-83-208-26.static.stcd.mn.charter.com] has joined #bitcoin-core-dev 19:23 -!- Miezel [~Miezel@64-83-208-26.static.stcd.mn.charter.com] has quit [Client Quit] 19:25 -!- Miezel [~Miezel@64-83-208-26.static.stcd.mn.charter.com] has joined #bitcoin-core-dev 19:43 < jonasschnelli> sipa: re #11167, is it a problem that you can send to BIP173 addresses when IsWitness is diabled? "addwitnessaddress" rejects while sendtoaddress doesn't... I guess since it's active on mainnet this doesn't matter anymore? 19:43 < gribble> https://github.com/bitcoin/bitcoin/issues/11167 | Full BIP173 (Bech32) support by sipa · Pull Request #11167 · bitcoin/bitcoin · GitHub 19:51 < sipa> jonasschnelli: right 19:52 < sipa> it was there to prevent creating a segwit address (which could be stolen from) before it activated 19:52 < sipa> but it's complicated by the fact that many tests in regtest operate in a state where it is not active yet 19:52 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-jipesvevoygcwajj] has joined #bitcoin-core-dev 19:59 -!- ThomasV_ [~thomasv@unaffiliated/thomasv] has quit [Ping timeout: 260 seconds] 20:16 -!- Cory [~Cory@unaffiliated/cory] has quit [Ping timeout: 248 seconds] 20:19 -!- echonaut [~echonaut@46.101.192.134] has quit [Remote host closed the connection] 20:21 -!- echonaut [~echonaut@46.101.192.134] has joined #bitcoin-core-dev 20:21 < esotericnonsense> whee! 0.15.0.1 successfully compiled and running on my phone. 20:22 < achow101> esotericnonsense: ... why? 20:22 < esotericnonsense> achow101: because i can! 20:22 < achow101> bitcoind or bitcoin-qt? 20:22 < esotericnonsense> bitcoind 20:22 < esotericnonsense> i don't think it's ever going to sync 20:23 < achow101> esotericnonsense: I think it has a higher probability of syncing than my bitcoin 0.1.0 node does 20:24 < esotericnonsense> even the 2009 blocks are slow 20:24 < achow101> how slow? 20:24 < esotericnonsense> the log is truncated, hang on 20:25 < esotericnonsense> 1m15s from 2010-01-01 to 2010-04-01 (height 32490 -> 48298) 20:26 < goatpig> you in for a week at this rate 20:27 < achow101> esotericnonsense: started at 21:27:28 utc, currently at 1661 20:27 < esotericnonsense> unfortunately the actually-possibly-useful thing that it could be used for won't work; it would be fun to use it as a trusted node in schildbach's wallet 20:27 < achow101> granted it has crashed multiple times and the vm it is in has also crashed a few times 20:27 < esotericnonsense> but i am going to guess that they'd clash on the ports and neither side can be configured 20:27 < esotericnonsense> (also if it's pruned it won't connect either) 20:27 < esotericnonsense> achow101: lol. 20:28 < achow101> I don't think it's ever going to get anywhere near being in sync 20:29 < esotericnonsense> are there any issues with copying datadirs across architectures? endianness? other stuff? 20:29 < achow101> shouldn't be 20:29 < esotericnonsense> (I could produce a pruned datadir on my main box and chuck that over) 20:43 < sipa> achow101: i think it should be totally possible to sync 20:44 < sipa> i got abcore to sync with 0.13 on my oneplus one (woth 3 GB ram) 20:44 < sipa> on my nexus 5x now i haven't tried, as it only has 2 GB ram, but with 0.15 i think it should be possible 20:48 < achow101> sipa: I was talking about my 0.1.0 node 20:49 < sipa> oh, i missed that 21:10 -!- goatpig [56f75683@gateway/web/freenode/ip.86.247.86.131] has quit [Quit: Page closed] 21:37 < luke-jr> jonasschnelli: https://github.com/bitcoin/bips/pull/592 fix readme? 21:50 -!- jtimon [~quassel@199.31.134.37.dynamic.jazztel.es] has quit [Ping timeout: 246 seconds] 22:07 -!- jtimon [~quassel@199.31.134.37.dynamic.jazztel.es] has joined #bitcoin-core-dev 22:11 -!- owowo [~ovovo@unaffiliated/ovovo] has quit [Ping timeout: 260 seconds] 22:11 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-jipesvevoygcwajj] has quit [Quit: Connection closed for inactivity] 22:16 -!- waxwing [~waxwing@unaffiliated/waxwing] has quit [Ping timeout: 248 seconds] 22:18 -!- waxwing [~waxwing@91.216.245.111] has joined #bitcoin-core-dev 22:24 -!- waxwing [~waxwing@91.216.245.111] has quit [Ping timeout: 248 seconds] 22:27 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Ping timeout: 248 seconds] 22:28 -!- waxwing [~waxwing@91.216.245.111] has joined #bitcoin-core-dev 22:29 -!- waxwing [~waxwing@91.216.245.111] has quit [Changing host] 22:29 -!- waxwing [~waxwing@unaffiliated/waxwing] has joined #bitcoin-core-dev 22:29 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-dev 22:32 -!- RubenSomsen [~RubenSoms@1.217.138.142] has quit [Ping timeout: 252 seconds] 22:43 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has quit [Remote host closed the connection] 22:44 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has joined #bitcoin-core-dev 23:07 < bitcoin-git> [bitcoin] sipa opened pull request #11389: Support having SegWit always active in regtest (master...201709_itsalwayssegwitinregtestia) https://github.com/bitcoin/bitcoin/pull/11389 23:11 < arubi> heh 23:20 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has joined #bitcoin-core-dev 23:22 -!- Miezel [~Miezel@64-83-208-26.static.stcd.mn.charter.com] has quit [Quit: This computer has gone to sleep] 23:34 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-ahkeosquksyyhphi] has joined #bitcoin-core-dev 23:36 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Ping timeout: 248 seconds] 23:37 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 23:42 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 23:43 -!- ndrst [~ndrst@unaffiliated/ndrst] has quit [Ping timeout: 240 seconds] 23:50 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Ping timeout: 240 seconds] 23:51 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev