--- Log opened Wed Dec 22 00:00:08 2021
00:22 -!- Guest55 [~Guest55@58.red-81-42-209.staticip.rima-tde.net] has joined #bitcoin-core-dev
00:22 -!- Guest55 [~Guest55@58.red-81-42-209.staticip.rima-tde.net] has quit [Client Quit]
00:40 -!- Guyver2 [~Guyver@guyver2.xs4all.nl] has joined #bitcoin-core-dev
01:10 -!- grettke [~grettke@184.62.226.206] has joined #bitcoin-core-dev
01:11 -!- grettke [~grettke@184.62.226.206] has quit [Client Quit]
01:18 -!- Victorsueca [~Victorsue@user/victorsueca] has quit [Ping timeout: 240 seconds]
01:26 -!- ___nick___ [~quassel@cpc68286-cdif17-2-0-cust533.5-1.cable.virginm.net] has joined #bitcoin-core-dev
01:30 -!- raj [~raj@2602:ffb6:4:e396:f816:3eff:fe47:ca2a] has quit [Killed (NickServ (GHOST command used by Guest2756!uid72176@user/raj))]
01:30 -!- raj_ [~raj@167.182.81.172.lunanode-rdns.com] has joined #bitcoin-core-dev
01:40 -!- Victorsueca [~Victorsue@user/victorsueca] has joined #bitcoin-core-dev
01:47 -!- RoyBatty [~me@107-139-231-17.lightspeed.irvnca.sbcglobal.net] has joined #bitcoin-core-dev
01:49 -!- RoyBatty [~me@107-139-231-17.lightspeed.irvnca.sbcglobal.net] has quit [Changing host]
01:49 -!- RoyBatty [~me@user/robyatty] has joined #bitcoin-core-dev
01:58 -!- Talkless [~Talkless@mail.dargis.net] has joined #bitcoin-core-dev
02:33 < laanwj> this issue while testing seems to always come back, sometimes it'd be useful to be able to completely override the IBD logic
02:48 -!- gnaf [~pi@86-91-224-60.opennet.kpn.net] has joined #bitcoin-core-dev
03:09 -!- tla2k21 [~tla2k21@gateway/tor-sasl/tla2k21] has quit [Remote host closed the connection]
03:09 -!- tla2k21 [~tla2k21@gateway/tor-sasl/tla2k21] has joined #bitcoin-core-dev
03:15 -!- Common [~Common@user/common] has quit [Quit: Leaving]
03:16 -!- Gimble [~G1mble2@2a01:4b00:8e07:7900:e79c:6460:44ed:8423] has joined #bitcoin-core-dev
03:36 -!- earnestly [~earnest@user/earnestly] has joined #bitcoin-core-dev
03:51 -!- yanmaani [~yanmaani@gateway/tor-sasl/yanmaani] has quit [Ping timeout: 276 seconds]
03:57 -!- Common [~Common@096-033-221-075.res.spectrum.com] has joined #bitcoin-core-dev
03:59 -!- Common [~Common@096-033-221-075.res.spectrum.com] has quit [Changing host]
03:59 -!- Common [~Common@user/common] has joined #bitcoin-core-dev
04:00 -!- jespada [~jespada@87.74.33.157] has quit [Ping timeout: 268 seconds]
04:02 -!- jespada [~jespada@87.74.33.157] has joined #bitcoin-core-dev
04:31 -!- mikehu44 [~quassel@206.189.41.250] has joined #bitcoin-core-dev
05:05 -!- mikehu44 [~quassel@206.189.41.250] has quit [Ping timeout: 240 seconds]
05:06 -!- mikehu44 [~quassel@206.189.41.250] has joined #bitcoin-core-dev
05:07 -!- masta`` [~oyster@user/masta/x-2645138] has joined #bitcoin-core-dev
05:13 -!- mikehu44 [~quassel@206.189.41.250] has quit [Ping timeout: 240 seconds]
05:14 -!- mikehu44 [~quassel@206.189.41.250] has joined #bitcoin-core-dev
05:24 -!- vasild [~vd@user/vasild] has quit [Ping timeout: 276 seconds]
05:35 -!- vasild [~vd@user/vasild] has joined #bitcoin-core-dev
05:47 -!- mikehu44 [~quassel@206.189.41.250] has quit [Ping timeout: 240 seconds]
05:48 -!- mikehu44 [~quassel@206.189.41.250] has joined #bitcoin-core-dev
06:09 -!- yanmaani [~yanmaani@gateway/tor-sasl/yanmaani] has joined #bitcoin-core-dev
06:10 -!- SpellChecker [~SpellChec@user/SpellChecker] has quit [Remote host closed the connection]
06:11 -!- SpellChecker [~SpellChec@user/SpellChecker] has joined #bitcoin-core-dev
06:13 -!- masta`` [~oyster@user/masta/x-2645138] has quit [Quit: Going offline, see ya! (www.adiirc.com)]
06:15 -!- gnaf [~pi@86-91-224-60.opennet.kpn.net] has quit [Ping timeout: 256 seconds]
06:31 -!- Guyver2_ [Guyver@guyver2.xs4all.nl] has joined #bitcoin-core-dev
06:35 -!- Guyver2 [~Guyver@guyver2.xs4all.nl] has quit [Ping timeout: 268 seconds]
06:35 -!- Guyver2_ is now known as Guyver2
06:42 -!- bomb-on [~bomb-on@194.144.47.113] has joined #bitcoin-core-dev
07:19 -!- x88x88x [~x88x88x@2001:19f0:5:39a8:5400:3ff:feb6:73cb] has quit [Ping timeout: 240 seconds]
07:22 -!- x88x88x [~x88x88x@149.28.53.172] has joined #bitcoin-core-dev
07:30 -!- gnaf [~pi@86-91-224-60.opennet.kpn.net] has joined #bitcoin-core-dev
07:33 -!- Guest97 [~Guest97@181-191-0-203.uplinkx.com.br] has joined #bitcoin-core-dev
07:36 -!- vasild [~vd@user/vasild] has quit [Ping timeout: 276 seconds]
07:39 < michaelfolkson> bitcoin-node in multiprocess uses UNIX sockets https://github.com/bitcoin/bitcoin/pull/19460
07:39 < michaelfolkson> How did it get around the libevent stuff?
07:39 < sipa> It doesn't use libevent.
07:41 < michaelfolkson> What does it do instead?
07:41 < michaelfolkson> So at least until UNIX sockets are implemented in Core non-multiprocess that's a reason for using multiprocess? If you want to use UNIX sockets?
07:42 < sipa> I can't understand your reasoning.
07:42 < sipa> They do different things.
07:42 < sipa> You don't "want" to use UNIX sockets. They're a tool to accomplish a goal.
07:42 < sipa> Using multiprocess doesn't let you make RPC connections over UNIX sockets.
07:43 < sipa> Because multiprocess isn't RPC.
07:43 < earnestly> capn proto is rpc
07:44 < sipa> Yes, multiprocess uses capnproto under the hood/
07:44 < sipa> But it doesn't (and can't) provide the Bitcoin Core RPC interface. It's used to provide the multiprocess interface.
07:45 < sipa> P2P also doesn't use libevent; it uses raw socket. It also doesn't provide the RPC interface (nor the multiprocess interface); it provides the P2P interface.
07:46 < sipa> If you're using Linux, and using bitcoin-qt, Qt is likely for some part at least using a UNIX domain socket to communicate with the X graphics driver. So if your goal was "I want my Bitcoin Core to use UNIX domain sockets!!!", then you probably already have it.
07:48 < MarcoFalke> why would using sockets be a goal by itself?
07:48 < sipa> It's not. That was my point - you don't care about using UNIX domain sockets on itself.
07:48 < MarcoFalke> right. It shouldn't matter too much to the user what multiprocess uses internally to communicate
07:49 < sipa> RPC, P2P, multiprocess, UI... they're all distinct ways in which Bitcoin Core interacts with other processes/systems; ... and they all have different needs, and use different tools to accomplish that. Just because one uses a particular technology under the hood doesn't mean it's easy to make another one use the same technology.
07:59 < michaelfolkson> I was thinking (incorrectly) that because multiprocess uses UNIX sockets that meant there was UNIX socket support for the equivalent of multiprocess RPC
07:59 < michaelfolkson> Thanks for the explanation
08:06 -!- vasild [~vd@user/vasild] has joined #bitcoin-core-dev
08:10 -!- bomb-on [~bomb-on@194.144.47.113] has quit [Quit: aллилѹіа!]
08:13 -!- grettke [~grettke@184.62.226.206] has joined #bitcoin-core-dev
08:14 -!- jespada [~jespada@87.74.33.157] has quit [Ping timeout: 256 seconds]
08:14 -!- grettke [~grettke@184.62.226.206] has quit [Read error: Connection reset by peer]
08:17 -!- jespada [~jespada@87.74.33.157] has joined #bitcoin-core-dev
08:18 -!- bomb-on [~bomb-on@194.144.47.113] has joined #bitcoin-core-dev
08:20 -!- arythmetic [~arythmeti@2605:8d80:680:c4f1:490d:4a8e:de79:f1a4] has joined #bitcoin-core-dev
08:24 -!- x88x88x [~x88x88x@149.28.53.172] has quit [Ping timeout: 240 seconds]
08:25 -!- jarthur [~jarthur@2603-8080-1540-002d-2893-5a12-7df9-5067.res6.spectrum.com] has joined #bitcoin-core-dev
08:31 -!- grettke [~grettke@184.62.226.206] has joined #bitcoin-core-dev
08:31 -!- x88x88x [~x88x88x@2001:19f0:5:39a8:5400:3ff:feb6:73cb] has joined #bitcoin-core-dev
08:32 -!- grettke [~grettke@184.62.226.206] has quit [Read error: Connection reset by peer]
08:41 -!- andrewtoth [~andrewtot@gateway/tor-sasl/andrewtoth] has quit [Remote host closed the connection]
08:42 -!- erik1 [~erik@181-191-0-203.uplinkx.com.br] has joined #bitcoin-core-dev
08:42 -!- Guest97 [~Guest97@181-191-0-203.uplinkx.com.br] has quit [Quit: Client closed]
08:44 -!- kexkey [~kexkey@static-198-54-132-89.cust.tzulo.com] has joined #bitcoin-core-dev
08:45 < jamesob> Okay, it seems something has changed with how -maxtipage is handled... I wonder if any of the commandline args handling stuff has changed (in this case `args.GetIntArg`)? Because I'm passing `-maxtipage=999999999999` and by the time we hit IsIBD, its value is 0
08:45 < jamesob> This wasn't the case last time I did assumeutxo functional testing a month or two ago
08:48 < jamesob> Hm, wonder if it was this change: https://github.com/bitcoin/bitcoin/commit/4343f114cc661cf031ec915538c11b9b030e2e15#diff-19427b0dd1a791adc728c82e88f267751ba4f1c751e19262cac03cccd2822216L597-R595
08:51 -!- vasild [~vd@user/vasild] has quit [Remote host closed the connection]
08:51 -!- vasild [~vd@user/vasild] has joined #bitcoin-core-dev
08:53 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Remote host closed the connection]
08:54 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #bitcoin-core-dev
08:55 -!- arythmetic [~arythmeti@2605:8d80:680:c4f1:490d:4a8e:de79:f1a4] has quit [Remote host closed the connection]
08:56 -!- geyaeb [~geyaeb@gateway/tor-sasl/geyaeb] has quit [Remote host closed the connection]
08:59 < jamesob> Ah yep, that was it. The value I'd been passing in the test script was too large for int64; old code I guess interpreted it as `std::numeric_limits<uint64_t>::max()`, new code gives 0. Little concerning that we don't warn on the incompatibility
08:59 -!- geyaeb [~geyaeb@gateway/tor-sasl/geyaeb] has joined #bitcoin-core-dev
09:00 -!- arythmetic [~arythmeti@38.112.106.99] has joined #bitcoin-core-dev
09:01 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Remote host closed the connection]
09:01 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #bitcoin-core-dev
09:06 -!- x88x88x [~x88x88x@2001:19f0:5:39a8:5400:3ff:feb6:73cb] has quit [Ping timeout: 240 seconds]
09:09 -!- tla2k21 [~tla2k21@gateway/tor-sasl/tla2k21] has quit [Remote host closed the connection]
09:09 -!- tla2k21 [~tla2k21@gateway/tor-sasl/tla2k21] has joined #bitcoin-core-dev
09:13 -!- jb55 [~jb55@user/jb55] has joined #bitcoin-core-dev
09:21 < MarcoFalke> jamesob: Integer overflow inside atoi is UB or at least unspecified behavior, last time I checked
09:22 -!- x88x88x [~x88x88x@149.28.53.172] has joined #bitcoin-core-dev
09:22 < MarcoFalke> That is: Parsing 999999999999 can give you any value (it doesn't have to be 0 or max or 999999999999 mod max)
09:23 < MarcoFalke> jamesob: It is also not used in consensus code, so this is not a consensus change
09:24 < jamesob> this is not consensus? https://github.com/bitcoin/bitcoin/pull/20452/files#diff-1db27ed1bfbf61ea0fe64447413ef9f24238be710e7ca4ae9c7bc7a5c994eca0L72-R72
09:26 < jamesob> so here's the tricky thing: our atoi64 wasn't actually using atoi, but strtoll - for which oveflow behavior is well defined: "The strtol() function returns the result of the conversion, unless the value would underflow or overflow. If an underflow occurs, strtol() returns LONG_MIN. If an overflow occurs, strtol() returns LONG_MAX."
09:26 < jamesob> ("The strtoll() function works just like the strtol() function but returns a long long integer value.")
09:28 < MarcoFalke> Yeah, not consensus. Could be used by bitcoin-util or some RPC function.
09:29 < jamesob> Phew
09:29 < MarcoFalke> Oh, I wasn't aware it is safe and saturating to produce an overflow. Still, an explicit error would be better than silent saturation.
09:32 < jamesob> Right... I think we should implement either full backwards compatibility to strtoll or an explicit error
09:36 < luke-jr> idk, being able to put 9999999999999 is convenient :p
09:37 < luke-jr> depends on the context it's used I suppose
09:37 < jamesob> luke-jr: I certainly thought so haha
09:37 < jamesob> but I mean the point is that IMO (even if it's a minor issue) we shouldn't change that behavior implicitly
09:38 < sipa> It was an unintended behavior change; such things should be caught during review.
09:38 < sipa> Whether the change is desirable or not, it shouldn't be made unintentionally.
09:41 < MarcoFalke> for bitcoin-tx it was broken either way (with or without overflow), already fixed in #23227
09:41 <@gribble> https://github.com/bitcoin/bitcoin/issues/23227 | bitcoin-tx: Avoid treating integer overflow as OP_0 by MarcoFalke · Pull Request #23227 · bitcoin/bitcoin · GitHub
09:42 < MarcoFalke> Same for rest, also fixed (#23213)
09:42 <@gribble> https://github.com/bitcoin/bitcoin/issues/23213 | rest: Return error when header count is not integral by MarcoFalke · Pull Request #23213 · bitcoin/bitcoin · GitHub
09:42 < MarcoFalke> I think arg parsing is the only place remaining that is affected by odd behavior
09:43 < MarcoFalke> If saturation is something that people rely on, we should have a test for this
09:43 < MarcoFalke> *should have had
09:44 < MarcoFalke> For a quick fix I expect saturation to be easier to re-add. Still, (long term) I'd prefer InitError on startup
09:46 < jamesob> I'll add saturation in the PR
09:48 < jamesob> Will also create an issue to surface InitErrors if we don't already have one
09:48 < luke-jr> MarcoFalke: kinda hard to remember maxint64's value tho; maybe if we also parse "inf" or something? :/
09:48 < luke-jr> or "max" might be more correct
09:48 < jamesob> luke-jr: I think just maintaining strict compatbility with the old method (strtoll) is probably the way to go
09:49 < MarcoFalke> jamesob: If you add saturation, please also add a test ;)
09:50 < jamesob> MarcoFalke: sure; though technically the one I already wrote should cover it, but agree that's maybe too implicit
09:50 < MarcoFalke> luke-jr: I understand why you don't want to rebase this and I support your choice, but practically speaking it takes less than a few seconds for you to rebase. However, modifying the merge script will take at least a few minutes. So picking the way of least resistance should be trivial here.
09:51 < jamesob> MarcoFalke: luke-jr: I think I'm missing context here... talking about same issue?
09:51 < MarcoFalke> jamesob: Right, should be enough if you add one more case for negative overflow
09:51 < MarcoFalke> jamesob: It is a separate thread 
09:51 < jamesob> gotcha
09:52 < MarcoFalke> (didn't want to spam github for it)
09:59 -!- x88x88x [~x88x88x@149.28.53.172] has quit [Ping timeout: 260 seconds]
10:06 -!- x88x88x [~x88x88x@149.28.53.172] has joined #bitcoin-core-dev
10:13 < sipa> ha, i didn't know this: cirrus has a big bitcoin core logo on their site under "Trusted by Open Source": https://cirrus-ci.org/
10:18 -!- bomb-on [~bomb-on@194.144.47.113] has quit [Quit: aллилѹіа!]
10:25 < luke-jr> MarcoFalke: perhaps, but shouldn't the merge script get fixed anyway?
10:25 < luke-jr> what's very curious there, is that my PR doesn't even *touch* the "conflicted" file
10:25 -!- bomb-on [~bomb-on@194.144.47.113] has joined #bitcoin-core-dev
10:25 < MarcoFalke> Yeah, it is a GitHub bug, but they are not interested in fixing it
10:25 < luke-jr> so I'm really at a loss for what's going on there
10:26 < MarcoFalke> I am not going to fix the merge script, maybe someone else?
10:26 < luke-jr> jamesob: we're discussing #23027
10:26 <@gribble> https://github.com/bitcoin/bitcoin/issues/23027 | Bugfix: Skip tests for tools not being built by luke-jr · Pull Request #23027 · bitcoin/bitcoin · GitHub
10:26 < luke-jr> MarcoFalke: does the merge script care what GitHub thinks? why? O.o
10:27 < MarcoFalke> Just a belt-and-suspender? Idk, I didn't write that
10:27 < MarcoFalke> Or to detect GitHub malfunction?
10:27 -!- yanmaani [~yanmaani@gateway/tor-sasl/yanmaani] has quit [Remote host closed the connection]
10:27 < jamesob> luke-jr: ah,t hanks
10:28 -!- yanmaani [~yanmaani@gateway/tor-sasl/yanmaani] has joined #bitcoin-core-dev
10:29 < luke-jr> skimming through the merge script, I don't see anything that I would expect to fail :/
10:31 < MarcoFalke> luke-jr: It fetches /merge from GitHub and compares it with the local one
10:31 < MarcoFalke> Just run it against your pull
10:32 < luke-jr> oh, and /merge doesn't exist because of github's issue :/
10:35 < luke-jr> sigh, rebased it
10:35 < luke-jr> do you happen to have the issue # for the github issue handy?
10:39 < MarcoFalke> No, it is an email thread from June 2018
10:39 -!- jarthur [~jarthur@2603-8080-1540-002d-2893-5a12-7df9-5067.res6.spectrum.com] has quit [Ping timeout: 240 seconds]
11:11 -!- mode/#bitcoin-core-dev [-b *!*@42.117.112.245] by ChanServ
11:13 -!- x88x88x [~x88x88x@149.28.53.172] has quit [Ping timeout: 240 seconds]
11:25 -!- x88x88x [~x88x88x@2001:19f0:5:39a8:5400:3ff:feb6:73cb] has joined #bitcoin-core-dev
11:26 -!- dviola [~diego@2803:2a00:2:f91d:76c:deb:ee80:6b4c] has joined #bitcoin-core-dev
11:42 -!- dviola [~diego@2803:2a00:2:f91d:76c:deb:ee80:6b4c] has left #bitcoin-core-dev [WeeChat 3.3]
11:43 -!- x88x88x [~x88x88x@2001:19f0:5:39a8:5400:3ff:feb6:73cb] has quit [Ping timeout: 240 seconds]
11:43 -!- jarthur [~jarthur@2603-8080-1540-002d-800a-95c0-a608-9494.res6.spectrum.com] has joined #bitcoin-core-dev
11:51 -!- x88x88x [~x88x88x@149.28.53.172] has joined #bitcoin-core-dev
12:00 < jamesob> Hm, did @gribble stop reporting on opened PRs?
12:07 -!- lukedashjr [~luke-jr@user/luke-jr] has joined #bitcoin-core-dev
12:10 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Ping timeout: 240 seconds]
12:11 -!- lukedashjr is now known as luke-jr
12:19 -!- yanmaani [~yanmaani@gateway/tor-sasl/yanmaani] has quit [Ping timeout: 276 seconds]
12:22 -!- mikehu44 [~quassel@206.189.41.250] has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
12:27 -!- yanmaani [~yanmaani@gateway/tor-sasl/yanmaani] has joined #bitcoin-core-dev
12:30 -!- sdfgsdfg [~sdfgsdfg@user/sdfgsdfg] has joined #bitcoin-core-dev
12:31 -!- Guest5811 [~Guest58@c-24-5-204-159.hsd1.ca.comcast.net] has joined #bitcoin-core-dev
12:31 -!- Guest5811 [~Guest58@c-24-5-204-159.hsd1.ca.comcast.net] has quit [Client Quit]
12:34 -!- grettke [~grettke@184.62.226.206] has joined #bitcoin-core-dev
12:39 -!- kexkey [~kexkey@static-198-54-132-89.cust.tzulo.com] has quit [Ping timeout: 256 seconds]
12:41 -!- kexkey [~kexkey@static-198-54-132-103.cust.tzulo.com] has joined #bitcoin-core-dev
12:44 -!- lukedashjr [~luke-jr@user/luke-jr] has joined #bitcoin-core-dev
12:46 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Ping timeout: 256 seconds]
12:46 -!- lukedashjr is now known as luke-jr
13:04 -!- ___nick___ [~quassel@cpc68286-cdif17-2-0-cust533.5-1.cable.virginm.net] has quit [Ping timeout: 260 seconds]
13:16 -!- darosior [~darosior@194.36.189.246] has quit [Quit: darosior]
13:16 -!- rex4539 [~rex4539@gateway/tor-sasl/rex4539] has joined #bitcoin-core-dev
13:17 -!- darosior [~darosior@194.36.189.246] has joined #bitcoin-core-dev
13:31 < dongcarl> Hey all, wondering if anyone has an idea on how best to test this functionality: https://github.com/bitcoin/bitcoin/blob/63b5dfac21613b984803347bfe81454da667016e/src/validation.cpp#L2225-L2230
13:31 < dongcarl> Basically we don't want to prune past the blockfilter index's best block.
13:31 < dongcarl> Thinking naively, a test would likely: 1. generate 200 blocks 2. sync the index up to 
13:32 < dongcarl> 200 blocks, 3. Stop the index, 4. generate another 500 blocks, 5. attempt to prune 300 blocks, 6. assert that only 200 were pruned
13:33 -!- arythmetic [~arythmeti@38.112.106.99] has quit [Remote host closed the connection]
13:34 < dongcarl> Okay I might have answered my own question by typing it out... 😅
13:34 -!- lukedashjr [~luke-jr@user/luke-jr] has joined #bitcoin-core-dev
13:34 < _aj_> dongcarl: was trying to figure out what the subtlety was :)
13:35 < dongcarl> :)
13:37 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Ping timeout: 240 seconds]
13:38 -!- lukedashjr is now known as luke-jr
13:56 -!- Talkless [~Talkless@mail.dargis.net] has quit [Quit: Konversation terminated!]
14:22 -!- Gimble [~G1mble2@2a01:4b00:8e07:7900:e79c:6460:44ed:8423] has quit [Quit: Leaving]
15:10 -!- Guyver2_ [~Guyver@guyver2.xs4all.nl] has joined #bitcoin-core-dev
15:12 -!- Guyver2 [Guyver@guyver2.xs4all.nl] has quit [Ping timeout: 256 seconds]
15:12 -!- Guyver2_ is now known as Guyver2
15:16 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:6834:5866:4b21:4a8b] has joined #bitcoin-core-dev
15:17 -!- sdfgsdfg [~sdfgsdfg@user/sdfgsdfg] has quit [Quit: ZzzZ]
15:19 -!- jarthur [~jarthur@2603-8080-1540-002d-800a-95c0-a608-9494.res6.spectrum.com] has quit [Ping timeout: 240 seconds]
15:20 -!- grettke [~grettke@184.62.226.206] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
15:24 -!- jarthur [~jarthur@2603-8080-1540-002d-4ce9-7fd7-2373-9fbb.res6.spectrum.com] has joined #bitcoin-core-dev
15:36 -!- grettke [~grettke@184.62.226.206] has joined #bitcoin-core-dev
15:41 -!- jarthur [~jarthur@2603-8080-1540-002d-4ce9-7fd7-2373-9fbb.res6.spectrum.com] has quit [Quit: jarthur]
15:45 -!- grettke [~grettke@184.62.226.206] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
15:55 -!- jarthur [~jarthur@2603-8080-1540-002d-4ce9-7fd7-2373-9fbb.res6.spectrum.com] has joined #bitcoin-core-dev
15:55 -!- grettke [~grettke@184.62.226.206] has joined #bitcoin-core-dev
15:59 < luke-jr> dongcarl: did you see #21726 ?
15:59 <@gribble> https://github.com/bitcoin/bitcoin/issues/21726 | Improve Indices on pruned nodes via prune blockers by fjahr · Pull Request #21726 · bitcoin/bitcoin · GitHub
15:59 < dongcarl> luke-jr: Did not! Will take a look
16:03 -!- Guyver2 [~Guyver@guyver2.xs4all.nl] has quit [Quit: Going offline, see ya! (www.adiirc.com)]
16:06 -!- grettke [~grettke@184.62.226.206] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
16:12 -!- bomb-on [~bomb-on@194.144.47.113] has quit [Quit: aллилѹіа!]
16:14 < jeremyrubin> howdy planet core. if you've had a chance to review and are feeling <something> on BIP-119 feel free to send me private feedback, positive or negative or if you feel that you could comment publicly you can pr (yes or no) to add your position to utxos.org/signals.
16:15 < jeremyrubin> (several folks have given me private feedback already which has been very helpful)
16:16 -!- grettke [~grettke@184.62.226.206] has joined #bitcoin-core-dev
16:20 < luke-jr> jeremyrubin: why not a wiki page like every other similar chart?
16:20 < jeremyrubin> luke-jr: it's a github repo
16:21 < jeremyrubin> you can just edit the data files and open PR.
16:21 < luke-jr> that's more effort than editing a wiki page :P
16:22 < luke-jr> (hmm, would be nice if github let people make PRs without having a fullblown repo fork..)
16:23 < jeremyrubin> you can i think?
16:23 < jeremyrubin> I just edit the page on github's website
16:23 < luke-jr> "These “soft signals” are non-binding until an actual concrete proposal has been formed, but are useful for measuring community consensus." <-- if you only include prominent people, I don't know that it's useful for that
16:23 < jeremyrubin> https://github.com/JeremyRubin/utxos.org/edit/master/data/devs.yaml
16:24 < jeremyrubin> luke-jr anyone who asks to be there is up there. the highlights were just that people were complaining about a bunch of unrecognizable names,
16:25 < luke-jr> i c
16:25 < luke-jr> still, the community is much wider than any webpage will ever show :P
16:25 < jeremyrubin> yep!
16:26 < jeremyrubin> i agree 100%... just needed 'something' to get an understanding of who has evaluated and likes it and if anyone wants anyone to read their dissent 
16:26 < jeremyrubin> and i've been pretty vocal about asking people to signal +/-
16:26 < jeremyrubin> not a perfect process by far
16:26 < jeremyrubin> do you have any suggestions on how to widen the net?
16:26 < jeremyrubin> Or other way to measure soft consensus?
16:30 -!- grettke [~grettke@184.62.226.206] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
16:31 -!- jarthur [~jarthur@2603-8080-1540-002d-4ce9-7fd7-2373-9fbb.res6.spectrum.com] has quit [Quit: jarthur]
16:36 -!- grettke [~grettke@184.62.226.206] has joined #bitcoin-core-dev
16:50 -!- grettke [~grettke@184.62.226.206] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
16:53 -!- An0rak [An0rak@user/an0rak] has joined #bitcoin-core-dev
17:17 -!- emcy_ [~emcy@user/emcy] has joined #bitcoin-core-dev
17:20 -!- emcy [~emcy@user/emcy] has quit [Ping timeout: 256 seconds]
17:24 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:6834:5866:4b21:4a8b] has quit [Remote host closed the connection]
17:24 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:6834:5866:4b21:4a8b] has joined #bitcoin-core-dev
17:59 -!- grettke [~grettke@184.62.226.206] has joined #bitcoin-core-dev
18:03 -!- grettke [~grettke@184.62.226.206] has quit [Client Quit]
18:05 -!- sdfgsdfg [~sdfgsdfg@user/sdfgsdfg] has joined #bitcoin-core-dev
18:07 -!- grettke [~grettke@184.62.226.206] has joined #bitcoin-core-dev
18:07 -!- grettke [~grettke@184.62.226.206] has quit [Read error: Connection reset by peer]
18:29 < jamesob> jeremyrubin: I'm pretty close to Concept ACK, just gotta take a few days to wander in the CTV desert
18:43 < jeremyrubin> 👍
18:44 -!- emcy_ [~emcy@user/emcy] has quit [Quit: Leaving]
19:05 -!- mikehu44 [~quassel@206.189.41.250] has joined #bitcoin-core-dev
19:05 -!- emcy [~emcy@user/emcy] has joined #bitcoin-core-dev
19:26 < jeremyrubin> FYI in response to some private feedback i've clarified a few points in the BIP around alternative vault designs (the original one is outdated from my latest thinking) and activation stuff https://github.com/bitcoin/bips/pull/1257 
19:27 < jeremyrubin> Much appreciated! If anyone else has anything they find confusing or unclear in the BIP language happy to add further clarifications
19:56 -!- saranshsharma [~saranshsh@59.93.233.14] has joined #bitcoin-core-dev
20:52 -!- saranshsharma [~saranshsh@59.93.233.14] has quit [Remote host closed the connection]
20:53 -!- saranshsharma [~saranshsh@59.93.233.14] has joined #bitcoin-core-dev
20:53 -!- jarthur [~jarthur@2603-8080-1540-002d-4ce9-7fd7-2373-9fbb.res6.spectrum.com] has joined #bitcoin-core-dev
20:54 -!- sdfgsdfg [~sdfgsdfg@user/sdfgsdfg] has quit [Quit: ZzzZ]
20:57 -!- saranshsharma [~saranshsh@59.93.233.14] has quit [Ping timeout: 268 seconds]
21:01 -!- cmirror [~cmirror@4.53.92.114] has quit [Remote host closed the connection]
21:01 -!- cmirror [~cmirror@4.53.92.114] has joined #bitcoin-core-dev
21:29 -!- sdfgsdfg [~sdfgsdfg@user/sdfgsdfg] has joined #bitcoin-core-dev
21:30 -!- jarthur [~jarthur@2603-8080-1540-002d-4ce9-7fd7-2373-9fbb.res6.spectrum.com] has quit [Quit: jarthur]
21:35 -!- jarthur [~jarthur@2603-8080-1540-002d-4ce9-7fd7-2373-9fbb.res6.spectrum.com] has joined #bitcoin-core-dev
21:40 -!- tooru [uid532895@user/tooru] has joined #bitcoin-core-dev
21:48 -!- earnestly [~earnest@user/earnestly] has quit [Ping timeout: 240 seconds]
21:53 -!- jarthur [~jarthur@2603-8080-1540-002d-4ce9-7fd7-2373-9fbb.res6.spectrum.com] has quit [Quit: jarthur]
22:01 -!- jarthur [~jarthur@2603-8080-1540-002d-4ce9-7fd7-2373-9fbb.res6.spectrum.com] has joined #bitcoin-core-dev
22:13 -!- mikehu44 [~quassel@206.189.41.250] has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
22:15 -!- jarthur [~jarthur@2603-8080-1540-002d-4ce9-7fd7-2373-9fbb.res6.spectrum.com] has quit [Quit: jarthur]
23:21 -!- sdfgsdfg [~sdfgsdfg@user/sdfgsdfg] has quit [Quit: ZzzZ]
23:43 -!- vasild [~vd@user/vasild] has quit [Ping timeout: 276 seconds]
23:52 -!- geyaeb [~geyaeb@gateway/tor-sasl/geyaeb] has quit [Remote host closed the connection]
23:53 -!- geyaeb [~geyaeb@gateway/tor-sasl/geyaeb] has joined #bitcoin-core-dev
--- Log closed Thu Dec 23 00:00:09 2021