--- Log opened Thu Jun 17 00:00:40 2021 00:07 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 00:07 < bitcoin-git> [bitcoin] MarcoFalke pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/d50302625e11...dd24567a243f 00:07 < bitcoin-git> bitcoin/master 754e802 Luke Dashjr: test: check rejected future block later accepted 00:07 < bitcoin-git> bitcoin/master dd24567 MarcoFalke: Merge bitcoin/bitcoin#22120: test: p2p_invalid_block: Check that a block r... 00:07 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 00:08 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 00:08 < bitcoin-git> [bitcoin] MarcoFalke merged pull request #22120: test: p2p_invalid_block: Check that a block rejected due to too-new tim… (master...qa_timetoonew_retry) https://github.com/bitcoin/bitcoin/pull/22120 00:08 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 00:41 -!- CaptainLion [~User@47.157.125.162] has quit [Ping timeout: 240 seconds] 00:42 -!- CaptainLion [~User@47.157.125.162] has joined #bitcoin-core-dev 00:42 < vasild> amiti: "why are these approach concerns only being raised now?" I wasn't aware of your work before yesterday. I think late concerns are normal annoyance in software development, not specific to Bitcoin Core or decentralized projects (I worked 10 years in Oracle, I know!). In the same way you seem to be unaware of previous attempts to fix the black holdes problem and explicit signaling for address 00:43 < vasild> relay: https://github.com/bitcoin/bitcoin/pull/17163 https://github.com/bitcoin/bitcoin/pull/17194 https://github.com/bitcoin/bips/pull/766#discussion_r336669541 https://github.com/bitcoin/bips/pull/907#issuecomment-686044611. It is annoying, but being late does not make the concerns automatically less valid. 00:45 -!- dermoth [~dermoth@user/dermoth] has quit [Ping timeout: 264 seconds] 00:50 -!- lkqwejhhgasdjhgn [~kljkljklk@p200300d46f03bc006e75391897515100.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 00:51 -!- dermoth [~dermoth@user/dermoth] has joined #bitcoin-core-dev 00:56 -!- sagi [~sagi@193.238.189.12] has quit [Ping timeout: 240 seconds] 01:07 < vasild> amiti: "In regards to the path forward for #21528 & #22245, it seems like the concerns are all focusing specifically on SENDADDRV2 and the wording of that specific bip" -- no, that's not the case. My biggest concern is changing the meaning of getaddr, addr, addrv2 (and sendaddrv2 if 22245 is considered). I explained that in https://github.com/bitcoin/bitcoin/pull/22245#issuecomment-862539375. My 01:07 <@gribble> https://github.com/bitcoin/bitcoin/issues/21528 | [p2p] Reduce addr blackholes by amitiuttarwar · Pull Request #21528 · bitcoin/bitcoin · GitHub 01:07 <@gribble> https://github.com/bitcoin/bitcoin/issues/22245 | [p2p] Stop sending SENDADDRV2 message to block-relay-only peers by amitiuttarwar · Pull Request #22245 · bitcoin/bitcoin · GitHub 01:07 < vasild> concern can be split in 2 sub-concerns: 1. these changes (extensions) to the protocol are done without a new BIP or modifying existent ones and 2. even if with BIP, on the technical level, I think assuming that if a node sends one of getaddr,addr,addrv2,sendaddrv2 then they participate in address relay is wrong, some examples: https://github.com/bitcoin/bitcoin/pull/21528#issuecomment-862312851 01:09 < sipa> vasild: i don't think that's the right takeaway - we already relay to everyone, there is no assumption right now that everyone participates in addr relay 01:10 < sipa> it's a heuristic for identifying situations where the receiver *doesn't* care about relay 01:11 < vasild> "*doesn't* care about relay" -- you mean "would not relay to other nodes", right? 01:11 < sipa> no, just in the most general sense, for whatever reason, does not care to receive unsolicited addr messages 01:11 < vasild> there may be nodes that do care about receiving addr relay but don't relay further 01:11 < sipa> whether they want those to relay further, to store in an addrman, to connect to, ... 01:11 < sipa> yes, definitely 01:12 < vasild> you would classify such nodes as "cares for addr relay"? 01:12 < sipa> yes 01:12 < vasild> ok 01:13 -!- ratatosk9 [~ratatosk9@185.195.233.168] has joined #bitcoin-core-dev 01:13 < sipa> i wrote a longer response with my thoughts here: https://github.com/bitcoin/bitcoin/pull/22245#issuecomment-862657075 01:14 < vasild> So, now we relay to everyone and the proposed change is to not relay to peers who never sent us getaddr,addr,addrv2,sendaddrv2? 01:14 < sipa> i suggest dropping sendaddrv2 from that list, but yes 01:16 < sipa> amiti went through a lot of effort to determine if such a change would actually hurt any software - without such an effort my thinking would be that we need an explicit separate bip for opting in/out of gossip 01:16 < sipa> and i think we may still want that over time 01:16 < sipa> but at the same time, this seems like a strictly better policy for now, absent any formalization 01:17 < vasild> What about nodes that "care about relay" (want to receive gossip), but never send getaddr,addr,addrv2 to anybody? Or send those messages occasionally to some random peers but we just don't happen to be amongst the chosen ones? 01:17 < sipa> it appears no such software exists 01:18 < sipa> but without a bunch of effort to actually go check what various pieces of software do, and posting on ML, ... i agree that would be a concern 01:19 < vasild> you mean for the first "never send to anybody" -- I don't object the research, assume no such one exists now, but is it safe to assume that no such one would exist in the future? As for the second type - "Or send those messages occasionally" -- bitcoin core is such. 01:20 < sipa> the proposed change is enabling addr relay on outbound non-block-only connections, or incoming connections that ever send (getaddr,addr,addrv2; and maybe sendaddrv2) 01:20 < vasild> (I have not read github posts for the last ~14 hours yet) 01:21 < sipa> i believe that policy wouldn't affect any bitcoin core versions in the past or those with the proposed change 01:24 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 01:24 < bitcoin-git> [bitcoin] endjkv opened pull request #22266: refactor: call GetBestBlock() before NewIterator() (master...master) https://github.com/bitcoin/bitcoin/pull/22266 01:24 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 01:24 < sipa> going to sleep now 01:25 < sipa> anyway, happy to discuss further to find a solution everyone is comfortable with 01:28 * vasild reading related code and github posts... 01:37 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 01:37 < bitcoin-git> [bitcoin] MarcoFalke opened pull request #22267: fuzz: Speed up crypto fuzz target (master...2106-fuzzSpeedCrypto) https://github.com/bitcoin/bitcoin/pull/22267 01:37 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 01:38 -!- rorie [~rorie@45.67.96.239] has joined #bitcoin-core-dev 01:46 -!- rorie [~rorie@45.67.96.239] has quit [Ping timeout: 250 seconds] 01:57 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 01:57 < bitcoin-git> [bitcoin] MarcoFalke opened pull request #22268: fuzz: Add Temporary debug assert for oss-fuzz issue (master...2106-fuzzAssert) https://github.com/bitcoin/bitcoin/pull/22268 01:57 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 02:02 -!- kexkey_ [~kexkey@static-198-54-132-142.cust.tzulo.com] has joined #bitcoin-core-dev 02:04 -!- kexkey [~kexkey@static-198-54-132-110.cust.tzulo.com] has quit [Ping timeout: 244 seconds] 02:26 -!- AaronvanW [~AaronvanW@71pc74.sshunet.nl] has joined #bitcoin-core-dev 02:38 -!- prakash [~prakash@user/prakash] has joined #bitcoin-core-dev 02:44 -!- rejvons [~ratatosk9@185.213.154.237] has joined #bitcoin-core-dev 02:47 -!- ratatosk9 [~ratatosk9@185.195.233.168] has quit [Ping timeout: 268 seconds] 02:54 -!- dviola [~diego@user/dviola] has quit [Quit: WeeChat 3.2] 02:56 -!- sagi [~sagi@193.238.189.12] has joined #bitcoin-core-dev 03:05 -!- rejvons [~ratatosk9@185.213.154.237] has quit [Ping timeout: 240 seconds] 03:26 -!- prakash_ [~prakash@191.96.121.204] has joined #bitcoin-core-dev 03:28 -!- prakash__ [~prakash@154.6.26.15] has joined #bitcoin-core-dev 03:30 -!- prakash [~prakash@user/prakash] has quit [Ping timeout: 268 seconds] 03:32 -!- prakash_ [~prakash@191.96.121.204] has quit [Ping timeout: 244 seconds] 03:35 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""] 03:35 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Quit: ZNC - http://znc.sourceforge.net] 03:37 -!- luke-jr [~luke-jr@user/luke-jr] has joined #bitcoin-core-dev 03:40 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Client Quit] 03:41 -!- luke-jr [~luke-jr@user/luke-jr] has joined #bitcoin-core-dev 03:47 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Quit: ZNC - http://znc.sourceforge.net] 03:50 -!- luke-jr [~luke-jr@user/luke-jr] has joined #bitcoin-core-dev 03:56 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 03:56 < bitcoin-git> [bitcoin] MarcoFalke pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/dd24567a243f...6eafa81b32fd 03:56 < bitcoin-git> bitcoin/master fa483e9 MarcoFalke: fuzz: Speed up crypto fuzz target 03:56 < bitcoin-git> bitcoin/master 6eafa81 MarcoFalke: Merge bitcoin/bitcoin#22267: fuzz: Speed up crypto fuzz target 03:56 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 03:56 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 03:56 < bitcoin-git> [bitcoin] MarcoFalke merged pull request #22267: fuzz: Speed up crypto fuzz target (master...2106-fuzzSpeedCrypto) https://github.com/bitcoin/bitcoin/pull/22267 03:56 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 04:19 -!- prakash_ [~prakash@58.182.42.155] has joined #bitcoin-core-dev 04:21 -!- prakash_ [~prakash@58.182.42.155] has quit [Client Quit] 04:22 -!- prakash__ [~prakash@154.6.26.15] has quit [Ping timeout: 244 seconds] 04:42 -!- Guest48 [~Guest48@103.102.116.37] has joined #bitcoin-core-dev 04:42 -!- Guest48 [~Guest48@103.102.116.37] has quit [Client Quit] 05:11 -!- emcy [~emcy@user/emcy] has joined #bitcoin-core-dev 05:49 -!- TheRec [~toto@84-75-225-47.dclient.hispeed.ch] has joined #bitcoin-core-dev 05:52 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 05:52 < bitcoin-git> [bitcoin] MarcoFalke opened pull request #22270: Add missing bitcoin-util help doc and tests (master...2106-utilTestDoc) https://github.com/bitcoin/bitcoin/pull/22270 05:52 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 05:56 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Quit: ZNC - http://znc.sourceforge.net] 05:56 -!- luke-jr [~luke-jr@user/luke-jr] has joined #bitcoin-core-dev 05:58 -!- TheRec [~toto@84-75-225-47.dclient.hispeed.ch] has quit [Changing host] 05:58 -!- TheRec [~toto@user/therec] has joined #bitcoin-core-dev 05:59 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 05:59 < bitcoin-git> [bitcoin] MarcoFalke pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/6eafa81b32fd...922abe8ca382 05:59 < bitcoin-git> bitcoin/master faf1af5 MarcoFalke: fuzz: Add Temporary debug assert for oss-fuzz issue 05:59 < bitcoin-git> bitcoin/master 922abe8 MarcoFalke: Merge bitcoin/bitcoin#22268: fuzz: Add temporary debug assert for oss-fuzz... 05:59 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 05:59 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 05:59 < bitcoin-git> [bitcoin] MarcoFalke merged pull request #22268: fuzz: Add temporary debug assert for oss-fuzz issue (master...2106-fuzzAssert) https://github.com/bitcoin/bitcoin/pull/22268 05:59 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 06:00 -!- rejvons [~ratatosk9@45.83.220.194] has joined #bitcoin-core-dev 06:02 -!- rejvons [~ratatosk9@45.83.220.194] has quit [Client Quit] 06:10 -!- ratatosk9 [~ratatosk9@45.83.220.218] has joined #bitcoin-core-dev 06:14 -!- kexkey_ is now known as kexkey 06:22 -!- ratatosk9 [~ratatosk9@45.83.220.218] has quit [Quit: Konversation terminated!] 06:24 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Quit: ZNC - http://znc.sourceforge.net] 06:24 -!- luke-jr [~luke-jr@user/luke-jr] has joined #bitcoin-core-dev 06:29 -!- laanwj [~laanwj@user/laanwj] has joined #bitcoin-core-dev 06:42 -!- reez [~textual@45-30-22-183.lightspeed.nsvltn.sbcglobal.net] has joined #bitcoin-core-dev 06:58 -!- emcy [~emcy@user/emcy] has quit [Quit: Leaving] 07:06 -!- sagi [~sagi@193.238.189.12] has quit [Ping timeout: 264 seconds] 07:14 -!- davterra [~davterra@178.128.106.205] has quit [Ping timeout: 268 seconds] 07:15 < michaelfolkson> Why did 0.21.1 include the ability to pay to (presumably mainnet) Taproot addresses? Shouldn't it have been just signet, regtest Taproot addresses until activation? 07:15 < michaelfolkson> https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes/release-notes-0.21.1.md#taproot-soft-fork 07:16 < michaelfolkson> Havent' 07:16 -!- davterra [~davterra@178.128.106.205] has joined #bitcoin-core-dev 07:16 < michaelfolkson> Haven't verified that it did but the release notes say it did 07:17 < jamesob> this is maybe a weird question but does anyone know of a way to have two nodes sync headers in functional tests without syncing the corresponding blocks? 07:18 < _aj_> jamesob: inject the headers via a P2PConnection ? 07:19 < jamesob> _aj_: ah good call 07:19 < jamesob> i.e. P2PConnection ferries headers from one to the other 07:19 -!- goatpig [~goat@blocksettle-gw.cust.31173.se] has quit [Quit: Konversation terminated!] 07:19 < _aj_> jamesob: can't have a single P2PConnection connected to two nodes per se, but yeah 07:20 < jamesob> _aj_: see this is why they pay you the big bucks 07:23 -!- emcy [~emcy@user/emcy] has joined #bitcoin-core-dev 07:27 < jnewbery> jamesob: you could also use the `submitheader` RPC. Might be easier than using P2PConnection: call `getblock` on the source node, take the first 80 bytes, and submit them to the destination node with `submitheader` 07:27 < jamesob> jnewbery: also appealing - thanks! 07:29 -!- roconnor [~roconnor@host-184-164-17-170.dyn.295.ca] has joined #bitcoin-core-dev 07:30 < roconnor> michaelfolkson: Surely Bitcoin Core can pay to any segwit address of any version? That's the whole point of having forward compatable addresses. 07:30 < roconnor> I guess 0.21.1 was the first version after Bech32m was designed. 07:33 -!- reez [~textual@45-30-22-183.lightspeed.nsvltn.sbcglobal.net] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 07:34 -!- provoostenator [~quassel@user/provoostenator] has joined #bitcoin-core-dev 07:35 < michaelfolkson> roconnor: It is a safeguard question. If we prevent Taproot descriptors (e.g. #22156) being imported why not also prevent sending to a SegWit v1 address using the RPC until activation? 07:35 <@gribble> https://github.com/bitcoin/bitcoin/issues/22156 | Allow tr() import only when Taproot is active by achow101 · Pull Request #22156 · bitcoin/bitcoin · GitHub 07:37 < michaelfolkson> I can't see any technical reason for not doing that... just a question of what safeguards are appropriate and what safeguards aren't 07:39 -!- goatpig [~goat@h-94-254-2-155.A498.priv.bahnhof.se] has joined #bitcoin-core-dev 07:39 < darosior> Importing a descriptor is for your own wallet when you don't validate the rules is a footgun. Sending to a Script with new rules that you don't validate yourself is forward compatibility. 07:40 < roconnor> The safeguards are no taproot spending rely and no generation of taproot addresses. But there is no need for my wallet to be taproot upgraded or taproot aware in order for me to pay to your taproot address, and relay of taproot paying transactions are similarly allowed. 07:41 < roconnor> Otherwise we get stuck in the segwitV0 address mire were no one starts using segwitv0 wallets because no wallets can pay to such addresses, and services don't upgrate their segwitv0 wallets because there is no demand to be paid. 07:47 < michaelfolkson> I was thinking the safeguard could be you can't generate a Taproot mainnet address until post activation height. Or lighter there is a warning when you do. But yeah that does link the RPC to current block height 07:50 < michaelfolkson> I'm getting confused what you can and can't do... You can't generate a Taproot address but you can pay to a Taproot address, it just isn't relayed 08:11 < sipa> michaelfolkson: the wallet won't let you import a taproot descriptor until after activation 08:15 < sipa> i think sending to taproot (or other future address formats) is far less of a risk, because it still falls on the receiver's shoulder 08:16 < sipa> someone has to create that address, and give it to the sender with a "pay me here"; if those funds are sent, the sender has paid - the fact that the receiver can get their coins stolen isn't the sender's problem 08:19 -!- Guest575 [~Guest57@fin-vz1.gullo.me] has joined #bitcoin-core-dev 08:19 < sipa> so the protection needs to be at address generation time 08:21 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 08:21 < bitcoin-git> [bitcoin] theStack opened pull request #22271: fuzz: Assert roundtrip equality for `CPubKey` (master...202106-fuzz-assert-CPubKey-deser-roundtrip) https://github.com/bitcoin/bitcoin/pull/22271 08:21 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 08:23 < michaelfolkson> Ok makes sense, thanks 08:24 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Quit: ZNC - http://znc.sourceforge.net] 08:26 -!- luke-jr [~luke-jr@user/luke-jr] has joined #bitcoin-core-dev 08:30 -!- evias_ [~evias__@196.red-88-6-131.staticip.rima-tde.net] has joined #bitcoin-core-dev 08:33 -!- evias [~evias__@user/evias] has quit [Ping timeout: 268 seconds] 08:44 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 08:44 < bitcoin-git> [bitcoin] laanwj pushed 4 commits to master: https://github.com/bitcoin/bitcoin/compare/922abe8ca382...7b45c5e875ca 08:44 < bitcoin-git> bitcoin/master 8cd8f37 Pieter Wuille: Introduce well-defined CAddress disk serialization 08:44 < bitcoin-git> bitcoin/master e2f0548 Pieter Wuille: Use addrv2 serialization in anchors.dat 08:44 < bitcoin-git> bitcoin/master f8866e8 Pieter Wuille: Add roundtrip fuzz tests for CAddress serialization 08:44 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 08:44 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 08:44 < bitcoin-git> [bitcoin] laanwj merged pull request #20516: Well-defined CAddress disk serialization, and addrv2 anchors.dat (master...202011_disk_addr) https://github.com/bitcoin/bitcoin/pull/20516 08:44 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 08:48 -!- kabaum [~kabaum@host-78-77-216-135.mobileonline.telia.com] has joined #bitcoin-core-dev 08:50 -!- lkqwejhhgasdjhgn [~kljkljklk@p200300d46f03bc006e75391897515100.dip0.t-ipconnect.de] has quit [Quit: Konversation terminated!] 08:55 -!- jtrag [~jtrag@c-71-207-125-151.hsd1.pa.comcast.net] has joined #bitcoin-core-dev 09:02 -!- jarthur [~jarthur@cpe-70-114-198-37.austin.res.rr.com] has joined #bitcoin-core-dev 09:09 -!- GIANTWORLDKEEPER [~pjetcetal@2.95.204.25] has quit [Ping timeout: 240 seconds] 09:13 -!- sagi [~sagi@bzq-79-180-140-8.red.bezeqint.net] has joined #bitcoin-core-dev 09:16 -!- kabaum [~kabaum@host-78-77-216-135.mobileonline.telia.com] has quit [Ping timeout: 244 seconds] 09:17 -!- sagi [~sagi@bzq-79-180-140-8.red.bezeqint.net] has quit [Ping timeout: 252 seconds] 09:39 -!- lightlike [~lightlike@user/lightlike] has joined #bitcoin-core-dev 09:44 -!- sagi [~sagi@bzq-79-180-140-8.red.bezeqint.net] has joined #bitcoin-core-dev 09:49 -!- gene [~gene@2a02:6f8:2020:216:100::100a] has joined #bitcoin-core-dev 09:50 -!- Talkless [~Talkless@mail.dargis.net] has joined #bitcoin-core-dev 10:03 -!- reez [~textual@45-30-22-183.lightspeed.nsvltn.sbcglobal.net] has joined #bitcoin-core-dev 10:07 -!- kabaum [~kabaum@host-78-77-216-135.mobileonline.telia.com] has joined #bitcoin-core-dev 10:07 -!- jtrag [~jtrag@c-71-207-125-151.hsd1.pa.comcast.net] has quit [Quit: <----- is PODAK (Passed out drunk at keyboard), and he has somehow managed to quit/disconnect...] 10:08 -!- Enki[m] [~enkimatri@2001:470:69fc:105::382c] has joined #bitcoin-core-dev 10:18 -!- evias_ [~evias__@196.red-88-6-131.staticip.rima-tde.net] has quit [Quit: This computer has gone to sleep] 10:44 -!- reez [~textual@45-30-22-183.lightspeed.nsvltn.sbcglobal.net] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 10:56 -!- sipsorcery [~sipsorcer@2a02:8084:6981:7880::3] has quit [Ping timeout: 244 seconds] 11:00 -!- Guest97 [~Guest97@49.206.122.18] has joined #bitcoin-core-dev 11:07 -!- sagi [~sagi@bzq-79-180-140-8.red.bezeqint.net] has quit [Ping timeout: 252 seconds] 11:07 -!- GIANTWORLDKEEPER [~pjetcetal@2.95.227.207] has joined #bitcoin-core-dev 11:16 -!- Guest575 [~Guest57@fin-vz1.gullo.me] has quit [Quit: Client closed] 11:24 -!- sipsorcery [~sipsorcer@2a02:8084:6981:7880::3] has joined #bitcoin-core-dev 11:24 -!- AaronvanW [~AaronvanW@71pc74.sshunet.nl] has quit [Remote host closed the connection] 11:29 -!- sagi [~sagi@bzq-79-180-140-8.red.bezeqint.net] has joined #bitcoin-core-dev 11:37 -!- Guest97 [~Guest97@49.206.122.18] has quit [Quit: Client closed] 11:55 -!- AaronvanW [~AaronvanW@71pc74.sshunet.nl] has joined #bitcoin-core-dev 12:00 < laanwj> #startmeeting 12:00 < core-meetingbot> Meeting started Thu Jun 17 19:00:47 2021 UTC. The chair is laanwj. Information about MeetBot at https://bitcoin.jonasschnelli.ch/ircmeetings. 12:00 < core-meetingbot> Available commands: action commands idea info link nick 12:00 < hebasto> hi 12:01 < laanwj> #bitcoin-core-dev Meeting: achow101 _aj_ amiti ariard BlueMatt cfields Chris_Stewart_5 darosior digi_james dongcarl elichai2 emilengler fanquake fjahr gleb glozow gmaxwell gwillen hebasto instagibbs jamesob jarolrod jb55 jeremyrubin jl2012 jnewbery jonasschnelli jonatack jtimon kallewoof kanzure kvaciral laanwj lightlike luke-jr maaku marcofalke meshcollider michagogo moneyball morcos 12:01 < laanwj> nehan NicolasDorier paveljanik petertodd phantomcircuit promag provoostenator ryanofsky sdaftuar sipa vasild 12:01 < ariard> hi 12:01 < meshcollider> hi 12:01 < jamesob> hi 12:01 < fjahr> hi 12:01 < kvaciral[m]> hi 12:01 < laanwj> one proposed meeting topic: CoreDev in 2021 (ariard) 12:02 < ariard> yep 12:02 -!- kabaum [~kabaum@host-78-77-216-135.mobileonline.telia.com] has quit [Ping timeout: 268 seconds] 12:02 < laanwj> for the rest it might make sense to discuss things on the 0.22 milestone https://github.com/bitcoin/bitcoin/milestone/47 (instead of high priority for review) 12:02 < MarcoFalke> hi 12:02 < jonasschnelli> hi 12:03 < laanwj> we've slipped the feature freeze but I think it would make to postpone it https://github.com/bitcoin/bitcoin/issues/20851#issuecomment-863132781 , though not sure by how much 12:03 < achow101> hi 12:03 < gene> hi 12:04 < laanwj> #topic 22.0 milestone 12:04 < core-meetingbot> topic: 22.0 milestone 12:05 < laanwj> so there are still plenty of PRs that can be seen as a feature tagged for 22.0, many close to being mergable (just need a bit more review), https://github.com/bitcoin/bitcoin/milestone/47 12:05 < laanwj> anything to add/remove? 12:05 < jonatack> hi 12:05 < hebasto> also https://github.com/bitcoin-core/gui/milestone/2 12:06 -!- baldur [~baldur@pool-108-30-51-126.nycmny.fios.verizon.net] has quit [Read error: Connection reset by peer] 12:07 < laanwj> hebasto: yes, that too 12:07 < sipa> i can't really pay much attentiin here right now 12:08 < laanwj> anyhow I hope people will get around to reviewing the remaining ones soon so they can still make it into 0.22 12:08 < sipa> will address review.comments on my prs soon, though 12:08 < laanwj> sipa: thanks! 12:08 < hebasto> if #21454 is gitian-specific and we moving to guix, maybe remove it? 12:08 <@gribble> https://github.com/bitcoin/bitcoin/issues/21454 | gitian: GLIBC_2.29 not found error at bitcoind startup on bionic · Issue #21454 · bitcoin/bitcoin · GitHub 12:09 < laanwj> hebasto: I'm not aware guix solves that, it uses the same glibc to build again 12:09 < hebasto> ok 12:09 < laanwj> hebasto: we need to get rid of these symbols uses somehow https://github.com/bitcoin/bitcoin/pull/22244#issuecomment-860932169 12:10 < ariard> i'm keeping an eye on #22147, if re-review is needed :) 12:10 < laanwj> "build against the correct glibc" is likely the best option though and more realistic in guix than in gitian 12:10 <@gribble> https://github.com/bitcoin/bitcoin/issues/22147 | p2p: Protect last outbound HB compact block peer by sdaftuar · Pull Request #22147 · bitcoin/bitcoin · GitHub 12:10 < laanwj> still, it doesn't warrant closing the issue yet 12:11 < laanwj> (or unmilestoning it) 12:11 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 12:11 < bitcoin-git> [bitcoin] dergoegge closed pull request #21706: log: Mitigate disk filling attacks by globally rate limiting LogPrintf(…) (master...g_log_ratelimiting) https://github.com/bitcoin/bitcoin/pull/21706 12:11 < jonatack> ariard: yup same, as well as #20234 12:11 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 12:11 <@gribble> https://github.com/bitcoin/bitcoin/issues/20234 | net: dont extra bind for Tor if binds are restricted by vasild · Pull Request #20234 · bitcoin/bitcoin · GitHub 12:12 < laanwj> thanks ariard and jonatack 12:13 < laanwj> #topic CoreDev in 2021 (ariard) 12:13 < core-meetingbot> topic: CoreDev in 2021 (ariard) 12:13 < ariard> hi 12:13 -!- jtrag [~jtrag@c-71-207-125-151.hsd1.pa.comcast.net] has joined #bitcoin-core-dev 12:14 < ariard> so i was told by a lot of OGs in this projects, that they had the feeling about a decrease in communication quality around the last months, partially due to the lack of in-person meetings 12:14 < ariard> and i was lucky to be in Miami, and it was super cool to see a lot of LN devs in-person :) 12:14 < ariard> and have far greater understanding of our opposite arguments, which can sometimes be heated 12:15 < ariard> so i'm curious about what's folks thinking about in-person meeting again, maybe even in 2021 ? 12:15 < jonatack> + 12:15 < jonasschnelli> always a good idea... 12:15 < jamesob> Would love one, happy to help organize if needed 12:15 < jonasschnelli> just make sure you pick a country with minimal restrictions 12:15 < jonatack> ^ not in the US though 12:15 < ariard> jonasschenelli: i know that's a lot of work, i'm happy to help there 12:16 < jonasschnelli> EU people can't travel to the US right now 12:16 < ariard> jonasschnelli: yeah i wouldn't advise doing in the US right now, europe start to be more chill 12:16 < ariard> but it's really a per-country question 12:16 < hebasto> someone cannot travel even in EU now 12:16 < jonatack> EU just opened its borders, at least for the summer i guess 12:16 < ariard> hebasto: i know gleb has the same issue :/ we might pick a non-eu country 12:17 < laanwj> NL is still difficult (though things are clearing up) 12:17 < jonasschnelli> EU seems fine. Everyone just needs to have a test (or vac.) 12:17 < jonatack> el zonte 12:17 < jonasschnelli> Switzerland is fine 12:17 < achow101> usually we do coredev before/after another conference, are there any upcoming for this year? 12:17 < ariard> achow101: yes maybe LN hacking days, and we'll have a BDK/LDK meeting in europe in autumn (hopefully) 12:18 < ariard> a LN hacking day in germany or portugal 12:18 < fjahr> I would be happy to, seems a lot more feasible from where I am lately but in several parts of the world things are still very complicated. But fall is probably the best bet. 12:19 < jonasschnelli> ariard: I think it is a great idea. Willing to help. We also have coredev funds available for location, food, travel subsidy, etc. 12:20 < ariard> yeah i know, we won't be able to get everyone, like australia is pretty closed rn, but more folks, more fun :) 12:20 < jonatack> there is a bitcoin conference in biarritz, france (next to spain on the atlantic) end-august 12:20 < jonatack> some devs have reached out or are already planning to come for it 12:21 < darosior> jonatack: the conference is entire in french though 12:21 < ariard> jonasschenlli: awesome, let me send a mail to the OGs who has done the last ones, to have a start on considerations 12:21 < jonatack> right, but not core dev :) 12:21 < ariard> darosior: well we're still working hard to make french the official LN language, no :p ? 12:21 < jonatack> darosior: i wasn't planning to attend the conf itself 12:21 < darosior> ariard: haha +1 12:21 < ariard> who should i cc as part of the mail jamesob, jonatack, who else wants to help ? 12:22 < ariard> i think previous ones have been jonasschnelli, moneyball, schmidty and jnewbery ? 12:22 < ariard> *organized by 12:22 -!- Talkless [~Talkless@mail.dargis.net] has quit [Quit: Konversation terminated!] 12:22 < jonasschnelli> ariard: yes. see https://coredev.tech/index.html#contact 12:23 < darosior> ariard: Happy to help, depending on the location of course i could be less useful.. 12:23 < ariard> jonasschnelli: i know, i was invited to such coooool kids reunion one day but it did never happen :,( 12:23 < jonatack> (here's the conf i mentioned: https://www.surfinbitcoin.com/2021) 12:25 < jonasschnelli> August might be a bit tight.. but France might be a good option (especially in summer, tourism keeps it open and easy) 12:25 < achow101> I expect things will be more open towards the end of the year 12:25 < achow101> maybe we should do it in november and have a taproot activation party at the same time :) 12:25 < ariard> achow101: hard to say, most of europe start to be really open, and yes french has a big lobby to re-open most of the things for the season 12:26 < laanwj> anywhere in the EU is fine with me (assuming I'm allowed to travel, but as said, things are getting better here now that everyone is getting vaccinated) 12:26 < ariard> achow101: too much kharma :p 12:26 < jonatack> jonasschnelli: yes, august-early sept is the best time of year there and prices goes way down after august 12:26 < jonatack> jonasschnelli: end-aug / all of september and october actually 12:27 < sipa> i'm happy to travel wherever i'm allowed.to go for a coredev meetup 12:27 -!- BlueMatt [~BlueMatt@ircb.bluematt.me] has quit [Quit: Quit] 12:27 -!- BlueMatt [~BlueMatt@ircb.bluematt.me] has joined #bitcoin-core-dev 12:27 < jonasschnelli> I think someone should just pick a date and a location (vague) and see how can attend. If there are enough people, book a venue and finalise the organisation 12:27 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 12:27 < bitcoin-git> [bitcoin] steffanjensen opened pull request #22272: Update transaction.cpp (master...master) https://github.com/bitcoin/bitcoin/pull/22272 12:27 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 12:28 < ariard> yeah we'll consider carefully the travel bans to pick up a location 12:28 < ariard> jonasschnelli: yep, rough consensus :) 12:28 -!- AaronvanW [~AaronvanW@71pc74.sshunet.nl] has quit [Ping timeout: 268 seconds] 12:29 < jonasschnelli> ariard: Happy to share my past experience in organising (did SF and Zurich) (and of course I can help with stuff) 12:29 < ariard> jonasschenlli: thanks a lot, i'll reach out :) 12:29 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 12:29 < bitcoin-git> [bitcoin] MarcoFalke closed pull request #22272: Update transaction.cpp (master...master) https://github.com/bitcoin/bitcoin/pull/22272 12:29 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 12:29 < jonasschnelli> always good to have someone near the planed venue 12:29 * jonasschnelli looking over to jonatack 12:29 < jonatack> sgtm 12:30 < jonatack> i don't like travelling :) 12:30 < ariard> jonatack: have you considered surfing across the atlantic as a travel mean :p ? 12:31 * fjahr sets meeting location to jon's house 12:31 < hebasto> hope being vaccinated will open EU borders for me 12:31 < ariard> okay, we'll do the things announced and share back news during next meetings :) 12:31 < laanwj> great! 12:32 < jonasschnelli> thanks ariard 12:32 < laanwj> any other last minute topics? 12:32 < jonatack> hebasto: i hope so 12:33 < laanwj> #endmeeting 12:33 < core-meetingbot> topic: Bitcoin Core development discussion and commit log | Feel free to watch, but please take commentary and usage questions to #bitcoin | Channel logs: http://www.erisian.com.au/bitcoin-core-dev/, http://gnusha.org/bitcoin-core-dev/ | Meeting topics http://gnusha.org/bitcoin-core-dev/proposedmeetingtopics.txt / http://gnusha.org/bitcoin-core-dev/proposedwalletmeetingtopics.txt 12:33 < core-meetingbot> Meeting ended Thu Jun 17 19:33:12 2021 UTC. 12:33 < core-meetingbot> Minutes: https://bitcoin.jonasschnelli.ch/ircmeetings/logs/bitcoin-core-dev/2021/bitcoin-core-dev.2021-06-17-19.00.moin.txt 12:33 < jonatack> thanks ariard, great idea 12:33 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 12:33 < bitcoin-git> [bitcoin] steffanjensen opened pull request #22273: the banks and bitcon shills don't want this update (master...master) https://github.com/bitcoin/bitcoin/pull/22273 12:33 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 12:34 < ariard> jonatack: you'll thank me when we'll all enjoy pain au chocolat in france or elsewhere :) 12:35 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 12:35 < bitcoin-git> [bitcoin] sipa closed pull request #22273: the banks and bitcon shills don't want this update (master...master) https://github.com/bitcoin/bitcoin/pull/22273 12:35 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 12:35 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 12:35 < bitcoin-git> [bitcoin] MarcoFalke reopened pull request #22273: the banks and bitcon shills don't want this update (master...master) https://github.com/bitcoin/bitcoin/pull/22273 12:35 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 12:35 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 12:35 < bitcoin-git> [bitcoin] MarcoFalke closed pull request #22273: the banks and bitcon shills don't want this update (master...master) https://github.com/bitcoin/bitcoin/pull/22273 12:35 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 12:36 < sipa> ariard: which for unfathomable reason is called a croissant in the US :) 12:38 < luke-jr> ariard: jonatack: jonasschnelli: I thought EU is even more restrictive than US? 12:38 < jonatack> ariard: here if you ask for that, you'll be corrected. south of bordeaux, pain au chocolat is a chocolatine 12:38 < jonasschnelli> luke-jr: depends on what type of restriction 12:38 < jonatack> sipa: whoa 12:38 < jonasschnelli> luke-jr: example: europeans can't travel to the US right now 12:38 < luke-jr> jonasschnelli: last I heard, US folks can't go there at all? 12:39 < MarcoFalke> luke-jr: They can with a test or vac IIRC 12:39 < jonasschnelli> luke-jr: not sure about france... but I guess switzerland would be no problem. 12:39 < jonatack> luke-jr: it was, but things are opening up quickly 12:39 < luke-jr> cool 12:39 < schmidty> ariard: Im happy to help planning. Some light discussions with Advancing Bitcoin about piggybacking there. But dates getting moved. 12:39 < jonasschnelli> US covid case numbers per c. are relatively low 12:40 < jonasschnelli> thus most counties have opened borders for US tourists 12:40 < luke-jr> it's unlikely I'll be able to make it, but if I can, it'd probably need to be in September :x 12:41 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 12:41 < bitcoin-git> [bitcoin] steffanjensen opened pull request #22274: This will be implemented into bitcoin core at one point, with or without you.. your choice. (master...master) https://github.com/bitcoin/bitcoin/pull/22274 12:41 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 12:41 < jamesob> ariard: jonatack: thanks for raising the point ariard, will be exciting to have something on the books 12:41 < schmidty> What is the best dashboard of international travel restrictions? 12:41 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 12:41 < bitcoin-git> [bitcoin] MarcoFalke closed pull request #22274: This will be implemented into bitcoin core at one point, with or without you.. your choice. (master...master) https://github.com/bitcoin/bitcoin/pull/22274 12:41 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 12:41 < MarcoFalke> can somone pls block this spammer 12:41 < gene> ^ 12:41 < jonasschnelli> As for france... I think US persons have to be vaccinated (no testing option). Which is kinda bad 12:42 < luke-jr> (but don't plan around me - like I said, I probably can't make it) 12:42 < luke-jr> sipa: what MarcoFalke said 12:42 < jonatack> jonasschnelli: i thought it was a also either negative test, or having had covid 12:43 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 12:43 < bitcoin-git> [bitcoin] MarcoFalke pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/7b45c5e875ca...8cb43077b370 12:43 < bitcoin-git> bitcoin/master 9550dff Sebastian Falbesoner: fuzz: Assert roundtrip equality for `CPubKey` 12:43 < bitcoin-git> bitcoin/master 8cb4307 MarcoFalke: Merge bitcoin/bitcoin#22271: fuzz: Assert roundtrip equality for `CPubKey`... 12:43 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 12:43 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 12:43 < bitcoin-git> [bitcoin] MarcoFalke merged pull request #22271: fuzz: Assert roundtrip equality for `CPubKey` (master...202106-fuzz-assert-CPubKey-deser-roundtrip) https://github.com/bitcoin/bitcoin/pull/22271 12:43 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 12:43 < jonasschnelli> jonatack: I thought so as well,... but than read https://fr.usembassy.gov/covid-19-information/ 12:43 < jonasschnelli> But I guess you can also get in with a PCR 12:43 < sipa> luke-jr: yeah, will do obce i'm home (10 min) 12:44 < sipa> i expect tjat in a month or two lots of.covid restrictions will be a lot more relaxed 12:44 < jonasschnelli> yes.. I hope so 12:44 < sipa> given how vaccination in many places ib europe is going 12:44 < jonasschnelli> Looks like france is also okay with a negative PCR test (72h) 12:45 < jonasschnelli> (it changed on June 9th) 12:45 < jonatack> yep, checked the french one https://www.interieur.gouv.fr/Actualites/L-actu-du-Ministere/Attestation-de-deplacement-et-de-voyage 12:47 < jonasschnelli> yeah. france would be awesome. Also great if it is in fall (Nov). Waves are better.. :) 12:47 < ariard> schmidty: yep, yep sending mail in the evening, advancing 2020 was a great conf 12:48 < jonasschnelli> schmidty: I used https://travelbans.org in the past 12:48 < jonatack> fwiw last summer we had a record number of tourists ever and case counts stayed cool 12:49 < jonasschnelli> I was one of them... :) 12:49 < jonatack> jonasschnelli: yes, best waves are sept/oct as well as best weather 12:59 -!- Vishal100 [~Vishal@117.237.250.206] has joined #bitcoin-core-dev 12:59 -!- smartin [~Icedove@88.135.18.171] has quit [Quit: smartin] 12:59 -!- Vishal100 [~Vishal@117.237.250.206] has quit [Client Quit] 12:59 -!- Vishal95 [~Vishal@117.237.250.206] has joined #bitcoin-core-dev 13:06 -!- Vishal95 [~Vishal@117.237.250.206] has quit [Quit: Client closed] 13:27 -!- moneyball_ [sid299869@id-299869.brockwell.irccloud.com] has joined #bitcoin-core-dev 13:32 -!- sagi [~sagi@bzq-79-180-140-8.red.bezeqint.net] has quit [Ping timeout: 268 seconds] 13:35 -!- Netsplit *.net <-> *.split quits: moneyball 13:35 -!- moneyball_ is now known as moneyball 13:41 -!- gene [~gene@2a02:6f8:2020:216:100::100a] has quit [Quit: gene] 13:43 -!- Guyver2 [Guyver@guyver2.xs4all.nl] has quit [Quit: Going offline, see ya! (www.adiirc.com)] 14:12 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 14:12 < bitcoin-git> [bitcoin] meshcollider pushed 13 commits to master: https://github.com/bitcoin/bitcoin/compare/8cb43077b370...5c2e2afe990a 14:12 < bitcoin-git> bitcoin/master dbb0ce9 Pieter Wuille: Add TaprootSpendData data structure, equivalent to script map for P2[W]SH 14:12 < bitcoin-git> bitcoin/master e77a283 Pieter Wuille: Use HandleMissingData also in CheckSchnorrSignature 14:12 < bitcoin-git> bitcoin/master a91d532 Pieter Wuille: Add CKey::SignSchnorr function for BIP 340/341 signing 14:12 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 14:13 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 14:13 < bitcoin-git> [bitcoin] meshcollider merged pull request #21365: Basic Taproot signing support for descriptor wallets (master...202102_taproot_sign) https://github.com/bitcoin/bitcoin/pull/21365 14:13 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 14:13 < meshcollider> Taproot wallet \o/ 14:15 < sipa> oh there were a few review comments i wanted to address 14:15 < sipa> i'll create a follow-up 14:15 < sipa> nothing blocking for release 14:15 < achow101> \o/ 14:25 -!- AaronvanW [~AaronvanW@71pc74.sshunet.nl] has joined #bitcoin-core-dev 14:29 -!- gribble [~gribble@bitcoin/bot/gribble] has quit [Read error: Connection reset by peer] 14:35 -!- gribble [~gribble@bitcoin/bot/gribble] has joined #bitcoin-core-dev 14:35 -!- mode/#bitcoin-core-dev [+o gribble] by ChanServ 14:42 -!- sagi [~sagi@bzq-79-180-140-8.red.bezeqint.net] has joined #bitcoin-core-dev 14:58 -!- jespada [~jespada@90.254.247.46] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 14:59 -!- AaronvanW [~AaronvanW@71pc74.sshunet.nl] has quit [Ping timeout: 240 seconds] 15:01 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 15:01 < bitcoin-git> [bitcoin] amitiuttarwar closed pull request #22245: [p2p] Stop sending SENDADDRV2 message to block-relay-only peers (master...2021-06-sendaddrv2) https://github.com/bitcoin/bitcoin/pull/22245 15:01 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 15:05 < ariard> jonasschnelli, jamesob, darosior, schmidty, jonatack: sent on your mail addresses (the ones i found with `git log | grep "$FIRST_NAME $LAST_NAME`) 15:05 < ariard> let me know if i you didn't receive or you prefer another mail addr :) 15:05 -!- jespada [~jespada@90.254.247.46] has joined #bitcoin-core-dev 15:06 < ariard> if anyone wasn't present to meeting and wants to contribute to the orga, feel free to raise the hand 15:34 -!- gribble [~gribble@bitcoin/bot/gribble] has quit [Remote host closed the connection] 15:40 -!- gribble [~gribble@bitcoin/bot/gribble] has joined #bitcoin-core-dev 15:40 -!- mode/#bitcoin-core-dev [+o gribble] by ChanServ 15:51 -!- reez [~textual@45-30-22-183.lightspeed.nsvltn.sbcglobal.net] has joined #bitcoin-core-dev 15:51 -!- sagi [~sagi@bzq-79-180-140-8.red.bezeqint.net] has quit [Ping timeout: 244 seconds] 16:10 -!- Guest89 [~Guest89@153.33.96.21] has joined #bitcoin-core-dev 16:11 -!- reez [~textual@45-30-22-183.lightspeed.nsvltn.sbcglobal.net] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 16:12 -!- sipsorcery [~sipsorcer@2a02:8084:6981:7880::3] has quit [Ping timeout: 272 seconds] 16:15 -!- GIANTWORLDKEEPER [~pjetcetal@2.95.227.207] has quit [Ping timeout: 252 seconds] 16:15 -!- GIANTWORLDKEEPER [~pjetcetal@2.95.227.207] has joined #bitcoin-core-dev 16:18 -!- Guest89 [~Guest89@153.33.96.21] has quit [Ping timeout: 250 seconds] 16:26 -!- sipsorcery [~sipsorcer@2a02:8084:6981:7880::3] has joined #bitcoin-core-dev 16:32 -!- GIANTWORLDKEEPER [~pjetcetal@2.95.227.207] has quit [Ping timeout: 244 seconds] 16:38 -!- baldur [~baldur@pool-108-30-51-126.nycmny.fios.verizon.net] has joined #bitcoin-core-dev 16:38 -!- baldur_ [~baldur@pool-108-30-51-126.nycmny.fios.verizon.net] has joined #bitcoin-core-dev 16:39 -!- baldur_ [~baldur@pool-108-30-51-126.nycmny.fios.verizon.net] has quit [Client Quit] 16:40 -!- GIANTWORLDKEEPER [~pjetcetal@2.95.227.207] has joined #bitcoin-core-dev 16:47 -!- lightlike [~lightlike@user/lightlike] has quit [Quit: Leaving] 16:56 -!- AaronvanW [~AaronvanW@71pc74.sshunet.nl] has joined #bitcoin-core-dev 17:04 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Quit: ZNC - http://znc.sourceforge.net] 17:05 -!- luke-jr [~luke-jr@user/luke-jr] has joined #bitcoin-core-dev 17:06 -!- belcher_ [~belcher@user/belcher] has joined #bitcoin-core-dev 17:09 -!- belcher [~belcher@user/belcher] has quit [Ping timeout: 244 seconds] 17:29 -!- AaronvanW [~AaronvanW@71pc74.sshunet.nl] has quit [Ping timeout: 268 seconds] 17:46 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Read error: Connection reset by peer] 17:47 -!- luke-jr [~luke-jr@user/luke-jr] has joined #bitcoin-core-dev 17:47 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 17:47 < bitcoin-git> [bitcoin] sipa opened pull request #22275: A few follow-ups for taproot signing (master...202106_taproot_sign_followup) https://github.com/bitcoin/bitcoin/pull/22275 17:47 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 18:32 -!- Guest45 [~Guest45@2804:388:502d:ef7c:8055:59bb:65e0:5637] has joined #bitcoin-core-dev 18:32 -!- Guest45 [~Guest45@2804:388:502d:ef7c:8055:59bb:65e0:5637] has quit [Client Quit] 18:32 -!- sipsorcery [~sipsorcer@2a02:8084:6981:7880::3] has quit [Ping timeout: 244 seconds] 18:50 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #bitcoin-core-dev 19:26 -!- AaronvanW [~AaronvanW@71pc74.sshunet.nl] has joined #bitcoin-core-dev 19:31 < fanquake> yea unfortunately it is non-trivial to get into, or out of, Australia the moment 19:37 < sipa> i think that's generally true... 19:38 < sipa> too much water on all sides 19:38 < hebasto> :D 19:59 -!- AaronvanW [~AaronvanW@71pc74.sshunet.nl] has quit [Ping timeout: 252 seconds] 20:04 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 20:04 < bitcoin-git> [bitcoin] Nishikoh closed pull request #18838: test: Check header hash in wait_for_getheaders (master...fix-wait_for_getheaders) https://github.com/bitcoin/bitcoin/pull/18838 20:04 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 21:04 -!- vnogueira [~vnogueira@user/vnogueira] has quit [Remote host closed the connection] 21:05 -!- vnogueira [~vnogueira@user/vnogueira] has joined #bitcoin-core-dev 21:47 -!- gene [~gene@gateway/tor-sasl/gene] has joined #bitcoin-core-dev 21:53 -!- gene [~gene@gateway/tor-sasl/gene] has quit [Quit: gene] 21:55 -!- AaronvanW [~AaronvanW@71pc74.sshunet.nl] has joined #bitcoin-core-dev 22:03 -!- gene [~ferneau.l@b9c17fec.host.njalla.net] has joined #bitcoin-core-dev 22:10 -!- sagi [~sagi@bzq-79-180-140-8.red.bezeqint.net] has joined #bitcoin-core-dev 22:16 -!- gene [~ferneau.l@b9c17fec.host.njalla.net] has quit [Quit: drained and gutted] 22:17 -!- gene [~gene@b9c17fec.host.njalla.net] has joined #bitcoin-core-dev 22:21 -!- gene [~gene@b9c17fec.host.njalla.net] has quit [Client Quit] 22:21 -!- gene [~gene@2a0a:3840:1337:127:0:b9c1:7fec:1337] has joined #bitcoin-core-dev 22:29 -!- AaronvanW [~AaronvanW@71pc74.sshunet.nl] has quit [Ping timeout: 252 seconds] 22:40 -!- vnogueira [~vnogueira@user/vnogueira] has quit [Remote host closed the connection] 22:48 -!- goatpig [~goat@h-94-254-2-155.A498.priv.bahnhof.se] has quit [Quit: Konversation terminated!] 22:51 < amiti> vasild: thanks for your replies, some follow ups- 22:51 < amiti> “I wasn't aware of your work before yesterday. I think late concerns are normal annoyance in software development, not specific to Bitcoin Core or decentralized projects (I worked 10 years in Oracle, I know!). It is annoying, but being late does not make the concerns automatically less valid.“ - I’m not suggesting that being late means the concerns are invalid. I am asking how we can pause to reflect on the disconnect. 22:51 < amiti> Rather than resign ourselves to the idea that this is just the way things are, I’m asking if we can communicate about how we can improve the way we collaborate as a team. 22:51 < amiti> For example, some things I wonder are - what are your main information streams for learning about ongoing work? (Also applies to the others who said they only recently learned about the work.) Do you usually read meeting logs and missing these ones were an outlier, or are meetings not something you usually pay attention to? My primary methods of communication were via the IRC meetings and the mailing list, so it’s useful 22:51 < amiti> information to know if these aren’t reaching the intended audience. I opened the PR and kept it in a draft state as I researched other clients, do you think this impacted your likelihood of noticing the work? Anyway, the point is, there was clearly a disconnect and I’m interested in understanding how we can learn from it. 22:51 < amiti> vasild: “In the same way you seem to be unaware of previous attempts to fix the black holdes problem and explicit signaling for address 22:51 < amiti> relay.. [examples]” - hm actually, I have seen these conversations, many of them were shared with me during the irc meetings. I reread them and don’t see anything that conflicts with what I’m proposing, so I’m not sure why you are making this claim. Please let me know if there’s something specific you think I am missing. 22:52 < amiti> In regards to the technical concerns of #21528, I’ve responded on the PR in an attempt to keep the conversation a bit cohesive. 22:52 <@gribble> https://github.com/bitcoin/bitcoin/issues/21528 | [p2p] Reduce addr blackholes by amitiuttarwar · Pull Request #21528 · bitcoin/bitcoin · GitHub 23:09 -!- vnogueira [~vnogueira@user/vnogueira] has joined #bitcoin-core-dev 23:09 -!- vnogueira [~vnogueira@user/vnogueira] has quit [Remote host closed the connection] 23:16 -!- goatpig [~goat@blocksettle-gw.cust.31173.se] has joined #bitcoin-core-dev 23:31 -!- chaotic_good [~chaotic_g@149.28.165.232] has joined #bitcoin-core-dev 23:33 -!- evias [~evias__@196.red-88-6-131.staticip.rima-tde.net] has joined #bitcoin-core-dev 23:33 -!- evias [~evias__@196.red-88-6-131.staticip.rima-tde.net] has quit [Changing host] 23:33 -!- evias [~evias__@user/evias] has joined #bitcoin-core-dev 23:40 -!- AaronvanW [~AaronvanW@71pc74.sshunet.nl] has joined #bitcoin-core-dev 23:47 -!- vnogueira [~vnogueira@user/vnogueira] has joined #bitcoin-core-dev 23:48 -!- chrysanthematic [~chrysanth@82.2.21.4] has joined #bitcoin-core-dev 23:58 -!- sipsorcery [~sipsorcer@2a02:8084:6981:7880::3] has joined #bitcoin-core-dev --- Log closed Fri Jun 18 00:00:41 2021