--- Log opened Fri Jan 28 00:00:42 2022
00:01 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has joined #bitcoin-core-dev
00:06 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c0a:deda:9648:d9a6] has joined #bitcoin-core-dev
00:10 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
00:10 < bitcoin-git> [bitcoin] MarcoFalke opened pull request #24189: refactor: [bdb] Make SafeDbt Span-like (master...2201-bdbSpan) https://github.com/bitcoin/bitcoin/pull/24189
00:10 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
00:31 -!- guest99100 [~guest9910@2001:700:300:4105:bc51:5aba:7e72:b740] has joined #bitcoin-core-dev
00:35 -!- sdfgsdfg [~dfghsfgs@user/sdfgsdfg] has joined #bitcoin-core-dev
00:35 -!- jespada [~jespada@87.74.36.188] has joined #bitcoin-core-dev
00:41 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has quit [Ping timeout: 245 seconds]
00:42 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
00:42 < bitcoin-git> [bitcoin] MarcoFalke closed pull request #24189: refactor: [bdb] Make SafeDbt Span-like (master...2201-bdbSpan) https://github.com/bitcoin/bitcoin/pull/24189
00:42 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
00:49 -!- bomb-on [~bomb-on@194.144.47.113] has joined #bitcoin-core-dev
01:03 -!- Guest15 [~Guest15@072-017-039-163.res.spectrum.com] has joined #bitcoin-core-dev
01:05 -!- sudoforge [~sudoforge@wireguard/tunneler/sudoforge] has quit [Ping timeout: 260 seconds]
01:09 -!- Guest15 [~Guest15@072-017-039-163.res.spectrum.com] has quit [Ping timeout: 256 seconds]
01:10 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c0a:deda:9648:d9a6] has quit [Ping timeout: 260 seconds]
01:13 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
01:13 < bitcoin-git> [bitcoin] Sjors closed pull request #22016: rpc: add period_start to version bits statistics (master...2021/05/versionbits_period_start) https://github.com/bitcoin/bitcoin/pull/22016
01:13 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
01:30 -!- sdfgsdfg [~dfghsfgs@user/sdfgsdfg] has quit [Quit: ayo yoyo ayo yoyo hololo, hololo.]
01:33 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
01:33 < bitcoin-git> [bitcoin] MarcoFalke opened pull request #24190: test: Fix sanitizer suppresions in streams_tests (master...2201-ts) https://github.com/bitcoin/bitcoin/pull/24190
01:33 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
01:38 -!- brunoerg [~brunoerg@187.183.47.88] has joined #bitcoin-core-dev
01:41 -!- kabaum [~kabaum@185.195.233.161] has quit [Ping timeout: 250 seconds]
01:44 -!- grettke [~grettke@cpe-65-29-228-30.wi.res.rr.com] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
01:56 -!- kabaum [~kabaum@185.65.135.241] has joined #bitcoin-core-dev
01:59 -!- sdfgsdfg [~dfghsfgs@user/sdfgsdfg] has joined #bitcoin-core-dev
02:00 -!- mikehu44 [~quassel@159.65.11.175] has quit [Ping timeout: 252 seconds]
02:06 -!- jonatack45 [~jonatack@user/jonatack] has joined #bitcoin-core-dev
02:07 -!- mikehu44 [~quassel@159.65.11.175] has joined #bitcoin-core-dev
02:09 -!- jonatack26 [jonatack@user/jonatack] has joined #bitcoin-core-dev
02:09 -!- jonatack [jonatack@user/jonatack] has quit [Ping timeout: 250 seconds]
02:13 -!- jonatack45 [~jonatack@user/jonatack] has quit [Ping timeout: 250 seconds]
02:16 -!- michagogo [uid14316@user/michagogo] has joined #bitcoin-core-dev
02:43 -!- brunoerg [~brunoerg@187.183.47.88] has quit [Ping timeout: 240 seconds]
02:46 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c0a:deda:9648:d9a6] has joined #bitcoin-core-dev
02:58 -!- NorrinRadd [~username@102.67.16.112] has joined #bitcoin-core-dev
03:08 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c0a:deda:9648:d9a6] has quit [Remote host closed the connection]
03:13 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
03:13 < bitcoin-git> [bitcoin] MarcoFalke opened pull request #24191: refactor: Make MessageBoxFlags enum underlying type unsigned (master...2201-nouiInt) https://github.com/bitcoin/bitcoin/pull/24191
03:13 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
03:21 -!- jonatack26 [jonatack@user/jonatack] has quit [Quit: Connection closed]
03:25 -!- jonatack [jonatack@user/jonatack] has joined #bitcoin-core-dev
03:26 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c0a:deda:9648:d9a6] has joined #bitcoin-core-dev
03:30 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c0a:deda:9648:d9a6] has quit [Ping timeout: 245 seconds]
03:30 -!- mikehu44 [~quassel@159.65.11.175] has quit [Ping timeout: 240 seconds]
03:31 -!- mikehu44 [~quassel@159.65.11.175] has joined #bitcoin-core-dev
03:36 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c0a:deda:9648:d9a6] has joined #bitcoin-core-dev
03:45 -!- guest99100 [~guest9910@2001:700:300:4105:bc51:5aba:7e72:b740] has quit [Ping timeout: 256 seconds]
03:48 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:ec87:c9ae:e756:6611] has joined #bitcoin-core-dev
03:52 < michaelfolkson> #proposedwalletmeetingtopic Taproot support in the wallet (open PRs, latest thinking)
04:01 -!- NorrinRadd [~username@102.67.16.112] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
04:01 -!- mikehu44 [~quassel@159.65.11.175] has quit [Ping timeout: 240 seconds]
04:09 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
04:09 < bitcoin-git> [bitcoin] MarcoFalke opened pull request #24192: test: Fix feature_init intermittent issues (master...2201-testFI) https://github.com/bitcoin/bitcoin/pull/24192
04:09 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
04:13 -!- sdfgsdfg [~dfghsfgs@user/sdfgsdfg] has quit [Quit: ayo yoyo ayo yoyo hololo, hololo.]
04:16 -!- sdfgsdfg [~dfghsfgs@user/sdfgsdfg] has joined #bitcoin-core-dev
04:18 < stickies-v> Is this the right place to ask for a CI retrigger? If so, could someone please restart #24098 - the fuzzer timed out but it seems unrelated to the PR.
04:18 <@gribble> https://github.com/bitcoin/bitcoin/issues/24098 | rest: Use query parameters to control resource loading by stickies-v · Pull Request #24098 · bitcoin/bitcoin · GitHub
04:23 -!- TheRec_ [~toto@84-75-225-47.dclient.hispeed.ch] has quit []
04:26 -!- NorrinRadd [~username@102.67.16.112] has joined #bitcoin-core-dev
04:27 -!- NorrinRadd [~username@102.67.16.112] has quit [Client Quit]
04:47 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
05:02 < _aj_> seems like CI's a bit broken, both fuzzer timeouts and "AssertionError: Fee of 0.00003160 BTC too high! (Should be 0.00003130 BTC)" error?
05:15 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:ec87:c9ae:e756:6611] has quit [Remote host closed the connection]
05:15 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:ec87:c9ae:e756:6611] has joined #bitcoin-core-dev
05:16 -!- michagogo [uid14316@user/michagogo] has quit [Quit: Connection closed for inactivity]
05:21 -!- tralfaz [~davterra@143.198.56.186] has quit [Remote host closed the connection]
05:22 -!- davterra [~davterra@143.198.56.186] has joined #bitcoin-core-dev
05:22 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c0a:deda:9648:d9a6] has quit [Remote host closed the connection]
05:22 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c0a:deda:9648:d9a6] has joined #bitcoin-core-dev
05:28 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
05:28 < bitcoin-git> [bitcoin] MarcoFalke opened pull request #24194: refactor: Use unsigned ignore() consistently (master...2201-streamIgnore) https://github.com/bitcoin/bitcoin/pull/24194
05:28 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
05:32 < jonatack> _aj_: yes (i think MarcoFalke opened a fix for the fuzzer timeout, and i opened an issue for the fee too high one)
05:33 < jonatack> #24179
05:33 <@gribble> https://github.com/bitcoin/bitcoin/issues/24179 | fuzz: Speed up script fuzz target by MarcoFalke · Pull Request #24179 · bitcoin/bitcoin · GitHub
05:33 < jonatack> and https://github.com/bitcoin/bitcoin/issues/24151
05:36 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
05:36 < bitcoin-git> [bitcoin] MarcoFalke closed pull request #24194: refactor: Use unsigned ignore() consistently (master...2201-streamIgnore) https://github.com/bitcoin/bitcoin/pull/24194
05:36 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
05:38 -!- bomb-on [~bomb-on@194.144.47.113] has quit [Read error: Connection reset by peer]
05:40 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:ec87:c9ae:e756:6611] has quit [Remote host closed the connection]
05:43 -!- Guyver2 [~Guyver@guyver2.xs4all.nl] has joined #bitcoin-core-dev
05:43 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:ec87:c9ae:e756:6611] has joined #bitcoin-core-dev
05:47 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:ec87:c9ae:e756:6611] has quit [Remote host closed the connection]
05:53 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:ec87:c9ae:e756:6611] has joined #bitcoin-core-dev
06:07 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
06:07 < bitcoin-git> [bitcoin] theStack closed pull request #24106: policy: treat P2TR outputs with invalid x-only pubkey as non-standard (master...202201-policy-treat_p2tr_with_invalid_xpubkey_as_nonstandard) https://github.com/bitcoin/bitcoin/pull/24106
06:07 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
06:09 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:ec87:c9ae:e756:6611] has quit [Remote host closed the connection]
06:17 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c0a:deda:9648:d9a6] has quit [Remote host closed the connection]
06:17 -!- vysn [~vysn@user/vysn] has quit [Ping timeout: 240 seconds]
06:18 -!- Guest41 [~Guest41@213.196.96.242] has joined #bitcoin-core-dev
06:18 < Guest41> Бьн
06:19 < Guest41> Hello
06:19 -!- brunoerg [~brunoerg@187.183.47.88] has joined #bitcoin-core-dev
06:19 -!- Guest41 [~Guest41@213.196.96.242] has quit [Client Quit]
06:22 -!- vysn [~vysn@user/vysn] has joined #bitcoin-core-dev
06:27 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
06:27 < bitcoin-git> [bitcoin] MarcoFalke pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/d4e92d843650...1245c62fef1d
06:27 < bitcoin-git> bitcoin/master faa75fa MarcoFalke: Avoid unsigned integer overflow in bitcoin-tx
06:27 < bitcoin-git> bitcoin/master 1245c62 MarcoFalke: Merge bitcoin/bitcoin#24139: Avoid unsigned integer overflow in bitcoin-tx...
06:27 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
06:28 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
06:28 < bitcoin-git> [bitcoin] MarcoFalke merged pull request #24139: Avoid unsigned integer overflow in bitcoin-tx (master...2201-utilTxOverflow) https://github.com/bitcoin/bitcoin/pull/24139
06:28 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
06:31 -!- vysn [~vysn@user/vysn] has quit [Ping timeout: 250 seconds]
06:31 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:ec87:c9ae:e756:6611] has joined #bitcoin-core-dev
06:32 -!- brunoerg [~brunoerg@187.183.47.88] has quit [Remote host closed the connection]
06:38 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:ec87:c9ae:e756:6611] has quit [Ping timeout: 240 seconds]
06:44 -!- jarthur [~jarthur@2603-8080-1540-002d-35e0-06b2-095d-de4d.res6.spectrum.com] has joined #bitcoin-core-dev
06:44 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:ec87:c9ae:e756:6611] has joined #bitcoin-core-dev
06:49 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c0a:deda:9648:d9a6] has joined #bitcoin-core-dev
06:53 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c0a:deda:9648:d9a6] has quit [Ping timeout: 250 seconds]
06:57 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
06:57 < bitcoin-git> [bitcoin] mzumsande opened pull request #24195: test: Fix failfast option for functional test runner (master...202201_testrunner_fix) https://github.com/bitcoin/bitcoin/pull/24195
06:57 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
07:10 -!- sdfgsdfg [~dfghsfgs@user/sdfgsdfg] has quit [Quit: ayo yoyo ayo yoyo hololo, hololo.]
07:21 -!- brunoerg [~brunoerg@187.183.47.88] has joined #bitcoin-core-dev
07:26 -!- brunoerg [~brunoerg@187.183.47.88] has quit [Ping timeout: 256 seconds]
07:31 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has joined #bitcoin-core-dev
07:53 -!- brunoerg [~brunoerg@187.183.47.88] has joined #bitcoin-core-dev
07:56 < sdaftuar> I'm seeing repeated ci timeouts in #20726, for the ci job "[fuzzer,address,undefined,integer, no depends]". i've tried re-running the job several times, but no luck -- each time it still times out.  anyone have ideas about how to get this to complete?
07:57 <@gribble> https://github.com/bitcoin/bitcoin/issues/20726 | p2p: Add DISABLETX message for negotiating block-relay-only connections by sdaftuar · Pull Request #20726 · bitcoin/bitcoin · GitHub
08:01 < lightlike> sdaftuar: There is #24179 which aims to fix the fuzzer timeouts (which appear all over the place).
08:01 <@gribble> https://github.com/bitcoin/bitcoin/issues/24179 | fuzz: Speed up script fuzz target by MarcoFalke · Pull Request #24179 · bitcoin/bitcoin · GitHub
08:01 -!- AaronvanW [~AaronvanW@user/AaronvanW] has quit [Quit: Leaving...]
08:02 < sdaftuar> ah, thank you! perhaps i'll just wait for that pr to get merged, and then restart the job
08:26 -!- brunoerg [~brunoerg@187.183.47.88] has quit [Remote host closed the connection]
08:29 -!- Talkless [~Talkless@mail.dargis.net] has joined #bitcoin-core-dev
08:39 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
08:39 < bitcoin-git> [bitcoin] MarcoFalke opened pull request #24196: Fix integer sanitizer suppressions in validation.cpp (master...2201-valInt) https://github.com/bitcoin/bitcoin/pull/24196
08:39 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
08:42 -!- brunoerg [~brunoerg@187.183.47.88] has joined #bitcoin-core-dev
08:55 -!- jespada [~jespada@87.74.36.188] has quit [Ping timeout: 240 seconds]
08:56 -!- grettke [~grettke@cpe-65-29-228-30.wi.res.rr.com] has joined #bitcoin-core-dev
08:57 -!- jespada [~jespada@87.74.36.188] has joined #bitcoin-core-dev
09:04 -!- sudoforge [~sudoforge@wireguard/tunneler/sudoforge] has joined #bitcoin-core-dev
09:04 -!- salvatoshi [~salvatosh@genymobile-2-6-86.fib.nerim.net] has quit [Ping timeout: 250 seconds]
09:15 -!- davterra [~davterra@143.198.56.186] has quit [Quit: Leaving]
09:24 -!- jarthur [~jarthur@2603-8080-1540-002d-35e0-06b2-095d-de4d.res6.spectrum.com] has quit [Quit: jarthur]
09:33 -!- kexkey_ [~kexkey@static-198-54-132-122.cust.tzulo.com] has quit [Ping timeout: 250 seconds]
09:37 -!- kexkey [~kexkey@static-198-54-132-138.cust.tzulo.com] has joined #bitcoin-core-dev
09:56 -!- davterra [~davterra@143.198.56.186] has joined #bitcoin-core-dev
09:57 -!- jarthur [~jarthur@2603-8080-1540-002d-35e0-06b2-095d-de4d.res6.spectrum.com] has joined #bitcoin-core-dev
09:58 -!- jesseposner [~jesse@c-24-5-105-39.hsd1.ca.comcast.net] has quit [Changing host]
09:58 -!- jesseposner [~jesse@user/jesseposner] has joined #bitcoin-core-dev
09:59 -!- jesseposner [~jesse@user/jesseposner] has quit [Quit: Textual IRC Client: www.textualapp.com]
09:59 -!- jesseposner [~jesse@user/jesseposner] has joined #bitcoin-core-dev
10:11 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has quit [Ping timeout: 250 seconds]
10:12 < darosior> #proposedwalletmeetingtopic labels for ranged descriptors
10:33 -!- vysn [~vysn@user/vysn] has joined #bitcoin-core-dev
10:36 -!- brunoerg [~brunoerg@187.183.47.88] has quit [Remote host closed the connection]
10:39 -!- brunoerg [~brunoerg@187.183.47.88] has joined #bitcoin-core-dev
10:46 -!- brunoerg [~brunoerg@187.183.47.88] has quit [Remote host closed the connection]
10:54 -!- sandipndev [sandipndev@2600:3c00::f03c:92ff:fe8e:dce6] has joined #bitcoin-core-dev
10:54 -!- da2ce7 [~da2ce7@user/da2ce7] has joined #bitcoin-core-dev
10:54 -!- uasf_ [~uasf@2604:a880:2:d0::1bda:1001] has joined #bitcoin-core-dev
10:55 -!- da2ce7_ [~da2ce7@user/da2ce7] has quit [Ping timeout: 256 seconds]
10:55 -!- sandipndev123 [~sandipnde@shindig.notmandatory.org] has quit [Ping timeout: 256 seconds]
10:55 -!- uasf [~uasf@157.230.135.166] has quit [Read error: Connection reset by peer]
10:55 -!- andytoshi [~apoelstra@user/andytoshi] has quit [Ping timeout: 256 seconds]
10:55 -!- gribble [~gribble@bitcoin/bot/gribble] has quit [Ping timeout: 256 seconds]
10:55 -!- cold [~cold@user/cold] has quit [Ping timeout: 256 seconds]
10:55 -!- andytosh1 [~apoelstra@user/andytoshi] has joined #bitcoin-core-dev
10:55 -!- michaelfolkson [~michaelfo@138.68.143.20] has quit [Ping timeout: 256 seconds]
10:55 -!- _aj_ [aj@user/aj/x-5857768] has quit [Ping timeout: 256 seconds]
10:55 -!- _aj_ [aj@cerulean.erisian.com.au] has joined #bitcoin-core-dev
10:55 -!- _aj_ [aj@cerulean.erisian.com.au] has quit [Changing host]
10:55 -!- _aj_ [aj@user/aj/x-5857768] has joined #bitcoin-core-dev
10:55 -!- michaelfolkson [~michaelfo@138.68.143.20] has joined #bitcoin-core-dev
10:56 -!- dodo [~dodo@user/dodo] has quit [Ping timeout: 256 seconds]
10:56 -!- dodo [~dodo@user/dodo] has joined #bitcoin-core-dev
10:58 < michaelfolkson> Please do darosior's topic first achow101, I'm just catching up
11:00 < achow101> #startmeeting
11:00 < core-meetingbot`> Meeting started Fri Jan 28 19:00:36 2022 UTC.  The chair is achow101. Information about MeetBot at https://bitcoin.jonasschnelli.ch/ircmeetings.
11:00 < core-meetingbot`> Available commands: action commands idea info link nick
11:00 < achow101> #bitcoin-core-dev Wallet 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 larryruane lightlike luke-jr maaku marcofalke meshcollider michagogo moneyball morcos Murch nehan NicolasDorier paveljanik 
11:00 < achow101> petertodd phantomcircuit promag provoostenator ryanofsky sdaftuar S3RK sipa vasild
11:01 < michaelfolkson> hi
11:01 -!- cryptapus [~cryptapus@user/cryptapus] has quit [Remote host closed the connection]
11:01 < darosior> hi
11:01 -!- cryptapus [~cryptapus@user/cryptapus] has joined #bitcoin-core-dev
11:01 < achow101> There's one pre-proposed meeting topic, any others people want to add?
11:01 < sipa> hi
11:01 < darosior> Hmm maybe i failed to add mine?
11:02 < michaelfolkson> [18:12:49]  <darosior> #proposedwalletmeetingtopic labels for ranged descriptors
11:02 < achow101> oops, 2 pre-proposed topics
11:02 < achow101> #topic labels for ranged descriptors (darosior)
11:02 < core-meetingbot`> topic: labels for ranged descriptors (darosior)
11:02 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c0a:deda:9648:d9a6] has joined #bitcoin-core-dev
11:02 < laanwj> hi
11:03 < darosior> So as part of the Miniscript work, i tested the branch against my application (which uses Miniscript internally and the descriptor wallet as watchonly to track 2 main descriptors) and discovered that labels are deactivated for range descriptors.
11:03 < darosior> However labels are pretty useful to differentiate the coins when you have multiple descriptors on the same watchonly wallet (which i think is the intent?). Typically for triage in the `listsinceblock` or `listunspent` results: i think i'm just an instance and they are useful as well.
11:03 < darosior> So i wondered what people here thought about enabling the same features to the descriptor level, to not have to add all addresses to the address book in advance (which i guessed is the reason to disable them for range descriptors in the first place?). Or if something else than labels was envisioned to enable the same features.
11:03 < darosior> s/and they are useful as well/ and they are useful as well to others/
11:04 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has joined #bitcoin-core-dev
11:04 < achow101> the reason that labels were not implemented originally was because it seemed odd to me that someone would want to assign the same label to all addresses generated by a descriptor
11:04 < sipa> What are you thinking of, something like a label template on the descriptor, with say a %i in it that gets replaced by the index?
11:04 < sipa> Or just the same label for everything?
11:04 < achow101> and also I think there was some complexity with applying labels to addresses that did not exist yet
11:05 < darosior> The same label for any address derived for this descriptor. Something to say "this received coin is for this descriptor"
11:05 -!- bomb-on [~bomb-on@194.144.47.113] has joined #bitcoin-core-dev
11:06 < achow101> if you think it's something people will use, go for it
11:06 < michaelfolkson> Sorry for the ELI5 but by label do you mean the subscripts of Miniscript?
11:07 < darosior> No i mean a metadata to identify a descriptor
11:07 < darosior> Could just add the descriptor itself to the result, i guess, although i'd to think how a client of the API would manage that
11:07 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c0a:deda:9648:d9a6] has quit [Ping timeout: 252 seconds]
11:07 < sipa> No, label, as in the setlabel RPC.
11:07 < sipa> and getaddressesbylabel
11:07 < michaelfolkson> Oh ok
11:08 < darosior> Ok, thanks. It was mainly to know if there were prior discussions on this topic. Guess i'm done :)
11:08 < achow101> I'm not sure I understand the use case, but I am ambivalent on this
11:09 < achow101> #topic Taproot support in the wallet (open PRs, latest thinking) (michaelfolkson)
11:09 < core-meetingbot`> topic: Taproot support in the wallet (open PRs, latest thinking) (michaelfolkson)
11:09 < sipa> Likewise.
11:09 < darosior> I can describe the motivation better in an issue, if that's helpful
11:09 < achow101> darosior: please do
11:09 < michaelfolkson> Ok.. so was just looking over the Taproot related PRs. #22558 is marked as high prio
11:10 -!- bomb-on [~bomb-on@194.144.47.113] has quit [Client Quit]
11:10 < michaelfolkson> This should be tested in tandem with #24043?
11:11 < achow101> they are orthogonal
11:11 < michaelfolkson> To do a Taproot multisig you need the Taproot multisig descriptor right?
11:11 < michaelfolkson> And that is only introduced in #24043
11:11 -!- vysn [~vysn@user/vysn] has quit [Ping timeout: 268 seconds]
11:11 < achow101> #22558 is just for the basic taproot fields to actually be able to do any kind of watchonly taproot spend
11:12 < michaelfolkson> But to be passing around Taproot multisig PSBTs you need to have setup a Taproot multisig.... right?
11:12 < sipa> the multisig part is in 24043
11:12 < achow101> psbt is for more than just multisigs
11:12 < sipa> the taproot psbt part is in 22558
11:12 < sipa> if you want taproot multisig psbt, then you indeed need both
11:12 < achow101> #22558 is needed to work with HWI for example
11:12 < achow101> just to do a single key taproot spend
11:13 -!- bomb-on [~bomb-on@194.144.47.113] has joined #bitcoin-core-dev
11:13 < michaelfolkson> Ah ok. So to test #24043 you should be doing a single key taproot spend
11:14 < michaelfolkson> And then to test Taproot multisig wait for #24043 or test in tandem with #24043
11:14 < achow101> too many 24043's in that sentence
11:14 < jonatack> hi
11:15 < michaelfolkson> I guess what I'm saying is to get #22558 merged test with a single key Taproot spend
11:16 < michaelfolkson> The alternative would be to make both #22558 and #24043 high prio
11:17 < michaelfolkson> Ok that makes sense (I think)
11:17 < achow101> yes, 22558 can be tested with single key spends
11:17 < michaelfolkson> So then moving to #24043
11:18 < michaelfolkson> This seems a stopgap to me (which is fine, just testing my understanding)
11:19 < michaelfolkson> But presumably longer term a Taproot enabled Miniscript would tell you which 2-of-3 arrangement is most efficient
11:19 < sipa> No, that information is implied by miniscript.
11:20 < sipa> If you have a miniscript/descriptor, the script is already decided.
11:20 < sipa> Which one is most efficient is trivial; the question is which one is applicable.
11:20 < sipa> Because using e.g. FROST threshold key as internal taproot key will always be the most efficient possible for any kind of multisig.
11:20 < michaelfolkson> So when you say "later replaced with Miniscript based implementation" what are you referring to?
11:21 < sipa> That's just an implementation aspect, not something observable.
11:21 < michaelfolkson> I see as a descriptor as a one to one mapping with script. But Miniscript is a one to many mapping to script depending on the subscripts
11:22 < sipa> What are subscripts?
11:22 < michaelfolkson> Like the _a etc
11:22 < sipa> No, miniscript is a 1-to-1 mapping with (a subset of) script.
11:22 < michaelfolkson> Sorry shouldn't say sub*script*, makes things complicated
11:23 < sipa> The functions in miniscript (e.g. "multi_a", "and_v", ...) we call "fragments". if you're looking for terminology.
11:23 < sipa> Let me try to explain what that sentence was about, unless someone has something else to discuss?
11:24 < sipa> achow101?
11:24 < michaelfolkson> There aren't any other topics
11:25 < achow101> I don't have any topics
11:25 < sipa> Ok, so, currently the bitcoin core codebase doesn't have miniscript implemented.
11:25 < sipa> Miniscript covers a bunch of different things, but it at least is sort of an extension of descriptors, as well as generic signing support for miniscript-compatible scripts, and a few other things.
11:26 < sipa> In the long term, with the miniscript codebase integrated into bitcoin core, a significant part of the logic around descriptors and signing can be handled by miniscript, which does lots of things generically.
11:26 < michaelfolkson> I'm thinking eventually you could almost ditch the term "descriptors" entirely. Everything would be Miniscript
11:27 < sipa> I very strongly hope it's the other way around.
11:27 < sipa> Miniscript is the name of research project, it's not something "visible".
11:27 < sipa> The part that is visible are what it enables in descriptors.
11:27 < michaelfolkson> Ok whatever, but it would all be one thing under one name
11:27 < sipa> Definitely.
11:28 < michaelfolkson> So this new multi_a descriptor would eventually be ditched right?
11:28 < sipa> No?
11:28 < sipa> In favor of what?
11:29 < michaelfolkson> A Miniscript equivalent that would give you the script for n-of-n which is optimal
11:30 < michaelfolkson> You say in the PR n-of-n isn't optimal, but k-of-n (k<n) is optimal
11:30 < sipa> Once we add support for a particular descriptor we cannot remove it, as it'd break wallets that have such a descriptor.
11:30 < sipa> michaelfolkson: Yes, and that miniscript equivalent would be called multi_a, which behaves exactly the same as the one we have now.
11:30 < sipa> Only it'd be done via the miniscript codebase, instead of a special-case inside the descriptor codebase.
11:31 < sipa> But as a user you wouldn't be able to tell the difference.
11:31 < michaelfolkson> There would be multi_a for k-of-n and say a multi_b for n-of-n?
11:31 < sipa> For example, yes.
11:31 < michaelfolkson> Ok gotcha
11:32 < michaelfolkson> The wallet estimating witness size incorrectly will be addressed in follow up PR?
11:32 < sipa> Or perhaps and_v(v:pk(A),v:pk(B),...,pk(Z)).
11:33 < sipa> Which is more in line with how miniscript treats the optimal n-of-n script.
11:33 < sipa> Size estimation is a hard question, I don't really have a good solution.
11:33 < sipa> You can't in general predict which branch signers will be using.
11:34 < sipa> Perhaps something where you can pass to the fundraw* RPC which keys/signers are available.
11:34 < sipa> I think people have discussed something like that in the past.
11:34 < michaelfolkson> Doesn't Miniscript give you the most efficient option (and hence can estimate the witness sizes of the various spending paths)?
11:34 < michaelfolkson> Solved by Miniscript (if we can get that merged)
11:34 < sipa> No.
11:35 < sipa> Miniscript is just a way of writing scripts in a different way that allows more generic reasoning over them.
11:35 < sipa> You're talking about the miniscript policy compiler, which is one application of the things you can do with miniscript.
11:35 < Murch> hi
11:35 < sipa> But that's not something I'm expecting would be integrated into Bitcoin Core.
11:36 < sipa> It's not estimating witness sizes that's hard - miniscript can do that, as can our current codebase.
11:36 < michaelfolkson> Ok gotcha. You will be able to do that external to Core but Core won't have access to the compiler (necessarily)
11:36 < sipa> The difficulty is making the code know which keys are available, so it knows which branch to pick.
11:36 < sipa> That's just a logistic issue.
11:37 < michaelfolkson> Ok final question (thanks btw). I'm assuming all the build stuff that was done for Minisketch will need to be done for Miniscript?
11:38 < sipa> nope, nothing
11:38 < sipa> because miniscript isn't a separate library
11:38 < sipa> it'll just be merged into bitcoin core
11:39 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c0a:deda:9648:d9a6] has joined #bitcoin-core-dev
11:39 < michaelfolkson> By separate library you just mean separate repo...?
11:39 < sipa> No.
11:39 < sipa> Minisketch is a library you build separately, with an API, you can build applications against, ...
11:40 < sipa> Miniscript is just a bunch of source files which are mostly intended to be integrated into Bitcoin Core.
11:40 < sipa> The future of the repository after that point is unclear; perhaps we keep it just for the compiler/website.
11:40 < michaelfolkson> There will be no Miniscript "API" or applications built using the Miniscript "library"?
11:40 < sipa> Perhaps people want to spend time on actually turning the miniscript codebase into a library that's independently usable, ...
11:41 < michaelfolkson> Oh ok you've answered that
11:41 < sipa> That's right. It needs Bitcoin Core right now.
11:41 < michaelfolkson> Ok thanks, all my questions
11:41 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has quit [Ping timeout: 268 seconds]
11:42 < achow101> any other topics?
11:43 < achow101> #endmeeting
11:43 < 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
11:43 < core-meetingbot`> Meeting ended Fri Jan 28 19:43:10 2022 UTC.  
11:43 < core-meetingbot`> Minutes:        https://bitcoin.jonasschnelli.ch/ircmeetings/logs/bitcoin-core-dev/2022/bitcoin-core-dev.2022-01-28-19.00.moin.txt
11:44 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c0a:deda:9648:d9a6] has quit [Ping timeout: 268 seconds]
11:44 < sipa> michaelfolkson: Not sure how clear that is, but what is shown/entered on my miniscript site (https://bitcoin.sipa.be/miniscript/) is two very different languages. They look similar which may make it confusing, but their purpose is completely different. One is the policy language, which is for writing "under what conditions should my output be spendable". The other is miniscript (which is a 1-to-1 mapping with Bitcoin Script, but a bit more readable). The
11:44 < sipa> policy compiler complies policy to miniscript, by finding out the most efficient miniscript way of doing what you want, specified by the policy.
11:46 < sipa> The thing that would be integrated into Bitcoin Core is the miniscript side of things, i.e., the output of the policy compiler if that's what you use to construct it.
11:47 -!- ZeroMaster_ [~webirc@95-42-105-42.ip.btc-net.bg] has quit [Ping timeout: 250 seconds]
11:47 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has joined #bitcoin-core-dev
11:50 < michaelfolkson> sipa: Right, I knew this, I was forgetting all the clever, analysis stuff happens with the compiler between Policy and Miniscript
11:50 < michaelfolkson> And Core doesn't have access to it
11:52 < sipa> I mean, it could... but there is no need for it. E.g. we could have a bitcoin-miniscript-compiler tool, or a "compileminiscript" RPC. But I doubt we'll want to put all that functionality inside bitcoin core, as it can be done externally just as well.
11:52 < michaelfolkson> The new multi_a descriptor would be Taproot'd Miniscript and multi (Taproot'd Policy) would compile down to multi_a (Taproot'd Miniscript)
11:52 < sipa> Right.
11:52 < michaelfolkson> Or compile down to multi_b (Taproot'd Miniscript) if you were doing n-of-n
11:53 < sipa> Once we have a taproot-enabled miniscript definition and compiler for it.
11:55 < michaelfolkson> I think Luke said on the PR he didn't like the tag (_a) and could we avoid it. But Miniscript has a number of tags, it is normal from a Miniscript perspective
11:55 < sipa> Yeah, and it's understandable, because right now the _a is completely redundant.
11:56 < sipa> You can only use multi_a inside tr(), and you can only use multi outside tr().
11:56 < michaelfolkson> Tag or fragment? I'm not sure on terminology. The literal (_a) is a tag? And the segment of Miniscript would be a fragment?
11:56 < sipa> suffix
11:57 < sipa> the fragment is the whole name (multi_a)
11:57 < michaelfolkson> Ok
11:58 < sipa> The idea is that the suffces like _a and wrappers (like the "v:" prefix) don't modify the policy implemented by the script.
11:58 < sipa> So if you just want to get an idea of "what does this script allow", you just ignore them.
11:58 < sipa> But they are relevant for specifying the actual script opcodes, and possibly its efficiency.
12:02 < michaelfolkson> [19:52:04]  <sipa> I mean, it could... but there is no need for it. E.g. we could have a bitcoin-miniscript-compiler tool, or a "compileminiscript" RPC. But I doubt we'll want to put all that functionality inside bitcoin core, as it can be done externally just as well.
12:02 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
12:02 < bitcoin-git> [bitcoin] jonatack opened pull request #24197: Replace lock with thread safety annotation in CBlockTreeDB::LoadBlockIndexGuts() (master...replace-lock-with-annotation-in-LoadBlockIndexGuts) https://github.com/bitcoin/bitcoin/pull/24197
12:02 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
12:03 < michaelfolkson> We can't assess the witness size for script path spends that would be a reason
12:03 < sipa> What? No, that's unrelated.
12:03 < sipa> Miniscript allows reasoning over witness sizes.
12:03 < sipa> The compiler uses that functionality to figure out the optimal script for a given policy.
12:04 < sipa> But you don't need the compiler to know the witness size for a miniscript.
12:04 -!- ZeroMaster [~webirc@95-42-105-42.ip.btc-net.bg] has joined #bitcoin-core-dev
12:06 < sipa> The only thing you need to compiler for is constructing miniscripts in a somewhat more user-friendly way.
12:06 < sipa> doing things with the resulting miniscript doesn't need to compiler
12:07 < michaelfolkson> The compiler will tell you what Miniscript is most efficient based on the size of witnesses that need to be provided? Hence it has to be able to assess the witness size that will be needed to spend from that Miniscript?
12:08 < sipa> Yes.
12:08 < sipa> It uses the miniscript codebase to figure out which script is most efficient.
12:08 < michaelfolkson> So as a result the compiler could assess the witness size for a script path spend
12:08 < michaelfolkson> And solve the problem that I quoted you?
12:08 < sipa> But the logic for determining witness sizes is in miniscript itself - so it's available to whatever uses it.
12:09 < sipa> There is no problem to be solved.
12:09 < sipa> Our current codebase in bitcoin core can already compute witness sizes.
12:09 < sipa> Once we integrate miniscript, it can do that too for the new scripts supported by miniscript.
12:10 < sipa> The "problem" is just logistical... at signing time you may not know which signers are available, and that affects which satisfaction of a script is available.
12:11 < michaelfolkson> "Wallet code will for now estimate witness size incorrectly for script path spends" <- This is solved by merging Miniscript being merged into Core. It doesn't need access to the Policy -> Miniscript compiler to solve this problem
12:11 < sipa> No, that problem is completely unrelated.
12:11 < sipa> It's just because there is no way to tell the wallet which signers are available, for the third time.
12:11 < sipa> It's not that it can't compute it.
12:11 < sipa> It's that it doesn't know, because there is no way to tell it.
12:12 < michaelfolkson> Ok sorry, I'll read this over again
12:13 < sipa> Imagine you have an output that can be spent by either A and B signing, or by C signing.
12:13 -!- brunoerg [~brunoerg@187.183.47.88] has joined #bitcoin-core-dev
12:13 < sipa> If C is available, then a witness with 1 signature suffices.
12:13 < sipa> If A and B are available, then a witness with 2 signatures is needed.
12:14 < sipa> There is no way to tell fundrawtransaction etc which of these two options is going to be used, and no way to give it the information to infer it.
12:14 < sipa> So it always assumes that whatever is cheapest/smallest will be used.
12:14 < sipa> This problem is exacerbated by miniscript, but not unique to it.
12:16 < michaelfolkson> fundrawtransaction doesn't know which option isn't going to be used and neither does Policy, Miniscript or the compiler. But the compiler knows the witness size needed to spend from each option
12:17 < sipa> Yes, and so does Miniscript, and our codebase. If it knew what option was going to be used, it could compute the expected witness size.
12:17 < michaelfolkson> Hence fundrawtransaction would want to say to the compiler "Hey this option is being used. What's the witness size needed to spend from this option?"
12:17 < sipa> But it currently has no way of knowing.
12:17 < sipa> This has nothing to do with the compiler!
12:17 -!- brunoerg [~brunoerg@187.183.47.88] has quit [Ping timeout: 250 seconds]
12:17 < sipa> All this information can be inferred from the script itself.
12:18 < sipa> The compiler is for constructing scripts.
12:18 < sipa> If you already have a script, the compiler isn't relevant.
12:20 < michaelfolkson> Ok I think I get it, fundrawtransaction can easily know what the witness size to spend from an option is but it doesn't know which option will be used ahead of time
12:21 < michaelfolkson> Sorry :)
12:22 -!- lukedashjr [~luke-jr@user/luke-jr] has joined #bitcoin-core-dev
12:24 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Ping timeout: 240 seconds]
12:24 -!- lukedashjr is now known as luke-jr
12:33 -!- amnrst [~amnrst@45-79-201-163.ip.linodeusercontent.com] has quit [Quit: The Lounge - https://thelounge.chat]
12:34 -!- amnrst [~amnrst@45-79-201-163.ip.linodeusercontent.com] has joined #bitcoin-core-dev
12:35 -!- piku [~piku@47.202.113.8] has joined #bitcoin-core-dev
12:41 -!- lukedashjr [~luke-jr@user/luke-jr] has joined #bitcoin-core-dev
12:42 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Ping timeout: 240 seconds]
12:43 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
12:43 < bitcoin-git> [gui] hebasto merged pull request #526: Add address relay/processed/rate-limited fields to peer details (master...add-addr-fields-to-peer-details) https://github.com/bitcoin-core/gui/pull/526
12:43 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
12:43 -!- lukedashjr is now known as luke-jr
12:43 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
12:43 < bitcoin-git> [bitcoin] hebasto pushed 5 commits to master: https://github.com/bitcoin/bitcoin/compare/1245c62fef1d...5b4b8f76f3ae
12:43 < bitcoin-git> bitcoin/master a465a66 Jon Atack: gui: add "Address Relay" (m_addr_relay_enabled) to peer details
12:43 < bitcoin-git> bitcoin/master 19623d3 Jon Atack: gui: add "Addresses Processed" (m_addr_processed) to peer details
12:43 < bitcoin-git> bitcoin/master 6cd132d Jon Atack: gui: add "Addresses Rate-Limited" (m_addr_rate_limited) to peer details
12:43 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
12:46 -!- Talkless [~Talkless@mail.dargis.net] has quit [Quit: Konversation terminated!]
12:51 -!- amnrst [~amnrst@45-79-201-163.ip.linodeusercontent.com] has quit [Quit: The Lounge - https://thelounge.chat]
12:51 -!- amnrst [~amnrst@45-79-201-163.ip.linodeusercontent.com] has joined #bitcoin-core-dev
13:06 -!- brunoerg [~brunoerg@187.183.47.88] has joined #bitcoin-core-dev
13:11 -!- brunoerg [~brunoerg@187.183.47.88] has quit [Ping timeout: 268 seconds]
13:13 -!- TheRec [~toto@84-75-225-47.dclient.hispeed.ch] has joined #bitcoin-core-dev
13:13 -!- TheRec [~toto@84-75-225-47.dclient.hispeed.ch] has quit [Changing host]
13:13 -!- TheRec [~toto@user/therec] has joined #bitcoin-core-dev
13:35 -!- amnrst [~amnrst@45-79-201-163.ip.linodeusercontent.com] has quit [Quit: The Lounge - https://thelounge.chat]
13:36 -!- amnrst [~amnrst@45-79-201-163.ip.linodeusercontent.com] has joined #bitcoin-core-dev
13:38 -!- amnrst [~amnrst@45-79-201-163.ip.linodeusercontent.com] has quit [Client Quit]
13:39 -!- amnrst [~amnrst@45-79-201-163.ip.linodeusercontent.com] has joined #bitcoin-core-dev
13:41 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c0a:deda:9648:d9a6] has joined #bitcoin-core-dev
13:43 -!- Guyver2 [~Guyver@guyver2.xs4all.nl] has quit [Quit: Going offline, see ya! (www.adiirc.com)]
13:46 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c0a:deda:9648:d9a6] has quit [Ping timeout: 268 seconds]
13:51 -!- ZeroMaster [~webirc@95-42-105-42.ip.btc-net.bg] has quit [Ping timeout: 250 seconds]
14:04 < mutatrum> Where do the drahtbot guix build end up? I want to test #24115 on a Raspberry.
14:04 -!- Alina-malina [~Alina-mal@user/alina-malina] has quit [Ping timeout: 250 seconds]
14:06 -!- Alina-malina [~Alina-mal@user/alina-malina] has joined #bitcoin-core-dev
14:07 < sipa> It'll post the results when it's done.
14:07 < sipa> I don't know when it'll run.
14:08 < sipa> I have a build for you, if you want.
14:08 < sipa> (usual risks about trusting someone else's binaries apply, obviously)
14:09 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:ec87:c9ae:e756:6611] has quit [Remote host closed the connection]
14:11 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:f1f3:3e:61e3:7b96] has joined #bitcoin-core-dev
14:12 < mutatrum> Thanks, I'll wait. Pi is not running at the moment anyways.
14:12 < sipa> I can confirm that the binary does have SHA2 ARM instructions in it.
14:14 < mutatrum> Good! I ran IBD on the Rock Pi 4, took 48 hours to block 700.000. Now running master for comparison.
14:17 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c0a:deda:9648:d9a6] has joined #bitcoin-core-dev
14:18 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:f1f3:3e:61e3:7b96] has quit [Ping timeout: 240 seconds]
14:18 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
14:18 < bitcoin-git> [bitcoin] brunoerg opened pull request #24198: wallet, rpc: add wtxid in WalletTxToJSON (master...2022-01-listtransactions-wtxid) https://github.com/bitcoin/bitcoin/pull/24198
14:18 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
14:20 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:f1f3:3e:61e3:7b96] has joined #bitcoin-core-dev
14:20 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c0a:deda:9648:d9a6] has quit [Remote host closed the connection]
14:23 < mutatrum> 65 hours*
14:25 -!- ZeroMaster [~webirc@95-42-105-42.ip.btc-net.bg] has joined #bitcoin-core-dev
14:29 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:f1f3:3e:61e3:7b96] has quit [Ping timeout: 245 seconds]
14:32 -!- sdfgsdfg [~dfghsfgs@user/sdfgsdfg] has joined #bitcoin-core-dev
14:35 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c0a:deda:9648:d9a6] has joined #bitcoin-core-dev
14:40 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c0a:deda:9648:d9a6] has quit [Ping timeout: 240 seconds]
14:51 -!- ziggie [uid521459@user/ziggie] has quit [Quit: Connection closed for inactivity]
14:55 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has quit [Ping timeout: 268 seconds]
14:57 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:1f6:b1ff:aa35:87a0] has joined #bitcoin-core-dev
15:10 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:1f6:b1ff:aa35:87a0] has quit [Ping timeout: 240 seconds]
15:12 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c0a:deda:9648:d9a6] has joined #bitcoin-core-dev
15:17 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c0a:deda:9648:d9a6] has quit [Ping timeout: 268 seconds]
15:20 -!- yanmaani [~yanmaani@gateway/tor-sasl/yanmaani] has quit [Remote host closed the connection]
15:26 -!- yanmaani [~yanmaani@gateway/tor-sasl/yanmaani] has joined #bitcoin-core-dev
15:27 -!- rex4539 [~rex4539@gateway/tor-sasl/rex4539] has quit [Ping timeout: 276 seconds]
15:43 -!- vysn [~vysn@user/vysn] has joined #bitcoin-core-dev
15:47 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c0a:deda:9648:d9a6] has joined #bitcoin-core-dev
15:48 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:1f6:b1ff:aa35:87a0] has joined #bitcoin-core-dev
15:50 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has joined #bitcoin-core-dev
15:52 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c0a:deda:9648:d9a6] has quit [Ping timeout: 250 seconds]
16:02 -!- jrayhawk_ is now known as jrayhawk
16:02 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:1f6:b1ff:aa35:87a0] has quit [Ping timeout: 250 seconds]
16:05 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:f1f3:3e:61e3:7b96] has joined #bitcoin-core-dev
16:08 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:f1f3:3e:61e3:7b96] has quit [Remote host closed the connection]
16:09 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:1f6:b1ff:aa35:87a0] has joined #bitcoin-core-dev
16:09 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:1f6:b1ff:aa35:87a0] has quit [Remote host closed the connection]
16:09 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:f1f3:3e:61e3:7b96] has joined #bitcoin-core-dev
16:10 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
16:10 < bitcoin-git> [bitcoin] jonatack opened pull request #24199: Add cs_main annotation to WriteBatchSync(), drop lock in CDiskBlockIndex (master...remove-cs_main-lock-in-CDiskBlockIndex) https://github.com/bitcoin/bitcoin/pull/24199
16:10 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
16:11 -!- mikehu44 [~quassel@159.65.11.175] has joined #bitcoin-core-dev
16:12 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:f1f3:3e:61e3:7b96] has quit [Remote host closed the connection]
16:23 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:f1f3:3e:61e3:7b96] has joined #bitcoin-core-dev
16:25 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has quit [Ping timeout: 240 seconds]
16:31 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:f1f3:3e:61e3:7b96] has quit [Ping timeout: 250 seconds]
16:39 -!- brunoerg [~brunoerg@187.183.47.88] has joined #bitcoin-core-dev
16:42 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@node-1w7jr9yi65te5s7k7qrc1fx3s.ipv6.telus.net] has quit [Remote host closed the connection]
16:43 -!- brunoerg [~brunoerg@187.183.47.88] has quit [Ping timeout: 256 seconds]
16:54 -!- rex4539 [~rex4539@gateway/tor-sasl/rex4539] has joined #bitcoin-core-dev
16:59 -!- rex4539 [~rex4539@gateway/tor-sasl/rex4539] has quit [Ping timeout: 276 seconds]
17:03 -!- grettke [~grettke@cpe-65-29-228-30.wi.res.rr.com] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
17:05 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@node-1w7jr9yi65te42alrqfekgj3g.ipv6.telus.net] has joined #bitcoin-core-dev
17:10 -!- sdfgsdfg [~dfghsfgs@user/sdfgsdfg] has quit [Quit: ayo yoyo ayo yoyo hololo, hololo.]
17:12 -!- jarthur_ [~jarthur@2603-8080-1540-002d-0dc7-4940-686f-5599.res6.spectrum.com] has joined #bitcoin-core-dev
17:13 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@node-1w7jr9yi65te42alrqfekgj3g.ipv6.telus.net] has quit [Ping timeout: 260 seconds]
17:13 -!- grettke [~grettke@cpe-65-29-228-30.wi.res.rr.com] has joined #bitcoin-core-dev
17:14 -!- jarthur [~jarthur@2603-8080-1540-002d-35e0-06b2-095d-de4d.res6.spectrum.com] has quit [Ping timeout: 250 seconds]
17:15 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c0a:deda:9648:d9a6] has joined #bitcoin-core-dev
17:18 -!- TallTim [~talltim@184-83-250-114-dynamic.midco.net] has joined #bitcoin-core-dev
17:19 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c0a:deda:9648:d9a6] has quit [Ping timeout: 240 seconds]
17:23 -!- sdfgsdfg [~dfghsfgs@user/sdfgsdfg] has joined #bitcoin-core-dev
17:25 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@node-1w7jr9yi65te42alrqfekgj3g.ipv6.telus.net] has joined #bitcoin-core-dev
17:41 -!- davterra [~davterra@143.198.56.186] has quit [Quit: Leaving]
17:48 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:1f6:b1ff:aa35:87a0] has joined #bitcoin-core-dev
18:07 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c0a:deda:9648:d9a6] has joined #bitcoin-core-dev
18:12 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c0a:deda:9648:d9a6] has quit [Ping timeout: 250 seconds]
18:29 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@node-1w7jr9yi65te42alrqfekgj3g.ipv6.telus.net] has quit [Ping timeout: 250 seconds]
18:30 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@node-1w7jr9yi65te42alrqfekgj3g.ipv6.telus.net] has joined #bitcoin-core-dev
18:34 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@node-1w7jr9yi65te42alrqfekgj3g.ipv6.telus.net] has quit [Remote host closed the connection]
18:34 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@node-1w7jr9yi65te42alrqfekgj3g.ipv6.telus.net] has joined #bitcoin-core-dev
18:40 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c0a:deda:9648:d9a6] has joined #bitcoin-core-dev
18:42 -!- rex4539 [~rex4539@gateway/tor-sasl/rex4539] has joined #bitcoin-core-dev
18:44 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c0a:deda:9648:d9a6] has quit [Ping timeout: 240 seconds]
18:47 -!- rex4539 [~rex4539@gateway/tor-sasl/rex4539] has quit [Ping timeout: 276 seconds]
18:57 -!- kexkey [~kexkey@static-198-54-132-138.cust.tzulo.com] has quit [Quit: kexkey]
18:59 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:1f6:b1ff:aa35:87a0] has quit [Remote host closed the connection]
19:07 -!- bomb-on [~bomb-on@194.144.47.113] has quit [Quit: aллилѹіа!]
19:10 -!- vysn [~vysn@user/vysn] has quit [Ping timeout: 240 seconds]
19:15 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c0a:deda:9648:d9a6] has joined #bitcoin-core-dev
19:16 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:f1f3:3e:61e3:7b96] has joined #bitcoin-core-dev
19:16 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:f1f3:3e:61e3:7b96] has quit [Remote host closed the connection]
19:16 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:f1f3:3e:61e3:7b96] has joined #bitcoin-core-dev
19:18 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:f1f3:3e:61e3:7b96] has quit [Remote host closed the connection]
19:20 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c0a:deda:9648:d9a6] has quit [Ping timeout: 268 seconds]
19:20 -!- jespada [~jespada@87.74.36.188] has quit [Ping timeout: 240 seconds]
19:22 -!- jespada [~jespada@87.74.36.188] has joined #bitcoin-core-dev
19:50 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c0a:deda:9648:d9a6] has joined #bitcoin-core-dev
19:54 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c0a:deda:9648:d9a6] has quit [Ping timeout: 250 seconds]
19:54 -!- jarthur_ [~jarthur@2603-8080-1540-002d-0dc7-4940-686f-5599.res6.spectrum.com] has quit [Ping timeout: 260 seconds]
20:04 -!- kexkey [~kexkey@static-198-54-132-154.cust.tzulo.com] has joined #bitcoin-core-dev
20:07 -!- jarthur [~jarthur@2603-8080-1540-002d-f868-291a-f5eb-cdc3.res6.spectrum.com] has joined #bitcoin-core-dev
20:11 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:f1f3:3e:61e3:7b96] has joined #bitcoin-core-dev
20:15 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:f1f3:3e:61e3:7b96] has quit [Ping timeout: 250 seconds]
20:23 -!- AaronvanW [~AaronvanW@user/AaronvanW] has joined #bitcoin-core-dev
20:24 -!- brunoerg [~brunoerg@187.183.47.88] has joined #bitcoin-core-dev
20:28 -!- brunoerg [~brunoerg@187.183.47.88] has quit [Ping timeout: 250 seconds]
20:30 -!- rex4539 [~rex4539@gateway/tor-sasl/rex4539] has joined #bitcoin-core-dev
20:36 -!- rex4539 [~rex4539@gateway/tor-sasl/rex4539] has quit [Ping timeout: 276 seconds]
20:40 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #bitcoin-core-dev
20:51 -!- gribble [~gribble@bitcoin/bot/gribble] has joined #bitcoin-core-dev
20:51 -!- mode/#bitcoin-core-dev [+o gribble] by ChanServ
21:01 -!- cmirror [~cmirror@4.53.92.114] has joined #bitcoin-core-dev
21:14 -!- rex4539 [~rex4539@gateway/tor-sasl/rex4539] has joined #bitcoin-core-dev
21:14 -!- sdfgsdfg [~dfghsfgs@user/sdfgsdfg] has quit [Quit: ayo yoyo ayo yoyo hololo, hololo.]
21:20 -!- rex4539 [~rex4539@gateway/tor-sasl/rex4539] has quit [Ping timeout: 276 seconds]
21:29 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c0a:deda:9648:d9a6] has joined #bitcoin-core-dev
21:33 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c0a:deda:9648:d9a6] has quit [Ping timeout: 250 seconds]
21:51 -!- sdfgsdfg [~dfghsfgs@user/sdfgsdfg] has joined #bitcoin-core-dev
22:03 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c0a:deda:9648:d9a6] has joined #bitcoin-core-dev
22:07 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c0a:deda:9648:d9a6] has quit [Ping timeout: 240 seconds]
22:11 -!- sudoforge [~sudoforge@wireguard/tunneler/sudoforge] has quit [Ping timeout: 250 seconds]
22:23 -!- rex4539 [~rex4539@gateway/tor-sasl/rex4539] has joined #bitcoin-core-dev
22:33 -!- rex4539 [~rex4539@gateway/tor-sasl/rex4539] has quit [Ping timeout: 276 seconds]
22:52 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c0a:deda:9648:d9a6] has joined #bitcoin-core-dev
22:57 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c0a:deda:9648:d9a6] has quit [Ping timeout: 268 seconds]
23:23 -!- Alina-malina [~Alina-mal@user/alina-malina] has quit [Ping timeout: 240 seconds]
23:24 -!- Alina-malina [~Alina-mal@user/alina-malina] has joined #bitcoin-core-dev
23:39 -!- jarthur [~jarthur@2603-8080-1540-002d-f868-291a-f5eb-cdc3.res6.spectrum.com] has quit [Quit: jarthur]
23:45 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c0a:deda:9648:d9a6] has joined #bitcoin-core-dev
23:49 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c0a:deda:9648:d9a6] has quit [Ping timeout: 240 seconds]
--- Log closed Sat Jan 29 00:00:43 2022