--- Day changed Mon Jan 08 2018 00:08 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Ping timeout: 272 seconds] 00:08 < bitcoin-git> [bitcoin] TexasSooner opened pull request #12114: update jan 8 (master...master) https://github.com/bitcoin/bitcoin/pull/12114 00:09 < bitcoin-git> [bitcoin] TexasSooner closed pull request #12114: update jan 8 (master...master) https://github.com/bitcoin/bitcoin/pull/12114 00:10 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 00:15 -!- Squidicc [~squid@pool-173-48-82-37.bstnma.fios.verizon.net] has quit [Read error: Connection reset by peer] 00:16 -!- Squidicc [~squid@pool-173-48-82-37.bstnma.fios.verizon.net] has joined #bitcoin-core-dev 00:16 -!- Danilo__ [~quassel@177.223.190.66] has joined #bitcoin-core-dev 00:17 -!- timothy [~tredaelli@redhat/timothy] has joined #bitcoin-core-dev 00:19 -!- Danilo_ [~quassel@177.223.190.66] has quit [Ping timeout: 246 seconds] 00:24 -!- Amuza [~Amuza@85.159.207.5] has joined #bitcoin-core-dev 00:28 -!- anome [~anome@customer-46-39-118-13.stosn.net] has joined #bitcoin-core-dev 00:30 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-mzsbrohjcshchmvt] has quit [Quit: Connection closed for inactivity] 00:31 -!- tri333 [631443d4@gateway/web/freenode/ip.99.20.67.212] has quit [Quit: Page closed] 00:33 -!- anome [~anome@customer-46-39-118-13.stosn.net] has quit [Changing host] 00:33 -!- anome [~anome@unaffiliated/anome] has joined #bitcoin-core-dev 00:40 -!- anome [~anome@unaffiliated/anome] has quit [] 00:41 -!- anome [~anome@unaffiliated/anome] has joined #bitcoin-core-dev 00:58 -!- anome [~anome@unaffiliated/anome] has quit [] 01:16 -!- JackH [~laptop@91.189.61.70] has joined #bitcoin-core-dev 01:23 -!- logicue [~logicue@p54B5F4A8.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 01:28 -!- anome [~anome@unaffiliated/anome] has joined #bitcoin-core-dev 01:42 -!- cysm [cysm@gateway/shell/elitebnc/x-xykfwqeaxowrghyh] has quit [Ping timeout: 248 seconds] 01:45 -!- promag [~promag@bl6-24-70.dsl.telepac.pt] has joined #bitcoin-core-dev 01:47 < sipa> BlueMatt: feel like having a look at #11403 again? 01:47 < gribble> https://github.com/bitcoin/bitcoin/issues/11403 | SegWit wallet support by sipa 路 Pull Request #11403 路 bitcoin/bitcoin 路 GitHub 01:50 < bitcoin-git> [bitcoin] MarcoFalke closed pull request #12113: Qt: Fixed styling in modaloverlay.cpp (master...ajkp/modaloverlay_styling) https://github.com/bitcoin/bitcoin/pull/12113 01:51 -!- promag [~promag@bl6-24-70.dsl.telepac.pt] has quit [Remote host closed the connection] 01:56 -!- promag [~promag@bl6-24-70.dsl.telepac.pt] has joined #bitcoin-core-dev 01:59 -!- cysm [cysm@gateway/shell/elitebnc/x-unflozakkcphzkrq] has joined #bitcoin-core-dev 02:14 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection] 02:18 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 02:23 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 240 seconds] 02:23 -!- whphhg [~whphhg@unaffiliated/whphhg] has joined #bitcoin-core-dev 02:24 -!- logicue [~logicue@p54B5F4A8.dip0.t-ipconnect.de] has quit [Quit: logicue] 02:27 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Remote host closed the connection] 02:32 -!- cysm [cysm@gateway/shell/elitebnc/x-unflozakkcphzkrq] has quit [Ping timeout: 268 seconds] 02:44 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 268 seconds] 02:45 -!- promag [~promag@bl6-24-70.dsl.telepac.pt] has quit [Remote host closed the connection] 02:45 -!- cysm [cysm@gateway/shell/elitebnc/x-tqzyikhogximxzxl] has joined #bitcoin-core-dev 02:49 -!- JackH [~laptop@91.189.61.70] has quit [Ping timeout: 260 seconds] 02:52 -!- promag [~promag@bl6-24-70.dsl.telepac.pt] has joined #bitcoin-core-dev 02:53 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has quit [Remote host closed the connection] 02:54 -!- promag [~promag@bl6-24-70.dsl.telepac.pt] has quit [Remote host closed the connection] 02:57 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has joined #bitcoin-core-dev 02:58 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 02:58 -!- shesek [~shesek@bzq-84-110-232-125.cablep.bezeqint.net] has joined #bitcoin-core-dev 02:58 -!- shesek [~shesek@bzq-84-110-232-125.cablep.bezeqint.net] has quit [Changing host] 02:58 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 02:59 -!- Boop [68de7539@gateway/web/freenode/ip.104.222.117.57] has joined #bitcoin-core-dev 02:59 -!- hirishaway is now known as hirish 02:59 -!- Boop [68de7539@gateway/web/freenode/ip.104.222.117.57] has quit [Client Quit] 03:02 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 260 seconds] 03:08 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 03:09 -!- promag [~promag@bl6-24-70.dsl.telepac.pt] has joined #bitcoin-core-dev 03:22 -!- Midak [59672359@gateway/web/freenode/ip.89.103.35.89] has joined #bitcoin-core-dev 03:29 -!- mrfrasha [~mrfrasha@66-188-250-34.dhcp.eucl.wi.charter.com] has quit [Quit: mrfrasha] 03:30 -!- Midak [59672359@gateway/web/freenode/ip.89.103.35.89] has quit [Quit: Page closed] 03:32 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 03:34 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has joined #bitcoin-core-dev 03:37 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 248 seconds] 03:39 -!- logicue [~logicue@p54B5F4A8.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 03:41 -!- anome [~anome@unaffiliated/anome] has quit [] 03:42 -!- larafale [~larafale@ax213-1-82-66-157-194.fbx.proxad.net] has joined #bitcoin-core-dev 03:46 -!- hirish is now known as hirishaway 03:50 -!- Amuza [~Amuza@85.159.207.5] has quit [Quit: Leaving] 03:52 -!- promag [~promag@bl6-24-70.dsl.telepac.pt] has quit [Remote host closed the connection] 03:57 -!- promag [~promag@bl6-24-70.dsl.telepac.pt] has joined #bitcoin-core-dev 03:57 -!- Amuza [~Amuza@85.159.207.5] has joined #bitcoin-core-dev 03:58 -!- Lauda [~quassel@unaffiliated/lauda] has quit [Remote host closed the connection] 03:59 -!- Lauda [~quassel@unaffiliated/lauda] has joined #bitcoin-core-dev 04:00 -!- Manu_ [3b5d0138@gateway/web/freenode/ip.59.93.1.56] has joined #bitcoin-core-dev 04:06 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 04:08 -!- anome [~anome@unaffiliated/anome] has joined #bitcoin-core-dev 04:10 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 240 seconds] 04:10 -!- anome [~anome@unaffiliated/anome] has quit [Client Quit] 04:14 -!- Manu_ [3b5d0138@gateway/web/freenode/ip.59.93.1.56] has quit [Quit: Page closed] 04:14 -!- Giszmo [~leo@pc-204-28-214-201.cm.vtr.net] has joined #bitcoin-core-dev 04:15 -!- JackH [~laptop@91.189.61.70] has joined #bitcoin-core-dev 04:16 -!- anome [~anome@unaffiliated/anome] has joined #bitcoin-core-dev 04:18 -!- anome [~anome@unaffiliated/anome] has quit [Client Quit] 04:21 -!- _flow_ [flow@star.geekplace.eu] has quit [Ping timeout: 240 seconds] 04:25 -!- anome [~anome@unaffiliated/anome] has joined #bitcoin-core-dev 04:27 -!- anome [~anome@unaffiliated/anome] has quit [Client Quit] 04:32 -!- DrFeelGood [~DrFeelGoo@unaffiliated/olufunmilayo] has quit [Read error: Connection reset by peer] 04:33 -!- anome [~anome@unaffiliated/anome] has joined #bitcoin-core-dev 04:33 -!- DrFeelGood [~DrFeelGoo@unaffiliated/olufunmilayo] has joined #bitcoin-core-dev 04:35 -!- anome [~anome@unaffiliated/anome] has quit [Client Quit] 04:43 -!- anome [~anome@unaffiliated/anome] has joined #bitcoin-core-dev 04:50 -!- anome [~anome@unaffiliated/anome] has quit [] 04:57 -!- Randolf [~randolf@96.53.47.42] has quit [Ping timeout: 276 seconds] 04:58 -!- logicue [~logicue@p54B5F4A8.dip0.t-ipconnect.de] has quit [Quit: logicue] 05:02 -!- promag [~promag@bl6-24-70.dsl.telepac.pt] has quit [Remote host closed the connection] 05:03 -!- anome [~anome@unaffiliated/anome] has joined #bitcoin-core-dev 05:06 -!- dqx [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 05:08 -!- _flow_ [flow@star.geekplace.eu] has joined #bitcoin-core-dev 05:10 -!- dqx [~dqx@unaffiliated/dqx] has quit [Ping timeout: 246 seconds] 05:16 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 05:20 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 260 seconds] 05:23 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Write error: Connection reset by peer] 05:23 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Read error: Connection reset by peer] 05:23 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Write error: Connection reset by peer] 05:25 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 05:26 -!- Monte35Osinski [~Monte35Os@ns334669.ip-5-196-64.eu] has joined #bitcoin-core-dev 05:28 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-dev 05:33 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #bitcoin-core-dev 05:37 -!- anome [~anome@unaffiliated/anome] has quit [] 05:41 -!- logicue [~logicue@p54B5F4A8.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 05:48 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 05:51 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 05:52 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 05:57 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 05:57 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 240 seconds] 06:05 -!- Randolf [~randolf@96.53.47.42] has joined #bitcoin-core-dev 06:05 -!- c01nkiller [47758d0e@gateway/web/freenode/ip.71.117.141.14] has joined #bitcoin-core-dev 06:06 -!- Chris_Stewart_5 [chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 06:07 -!- Eetsi123 [~Eetsi123@85-76-106-188-nat.elisa-mobile.fi] has quit [Ping timeout: 276 seconds] 06:12 -!- logicue [~logicue@p54B5F4A8.dip0.t-ipconnect.de] has quit [Quit: logicue] 06:14 -!- belcher [~belcher@unaffiliated/belcher] has joined #bitcoin-core-dev 06:17 -!- anome [~anome@unaffiliated/anome] has joined #bitcoin-core-dev 06:19 -!- anome [~anome@unaffiliated/anome] has quit [Client Quit] 06:21 -!- DrFeelGood [~DrFeelGoo@unaffiliated/olufunmilayo] has quit [Quit: DrFeelGood] 06:21 -!- DrFeelGood [~DrFeelGoo@unaffiliated/olufunmilayo] has joined #bitcoin-core-dev 06:22 -!- Chris_Stewart_5 [chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 248 seconds] 06:24 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [] 06:25 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 06:30 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 268 seconds] 06:32 -!- c01nkiller [47758d0e@gateway/web/freenode/ip.71.117.141.14] has quit [Quit: Page closed] 06:33 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 06:35 -!- anome [~anome@unaffiliated/anome] has joined #bitcoin-core-dev 06:37 -!- anome [~anome@unaffiliated/anome] has quit [Client Quit] 06:39 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 276 seconds] 06:57 -!- zautomata [~zautomata@unaffiliated/zautomata] has joined #bitcoin-core-dev 06:57 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 06:58 < BlueMatt> sipa: yep, will do today 07:01 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 240 seconds] 07:05 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 07:14 -!- Squidicc [~squid@pool-173-48-82-37.bstnma.fios.verizon.net] has quit [Quit: Oh no, not again] 07:14 -!- Squidicuz [~squid@pool-173-48-82-37.bstnma.fios.verizon.net] has joined #bitcoin-core-dev 07:18 -!- Emcy [~Emcy@unaffiliated/emcy] has quit [Ping timeout: 256 seconds] 07:18 -!- Emcy [~Emcy@unaffiliated/emcy] has joined #bitcoin-core-dev 07:20 -!- Amuza [~Amuza@85.159.207.5] has quit [Quit: Leaving] 07:21 -!- dqx [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 07:25 -!- dqx [~dqx@unaffiliated/dqx] has quit [Ping timeout: 240 seconds] 07:27 -!- anome [~anome@unaffiliated/anome] has joined #bitcoin-core-dev 07:29 -!- Chris_Stewart_5 [chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 07:32 -!- logicue [~logicue@p54B5F4A8.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 07:33 -!- mandric [~mandric@108-228-58-104.lightspeed.cicril.sbcglobal.net] has joined #bitcoin-core-dev 07:36 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 07:41 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 248 seconds] 07:42 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection] 07:43 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-dev 07:47 -!- dqx [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 07:47 -!- MrPaz [~PazPazPaz@104-52-130-247.lightspeed.cicril.sbcglobal.net] has joined #bitcoin-core-dev 07:47 -!- Monte35Osinski [~Monte35Os@ns334669.ip-5-196-64.eu] has quit [Ping timeout: 264 seconds] 07:48 -!- logicue [~logicue@p54B5F4A8.dip0.t-ipconnect.de] has quit [Quit: logicue] 07:50 -!- dqx_ [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 07:51 -!- dqx [~dqx@unaffiliated/dqx] has quit [Read error: Connection reset by peer] 07:53 -!- wxss [~user@78.129.181.190] has joined #bitcoin-core-dev 07:55 -!- dqx_ [~dqx@unaffiliated/dqx] has quit [Remote host closed the connection] 08:03 -!- Schwineigel [adaeff3c@gateway/web/freenode/ip.173.174.255.60] has joined #bitcoin-core-dev 08:03 < Schwineigel> help 08:04 < Schwineigel> first transaction did not go through. 08:04 < Schwineigel> it was sent 6 jan 18 08:05 < Schwineigel> what do i do 08:05 < Lauda> Schwineigel: #bitcoin 08:05 < Schwineigel> hi 08:07 < Schwineigel> My first transaction sending satoshi out did not work what do i do? 08:07 < Schwineigel> It was sent 6 Jan 18 it is still pending 08:10 < Schwineigel> i guess i came to the wrong place for help 08:10 -!- dqx [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 08:12 < Schwineigel> i came here to find help 08:13 < Schwineigel> My trasnaction has not gone through, i made it on 6 jan 08:13 < achow101> Schwineigel: this channel is for Bitcoin Core development, not for helping users 08:13 < achow101> for general help, go to #bitcoin 08:14 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 08:14 < Schwineigel> ok sorry to bother you. thanks for the info 08:14 -!- Schwineigel [adaeff3c@gateway/web/freenode/ip.173.174.255.60] has quit [Quit: Page closed] 08:15 -!- dqx [~dqx@unaffiliated/dqx] has quit [Ping timeout: 252 seconds] 08:16 -!- zautomata1 [~zautomata@unaffiliated/zautomata] has joined #bitcoin-core-dev 08:17 -!- interestedbystan [8bb8dfb5@gateway/web/freenode/ip.139.184.223.181] has joined #bitcoin-core-dev 08:18 -!- Abdul [5e007056@gateway/web/freenode/ip.94.0.112.86] has joined #bitcoin-core-dev 08:18 -!- zautomata [~zautomata@unaffiliated/zautomata] has quit [Ping timeout: 265 seconds] 08:18 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 248 seconds] 08:18 -!- Abdul [5e007056@gateway/web/freenode/ip.94.0.112.86] has quit [Client Quit] 08:19 -!- interestedbystan [8bb8dfb5@gateway/web/freenode/ip.139.184.223.181] has quit [Client Quit] 08:19 -!- dqx [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 08:19 -!- m8tion [~m8tion@81-65-53-254.rev.numericable.fr] has joined #bitcoin-core-dev 08:21 -!- mcochrane [~mcochrane@121-200-10-182.NBN.syd.aussiebb.net] has quit [Quit: Konversation terminated!] 08:22 -!- mrfrasha [~mrfrasha@66-188-250-34.dhcp.eucl.wi.charter.com] has joined #bitcoin-core-dev 08:27 -!- mandric [~mandric@108-228-58-104.lightspeed.cicril.sbcglobal.net] has quit [Quit: Computer has gone to sleep.] 08:28 -!- JackH [~laptop@91.189.61.70] has quit [Ping timeout: 276 seconds] 08:33 -!- Murch [~murch@96-82-80-28-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev 08:35 -!- laurentmt [~Thunderbi@176.158.157.202] has joined #bitcoin-core-dev 08:45 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 08:48 < ossifrage> still no love building bitcoin-qt with -flto: ./libtool: line 1720: 18164 Segmentation fault (core dumped) /usr/bin/gcc-ranlib .libs/libsecp256k1.a 08:50 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 248 seconds] 08:51 -!- laurentmt [~Thunderbi@176.158.157.202] has quit [Quit: laurentmt] 08:54 < BlueMatt> ossifrage: segfault in ranlib sounds like a gcc bug to be reported upstream, no? 08:54 -!- Randolf [~randolf@96.53.47.42] has quit [Ping timeout: 256 seconds] 08:55 -!- blackeye01 [31ed96e9@gateway/web/freenode/ip.49.237.150.233] has joined #bitcoin-core-dev 08:57 -!- Murch [~murch@96-82-80-28-static.hfc.comcastbusiness.net] has quit [Quit: Snoozing.] 09:04 -!- blackeye01 [31ed96e9@gateway/web/freenode/ip.49.237.150.233] has quit [Ping timeout: 260 seconds] 09:05 -!- Murch [~murch@96-82-80-28-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev 09:05 -!- laurentmt [~Thunderbi@176.158.157.202] has joined #bitcoin-core-dev 09:06 -!- dqx [~dqx@unaffiliated/dqx] has quit [Remote host closed the connection] 09:06 -!- anome [~anome@unaffiliated/anome] has quit [] 09:07 -!- laurentmt [~Thunderbi@176.158.157.202] has quit [Client Quit] 09:07 -!- anome [~anome@unaffiliated/anome] has joined #bitcoin-core-dev 09:15 -!- Randolf [~randolf@96.53.47.42] has joined #bitcoin-core-dev 09:16 -!- flotwig [unknown@2604:180::7d9b:354f] has joined #bitcoin-core-dev 09:19 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 09:22 -!- jtimon [~quassel@41.31.134.37.dynamic.jazztel.es] has joined #bitcoin-core-dev 09:24 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 256 seconds] 09:24 -!- PaulCapestany [~PaulCapes@ip68-100-207-91.dc.dc.cox.net] has quit [Ping timeout: 240 seconds] 09:25 -!- PaulCape_ [~PaulCapes@ip68-100-207-91.dc.dc.cox.net] has joined #bitcoin-core-dev 09:29 -!- dqx [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 09:31 -!- Szadek [~Szadek@82.102.24.187] has joined #bitcoin-core-dev 09:33 -!- rlesias [~rlesias@109.134.207.71] has joined #bitcoin-core-dev 09:38 -!- rlesias [~rlesias@109.134.207.71] has quit [] 09:44 -!- mandric [~mandric@108-228-58-104.lightspeed.cicril.sbcglobal.net] has joined #bitcoin-core-dev 09:45 < ossifrage> BlueMatt, yeah it should be reported upstream, but I haven't put the effort in to find a clean testcase 09:50 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 09:54 -!- Murch [~murch@96-82-80-28-static.hfc.comcastbusiness.net] has quit [Quit: Snoozing.] 09:54 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 264 seconds] 09:56 -!- Murch [~murch@96-82-80-28-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev 10:03 -!- litecoinDev [6f5c1bda@gateway/web/freenode/ip.111.92.27.218] has joined #bitcoin-core-dev 10:04 -!- litecoinDev [6f5c1bda@gateway/web/freenode/ip.111.92.27.218] has quit [Client Quit] 10:05 -!- MrPaz [~PazPazPaz@104-52-130-247.lightspeed.cicril.sbcglobal.net] has quit [Ping timeout: 265 seconds] 10:13 -!- hirishaway is now known as hirish 10:15 -!- Murch [~murch@96-82-80-28-static.hfc.comcastbusiness.net] has quit [Quit: Snoozing.] 10:16 -!- George [a2cac893@gateway/web/freenode/ip.162.202.200.147] has joined #bitcoin-core-dev 10:16 -!- mandric [~mandric@108-228-58-104.lightspeed.cicril.sbcglobal.net] has quit [Quit: Computer has gone to sleep.] 10:17 -!- Murch [~murch@96-82-80-28-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev 10:17 -!- MrPaz [~PazPazPaz@104-52-130-247.lightspeed.cicril.sbcglobal.net] has joined #bitcoin-core-dev 10:18 -!- anome [~anome@unaffiliated/anome] has quit [] 10:20 -!- m8tion [~m8tion@81-65-53-254.rev.numericable.fr] has quit [Quit: Leaving] 10:23 -!- timothy [~tredaelli@redhat/timothy] has quit [Quit: Konversation terminated!] 10:25 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 10:27 -!- cncr04s [~cncr04s@unaffiliated/cncr04s] has joined #bitcoin-core-dev 10:30 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 248 seconds] 10:32 -!- kexkey [~kexkey@173.209.63.133] has joined #bitcoin-core-dev 10:35 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 10:40 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Ping timeout: 256 seconds] 10:45 -!- logicue [~logicue@p54B5F4A8.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 10:50 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 10:51 -!- MrPaz [~PazPazPaz@104-52-130-247.lightspeed.cicril.sbcglobal.net] has quit [Ping timeout: 240 seconds] 10:56 -!- dqx [~dqx@unaffiliated/dqx] has quit [Remote host closed the connection] 10:57 -!- dqx [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 10:59 < bitcoin-git> [bitcoin] sdaftuar opened pull request #12118: Sort mempool by min(feerate, ancestor_feerate) (master...2018-01-fix-mempool-score) https://github.com/bitcoin/bitcoin/pull/12118 11:04 -!- dqx [~dqx@unaffiliated/dqx] has quit [Ping timeout: 268 seconds] 11:04 -!- jb55 [~jb55@209.52.229.194] has joined #bitcoin-core-dev 11:08 -!- dqx [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 11:09 -!- logicue [~logicue@p54B5F4A8.dip0.t-ipconnect.de] has quit [Quit: logicue] 11:11 -!- MrPaz [~PazPazPaz@104-52-130-247.lightspeed.cicril.sbcglobal.net] has joined #bitcoin-core-dev 11:13 -!- dqx [~dqx@unaffiliated/dqx] has quit [Ping timeout: 248 seconds] 11:20 -!- jb55 [~jb55@209.52.229.194] has quit [Ping timeout: 276 seconds] 11:20 -!- Dizzle [~dizzle@108.171.182.16] has joined #bitcoin-core-dev 11:25 < bitcoin-git> [bitcoin] Sjors opened pull request #12119: [wallet] use bech32 change address if all destinations are bech32 (master...bech32-change) https://github.com/bitcoin/bitcoin/pull/12119 11:26 -!- zautomata2 [~zautomata@unaffiliated/zautomata] has joined #bitcoin-core-dev 11:27 -!- zautomata1 [~zautomata@unaffiliated/zautomata] has quit [Ping timeout: 240 seconds] 11:34 < bitcoin-git> [bitcoin] TheBlueMatt opened pull request #12120: Add dev guideline limiting auto usage. (master...2018-01-auto-devnotes) https://github.com/bitcoin/bitcoin/pull/12120 11:34 * BlueMatt is gonna have to start a policy of auto-nacking anything with auto that doesnt save at least 30 chars of typing 11:42 < sipa> BlueMatt: :( 11:43 * achow101 replaces every word in the repo with auto 11:45 < TD-Linux> #define let const auto 11:46 -!- Szadek [~Szadek@82.102.24.187] has quit [Quit: 馃敟] 11:47 -!- HollowRiddler [~HRiddler@azi214.neoplus.adsl.tpnet.pl] has joined #bitcoin-core-dev 11:48 -!- dqx [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 11:49 < Chris_Stewart_5> Does the bitcoin core software dump txs back into the mempool when a chain is clearly orphaned? 11:49 * BlueMatt is an auto-kermudgen 11:49 < sipa> BlueMatt: i don't understand the rationale for that. in the case you reference, just see it as a replacement for inlining 11:50 -!- anome [~anome@unaffiliated/anome] has joined #bitcoin-core-dev 11:50 < sipa> (you could replace the two instances of 'key' with a call to GetKeyForDestination) 11:51 < sipa> anyway, i don't feel strongly and if you insist i'll gladly change it... but i think making the type explicit there is less readable 11:54 < Dizzle> Chris_Stewart_5: yep! It will not automatically rebroadcast them though. It will of course send along its revised mempool to any other peer that asks for it though. 11:55 < luke-jr> I can see places where auto can help readability, and also places where it can hurt readability. 11:55 < BlueMatt> sipa: I mean my objection in cases like that is if i want to go audit what IsNull does, I now have to go lookup two things, indeed there is a tradeoff because there may be a type conversion hiding in the = (evil, evil C++), but... 11:55 < sipa> with auto you know no implciit type conversion can happen :) 11:56 < BlueMatt> (and, yes, I do look up things like what IsNull() does quite often in review, but of course it depends on what the type is of if I know what it does already....) 11:56 -!- dqx [~dqx@unaffiliated/dqx] has quit [Remote host closed the connection] 11:56 < BlueMatt> indeed, thats the tradeoff...I wish there were a "this type, and no fucking conversion you piece of shit compiler" option in C++ 11:56 < sipa> or make all type conversions explicit :) 11:56 < BlueMatt> well, yea 11:57 * BlueMatt hates surprises 11:57 -!- anome [~anome@unaffiliated/anome] has quit [] 11:57 < BlueMatt> with the auto in the case mentioned, I have to go do a speculative lookup of the type and use that to speculatively lookup what IsNull() does....waiiiitttttt 11:58 < sipa> right... but if thete was only one instance of 'key' in the function, and the GetKeyForDestination clal was inlined into it.... would you complain about that too? 11:58 < sipa> this is just a more efficient way of doing that 12:00 * BlueMatt has been reading too many spectre posts this weekend, clearly 12:00 < cncr04s> Is it possible to implement working mainnet LN on my service? 12:01 < Chris_Stewart_5> Dizzle: Is there a specific amount of confirmations required to do this? I.e. one chain is ahead of the orphaned chain by 6 confirmations 12:02 -!- dqx [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 12:02 < luke-jr> BlueMatt: happen to find a usable workaround? :x 12:02 -!- mandric [~mandric@c-73-73-148-9.hsd1.il.comcast.net] has joined #bitcoin-core-dev 12:03 -!- dqx [~dqx@unaffiliated/dqx] has quit [Remote host closed the connection] 12:03 < BlueMatt> sipa: no, in that case I likely wouldnt have looked up the type, but I probably should have to check for implicit conversion, but mostly in that case I would have just go read the function taking it as argument and found the type in the signature, the issue is that its actually used for more than the pass-through 12:03 < sipa> BlueMatt: you misunderstand 12:04 < BlueMatt> luke-jr: depends on how many syscalls you do....also, the fucking intel microcode updates are all-but-undocumented 12:04 -!- dqx [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 12:04 < CryptAxe> Chris_Stewart_5 : https://github.com/bitcoin/bitcoin/blob/master/src/validation.cpp#L2199-L2243 12:04 < CryptAxe> specifically: https://github.com/bitcoin/bitcoin/blob/master/src/validation.cpp#L2223-L2234 12:04 < CryptAxe> Looks like they are added to the mempool right when the block is disconnected 12:05 < sipa> BlueMatt: imagine that instead of key.IsNull() it was GetKeyForDestination(*pwallet, dest).IsNull() 12:05 < sipa> CryptAxe, Chris_Stewart_5: yes, immediately... what else? 12:05 -!- Murch [~murch@96-82-80-28-static.hfc.comcastbusiness.net] has quit [Quit: Snoozing.] 12:05 < BlueMatt> then I'd have to do the same lookup as the auto, but possibly wouldnt have complained, no, it still sucks just as much 12:06 < sipa> okay :) 12:06 -!- dqx [~dqx@unaffiliated/dqx] has quit [Remote host closed the connection] 12:06 -!- dqx [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 12:06 < sipa> so you're basically saying that every intermediate expression should be annotated explicitly with its type (apart from that being unreasonable) 12:07 -!- Murch [~murch@96-82-80-28-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev 12:07 < BlueMatt> it would assist with review, and were it roughly as readable, I'd highly, highly prefer that 12:07 < Chris_Stewart_5> CryptAxe: Thanks! 12:07 * BlueMatt hates surprises :p 12:08 < sipa> BlueMatt: fair; i guess i just disagree that that is more readable :) 12:08 < BlueMatt> its all of 4 chars longer on a short line :( 12:09 < BlueMatt> maybe I just need to hack my editor to pull shit out of the C++ ast and display the types :p 12:12 -!- Tennis [~Tennis@unaffiliated/tennis] has joined #bitcoin-core-dev 12:15 -!- isle2983 [~isle2983@72.53.24.136] has joined #bitcoin-core-dev 12:20 -!- dqx [~dqx@unaffiliated/dqx] has quit [Remote host closed the connection] 12:21 -!- dqx [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 12:24 -!- logicue [~logicue@p54B5F4A8.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 12:25 -!- dqx [~dqx@unaffiliated/dqx] has quit [Ping timeout: 240 seconds] 12:26 -!- Murch [~murch@96-82-80-28-static.hfc.comcastbusiness.net] has quit [Quit: Snoozing.] 12:29 -!- Randolf [~randolf@96.53.47.42] has quit [Ping timeout: 240 seconds] 12:30 -!- eck [~eck@fsf/member/eck] has joined #bitcoin-core-dev 12:30 -!- jb55 [~jb55@209.52.229.194] has joined #bitcoin-core-dev 12:36 -!- dqx [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 12:37 < BlueMatt> sipa: wait, for bech32 addresses, why do we need to add the p2sh-wrapped segwit thinggy to the wallet? 12:38 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 12:39 < sipa> BlueMatt: because the IsMine logic added in 0.13.1 (for maximal conservativeness at the time) requires the presence of the redeemscript in the keystore even for native segwit output 12:39 -!- not-a-bot [a7730f03@gateway/web/freenode/ip.167.115.15.3] has joined #bitcoin-core-dev 12:40 < BlueMatt> ah, ok, didnt realize that 12:40 < BlueMatt> or...recall that 12:40 < sipa> this was to make sure we don't accidentally treat outputs to uncompressed keys in witness versionas ours 12:40 < BlueMatt> yea 12:41 < sipa> i think that was overkill now, but it was not a bad strategy to need something explicit to mark a partocular output as ours 12:41 < BlueMatt> yea 12:42 < BlueMatt> oh, while you're here, have you tested adding a bech32 address to the addressbook and then trying to open the wallet with 0.15 qt? 12:43 < sipa> no, i haven't tried qt 12:44 < sipa> i've made necessary changes for it to compile, but there may be other changes necessary (especially if we want bech32 error detection in the gui) 12:44 < BlueMatt> well, ok, have you tested adding a bech32 address to the addressbook and then calling 0.15 getaddressesbyaccount on the same wallet? 12:46 < sipa> no, i haven't tested anything with the gui 12:46 < BlueMatt> not gui 12:46 < BlueMatt> rpc 12:48 < sipa> ah 12:49 < BlueMatt> does it blow up? I really have no idea, it just looks like it should blow up or UB or do something strange 12:49 < sipa> p2sh certainly is tested, as most rpc tests use the default addresstype 12:49 < sipa> how s? 12:49 < BlueMatt> what happens when you blindly cast from a variant to a CBitcoinAddress? 12:50 < sipa> cast? 12:50 < sipa> those are not compatible types 12:50 < BlueMatt> yes, thats what I thought, but we do a for (pair& : mapAddressBook) 12:51 < BlueMatt> which reads to me as "wat" 12:51 < BlueMatt> and if you put bech32 in the address book, I think 0.15 will end up with a CNoDestination in your mapAddressBook 12:52 -!- mandric_ [~mandric@c-73-73-148-9.hsd1.il.comcast.net] has joined #bitcoin-core-dev 12:52 -!- Emcy_ [~Emcy@unaffiliated/emcy] has joined #bitcoin-core-dev 12:52 -!- hirish [~hirish@hirish.cloudns.org] has quit [Ping timeout: 265 seconds] 12:53 -!- mandric [~mandric@c-73-73-148-9.hsd1.il.comcast.net] has quit [Ping timeout: 240 seconds] 12:54 -!- hirish [~hirish@hirish.cloudns.org] has joined #bitcoin-core-dev 12:54 -!- Emcy [~Emcy@unaffiliated/emcy] has quit [Ping timeout: 265 seconds] 12:54 < sipa> BlueMatt: oh, on downgrade! 12:54 < sipa> ouch 12:54 < BlueMatt> yes, I think we're like...kinda fucked 12:54 < BlueMatt> I dunno how to fix that aside from a whole new map for segwit address labels :/ 12:55 < BlueMatt> (which isnt the worst idea, but its a big change) 12:55 < BlueMatt> should check if my reading is actually correct, I'm still a bit foggy 12:55 < sipa> well, as soon as you request a bech32 address - which is always an explicit action - you can't downgrade anymore i guess 12:55 < sipa> maybe that means we neeed an uogradewallet to permit bech32 12:56 < BlueMatt> yea, but we also cant do an upgradwallet without doing an hd upgrade..... 12:56 < BlueMatt> or without introducing heaps of stupid hacks 12:56 < sipa> well it could be like uogradewallet 12:56 < BlueMatt> yea, i mean could, but it sucks 12:56 < sipa> similar to how encryption a walletade it incompatible with 0.3 12:56 < sipa> sorry, walking 12:56 < sipa> my typing sucks 13:02 < BlueMatt> also, it does seem weird to let someone have a different label for the bech32, the p2sh-wrapped and the p2ph versions of a pubkey -> address mapping :( 13:04 < sipa> why? 13:05 < sipa> that's certainly how it should be in the long term (when IsMine is also not related anymore) 13:06 < sipa> it's kinda hacky that for some things we need labels on just one of them, and sometimes all 13:06 < luke-jr> well, it shouldn't be possible to have more than one address style per key really 13:07 < sipa> right; eventually that will be the case i think 13:07 < sipa> though right now it's impossible to do that - our IsMine logoc will happily accept anything it can sign for 13:08 -!- Murch [~murch@96-82-80-28-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev 13:09 -!- dqx [~dqx@unaffiliated/dqx] has quit [Remote host closed the connection] 13:11 -!- mandric_ [~mandric@c-73-73-148-9.hsd1.il.comcast.net] has quit [Quit: Computer has gone to sleep.] 13:15 -!- dqx [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 13:16 -!- dqx_ [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 13:17 -!- dqx [~dqx@unaffiliated/dqx] has quit [Read error: Connection reset by peer] 13:17 < BlueMatt> sipa: what luke said, the fact that we have multiple pubkey->addr mappings right now is kinda a hack which will be for backwards compat eventually 13:17 < BlueMatt> sipa: I mention it because if we did labels only for the P2PH version of an address then we'd sidestep the above issue 13:18 -!- not-a-bot [a7730f03@gateway/web/freenode/ip.167.115.15.3] has quit [Ping timeout: 260 seconds] 13:18 -!- zautomata2 [~zautomata@unaffiliated/zautomata] has quit [Ping timeout: 240 seconds] 13:18 < BlueMatt> ofc there's still the issue of people who already have entries for the p2sh wrapped version which mismatch the p2ph version :/ 13:20 -!- Tennis [~Tennis@unaffiliated/tennis] has quit [Quit: Leaving] 13:21 -!- zautomata2 [~zautomata@unaffiliated/zautomata] has joined #bitcoin-core-dev 13:22 -!- opovo [~duarte@2a02:a03f:521b:1b00:3dee:29ca:2dbd:e787] has joined #bitcoin-core-dev 13:23 -!- not-a-bot [a7730f03@gateway/web/freenode/ip.167.115.15.3] has joined #bitcoin-core-dev 13:27 -!- anome [~anome@unaffiliated/anome] has joined #bitcoin-core-dev 13:28 -!- Tennis [~Tennis@unaffiliated/tennis] has joined #bitcoin-core-dev 13:29 < Lauda> BlueMatt: What was that with adding bech32 to the address book? I can test that right now in the GUI 13:31 < BlueMatt> Lauda: give a bech32 address a label, then downgrade 13:31 < BlueMatt> what is in address book window? 13:31 < sipa> and does it even start at all 13:32 < Lauda> You mean create wallet with the PR, add a label to bech and try opening with 0.15.1? 13:32 < sipa> indeed, use getnewaddress with addresstype=bech32 13:32 < sipa> and then downgrade to 0.15.1 13:33 < Lauda> Error loading wallet.dat: Wallet requires newer version of Bitcoin Core. 13:33 < BlueMatt> ryanofsky: points out if anything it may be most likely to simply have a dummy entry from a default-constructed temporary 13:33 < sipa> heh, why is that 13:34 < BlueMatt> have to create with 15.1 13:34 < BlueMatt> then upgrade, then get addr, then downgrade 13:34 < Lauda> Oh 13:34 < sipa> oh, the default key thing? 13:34 < Lauda> sec, let me try that 13:34 < sipa> Lauda: thanks! 13:36 < Lauda> sipa: yw! 13:36 < Lauda> It does open.. 13:37 < Lauda> label is not working and address is just '3QJmnh' 13:37 < sipa> ugh. 13:37 < Lauda> '3QJmnh' *is* the bech32 I generated.. weird cut-off 13:37 < sipa> what if you have multiple bech32 addresses in the wallet? 13:37 < BlueMatt> yea, so ryanofsky was right 13:37 < Lauda> testing brb 13:37 < sipa> lauda: that's not a bech32 address 13:37 < BlueMatt> sipa: I'm pretty sure just 1 entry 13:38 < BlueMatt> cause the map is indexed then by a CNoDestination 13:38 < sipa> that's p2sh 13:38 < Lauda> sipa it was bech32, after downgrade all I saw was "3QJmnh" 13:38 < sipa> oh 13:38 < Lauda> Let me generate a few of them 13:38 < Lauda> and I'll screen 13:38 < sipa> that's probabpy the empty array converted to base58 13:39 < BlueMatt> sipa: sure its not just the checksum 13:39 < BlueMatt> ? 13:39 < BlueMatt> yea 13:39 < sipa> right 13:41 < BlueMatt> well, better than crash 13:41 < BlueMatt> i mean i guess not so bad, but still worth fixing, problem is any fix is ugly 13:42 < BlueMatt> unless we want to not support more than one address book entry per pubkey 13:42 < BlueMatt> which I dont mind, but.... 13:42 < Lauda> uhm sipa 13:42 < Lauda> I made multiple bech 13:42 < Lauda> after downgrade 13:42 < Lauda> all are gone 13:42 < Lauda> o.o 13:42 < sipa> that's kind of expected 13:43 < sipa> though i think that if you had incoming payments to those bech32 addresses, you'd still have the balance 13:43 < Lauda> Alright, so when making one and adding label it is weird. When I make multiple and add labels, they disappear. Anything else I should check? 13:43 < BlueMatt> it should still have the one 3QJmnh 13:43 < sipa> but the transaction list and address book woild be cut off 13:43 < Lauda> BlueMatt: New wallet 13:43 < sipa> *messed up 13:45 < BlueMatt> Lauda: no, if you do the same thing again the address should not change 13:46 < BlueMatt> and if you have multiple, it should still be the same, one, address in the address book in 0.15 13:47 < Lauda> Sec, reproducing 13:47 -!- opovo [~duarte@2a02:a03f:521b:1b00:3dee:29ca:2dbd:e787] has left #bitcoin-core-dev [] 13:48 -!- Randolf [~randolf@24.244.32.210] has joined #bitcoin-core-dev 13:48 < Lauda> New wallet, generated bech again (so diff. address) and it still turned into '3QJmnh'. 13:49 < BlueMatt> yes, ok 13:49 < sipa> maybe we should just delete the defaultkey thing whenever a bech32 address is generator 13:49 < BlueMatt> please no such hacks 13:49 < sipa> why not? 13:50 < sipa> it's not very different from the wallet version, except we can't really do that due to the HD thing 13:50 < Lauda> Back with that wallet to 15.99, (2nd) bech address. Back to 15.1 13:50 < Lauda> now both have 3QJmnh and no labels 13:50 < Lauda> uh. 13:50 < BlueMatt> such a hack, and I'd kinda rather have the 3QJmnh bug than completely blow up backwards compat 13:51 < sipa> well i guess it depends on how we deal with transactions to bech32 addresses and then downgrade 13:52 < BlueMatt> I dont (think) the 3QJmnh bug will break on-disk state, only in-memory/display 13:52 < sipa> agree 13:52 < BlueMatt> so its not the end of the world, but we should fix it, breaking backwards compat is a huge hammer to fix one small bug, and is really ugly for ux 13:52 < BlueMatt> I mean we'd have to at least make it explicit 13:53 < BlueMatt> -upgradewallettobech32segwit 13:54 < sipa> for 0.16? 13:54 < sipa> or later? 13:55 < Lauda> If I import a privkey from a bech32 wallet (0.15.99) created, into the old one 13:55 < Lauda> it gives me 3 addresses. Is this supposed to happen? 13:55 < sipa> yes, unfortunately 13:56 < Lauda> :< 13:56 -!- Randolf [~randolf@24.244.32.210] has quit [Ping timeout: 255 seconds] 13:57 < sipa> when importing there is no way to know which of the addresses you want to use 13:57 < sipa> importmulti doesn't have that problem as you must explicitly state the address or script as well 13:57 < sipa> (but importmulti doesn't support segwit yet, that needs a follow-up pr) 13:58 -!- not-a-bot [a7730f03@gateway/web/freenode/ip.167.115.15.3] has quit [Ping timeout: 260 seconds] 13:59 < Lauda> I added a bech address that has coins on it without rescan, downgraded and will rescan now 14:00 < BlueMatt> sipa: for 0.16? 14:00 -!- mandric [~mandric@172.58.139.49] has joined #bitcoin-core-dev 14:02 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 276 seconds] 14:02 < BlueMatt> cfields: so when libevent? #12123 14:03 < gribble> https://github.com/bitcoin/bitcoin/issues/12123 | [Performance] LevelDB options.max_open_files = 64 parameter (Windows 10) 路 Issue #12123 路 bitcoin/bitcoin 路 GitHub 14:04 < sipa> BlueMatt: i'm not following 14:04 < BlueMatt> sipa: nor am I 14:04 < sipa> i thought you just said you prefer the 3QJmnh bug 14:04 < sipa> and don't want to break backward compatibility 14:05 < BlueMatt> I said I prefer the 3QJmnh to blindly deleting the default key...if we want to break backwards compat, which I dont like at all, then we'd have to require a manual upgrade 14:05 < BlueMatt> I'd prefer we fix the bug 14:05 < sipa> oh, i mean deleting the default whenever you decide you want bech32 14:05 < sipa> whether that's explicit or implicit i don't care much 14:06 < BlueMatt> it absolutely should not be implicit 14:06 < BlueMatt> s/should/can/ 14:06 < sipa> ok, if you feel strongly 14:06 < BlueMatt> since when do we blindly break downgrade implicitly on random actions? 14:06 < sipa> encrpytion was one 14:07 < BlueMatt> was that not documented? and thats a much less random action, imo, you can get a bech32 wallet in any one of 5 places... 14:07 < BlueMatt> also importing a private key... 14:07 < sipa> sure it needs to be documented 14:08 < sipa> but i don't think it's unreasonable to say "if you generate a bech32 address, you can't open the wallet anymore in software that doesn't support bech32 addresses" 14:08 < sipa> yeah, importprivkey is annoying 14:08 -!- belcher [~belcher@unaffiliated/belcher] has joined #bitcoin-core-dev 14:08 < BlueMatt> anyway, so options to fix the bug: a) store bech32 address book entries in a different db key space, b) dont allow multiple address book entries per public key 14:08 < sipa> bah 14:08 < BlueMatt> if there wer only one place you can "generate a bech32 address" I might agree, but there's many... 14:08 < BlueMatt> I mean we will eventually implicitly have b 14:08 < sipa> b is not possible without breaking importprivkey 14:09 < BlueMatt> well by "allow" I mean look things up by their implied P2PH form 14:09 < sipa> god no please 14:09 < sipa> no more hacks 14:10 < BlueMatt> how is that a hack? 14:10 < BlueMatt> we jsut switch address book entries to be per-pubkey 14:10 < BlueMatt> what the map is indexed by, who cares 14:10 < sipa> bah 14:10 < BlueMatt> we will get that implicitly eventually anyway... 14:10 < sipa> no? 14:11 < sipa> labels are for an address 14:11 < sipa> not for a key 14:11 < BlueMatt> yes, but if you only have one address per key, you also only have one label per key 14:11 < sipa> you can have labels for p2sh multisig too 14:11 < sipa> there is no good key there 14:11 < BlueMatt> and, really, I think its super weird that you can do importprivkey on a key, get three address book entries, edit one address book entry and.... 14:11 < bitcoin-git> [bitcoin] laudaa opened pull request #12124: [wallet] Remove segwit status check (master...master) https://github.com/bitcoin/bitcoin/pull/12124 14:12 < sipa> you can have lavels for addresses you don't have a key for even (watch only) 14:12 < sipa> or only have a pubkey for 14:12 < sipa> or p2sh 14:12 < BlueMatt> yes, I'm aware 14:12 < BlueMatt> ah, dont have a key for is annoying 14:12 < sipa> having the label be associated with the key is just the wrong way to do it 14:13 < BlueMatt> wrong way or not the result is much nicer in practice 14:13 < BlueMatt> but, indeed, not having a key for it kinda blows that up 14:13 < sipa> keys are things you spend with 14:13 < sipa> addresses are things you receive with 14:13 -!- Chris_Stewart_5 [chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 248 seconds] 14:13 < sipa> labels belong to the latter 14:14 < BlueMatt> I agree, but practice != theory, in any case, it doesnt work in practice either :p 14:14 < sipa> how do you mean? 14:14 < sipa> the bug is that 0.15 doesn't support bech32 addresses 14:14 < BlueMatt> in the case you want to add a label to a dont-have-pubkey bech32 address 14:15 < sipa> and that we don't have a good way to mark a wallet to support bech32 14:15 < BlueMatt> err, no it still workrs 14:16 < sipa> i think we're spending an extraordinary amount of time here on compatibility with older software 14:16 < sipa> and i wish we had better procedures for dealing with that 14:16 -!- anome [~anome@unaffiliated/anome] has quit [] 14:17 < BlueMatt> we do have better procedures, but we blew then up with hd 14:17 < ryanofsky> haven't followed everything above, but shouldn't it be possible to fix this with a simple change to serialization code in walletdb? 14:17 < sipa> ryanofsky: how so? 14:17 < BlueMatt> ryanofsky: that was my (a), above 14:17 < BlueMatt> anyway, so options to fix the bug: a) store bech32 address book entries in a different db key space, b) dont allow multiple address book entries per public key 14:17 < sipa> meh 14:17 < ryanofsky> by serializing new addressbook entries with a different bdb key 14:17 < sipa> you're much better off just making the wallet file incompatibe 14:18 < ryanofsky> seems simple, and would require no change to regular wallet code 14:18 < sipa> moving it to a different key space will not actually make things work - you'll still not see the labels in an old version 14:18 < sipa> that's not desirable 14:18 -!- Arokh [~Arokh@extknot.com] has quit [Ping timeout: 272 seconds] 14:18 < sipa> if it's not going to actually work, it should actually not work 14:18 < BlueMatt> man I miss the original plan of "fix hd upgrade, require walletupgrade for segwit wallet" 14:19 < ryanofsky> oh, i didn't think that would be possible at all 14:19 < sipa> having 3QJmnh show up is IMHO better than silently hiding things :) 14:20 < ryanofsky> i see. really any of these options seem not that bad to me 14:20 < sipa> agree 14:20 < BlueMatt> which options? 14:21 < ryanofsky> hiding keys, showing mangled keys, different keyspace workaround, collapsed keyspace workaround, or requiring explicit upgrade 14:22 < sipa> my preference is either doing nothing and giving a nice big release notes warning that you may lose labels when downgrading after creating bech32 addresses 14:23 < sipa> or making the wallet file backward incompatible whenever the first bech32 address is created 14:23 < sipa> (explicitly with an action, or not) 14:25 -!- wxss [~user@78.129.181.190] has quit [Quit: leaving] 14:25 < BlueMatt> labels arent copied anywhere else, right? so there's no other way for it to break your on-disk state? 14:26 < sipa> i don't think so, no 14:26 < sipa> after upgrading again everything should be fine 14:26 < sipa> you can even create a bach32 address, give it out, downgrade, receive a transaction, upgrade... and all will work fine without rescan 14:27 < BlueMatt> yes, thats my impression 14:28 < sipa> also, when using importprivkey things will work as expected as long as you don't actually use the bech32 address 14:28 < BlueMatt> yea, that really sucks, but there's nothing we can do to support any such workflows anyway, the transaction as displayed in 0.15.1 will always be missing the label anyway 14:29 < sipa> there'll (from old software perspective) just be a weird unrelated addressbook entry added as well 14:29 -!- Cogito_Ergo_Sum [~Myself@unaffiliated/cogito-ergo-sum/x-7399460] has quit [] 14:33 -!- larafale [~larafale@ax213-1-82-66-157-194.fbx.proxad.net] has quit [Remote host closed the connection] 14:40 -!- Arokh [~Arokh@62.75.169.41] has joined #bitcoin-core-dev 14:41 -!- Randolf [~randolf@96.53.47.42] has joined #bitcoin-core-dev 14:43 -!- dqx_ [~dqx@unaffiliated/dqx] has quit [Remote host closed the connection] 14:44 -!- dqx [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 14:49 -!- dqx [~dqx@unaffiliated/dqx] has quit [Ping timeout: 248 seconds] 14:49 -!- Randolf [~randolf@96.53.47.42] has quit [Ping timeout: 260 seconds] 14:49 -!- Randolf [~randolf@96.53.47.42] has joined #bitcoin-core-dev 14:51 -!- MrPaz [~PazPazPaz@104-52-130-247.lightspeed.cicril.sbcglobal.net] has quit [Ping timeout: 256 seconds] 14:54 -!- dqx [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 14:55 -!- jb55 [~jb55@209.52.229.194] has quit [Ping timeout: 260 seconds] 14:57 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has quit [Quit: Going offline, see ya! (www.adiirc.com)] 14:58 -!- dqx [~dqx@unaffiliated/dqx] has quit [Ping timeout: 248 seconds] 15:04 -!- MrPaz [~PazPazPaz@104-52-130-247.lightspeed.cicril.sbcglobal.net] has joined #bitcoin-core-dev 15:05 -!- DrFeelGood [~DrFeelGoo@unaffiliated/olufunmilayo] has quit [Quit: DrFeelGood] 15:12 < BlueMatt> sipa: heh, AddAndGetDestinationForScript is only called in one place, but a AddAndGetDestinationForKey would be used in a bunch of places 15:21 -!- DrFeelGood [~DrFeelGoo@unaffiliated/olufunmilayo] has joined #bitcoin-core-dev 15:26 < sipa> BlueMatt: yes 15:27 < sipa> is that a problem? 15:29 < sipa> it's different because AddAndGetScript is harder to split up without doing double work 15:30 -!- zautomata3 [~zautomata@unaffiliated/zautomata] has joined #bitcoin-core-dev 15:30 < BlueMatt> its not a problem, just found it funny 15:30 < BlueMatt> i guess we dont care about wtf importwallet does? 15:31 < sipa> todo for a follow up PR 15:31 < sipa> just like signmessage and importmulti 15:31 < BlueMatt> I mean I dont think it'll *break* anything, ....ah ok 15:31 -!- zautomata2 [~zautomata@unaffiliated/zautomata] has quit [Ping timeout: 265 seconds] 15:31 -!- Emcy_ [~Emcy@unaffiliated/emcy] has quit [Read error: Connection reset by peer] 15:31 < sipa> (it's listed as such in the PR description, i think!) 15:32 < sipa> but i also think it'll just work, apart from maybe birthdates and labels 15:32 < BlueMatt> heh, text? ewwww why would i read that 15:36 -!- Emcy [~Emcy@unaffiliated/emcy] has joined #bitcoin-core-dev 15:36 -!- zautomata3 [~zautomata@unaffiliated/zautomata] has quit [Ping timeout: 256 seconds] 15:38 -!- zautomata3 [~zautomata@unaffiliated/zautomata] has joined #bitcoin-core-dev 15:42 < sipa> i know 15:44 -!- dqx [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 15:45 -!- BashCo_ [~BashCo@unaffiliated/bashco] has quit [Ping timeout: 252 seconds] 15:46 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 15:47 -!- Emcy_ [~Emcy@unaffiliated/emcy] has joined #bitcoin-core-dev 15:49 -!- dqx [~dqx@unaffiliated/dqx] has quit [Ping timeout: 240 seconds] 15:49 -!- Emcy [~Emcy@unaffiliated/emcy] has quit [Ping timeout: 268 seconds] 15:54 -!- mandric [~mandric@172.58.139.49] has quit [Quit: Computer has gone to sleep.] 15:58 -!- logicue [~logicue@p54B5F4A8.dip0.t-ipconnect.de] has quit [Quit: logicue] 16:01 -!- Chris_Stewart_5 [chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 16:04 -!- MrPaz [~PazPazPaz@104-52-130-247.lightspeed.cicril.sbcglobal.net] has quit [Ping timeout: 268 seconds] 16:07 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-uqpwbwklayjqxwgb] has joined #bitcoin-core-dev 16:07 < Lauda> sipa: Tested rescan 16:08 < Lauda> The balance is there, looks spendable. Received from in Transactions shows an empty label 16:09 < Lauda> Coin control shows nothing though. 16:12 < Randolf> With the help of folks in the NetBSD community, I can now compile bitcoind (and friends) in NetBSD 7.0 after making a few minor changes to 2 files. I also added one "doc" file which provides build instructions. Since I'm new to GitHub and this is my first contribution to bitcoin, I want to make 16:12 < Randolf> sure that I don't proceed incorrectly. Do I just create a new Pull Request so that peer-review can commence, or does peer-review come first? (2 files have minor changes, and 1 new file containing instructions was added for NetBSD users.) Thanks in advance. 16:13 < sipa> Randolf: unless you're very unsure about the approach, i suggest you just open a PR 16:13 -!- George [a2cac893@gateway/web/freenode/ip.162.202.200.147] has quit [Ping timeout: 260 seconds] 16:14 < Randolf> sipa: Okay, I assume PR is short of Pull Request, and not Problem Report? 16:14 < Lauda> Yes 16:14 < Randolf> s/short of/short for/ 16:14 < Randolf> Thank. 16:14 < Randolf> Thanks. 16:19 < sipa> yes, pull request 16:21 -!- Dizzle [~dizzle@108.171.182.16] has quit [Quit: Leaving...] 16:22 -!- dqx [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 16:26 -!- eck [~eck@fsf/member/eck] has quit [Quit: we out here] 16:31 -!- Chris_Stewart_5 [chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 240 seconds] 16:32 -!- mrfrasha [~mrfrasha@66-188-250-34.dhcp.eucl.wi.charter.com] has quit [Quit: mrfrasha] 16:35 < bitcoin-git> [bitcoin] randolf opened pull request #12125: Fix NetBSD compilation (master...master) https://github.com/bitcoin/bitcoin/pull/12125 16:50 -!- wacawacawaca [~user@cpe-172-101-144-51.rochester.res.rr.com] has joined #bitcoin-core-dev 16:55 -!- zautomata4 [~zautomata@unaffiliated/zautomata] has joined #bitcoin-core-dev 16:56 -!- zautomata3 [~zautomata@unaffiliated/zautomata] has quit [Ping timeout: 264 seconds] 16:59 -!- kexkey [~kexkey@173.209.63.133] has quit [Quit: Leaving] 16:59 -!- kexkey [~kexkey@173.209.63.133] has joined #bitcoin-core-dev 17:00 -!- zautomata [~zautomata@unaffiliated/zautomata] has joined #bitcoin-core-dev 17:01 -!- zautomata4 [~zautomata@unaffiliated/zautomata] has quit [Ping timeout: 240 seconds] 17:06 -!- dabura667 [~dabura667@153.142.228.110] has joined #bitcoin-core-dev 17:08 -!- mrfrasha [~mrfrasha@66-188-250-34.dhcp.eucl.wi.charter.com] has joined #bitcoin-core-dev 17:13 -!- HollowRiddler [~HRiddler@azi214.neoplus.adsl.tpnet.pl] has quit [Remote host closed the connection] 17:19 -!- Tennis [~Tennis@unaffiliated/tennis] has quit [Quit: Leaving] 17:20 -!- MrPaz [~PazPazPaz@104-52-130-247.lightspeed.cicril.sbcglobal.net] has joined #bitcoin-core-dev 17:22 < bitcoin-git> [bitcoin] sdaftuar opened pull request #12127: Remove unused mempool index (master...2018-01-remove-unused-index) https://github.com/bitcoin/bitcoin/pull/12127 17:28 -!- zautomata1 [~zautomata@unaffiliated/zautomata] has joined #bitcoin-core-dev 17:30 -!- zautomata [~zautomata@unaffiliated/zautomata] has quit [Ping timeout: 248 seconds] 17:36 -!- zautomata2 [~zautomata@unaffiliated/zautomata] has joined #bitcoin-core-dev 17:38 -!- zautomata1 [~zautomata@unaffiliated/zautomata] has quit [Ping timeout: 240 seconds] 17:44 -!- Murch [~murch@96-82-80-28-static.hfc.comcastbusiness.net] has quit [Quit: Snoozing.] 17:50 -!- Chris_Stewart_5 [chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 17:55 -!- jb55 [~jb55@2605:8d80:4c2:e2f2:a2af:bdff:fef0:c102] has joined #bitcoin-core-dev 17:58 -!- dqx [~dqx@unaffiliated/dqx] has quit [Remote host closed the connection] 17:58 -!- Danilo__ [~quassel@177.223.190.66] has quit [Remote host closed the connection] 18:10 -!- dqx [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 18:16 -!- dqx [~dqx@unaffiliated/dqx] has quit [Ping timeout: 268 seconds] 18:17 -!- zautomata3 [~zautomata@unaffiliated/zautomata] has joined #bitcoin-core-dev 18:18 -!- zautomata2 [~zautomata@unaffiliated/zautomata] has quit [Ping timeout: 240 seconds] 18:21 -!- jb55 [~jb55@2605:8d80:4c2:e2f2:a2af:bdff:fef0:c102] has quit [Ping timeout: 265 seconds] 18:21 -!- zautomata4 [~zautomata@unaffiliated/zautomata] has joined #bitcoin-core-dev 18:22 -!- mappum [sid43795@gateway/web/irccloud.com/x-zjpsiozdrqgsznkg] has quit [Ping timeout: 252 seconds] 18:23 -!- mrfrasha [~mrfrasha@66-188-250-34.dhcp.eucl.wi.charter.com] has quit [Quit: mrfrasha] 18:23 -!- zautomata3 [~zautomata@unaffiliated/zautomata] has quit [Ping timeout: 240 seconds] 18:23 -!- mappum [sid43795@gateway/web/irccloud.com/x-drhwikprlbtuojkw] has joined #bitcoin-core-dev 18:36 -!- eragmus [sid136308@gateway/web/irccloud.com/x-fpwzohvonqrweiue] has quit [Read error: Connection reset by peer] 18:37 -!- eragmus [sid136308@gateway/web/irccloud.com/x-cilmyuohcslxcvmm] has joined #bitcoin-core-dev 18:42 < kexkey> Hi! listunspent returns a list of UTXOs and some of them have an amount of 0. Weird. I thought I could use coin control to get rid of those UTXOs but looks like the feature uses UTXOs with amount > 0. How can I clean those UTXOs? Thanks! 18:49 < bitcoin-git> [bitcoin] jtimon opened pull request #12128: Refactor: One CBaseChainParams should be enough (master...b16-baseparams-nohierarchy) https://github.com/bitcoin/bitcoin/pull/12128 18:51 -!- belcher [~belcher@unaffiliated/belcher] has quit [Remote host closed the connection] 18:51 -!- hirish is now known as hirishaway 19:06 -!- kallewoof [~karl@67.205.138.199] has quit [Quit: WeeChat 1.9] 19:09 -!- zautomata4 [~zautomata@unaffiliated/zautomata] has quit [Ping timeout: 256 seconds] 19:10 -!- zautomata [~zautomata@unaffiliated/zautomata] has joined #bitcoin-core-dev 19:16 -!- zautomata1 [~zautomata@unaffiliated/zautomata] has joined #bitcoin-core-dev 19:16 -!- Giszmo [~leo@pc-204-28-214-201.cm.vtr.net] has quit [Quit: Leaving.] 19:17 -!- zautomata [~zautomata@unaffiliated/zautomata] has quit [Ping timeout: 265 seconds] 19:17 < meshcollider> keykey: the fifth parameter to listunspent is "query_options" which allows you to specify minimumAmount, is that what you are looking for? 19:18 < meshcollider> kexkey* 19:18 -!- Giszmo [~leo@pc-204-28-214-201.cm.vtr.net] has joined #bitcoin-core-dev 19:19 < meshcollider> kexkey: the fact that is shows 0 value UTXOs was exlicitly added in #6036 though, its not weird :) 19:19 < gribble> https://github.com/bitcoin/bitcoin/issues/6036 | Show zero value txouts in listunspent. by gmaxwell 路 Pull Request #6036 路 bitcoin/bitcoin 路 GitHub 19:19 -!- MrPaz [~PazPazPaz@104-52-130-247.lightspeed.cicril.sbcglobal.net] has quit [Quit: Leaving] 19:21 -!- dqx [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 19:21 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Remote host closed the connection] 19:21 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #bitcoin-core-dev 19:26 -!- warxhead [warxhead@c-73-243-180-191.hsd1.co.comcast.net] has joined #bitcoin-core-dev 19:29 -!- tknp [~tknp@unaffiliated/tknp] has quit [Quit: tknp] 19:29 -!- contrapumpkin [~copumpkin@haskell/developer/copumpkin] has joined #bitcoin-core-dev 19:31 -!- dqx [~dqx@unaffiliated/dqx] has quit [Remote host closed the connection] 19:34 -!- Chris_Stewart_5 [chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 260 seconds] 19:35 -!- tknp [~tknp@unaffiliated/tknp] has joined #bitcoin-core-dev 19:42 -!- dqx [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 19:43 -!- dqx [~dqx@unaffiliated/dqx] has quit [Remote host closed the connection] 19:55 -!- contrapumpkin [~copumpkin@haskell/developer/copumpkin] has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz鈥 20:06 -!- dqx [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 20:06 -!- dqx [~dqx@unaffiliated/dqx] has quit [Remote host closed the connection] 20:06 -!- dqx [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 20:09 < bitcoin-git> [bitcoin] threepehr opened pull request #12130: Update chain.h (master...dev) https://github.com/bitcoin/bitcoin/pull/12130 20:09 -!- Chris_Stewart_5 [chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 20:10 < bitcoin-git> [bitcoin] threepehr closed pull request #12130: Update chain.h (master...dev) https://github.com/bitcoin/bitcoin/pull/12130 20:18 -!- Chris_Stewart_5 [chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 248 seconds] 20:29 -!- dqx [~dqx@unaffiliated/dqx] has quit [Remote host closed the connection] 20:37 -!- Chris_Stewart_5 [chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 20:54 -!- kallewoof [~karl@fp96f94c66.tkyc515.ap.nuro.jp] has joined #bitcoin-core-dev 21:09 -!- Chris_Stewart_5 [chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 248 seconds] 21:10 -!- whphhg [~whphhg@unaffiliated/whphhg] has quit [Remote host closed the connection] 21:11 -!- whphhg [~whphhg@unaffiliated/whphhg] has joined #bitcoin-core-dev 21:26 -!- eeidoiii [4445a482@gateway/web/freenode/ip.68.69.164.130] has joined #bitcoin-core-dev 21:30 -!- zautomata1 [~zautomata@unaffiliated/zautomata] has quit [Ping timeout: 265 seconds] 21:31 -!- zautomata2 [~zautomata@unaffiliated/zautomata] has joined #bitcoin-core-dev 21:36 -!- eeidoiii [4445a482@gateway/web/freenode/ip.68.69.164.130] has quit [Quit: Page closed] 21:57 -!- dqx [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 22:02 -!- dqx [~dqx@unaffiliated/dqx] has quit [Ping timeout: 276 seconds] 22:38 -!- circ-user-IUGLY [~circuser-@219.146.242.179] has joined #bitcoin-core-dev 22:39 -!- circ-user-IUGLY is now known as anuby 22:46 < anuby> hi 22:47 < anuby> how to get test bitcoin 22:51 < echeveria> anuby: ask nicely. 22:51 < echeveria> (and post an address) 22:51 -!- mrfrasha [~mrfrasha@66-188-250-34.dhcp.eucl.wi.charter.com] has joined #bitcoin-core-dev 22:52 < anuby> @echeveria thx, mwqYfSNTb3onBSp9bnsdJXPpxDepB6Y6UD 22:53 < echeveria> you're now rich. 22:53 < anuby> thx 22:53 -!- wacawacawaca [~user@cpe-172-101-144-51.rochester.res.rr.com] has quit [Ping timeout: 248 seconds] 22:54 < anuby> @echeveria thank you 23:16 < kexkey> meshcollider, I should have said "surprising" instead of weird. :) Well, displaying 0 value UTXOs is expected, but creating them is surprising, I wonder what's the point of having 0 value UTXOs. Now is it possible to used them as inputs? I'll try that tomorrow. :) Thanks! 23:18 -!- tknp [~tknp@unaffiliated/tknp] has quit [Quit: tknp] 23:19 < kexkey> meshcollider, oh and thanks for the PR number, I'll have a look at it. :) 23:19 < meshcollider> kexkey: yeah I think the PR describes why better than i can 23:47 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Remote host closed the connection] 23:48 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #bitcoin-core-dev 23:49 -!- jimpo [~jimpo@ec2-52-42-179-84.us-west-2.compute.amazonaws.com] has quit [Ping timeout: 252 seconds] 23:49 -!- jimpo [~jimpo@ec2-52-42-179-84.us-west-2.compute.amazonaws.com] has joined #bitcoin-core-dev 23:50 -!- andytoshi [~apoelstra@unaffiliated/andytoshi] has quit [Ping timeout: 240 seconds] 23:50 -!- andytoshi [~apoelstra@wpsoftware.net] has joined #bitcoin-core-dev