--- Day changed Mon Dec 25 2017 00:04 -!- arioBarzan [~arioBarza@unaffiliated/ariobarzan] has left #bitcoin-core-dev ["Leaving..."] 00:10 -!- quantbot [~quantbot@47.18.93.152] has joined #bitcoin-core-dev 00:11 -!- Syde [~root@64.140.119.122] has quit [Remote host closed the connection] 00:14 -!- quantbot [~quantbot@47.18.93.152] has quit [Ping timeout: 256 seconds] 00:14 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-wfjnfpyxhxjmyswx] has joined #bitcoin-core-dev 00:23 -!- zshlyk [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 00:24 -!- zshlyk [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 00:28 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has joined #bitcoin-core-dev 01:06 -!- BTC^ [~jk@178-164-109.83.3p.ntebredband.no] has quit [Ping timeout: 260 seconds] 01:19 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has quit [Quit: Going offline, see ya! (www.adiirc.com)] 01:24 -!- zshlyk [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 01:25 -!- zshlyk [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 01:25 -!- aguycalled [~aguycalle@37.120.32.46] has joined #bitcoin-core-dev 01:37 -!- imnothreat [~billiondo@178.71.56.191] has joined #bitcoin-core-dev 01:51 -!- goatpig [56f75683@gateway/web/freenode/ip.86.247.86.131] has quit [Quit: Page closed] 01:56 -!- akash_ [c4cf78cf@gateway/web/freenode/ip.196.207.120.207] has joined #bitcoin-core-dev 01:57 < akash_> i am expert in giving suggestion how to stop frauds in bitcoin transaction 02:03 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-yrthaboimxzjqepl] has quit [Quit: Connection closed for inactivity] 02:03 -!- zshlyk [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 02:05 -!- zshlyk [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 02:09 -!- akash_ [c4cf78cf@gateway/web/freenode/ip.196.207.120.207] has quit [Ping timeout: 260 seconds] 02:25 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Remote host closed the connection] 02:25 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #bitcoin-core-dev 02:40 -!- imnothreat [~billiondo@178.71.56.191] has quit [Quit: Ex-Chat] 03:04 -!- zshlyk [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 03:04 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Remote host closed the connection] 03:05 -!- zshlyk [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 03:05 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #bitcoin-core-dev 03:10 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Remote host closed the connection] 03:11 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #bitcoin-core-dev 03:19 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-qkpubytoffholjnw] has joined #bitcoin-core-dev 03:19 -!- meshcoll- is now known as mesh_ 03:20 -!- zshlyk [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 03:21 -!- zshlyk [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 03:45 -!- JoeDoe358 [584aded7@gateway/web/freenode/ip.88.74.222.215] has joined #bitcoin-core-dev 03:47 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 03:47 -!- JoeDoe358 [584aded7@gateway/web/freenode/ip.88.74.222.215] has quit [Client Quit] 03:48 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection] 03:49 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 03:52 -!- aguycall_ [~aguycalle@159.89.4.33] has joined #bitcoin-core-dev 03:55 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has quit [Remote host closed the connection] 03:55 -!- aguycalled [~aguycalle@37.120.32.46] has quit [Ping timeout: 268 seconds] 03:56 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has joined #bitcoin-core-dev 04:10 -!- billbrofaggins [792cf03b@gateway/web/freenode/ip.121.44.240.59] has joined #bitcoin-core-dev 04:15 -!- billbrofaggins [792cf03b@gateway/web/freenode/ip.121.44.240.59] has left #bitcoin-core-dev [] 04:16 -!- ibbl564rk75eu [~ibbl564rk@62.102.148.162] has joined #bitcoin-core-dev 04:22 -!- ibbl564rk75eu [~ibbl564rk@62.102.148.162] has quit [Quit: Leaving] 04:25 -!- Sentineo [~Undefined@unaffiliated/sentineo] has quit [Remote host closed the connection] 04:41 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #bitcoin-core-dev 04:42 -!- Guest5165 [~Andre@170.239.109.88] has joined #bitcoin-core-dev 04:42 -!- Guest5165 [~Andre@170.239.109.88] has quit [Client Quit] 04:52 -!- laurentmt [~Thunderbi@176.158.157.202] has joined #bitcoin-core-dev 05:00 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Ping timeout: 272 seconds] 05:03 -!- laurentmt [~Thunderbi@176.158.157.202] has quit [Quit: laurentmt] 05:08 -!- zshlyk [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 05:09 -!- zshlyk [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 05:10 -!- zshlyk [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 05:10 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-dev 05:11 -!- zshlyk [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 05:12 -!- Suley [458e9382@gateway/web/freenode/ip.69.142.147.130] has joined #bitcoin-core-dev 05:19 -!- Suley [458e9382@gateway/web/freenode/ip.69.142.147.130] has quit [Ping timeout: 260 seconds] 05:23 -!- zshlyk [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 05:24 -!- ZiNC [~zinc@5.102.224.109] has joined #bitcoin-core-dev 05:24 < ZiNC> Hi. 05:24 -!- zshlyk [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 05:25 -!- aguycalled [~aguycalle@37.120.32.46] has joined #bitcoin-core-dev 05:29 -!- aguycall_ [~aguycalle@159.89.4.33] has quit [Ping timeout: 248 seconds] 05:31 < ZiNC> Are there debug symbols available for download? 05:41 -!- btcdrak [uid234579@gateway/web/irccloud.com/x-fslcloezveyvgaxi] has quit [Quit: Connection closed for inactivity] 05:55 -!- instagibbs [~instagibb@pool-100-15-116-35.washdc.fios.verizon.net] has quit [Ping timeout: 248 seconds] 05:56 -!- instagibbs [~instagibb@pool-100-15-116-35.washdc.fios.verizon.net] has joined #bitcoin-core-dev 05:59 -!- laurentmt [~Thunderbi@176.158.157.202] has joined #bitcoin-core-dev 06:02 -!- laurentmt [~Thunderbi@176.158.157.202] has quit [Client Quit] 06:04 -!- zshlyk [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 06:05 -!- zshlyk [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 06:10 -!- aguycalled [~aguycalle@37.120.32.46] has quit [Read error: Connection reset by peer] 06:10 -!- aguycalled [~aguycalle@37.120.32.46] has joined #bitcoin-core-dev 06:19 -!- quantbot [~quantbot@47.18.93.152] has joined #bitcoin-core-dev 06:19 -!- quantbot [~quantbot@47.18.93.152] has quit [Remote host closed the connection] 06:22 -!- laurentmt [~Thunderbi@176.158.157.202] has joined #bitcoin-core-dev 06:23 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-qkpubytoffholjnw] has quit [Quit: Connection closed for inactivity] 06:24 -!- Anant [31233780@gateway/web/freenode/ip.49.35.55.128] has joined #bitcoin-core-dev 06:24 < Anant> help 06:24 < Anant> how to exchange bitcoin with other coins? 06:25 < Anant> earn exchange fees? 06:26 < sipa> Anant: #bitcoin 06:26 -!- Anant [31233780@gateway/web/freenode/ip.49.35.55.128] has quit [Client Quit] 06:27 -!- zshlyk [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 06:28 -!- zshlyk [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 06:30 -!- CubicEarths [~cubiceart@c-73-68-232-79.hsd1.ma.comcast.net] has joined #bitcoin-core-dev 06:31 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 248 seconds] 06:36 -!- larafale [~larafale@ax213-1-82-66-157-194.fbx.proxad.net] has joined #bitcoin-core-dev 06:42 -!- btcdrak [uid234579@gateway/web/irccloud.com/x-omemanxpzastizcz] has joined #bitcoin-core-dev 06:57 -!- Murch [~murch@c-73-223-113-121.hsd1.ca.comcast.net] has joined #bitcoin-core-dev 07:05 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 07:13 -!- laurentmt [~Thunderbi@176.158.157.202] has quit [Quit: laurentmt] 07:22 -!- tyrick [~tyrick@ip70-162-128-254.ph.ph.cox.net] has joined #bitcoin-core-dev 07:23 -!- zshlyk [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 07:24 -!- yoctopede [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 07:30 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 07:41 -!- quantbot [~quantbot@47.18.93.152] has joined #bitcoin-core-dev 07:41 -!- quantbot [~quantbot@47.18.93.152] has quit [Remote host closed the connection] 07:43 -!- CubicEarths [~cubiceart@c-73-68-232-79.hsd1.ma.comcast.net] has quit [] 07:53 -!- wxss [~user@194.88.105.17] has quit [Ping timeout: 260 seconds] 07:54 -!- wxss [~user@194.88.105.17] has joined #bitcoin-core-dev 07:57 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has quit [Remote host closed the connection] 07:58 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has joined #bitcoin-core-dev 08:02 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has joined #bitcoin-core-dev 08:11 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has quit [Ping timeout: 260 seconds] 08:12 -!- aguycalled [~aguycalle@37.120.32.46] has quit [Read error: Connection reset by peer] 08:12 -!- aguycalled [~aguycalle@37.120.32.46] has joined #bitcoin-core-dev 08:13 -!- satwo [~textual@2602:306:378a:6fb0:541f:9dfb:420b:9e1c] has joined #bitcoin-core-dev 08:16 -!- yoctopede [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 08:17 -!- yoctopede [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 08:19 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 248 seconds] 08:22 -!- wxss [~user@194.88.105.17] has quit [Quit: leaving] 08:29 -!- yoctopede [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 08:30 -!- yoctopede [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 08:31 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 272 seconds] 08:44 -!- quantbot [~quantbot@47.18.93.152] has joined #bitcoin-core-dev 08:44 -!- quantbot [~quantbot@47.18.93.152] has quit [Remote host closed the connection] 08:46 -!- wxss [~user@194.88.105.17] has joined #bitcoin-core-dev 08:50 -!- Murch [~murch@c-73-223-113-121.hsd1.ca.comcast.net] has quit [Quit: Snoozing.] 08:51 -!- btcdrak [uid234579@gateway/web/irccloud.com/x-omemanxpzastizcz] has quit [Quit: Connection closed for inactivity] 08:52 -!- quantbot [~quantbot@47.18.93.152] has joined #bitcoin-core-dev 08:52 -!- quantbot [~quantbot@47.18.93.152] has quit [Remote host closed the connection] 09:10 -!- yoctopede [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 09:11 -!- yoctopede [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 09:11 -!- yoctopede [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 09:12 -!- yoctopede [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 09:31 -!- Thamer [~tessit@46.186.192.162] has joined #bitcoin-core-dev 09:43 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Remote host closed the connection] 09:43 -!- arubi_ [~ese168@gateway/tor-sasl/ese168] has joined #bitcoin-core-dev 09:44 -!- belcher [~belcher@unaffiliated/belcher] has joined #bitcoin-core-dev 09:45 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has joined #bitcoin-core-dev 09:45 -!- arubi_ is now known as arubi 09:46 -!- rabidus [~rabidus@91-145-115-22.bb.dnainternet.fi] has quit [Ping timeout: 276 seconds] 10:05 -!- Danilo__ [~quassel@179.97.232.153] has joined #bitcoin-core-dev 10:16 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 10:18 -!- yoctopede [~zshlyk@gateway/tor-sasl/intcat] has quit [Ping timeout: 272 seconds] 10:18 -!- vasp [~antony@modemcable139.60-131-66.mc.videotron.ca] has joined #bitcoin-core-dev 10:26 -!- contrapumpkin [~copumpkin@haskell/developer/copumpkin] has quit [Quit: Textual IRC Client: www.textualapp.com] 10:32 -!- rabidus [~rabidus@91-145-115-22.bb.dnainternet.fi] has joined #bitcoin-core-dev 10:33 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 10:40 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 10:45 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 10:54 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 10:58 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [] 10:59 -!- goatpig [56f75683@gateway/web/freenode/ip.86.247.86.131] has joined #bitcoin-core-dev 11:09 -!- GoldenBear [~GoldenBea@hwsrv-209636.hostwindsdns.com] has quit [Quit: bai] 11:20 -!- contrapumpkin [~copumpkin@haskell/developer/copumpkin] has joined #bitcoin-core-dev 11:21 -!- GoldenBear [~GoldenBea@hwsrv-209636.hostwindsdns.com] has joined #bitcoin-core-dev 11:31 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Remote host closed the connection] 11:43 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has joined #bitcoin-core-dev 11:54 -!- Murch [~murch@73.223.113.121] has joined #bitcoin-core-dev 12:04 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 248 seconds] 12:18 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 12:19 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 12:27 -!- Randolf [~randolf@96.53.47.42] has quit [Ping timeout: 240 seconds] 12:29 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 12:30 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 12:43 -!- Danilo___ [~quassel@179.97.232.153] has joined #bitcoin-core-dev 12:45 -!- Danilo__ [~quassel@179.97.232.153] has quit [Ping timeout: 252 seconds] 12:48 -!- aguycalled [~aguycalle@37.120.32.46] has quit [] 12:51 -!- Danilo___ [~quassel@179.97.232.153] has quit [Remote host closed the connection] 13:01 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 13:02 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection] 13:03 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 13:03 -!- lnostdal [~lnostdal@62.90-149-73.nextgentel.com] has quit [Quit: https://localbitcoins.com/ad/647341/cash-out-your-bitcoins-any-altcoin-eth-xrp-ripple-xmr-monero-iota] 13:04 -!- satwo [~textual@2602:306:378a:6fb0:541f:9dfb:420b:9e1c] has quit [Ping timeout: 265 seconds] 13:10 -!- laurentmt [~Thunderbi@176.158.157.202] has joined #bitcoin-core-dev 13:24 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 13:25 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 13:30 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 13:34 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 13:37 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection] 13:38 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 13:39 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection] 13:41 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has quit [Ping timeout: 252 seconds] 13:58 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-bvqxowminpgtkuaf] has joined #bitcoin-core-dev 13:58 -!- teste30 [bd1b29dd@gateway/web/freenode/ip.189.27.41.221] has joined #bitcoin-core-dev 14:01 -!- LucasMZanella_ [b34efc5c@gateway/web/freenode/ip.179.78.252.92] has joined #bitcoin-core-dev 14:02 < LucasMZanella_> Why we must reference the entire txid on a transaction? Could somebody give a feedback on this idea of mine? https://bitcoin.stackexchange.com/questions/66464/why-we-must-reference-the-entire-txid-for-each-output-we-want-to-spend 14:05 -!- GoldenBear [~GoldenBea@hwsrv-209636.hostwindsdns.com] has quit [Quit: bai] 14:05 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 14:06 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 14:08 -!- Randolf [~randolf@96.53.47.42] has joined #bitcoin-core-dev 14:09 < goatpig> you are introducing some serious complexity and attack vectors with that kind of approach 14:13 < bitcoin-git> [bitcoin] blockcash opened pull request #12022: test (master...master) https://github.com/bitcoin/bitcoin/pull/12022 14:15 -!- laurentmt [~Thunderbi@176.158.157.202] has quit [Quit: laurentmt] 14:16 < bitcoin-git> [bitcoin] sipa closed pull request #12022: test (master...master) https://github.com/bitcoin/bitcoin/pull/12022 14:18 < LucasMZanella_> The only attack I can think of is someone 'mining' a transaction until its txid has the same first digits as another. However there's a minimum number of digits that we can choose that would guarantee a million year of brute forcing 14:19 < goatpig> not with segwit 14:20 < sipa> LucasMZanella_: you'd need at least 128 bits 14:20 < LucasMZanella_> What is different with segwit? 14:20 < sipa> otherwise the security of referencing old transactions would be below that of the digital signatures 14:20 < goatpig> the outpoint is taking the wtxid instead of the txid 14:20 < sipa> so you can probabbly save 16 bytes per txin 14:20 < goatpig> the wtxid has no sig in it 14:20 < LucasMZanella_> 128 bits is already good, isn't it? 14:20 < goatpig> therefor it's easy to "mine" a collision 14:21 < sipa> goatpig: no, txid 14:21 < goatpig> hmm am i getting confused here? 14:21 < sipa> yes 14:21 < sipa> wtxid = inclides witness, txid = no witness 14:21 < goatpig> oh ok 14:21 < goatpig> well anyways 14:22 < sipa> it's also irrelevant in this discussion 14:22 < goatpig> sw refers to outpoints by the unmalleable id 14:22 < goatpig> well it's entirely easier to produce collision the txid than the wtxid 14:22 < goatpig> but sure, that's orhtogonal 14:22 < sipa> LucasMZanella_: yes, perhaps. it's not worth the effort to change it though 14:23 < goatpig> you could construct attacks where you force tons of unnecessary hashing per tx 14:23 < sipa> no 14:23 < sipa> hmm, nevermind 14:24 < sipa> you need collision resistance 14:24 < sipa> goatpig: you're right 14:24 < goatpig> yeah which has you increase the size of your hash "shortcuts" and kills the size benefit anyways 14:24 < sipa> LucasMZanella_: disregard what i said; you really need 256-bit hashes in transactions 14:25 < goatpig> while increasing the cost size of low input tx 14:25 < LucasMZanella_> How much hashes we need to get a sha256 output to begin with 7 chosen digits? 14:25 < goatpig> look at miners 14:25 < sipa> LucasMZanella_: for a collision attack you only need half 14:25 < LucasMZanella_> Half of what? 14:25 < sipa> the attacker may be the one doing the reference, which can refer to a transaction that he did a grinsing on before publishing 14:25 < goatpig> birthday attack 14:26 < goatpig> well basically you'd mine lots of tx with the starting 7 bytes in the txid 14:26 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 14:26 < goatpig> then create one tx spending like 1000 inputs 14:26 < goatpig> however many you get 14:26 < goatpig> and use the the first input as your collided hash 14:26 < goatpig> forcing tons of hashing for no reason 14:26 < sipa> goatpig: it's far worse 14:26 < goatpig> then to reproduce the attack 14:27 < sipa> you can create a consensus failure 14:27 < goatpig> ive thought of that but cant come with an example of that attack on the top of my head 14:27 < sipa> by creating two transactions with the same starting bits 14:27 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 14:27 < sipa> and then spending it 14:28 < sipa> making sure one is valid and the other is invalid 14:28 < goatpig> you mean while unconfirmed? 14:28 < sipa> hmm, but the chain provides an ordering of course 14:28 < goatpig> his proposal is to basically attach a merkle root in there 14:29 < goatpig> with the "shortcuts" 14:29 < goatpig> i tihnk that's enough to remain deterministic, therefor avoid consensus failures 14:29 < goatpig> but it's easily attackable 14:30 < sipa> fair, it's doable in a way that does not cause consensus failure 14:30 < goatpig> but there's also the cost of increasing the size of low input tx 14:30 < goatpig> i guess you could "modulate" this, have tx version that uses this proposal to cut on large tx 14:31 < goatpig> but even then, taht does not reduce the attack vector 14:31 < sipa> it's also a terrible hard fork 14:31 < goatpig> couldnt you softfork that ala segwit? 14:32 < sipa> (as in: not just miners and nodes, but every piece of software will fail without modification) 14:32 < sipa> no 14:32 < LucasMZanella_> Could be a soft one 14:32 < goatpig> i guess you can't pull the segwit trick twice 14:32 < sipa> segwit didn't remove any existing structures 14:32 < sipa> it just added an optional new ones 14:32 -!- GoldenBear [~GoldenBea@hwsrv-209636.hostwindsdns.com] has joined #bitcoin-core-dev 14:32 < sipa> truncating txids is not something that fits into that 14:32 < goatpig> no but (correct me if im wrong) to a not update node, the marker and flag of a segwit tx makes the tx body invisible to the node 14:33 < sipa> you can't remove the txids without breaking things 14:33 < LucasMZanella_> Transactions could maintain the structure, but the txid being referenced would be the merkle root. And the 7 digits each would be added inside script 14:33 < sipa> goatpig: that's just serialization 14:33 < goatpig> at any rate i wouldnt want that kind of change done without a hf 14:33 < sipa> i'm not even talking about that 14:34 < goatpig> sipa: if you can make the content of the tx invisible to older nodes, you can shove anything you want in there basically 14:34 < sipa> then you don't have any transactions left 14:34 < sipa> sure, you can move everything to an extension block 14:34 < sipa> that's always possible 14:35 < sipa> but that doesn't share anything anymore with existing nodes 14:35 < sipa> they wouldn't even see the transactions of the new system anymore 14:36 < LucasMZanella_> Yeah, the old nodes would invalidate the transaction because txid is nonsense 14:36 < goatpig> sipa: a bit too aggressive i guess =D 14:36 < sipa> LucasMZanella_: what is the objective? 14:36 < goatpig> optimize block space usage im guessing 14:37 < sipa> if it's just bandwidth/storage, a new serialization for transaction could be constructed that does what you're saying (and more) 14:37 < sipa> but without actually modifying the transactions 14:37 < sipa> only changing how they're stored 14:37 < sipa> which means that the full txids still count towards the weight limit 14:37 < LucasMZanella_> Objective of what? The idea was to be able to spend from lots of txs without having to add one signature + one txid for each. My idea would reduce txid usage in transactions, and schnoor would reduce signature usage 14:37 < sipa> but still reclaim disk space and bandwidth 14:38 < sipa> in a completely optional and compatible way 14:39 < goatpig> in taht spirit, could there be an alley to use block height + tx# instead of hash for old, buried outputs in the future? 14:39 < sipa> monero uses a pretty extreme version of what you're suggesting iirc; they refer to previous outputs just using the position in the chain when they were created 14:40 < sipa> goatpig: requires a nasty index, unfortunately 14:40 < sipa> but yes 14:41 < goatpig> sipa: index for what purpose? ordering tx per block height? i mean you konw that height won't change if we're talkign blocks with 100k+ confs 14:41 < LucasMZanella_> If you use new addresses everytime someone is going to send you something, then moving a large quantity of your funds is going to take a lot of txids and signatures. Schnoor already condenses signs, my idea was to condense txids 14:42 < bitcoin-git> [bitcoin] janstary opened pull request #12023: update the OpenBSD build guide (master...openbsd) https://github.com/bitcoin/bitcoin/pull/12023 14:43 < LucasMZanella_> I thought this could be done with a soft fork but now I don't know anymore. I guess old nodes would always miss transactions 14:43 < LucasMZanella_> as you said :) 14:43 < goatpig> LucasMZanella_: you'd have to make the tx body invisible to old nodes 14:43 < goatpig> that's too extreme 14:45 -!- Cheeseo [~Cheeseo@unaffiliated/cheeseo] has joined #bitcoin-core-dev 14:46 < LucasMZanella_> I thought as using an entire txid and add the merkle root + other txids inside the script, but old nodes would not accept txids inside the script 14:46 < LucasMZanella_> I guess it can only be done with a hardfork by changing the transaction format version 14:46 < goatpig> whichever way you do it, you are introducing computational overhead that is exploitable 14:47 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 14:47 < LucasMZanella_> Yes, but we could make the required n digits vary according to the block difficulty 14:48 < LucasMZanella_> If a person is able to exploit the n digits then he would be able to mine 51% or something like that 14:49 < goatpig> sure but you to consider that it would then proportionally increase the size of tx with less inputs 14:50 < goatpig> cause you are always carrying at least 32 bytes worth of merkle + compressed ids 14:50 < LucasMZanella_> Why it would increase? 14:50 < goatpig> in your current proposal 14:50 < goatpig> a single input tx is already larger 14:50 < goatpig> cause it needs a merkle + 7bytes for 1 compressed id 14:50 < LucasMZanella_> The merkle root would substitute the txid at all in the new transaction format 14:51 < LucasMZanella_> If there is only one input, the merkle root would match the txid being referenced 14:51 < goatpig> you need an id per output + the merkle 14:51 < goatpig> yes but as soon as you hit over 128bits compressed ids 14:51 < goatpig> now 2 inputs tx are larger than the legacy outpoints 14:53 < LucasMZanella_> Can't follow your thinking, I'm confused 14:53 < goatpig> you need the merkle root per tx 14:53 < goatpig> + 1 id per input 14:53 < goatpig> if your ids are 129bits 14:54 < goatpig> your 2 input tx is now 258bits of outpoints + 256bit of merkle 14:54 < goatpig> currently a 2 inputs is 256x2 bits of outpoints 14:54 < goatpig> not including the outpoint id in there cause it's constant accross models 14:54 < LucasMZanella_> Then for that case the person could use the old transaction format 14:55 < goatpig> now you have discussion of whether that's desirable at all 14:55 < goatpig> having 2 models that overlap 14:55 -!- btcdrak [uid234579@gateway/web/irccloud.com/x-dgncxndthnxojmkv] has joined #bitcoin-core-dev 14:56 < LucasMZanella_> Wouldn't the model be inneficient just for 2 inputs? 14:56 < goatpig> it would be inneficient generally for low input tx 14:56 < goatpig> but there's a debate to be had 14:56 < LucasMZanella_> I don't think there's a problem in using 2 different transaction formats 14:56 < goatpig> of how desirable such a massive change (hf and all) is when you compare the complexity to implement and operate vs the benefit 14:57 < goatpig> i have not thought about whether that is a problem or not 14:57 < goatpig> but i'd rather err on the side of caution and not introduce complexity 14:57 < LucasMZanella_> Yes, but if we're going to ever hard fork for some other reason, this could be included 14:58 < LucasMZanella_> I agree with you, but the benefits are huge. Coinjoin, being able to still use one address per transaction, and less fees (the greatest problem) 14:58 < goatpig> if it can demonstrated that it is safe 14:58 < goatpig> and fees arent a problem that needs to be addressed at consensus level 14:58 < goatpig> if they are a problem at all (i dont believe they are) 14:59 -!- Hej [5760eca2@gateway/web/freenode/ip.87.96.236.162] has joined #bitcoin-core-dev 15:04 -!- Hej [5760eca2@gateway/web/freenode/ip.87.96.236.162] has quit [Ping timeout: 260 seconds] 15:05 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has quit [Quit: Going offline, see ya! (www.adiirc.com)] 15:08 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 15:09 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 15:10 -!- Cheeseo [~Cheeseo@unaffiliated/cheeseo] has quit [Ping timeout: 265 seconds] 15:16 -!- LucasMZanella_ [b34efc5c@gateway/web/freenode/ip.179.78.252.92] has quit [Ping timeout: 260 seconds] 15:20 -!- teste30 [bd1b29dd@gateway/web/freenode/ip.189.27.41.221] has quit [Ping timeout: 260 seconds] 15:23 -!- ZiNC [~zinc@5.102.224.109] has quit [] 15:29 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 15:30 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 15:35 -!- echonaut7 [~echonaut@46.101.192.134] has quit [Remote host closed the connection] 15:35 -!- echonaut [~echonaut@46.101.192.134] has joined #bitcoin-core-dev 15:39 -!- larafale [~larafale@ax213-1-82-66-157-194.fbx.proxad.net] has quit [Remote host closed the connection] 15:43 -!- Danilo__ [~quassel@179.97.232.153] has joined #bitcoin-core-dev 15:43 -!- harrymm [~harrymm@104.207.83.57] has quit [] 15:48 -!- harrymm [~harrymm@104.207.83.37] has joined #bitcoin-core-dev 15:59 -!- mandric [~mandric@108-228-58-104.lightspeed.cicril.sbcglobal.net] has joined #bitcoin-core-dev 16:04 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 16:08 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 16:13 -!- Giszmo [~leo@pc-204-28-214-201.cm.vtr.net] has joined #bitcoin-core-dev 16:13 -!- mandric [~mandric@108-228-58-104.lightspeed.cicril.sbcglobal.net] has quit [Quit: Computer has gone to sleep.] 16:14 -!- harrymm [~harrymm@104.207.83.37] has quit [Ping timeout: 252 seconds] 16:27 -!- harrymm [~harrymm@104.207.83.14] has joined #bitcoin-core-dev 16:44 -!- wangyuan [72f1b203@gateway/web/freenode/ip.114.241.178.3] has joined #bitcoin-core-dev 16:46 -!- wangyuan [72f1b203@gateway/web/freenode/ip.114.241.178.3] has quit [Client Quit] 16:49 -!- Randolf [~randolf@96.53.47.42] has quit [Ping timeout: 248 seconds] 16:56 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has joined #bitcoin-core-dev 17:05 -!- btcdrak [uid234579@gateway/web/irccloud.com/x-dgncxndthnxojmkv] has quit [Quit: Connection closed for inactivity] 17:13 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 268 seconds] 17:14 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 17:15 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 17:21 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 17:21 -!- Scrx [881cd74c@gateway/web/freenode/ip.136.28.215.76] has joined #bitcoin-core-dev 17:22 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has quit [Remote host closed the connection] 17:22 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 17:22 < Scrx> Hello. I have a question regarding miners broadcasting blocks. What would happen if a miner wants to spend its resources to deliberately slow down another miner, by broadcasting invalid blocks to the network (or specifically to the full nodes it connects to)? 17:25 < Scrx> In other words, if a miner X wants to impact Y, it can connect to it and continuously broadcast bogus messages. What would be such impact in Y, considering all X is trying to do is not impact the network but simply impact Y. 17:32 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-wfjnfpyxhxjmyswx] has quit [Quit: Connection closed for inactivity] 17:33 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving] 17:34 < echeveria> Scrx: the proof of work is able to be validated in milliseconds. more a question for #bitcoin. 17:39 -!- harrymm [~harrymm@104.207.83.14] has quit [Ping timeout: 252 seconds] 17:43 < bitcoin-git> [bitcoin] achow101 opened pull request #12024: Remove most recent transaction timestamp stuff from nTimeSmart (master...fix-timesmart) https://github.com/bitcoin/bitcoin/pull/12024 17:44 -!- Scrx [881cd74c@gateway/web/freenode/ip.136.28.215.76] has quit [Ping timeout: 260 seconds] 17:52 -!- harrymm [~harrymm@104.207.83.57] has joined #bitcoin-core-dev 18:24 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 18:25 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 18:25 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 18:30 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 18:44 -!- unholymachine [~quassel@2601:8c:c003:9f16:4930:bba7:1993:fc78] has quit [Remote host closed the connection] 18:46 -!- unholymachine [~quassel@2601:8c:c003:9f16:cc1f:721c:6249:48c] has joined #bitcoin-core-dev 18:46 -!- Sinclair6 [~sinclair6@2602:306:c4b1:2570:2939:50bb:9e05:9484] has quit [Remote host closed the connection] 18:51 -!- Randolf [~randolf@S01066872516d2e74.vc.shawcable.net] has joined #bitcoin-core-dev 18:55 -!- Randolf [~randolf@S01066872516d2e74.vc.shawcable.net] has quit [Ping timeout: 260 seconds] 19:17 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 19:18 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 19:18 -!- Randolf [~randolf@S01066872516d2e74.vc.shawcable.net] has joined #bitcoin-core-dev 19:42 -!- Randolf [~randolf@S01066872516d2e74.vc.shawcable.net] has quit [Ping timeout: 248 seconds] 19:50 -!- CubicEarths [~cubiceart@c-73-68-232-79.hsd1.ma.comcast.net] has joined #bitcoin-core-dev 20:02 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 20:03 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 20:05 -!- CubicEarths [~cubiceart@c-73-68-232-79.hsd1.ma.comcast.net] has quit [] 20:12 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 20:13 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 20:16 -!- CubicEarths [~cubiceart@c-73-68-232-79.hsd1.ma.comcast.net] has joined #bitcoin-core-dev 20:21 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 20:22 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 20:22 -!- Giszmo [~leo@pc-204-28-214-201.cm.vtr.net] has quit [Quit: Leaving.] 20:29 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 20:38 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection] 20:38 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-dev 20:57 -!- Danilo__ [~quassel@179.97.232.153] has quit [Remote host closed the connection] 21:08 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has joined #bitcoin-core-dev 21:09 < echeveria> can anybody run through the justification of CreateNewBlock() verifying txins? 21:09 < echeveria> items in the mempool being valid seems like a pretty solid assumption. 21:18 -!- t0adst00l [~sluggo@38.95.111.67] has joined #bitcoin-core-dev 21:19 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 21:20 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 21:21 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has quit [Remote host closed the connection] 21:21 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 21:21 -!- quantbot [~quantbot@47.18.93.152] has joined #bitcoin-core-dev 21:22 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has joined #bitcoin-core-dev 21:22 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 21:24 -!- CubicEarths [~cubiceart@c-73-68-232-79.hsd1.ma.comcast.net] has quit [] 21:24 -!- pkx2 [~pkx@unaffiliated/pkx] has joined #bitcoin-core-dev 21:28 -!- t0adst00l [~sluggo@38.95.111.67] has quit [Quit: Leaving] 21:34 -!- pkx2 [~pkx@unaffiliated/pkx] has quit [Read error: Connection reset by peer] 21:38 -!- t0adst00l [~sluggo@38.95.111.67] has joined #bitcoin-core-dev 21:40 -!- t0adst00l [~sluggo@38.95.111.67] has quit [Read error: Connection reset by peer] 21:45 -!- profall [sid29922@gateway/web/irccloud.com/x-yitguvvwqklfxett] has quit [Quit: Connection closed for inactivity] 21:45 -!- pkx2 [~pkx@unaffiliated/pkx] has joined #bitcoin-core-dev 21:56 -!- t0adst00l [~sluggo@38.95.111.67] has joined #bitcoin-core-dev 21:57 -!- quantbot [~quantbot@47.18.93.152] has quit [Read error: Connection reset by peer] 22:02 -!- t0adst00l [~sluggo@38.95.111.67] has quit [Quit: Leaving] 22:06 < gmaxwell> echeveria: it is not a solid assumption, there are been issues in the past on several occasions that resulted in the mempool returning consensus inconsistent results. 22:08 < gmaxwell> This is especially easy to happen with reorgs and changing consensus rules, doubly so since some miners go and modify the transaction selection logic. 22:09 < gmaxwell> There is a secondary benefit of running that validation: it reheats the caches after a flush. 22:10 < echeveria> feels expensive, but I guess that's reasonable. 22:11 < gmaxwell> everything is cached, so it's not very expensive. 22:11 < echeveria> what's 80ms between friends I guess. 22:12 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 240 seconds] 22:13 < gmaxwell> and considering that virtually all SPV wallets show 'confirmed' at a single confirmation and don't distinguish one from more than one, ... and there have been at least two invalid blocks created by miners in the last year that would have been stopped by this kind of check ... 22:13 -!- grio [~grio@ip68-102-158-172.ks.ok.cox.net] has joined #bitcoin-core-dev 22:14 -!- Randolf [~randolf@96.53.47.42] has joined #bitcoin-core-dev 22:14 < gmaxwell> 80ms? you mining on a rpi? :P it's 23ms here on a system from 2011. 22:14 < echeveria> 80 for the total assembly and validation, it's lower on proper hardware. 22:16 -!- Danilo__ [~quassel@179.97.232.153] has joined #bitcoin-core-dev 22:16 -!- t0adst00l [~sluggo@38.95.111.67] has joined #bitcoin-core-dev 22:16 < gmaxwell> echeveria: yea, 36.4ms here. 22:17 -!- pkx2 [~pkx@unaffiliated/pkx] has quit [Remote host closed the connection] 22:18 -!- pkx2 [~pkx@unaffiliated/pkx] has joined #bitcoin-core-dev 22:18 -!- t0adst00l [~sluggo@38.95.111.67] has quit [Remote host closed the connection] 22:18 -!- grio [~grio@ip68-102-158-172.ks.ok.cox.net] has quit [Quit: Leaving] 22:19 < echeveria> the underlying machine does really seem matter with getting performance bitcoind. 22:23 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 22:24 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 22:28 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 22:29 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 22:30 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has quit [Quit: WeeChat 1.9.1] 22:30 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev 22:35 -!- prometheus_falli [~sluggo@gateway/tor-sasl/prometheusfalli/x-99064168] has joined #bitcoin-core-dev 23:03 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 23:05 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 23:06 -!- t0adst00l [~sluggo@gateway/tor-sasl/prometheusfalli/x-99064168] has joined #bitcoin-core-dev 23:12 -!- t0adst00l [~sluggo@gateway/tor-sasl/prometheusfalli/x-99064168] has quit [Quit: Leaving] 23:12 -!- t0adst00l [~sluggo@gateway/tor-sasl/prometheusfalli/x-99064168] has joined #bitcoin-core-dev 23:23 -!- prometheus_falli [~sluggo@gateway/tor-sasl/prometheusfalli/x-99064168] has quit [Quit: Leaving] 23:24 -!- prometheus_falli [~sluggo@gateway/tor-sasl/prometheusfalli/x-99064168] has joined #bitcoin-core-dev 23:25 -!- prometheus_falli [~sluggo@gateway/tor-sasl/prometheusfalli/x-99064168] has quit [Remote host closed the connection] 23:26 -!- prometheus_falli [~sluggo@gateway/tor-sasl/prometheusfalli/x-99064168] has joined #bitcoin-core-dev 23:56 -!- prometheus_falli [~sluggo@gateway/tor-sasl/prometheusfalli/x-99064168] has quit [Quit: Leaving] 23:57 -!- prometheus_falli [~sluggo@gateway/tor-sasl/prometheusfalli/x-99064168] has joined #bitcoin-core-dev 23:59 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-iixgjobkjzznkqye] has joined #bitcoin-core-dev