--- Log opened Mon Aug 16 00:00:39 2021
00:08 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has joined #bitcoin-core-dev
00:23 -!- grettke [~grettke@cpe-65-29-228-30.wi.res.rr.com] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
00:23 -!- stick[m] [~stickmatr@2001:470:69fc:105::98c] has joined #bitcoin-core-dev
00:24 -!- babasancheti [~babasanch@43.249.232.30] has quit [Quit: Client closed]
00:26 -!- vhs43[m] [~vhs43matr@2001:470:69fc:105::ba6d] has joined #bitcoin-core-dev
00:29 -!- darosior [~darosior@194.36.189.246] has quit [Quit: ya vps net disruption]
00:29 -!- darosior [~darosior@194.36.189.246] has joined #bitcoin-core-dev
00:30 -!- darosior [~darosior@194.36.189.246] has quit [Client Quit]
00:30 -!- darosior [~darosior@194.36.189.246] has joined #bitcoin-core-dev
00:38 -!- darosior [~darosior@194.36.189.246] has quit [Quit: darosior]
00:38 -!- darosior [~darosior@194.36.189.246] has joined #bitcoin-core-dev
00:39 -!- darosior [~darosior@194.36.189.246] has quit [Client Quit]
00:40 -!- darosior [~darosior@194.36.189.246] has joined #bitcoin-core-dev
00:40 -!- bomb-on [~bomb-on@194.144.47.113] has joined #bitcoin-core-dev
00:40 -!- darosior [~darosior@194.36.189.246] has quit [Client Quit]
00:40 -!- darosior [~darosior@194.36.189.246] has joined #bitcoin-core-dev
00:41 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 246 seconds]
00:41 -!- darosior [~darosior@194.36.189.246] has quit [Client Quit]
00:42 -!- darosior [~darosior@194.36.189.246] has joined #bitcoin-core-dev
00:54 -!- lkqwejhhgasdjhgn [~kljkljklk@p200300d46f05b80032ea23541467908d.dip0.t-ipconnect.de] has joined #bitcoin-core-dev
01:00 -!- Talkless [~Talkless@mail.dargis.net] has joined #bitcoin-core-dev
01:09 -!- bomb-on [~bomb-on@194.144.47.113] has quit [Quit: aллилѹіа!]
01:15 -!- earnestly [~earnest@user/earnestly] has joined #bitcoin-core-dev
01:19 -!- babasancheti [~babasanch@43.249.232.30] has joined #bitcoin-core-dev
01:22 -!- bomb-on [~bomb-on@194.144.47.113] has joined #bitcoin-core-dev
01:49 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
01:49 < bitcoin-git> [bitcoin] MarcoFalke pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/3facf0a8ae99...42b00a37580a
01:49 < bitcoin-git> bitcoin/master fa77183 MarcoFalke: fuzz: Avoid OOM in system fuzz target
01:49 < bitcoin-git> bitcoin/master 42b00a3 MarcoFalke: Merge bitcoin/bitcoin#22649: fuzz: Avoid OOM in system fuzz target
01:49 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
01:50 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
01:50 < bitcoin-git> [bitcoin] MarcoFalke merged pull request #22649: fuzz: Avoid OOM in system fuzz target (master...2108-fuzzSystemOOM) https://github.com/bitcoin/bitcoin/pull/22649
01:50 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
01:52 -!- bomb-on [~bomb-on@194.144.47.113] has quit [Quit: aллилѹіа!]
02:04 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has quit [Ping timeout: 245 seconds]
02:24 -!- Guyver2_ [Guyver@guyver2.xs4all.nl] has joined #bitcoin-core-dev
02:24 -!- aitorjs [~aitorjs@184.76.76.188.dynamic.jazztel.es] has joined #bitcoin-core-dev
02:27 -!- Guyver2 [Guyver@guyver2.xs4all.nl] has quit [Ping timeout: 245 seconds]
02:29 -!- aitorjs [~aitorjs@184.76.76.188.dynamic.jazztel.es] has quit [Client Quit]
02:35 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-dev
02:37 -!- jungly_ [~jungly@host-87-9-31-76.retail.telecomitalia.it] has joined #bitcoin-core-dev
02:55 -!- prayank [~andr0irc@51.158.144.32] has joined #bitcoin-core-dev
02:58 < prayank> luke-jr: CI is failing for #22693
02:58 <@gribble> https://github.com/bitcoin/bitcoin/issues/22693 | RPC/Wallet: Add "use_txids" to output of getaddressinfo by luke-jr · Pull Request #22693 · bitcoin/bitcoin · GitHub
02:58 -!- emzy [~quassel@user/emzy] has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]
03:28 < laanwj> PSA: 0.21.2rc1 binaries up https://bitcoincore.org/bin/bitcoin-core-0.21.2/test.rc1/
03:28 < fanquake> 🚀
03:36 -!- kuler [~kulernil@gateway/tor-sasl/kuler] has quit [Remote host closed the connection]
03:42 -!- jungly_ [~jungly@host-87-9-31-76.retail.telecomitalia.it] has quit [Ping timeout: 245 seconds]
03:44 < jonatack> congrats!
03:46 -!- vysn [~vysn@user/vysn] has quit [Ping timeout: 245 seconds]
03:57 -!- belcher_ is now known as belcher
04:21 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
04:46 -!- kuler [~kulernil@gateway/tor-sasl/kuler] has joined #bitcoin-core-dev
04:57 -!- kuler [~kulernil@gateway/tor-sasl/kuler] has left #bitcoin-core-dev [Leaving]
05:14 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has joined #bitcoin-core-dev
05:14 -!- b10c [uid500648@id-500648.charlton.irccloud.com] has joined #bitcoin-core-dev
05:19 -!- dermoth [~dermoth@user/dermoth] has quit [Quit: Leaving]
05:22 -!- maria_elis [~iskra@2804:14d:78c3:a3c0:1a3d:a2ff:fe09:cec4] has quit [Quit: WeeChat 2.8]
05:28 < prayank> I was reading the comments in this issue and wanted to know if someone has written any blog post or detailed answer somewhere that explains eviction process followed by Bitcoin Core.
05:28 < prayank> https://github.com/bitcoin/bitcoin/issues/22716
05:31 -!- gribble [~gribble@bitcoin/bot/gribble] has quit [Remote host closed the connection]
05:31 < prayank> Another question: vasild mentioned in this comment that onlynet=ipv4 with Tor proxy is contradictory. Is it possible that someone wants to have only ipv4 nodes for outgoing but use Tor proxy for making these connections?
05:31 < prayank> https://github.com/bitcoin/bitcoin/pull/22651#issuecomment-895069245
05:34 < laanwj> right: using a proxy is independent from which network classes you want to connect to
05:35 < laanwj> this is why the network is called *onion*, it's only about .onions, it's perfectly valid to want to use tor to connect to ipv4 only
05:35 < laanwj> people keep confusing this, in other places as well
05:39 < prayank> laanwj: Thanks. That clears my doubt I had in second question.
05:59 -!- gribble [~gribble@bitcoin/bot/gribble] has joined #bitcoin-core-dev
05:59 -!- mode/#bitcoin-core-dev [+o gribble] by ChanServ
06:02 -!- goatpig [~goat@blocksettle-gw.cust.31173.se] has quit [Quit: Konversation terminated!]
06:02 < vasild> prayank: laanwj: ok, specifying onlynet=ipv4 with "a proxy to connect to *.onion addresses" is contradictory (because *.onion addresses are not ipv4 so we would not be connecting to them). But specifying an outgoing socks5 proxy for reaching ipv4 address is not contradictory, it may as well be some normal (non-tor) socks5 proxy required to be used in some certain network environments.
06:04 -!- pinheadmz [~pinheadmz@hns-contributor.dev] has joined #bitcoin-core-dev
06:04 < vasild> so "onlynet=ipv4 onion=..." is contradictory, but "onlynet=ipv4 proxy=..." is not. So far, so good. Now... onion= defaults to proxy= :-X
06:04 < sipa> vasild: not *exactly*; with onlynet=ipv4 you can still specify .onions in -connect or addnode i believe
06:04 < sipa> but it's very close
06:05 < vasild> oh, well, that too :)
06:07 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
06:07 < bitcoin-git> [bitcoin] jamesob closed pull request #22699: doc: add libboost-thread-dev to build-unix (master...2021-08-build-unix-boost-thread) https://github.com/bitcoin/bitcoin/pull/22699
06:07 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
06:12 < prayank> I think we should remove "only" from `onlynet` to reduce confusion around these options. Maybe `net_out` if underscores are okay.
06:13 -!- gene [~gene@2a0a:3840:1337:127:0:b9c1:7fec:1337] has quit [Quit: drained and gutted]
06:13 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Ping timeout: 258 seconds]
06:14 -!- emzy [~quassel@user/emzy] has joined #bitcoin-core-dev
06:14 < laanwj> yes, the option name is confusing; as for underscores, iirc there are no option names with any kind of separator right now, probably better to keep it that way (underscores work really badly with - options)
06:15 < jonatack> I'm not sure how config options can be changed without breaking user space. Even if only to rename them.  Is it really worth it, etc.
06:15 < laanwj> yeah...
06:15 -!- luke-jr [~luke-jr@user/luke-jr] has joined #bitcoin-core-dev
06:16 < jonatack> Right, I recall we had an irc discussion about config options naming some time ago, and the consensus was to continue with no separators
06:16 < prayank> jonatack: I have seen few other users confused about this option. So I am assuming the option is already not used correctly by many. So it's already broken.
06:17 < jonatack> prayank: the issue is about breaking user space for those who do use them, not for those who don't
06:18 -!- vysn [~vysn@user/vysn] has joined #bitcoin-core-dev
06:18 < prayank> If 100 people are using this option. I am assuming 30 are not using it correctly or unaware of issues.
06:19 < jonatack> in any case, i proposed some doc changes in #22648 to clarify the use of -onlynet 
06:19 <@gribble> https://github.com/bitcoin/bitcoin/issues/22648 | doc, test: improve i2p/tor docs and i2p reachable unit tests by jonatack · Pull Request #22648 · bitcoin/bitcoin · GitHub
06:19 < jonatack> in both tor.md and i2p.md
06:21 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Ping timeout: 245 seconds]
06:22 < prayank> Yes I have ACKed it with couple of nits. Hopefully docs should help users understand this option.
06:25 < jonatack> prayank: thanks! i'll look at the feedback.  it also depends on what we do with  #22651.
06:25 <@gribble> https://github.com/bitcoin/bitcoin/issues/22651 | tor: respect non-onion -onlynet= for outgoing Tor connections by vasild · Pull Request #22651 · bitcoin/bitcoin · GitHub
06:38 -!- luke-jr [~luke-jr@user/luke-jr] has joined #bitcoin-core-dev
06:41 -!- iramaro [~lore@187.3.220.187] has joined #bitcoin-core-dev
06:42 -!- lukedashjr [~luke-jr@user/luke-jr] has joined #bitcoin-core-dev
06:43 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Ping timeout: 240 seconds]
06:46 -!- luke-jr [~luke-jr@user/luke-jr] has joined #bitcoin-core-dev
06:47 -!- lukedashjr [~luke-jr@user/luke-jr] has quit [Ping timeout: 258 seconds]
06:49 < laanwj> bitcoin-cli prints "timeout on transient error: ..." when the RPC port is not open, this is slightly confusing (though it does appropriately print a message about bitcoind not running afterwards)
06:53 -!- lukedashjr [~luke-jr@user/luke-jr] has joined #bitcoin-core-dev
06:53 -!- lukedashjr [~luke-jr@user/luke-jr] has quit [Read error: Connection reset by peer]
06:54 -!- lukedashjr [~luke-jr@user/luke-jr] has joined #bitcoin-core-dev
06:56 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Ping timeout: 245 seconds]
06:57 -!- luke-jr [~luke-jr@user/luke-jr] has joined #bitcoin-core-dev
06:59 -!- lukedashjr [~luke-jr@user/luke-jr] has quit [Ping timeout: 240 seconds]
07:02 -!- emcy [~emcy@user/emcy] has quit [Quit: Leaving]
07:06 -!- bomb-on [~bomb-on@194.144.47.113] has joined #bitcoin-core-dev
07:15 -!- emcy [~emcy@user/emcy] has joined #bitcoin-core-dev
08:03 -!- aechu [~major@gateway/tor-sasl/major] has quit [Remote host closed the connection]
08:27 -!- meshcollider [meshcollid@user/meshcollider] has quit [Remote host closed the connection]
08:44 -!- meshcollider [meshcollid@meshcollider.jujube.ircnow.org] has joined #bitcoin-core-dev
08:48 -!- gambpang [~ian@207.181.230.156] has joined #bitcoin-core-dev
09:00 -!- prayank [~andr0irc@51.158.144.32] has quit [Quit: irc thread exit]
09:03 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
09:03 < bitcoin-git> [bitcoin] MarcoFalke opened pull request #22718: doc: Add missing PR 16333 release note (master...2108-docRel) https://github.com/bitcoin/bitcoin/pull/22718
09:03 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
09:16 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
09:16 < bitcoin-git> [bitcoin] MarcoFalke pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/42b00a37580a...b935abb9eb2e
09:16 < bitcoin-git> bitcoin/master e2ff385 Sebastian Falbesoner: test: check for invalid `-prune` parameters
09:16 < bitcoin-git> bitcoin/master b935abb MarcoFalke: Merge bitcoin/bitcoin#22684: test: check for invalid `-prune` parameters
09:16 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
09:17 -!- lkqwejhhgasdjhgn [~kljkljklk@p200300d46f05b80032ea23541467908d.dip0.t-ipconnect.de] has quit [Quit: Konversation terminated!]
09:26 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
09:26 < bitcoin-git> [bitcoin] MarcoFalke closed pull request #22684: test: check for invalid `-prune` parameters (master...202108-test-check_invalid_prune_parameters) https://github.com/bitcoin/bitcoin/pull/22684
09:26 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
09:38 -!- jonatack [~jonatack@user/jonatack] has quit [Quit: Client closed]
09:41 -!- lightlike [~lightlike@user/lightlike] has joined #bitcoin-core-dev
09:44 -!- babasancheti [~babasanch@43.249.232.30] has quit [Quit: Client closed]
09:51 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has quit [Ping timeout: 245 seconds]
09:53 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-dev
09:57 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has joined #bitcoin-core-dev
09:57 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
09:57 < bitcoin-git> [bitcoin] hebasto closed pull request #19882: depends: Export variables from make to environment explicitly (master...200905-build) https://github.com/bitcoin/bitcoin/pull/19882
09:57 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
10:01 -!- grettke [~grettke@cpe-65-29-228-30.wi.res.rr.com] has joined #bitcoin-core-dev
10:24 < BlueMatt> the standardization of any segwit output script is less useful for lightning and upgradability of similar systems than it looks because we don't know today what the dust limit will be on these outputs in the future
10:25 < BlueMatt> would it be reasonable to commit(-ish) to a fixed dust limit based on today's calculation for future segwit output types (and, relatedly, it apepars the dust limits were not changed for taproot, is that on purpose or should we consider it a feature not a bug :)
10:25 < BlueMatt> cc sipa 
10:37 -!- jonatack [~jonatack@user/jonatack] has quit [Quit: Client closed]
10:39 -!- bomb-on [~bomb-on@194.144.47.113] has quit [Quit: aллилѹіа!]
10:43 -!- gene [~gene@gateway/tor-sasl/gene] has joined #bitcoin-core-dev
10:45 -!- Guest6 [~Guest6@2804:14d:b083:538e:2c0d:59ca:11d4:1b4b] has joined #bitcoin-core-dev
10:46 -!- Guest6 [~Guest6@2804:14d:b083:538e:2c0d:59ca:11d4:1b4b] has quit [Client Quit]
10:47 < michaelfolkson> BlueMatt: I'm not sure what a commit(-ish)ment looks like or who could provide it. I'd guess (like a number of things in this space) that it would only change if it became absurd and hence was easier to get consensus on changing it
10:49 < sipa> BlueMatt: i think it's an oversight, i hadn't really thought about this
10:50 < BlueMatt> sipa: I mean obviously I'd kinda prefer we not change it, or change it ever again for segwit outputs, at least from a lightning perspective, but its an interesting question.
10:50 < BlueMatt> sipa: I wonder if maybe it makes sense to bump it in a one-time change and then leave it?
10:50 < BlueMatt> like, set it to something calculated on 5 sat/vbyte or 10 sat/vbyte instead of 3, so that it doesn't float down to 1 if future versions require larger witnesses?
10:50 < sipa> BlueMatt: i mean, it's per node configurable even - i'm not sure the current approach maps well to a well-defined promise
10:51 < sipa> as a config settin
10:51 < BlueMatt> I mean in practice no one overrides that, and also in practice whether we like it or not its an important security metric for lightning nodes.
10:51 < BlueMatt> whether we like it or not, lightning is very sensitive to transaction propagation.
10:51 < sipa> i'm very uncomfortable with anything relying on it being predictable tbh
10:51 < BlueMatt> then suggest an entirely different L2 system :p
10:52 < BlueMatt> and novel one
10:53 < BlueMatt> the standardness rules are now a security assumption for large amounts of money, even though they were never really intended to be that explicit.
10:53 < sipa> that's beyond scary to me
10:53 < BlueMatt> well I dont think think "sorry, you shouldn't use lightning, we cant do anything for it" is an acceptable answer
10:53 < sipa> can't you just have it loudly complain to users when something doesn't seem to confirm, yelling that they should be broadcasting it through smoke signals or so
10:54 < sipa> sorry, very tired, i'm not very useful to discuss things right now
10:54 < BlueMatt> most users dont monitor their node actively
10:54 < BlueMatt> and even if they did, what do you tell them? call your local mining pool? I mean I dunno if any would respond lol
10:54 < sipa> i don't have an answer
10:55 < BlueMatt> well then back to the specific initial question - should we bump/drop the dust threshold for taproot outputs
10:55 < BlueMatt> and if so, can we just bump it once and set it for segwit outputs with a "we hope to keep this in the future metric
10:55 < sipa> i'm ok with that
10:56 < BlueMatt> for future segwit versions, that is
10:56 < sipa> key path spending for p2tr outputs is probably a very reasonable lower bound of spending weight
10:57 < BlueMatt> right, so probably use that weight and a slightly higher dust fee rate and move on?
10:57 < BlueMatt> cause 3 is quite low, though changing for existing segwit stuff is probably unreasonably high change for the ecosystem
11:00 < sipa> just reducing the spending weight calculation for p2tr and other witness versions seems like something that could reasonably be called a bugfix
11:01 < sipa> anything beyond, including some plan on a fixed policy (yuck, hardcoded feerates :s). sounds like it'd need a wider discussion
11:01 < BlueMatt> sure, but I dunno if "reduce dust threshold" is a good thing a-priori. eg 3 sat/vbyte is a quite-low feerate in a modern context, so a-priori it may make sense to increase not decrease. more to the point - if we're talking about dust thresholds for *future* segwit versions, I don't know that we want to go for a lower-bound, more like "reasonable upper-bound"
11:06 < harding> LN doesn't need to use the same dust limit Bitcoin Core does.  Y'all can choose to treat as dust outputs that would cost more to spend than they're worth at 20 s/b, and so be insulated against any reasonable change in Bitcoin Core (especially since changes in Bitcoin Core should take a long time to become predominant across relay and mining).
11:06 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has quit [Ping timeout: 240 seconds]
11:06 < BlueMatt> true, but you *really* dont want a low dust threshold in lightning, there's already more than enough issues with funds loss due to burning-to-dust
11:06 < BlueMatt> errr, high dust threshold
11:11 < harding> Sure, but if feerates increase significantly (and that certainly seems like a plausible scenario), those problems are going to need to be dealt with anyway.  I don't think we should be forcing anyone to deal with those problems now, but I also kinda feel like some of the attention on the dust limit problem should be focused on improving LN rather than changing Bitcoin Core.
11:18 < BlueMatt> well its somewhat of a tradeoff in LN - you can just include dust outputs with no desire to ever claim them, or at least only maybe claim them, which is probably better for ln than skipping those outputs
11:18 < BlueMatt> but of course that's massively anti-social cause you just create outputs on chain you'll never claim
11:18 < BlueMatt> which is kinda the reason for the dust limit in core to begin with - to prevent stupid anti-social behavior like that.
11:19 < BlueMatt> so if lightning "has to deal with it" you get anti-social outcomes, probably.
11:23 < harding> I meant "deal with it" in the sense of implementing probabalistic payments or bundling tiny payments into a pre-funded output that gets donated to charity or some other solution.
11:24 < BlueMatt> right, could bundle "below dust" outputs to charity instead of sending to miners.
11:24 < BlueMatt> or just burn them with OP_RETURN
11:24 < BlueMatt> "charity" of reducing total bitcoin supply :)
11:26 -!- AaronvanW [~AaronvanW@190.150.148.22] has joined #bitcoin-core-dev
11:27 < BlueMatt> of course even that doesn't "solve" the issue without some kind of commonly agreed upon lower-bound
11:27 < harding> Yeah.  We could also have a very low dust limit for pay to OP_TRUE, since miners will be able to remove those from the UTXO set during future periods of low prevailing feerates.
11:27 < BlueMatt> cause lightning nodes have to enforce the rules on *each other*
11:28 -!- bomb-on [~bomb-on@194.144.47.113] has joined #bitcoin-core-dev
11:29 < BlueMatt> no, OP_TRUE does not solve the issue
11:30 < BlueMatt> right now lightning with a counterparty who is, or is collaborating with a miner, is really really not ok
11:30 < harding> I don't think it's any worse than paying to fees?
11:31 < BlueMatt> right, its the *same* as paying to fees, but the problem right now is precisely that paying to fees is not ok :p
11:31 < harding> It might be better in the sense that, for very low values, it's not economical for the current miner to claim it, so it's pay to future miner.
11:32 < BlueMatt> sure, its more social, but it doesn't solve the issue lightning has today
11:32 -!- gene_ [~gene@gateway/tor-sasl/gene] has joined #bitcoin-core-dev
11:32 < harding> Sure, but if that's the problem, someone should be working on probabalistic payments.  That certainly wants new opcodes, which is why it's probably better someone start working on it sooner.
11:32 -!- gene_ [~gene@gateway/tor-sasl/gene] has quit [Client Quit]
11:33 -!- gene_ [~gene@gateway/tor-sasl/gene] has joined #bitcoin-core-dev
11:33 -!- jessebarton [~jessebart@ip72-203-188-10.tu.ok.cox.net] has quit [Ping timeout: 248 seconds]
11:33 < BlueMatt> there are other shorter-term changes we can make to address the issues without prob payments, but everything around the dust limit sucks, precisely cause we can't get some reasonable lower-bound that ensures broadcastability
11:34 -!- gene [~gene@gateway/tor-sasl/gene] has quit [Remote host closed the connection]
11:37 < harding> I mean, you do have a reasonable lower bound---the current bound, which should take at least months to change in all non-emergency scenarios (and which seems unlikely to ever require an emergency change).
11:38 < BlueMatt> sadly we need one for non-v0 segwit outputs as well
11:38 < BlueMatt> which was my original question here - what is a reasonable lowerbound for non-v0 segwit outputs
11:38 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-dev
11:38 < harding> And it should be easy for any future changes to just gate that with a time delay, e.g. if (time > x) { new_dust_limit } else { old_dust_limit }
11:39 < BlueMatt> sure, but that kind of thing requires at least a loose commitment from bitcoin core to do dust limit changes in a way that is compatible with that :p
11:39 < BlueMatt> which, when the response to questions like this is "lol lightning shouldnt rely on dust limit being X", then I dont feel like we have that
11:40 < harding> Sure, but I think Bitcoin Core's open development process has a pretty strong commitment to listening to LN devs and other ecosystem devs, so I think that's implicitly covered
11:40 < harding> Sorry.
11:41 < BlueMatt> that's what I'd generally expect, but i dunno many/any lightning devs who follow bitcoin core closely enough to ensure that, which is part of the reason for me flagging now that non-v0 segwit output dust limit *also* falls under the "plz notify lightning devs and give us time to adapt before you change this" category
11:41 < BlueMatt> because it isn't trivially obvious for core devs that it would fall into that category, I'd think
11:42 < harding> That's one of the reasons we publish "notable merged PRs" in the Optech newsletter each week.  We've covered every standardness change in the past three years, so any LN devs who read the newsletter should be made aware of any changes well before they get released, and can then go and ask for reverts or alterations.
11:44 < harding> I know someone reading about the merge of disabling BIP37 by default ended up in the discussion that got it continued for an extra release, so that kind of communication works at least some times.
11:47 -!- jessebarton [~jessebart@184.179.34.210] has joined #bitcoin-core-dev
11:52 -!- common [~common@096-033-221-075.res.spectrum.com] has joined #bitcoin-core-dev
12:02 -!- gene_ is now known as gene
12:04 -!- jesseposner [~jesse@2601:647:0:89:6c85:a85c:e54c:19e5] has joined #bitcoin-core-dev
12:08 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
12:08 < bitcoin-git> [bitcoin] MarcoFalke pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/b935abb9eb2e...8a40b227a61b
12:08 < bitcoin-git> bitcoin/master fa76ebd MarcoFalke: doc: Add missing PR 16333 release note
12:08 < bitcoin-git> bitcoin/master 8a40b22 MarcoFalke: Merge bitcoin/bitcoin#22718: doc: Add missing PR 16333 release note
12:08 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
12:08 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
12:08 < bitcoin-git> [bitcoin] MarcoFalke merged pull request #22718: doc: Add missing PR 16333 release note (master...2108-docRel) https://github.com/bitcoin/bitcoin/pull/22718
12:08 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
12:20 -!- dermoth [~dermoth@user/dermoth] has joined #bitcoin-core-dev
12:22 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has joined #bitcoin-core-dev
12:23 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
12:23 < bitcoin-git> [bitcoin] jonatack closed pull request #22586: p2p: fix ubsan implicit conversion error in CSubNet::ToString() (master...fix-netaddress-implicit-signed-integer-truncation) https://github.com/bitcoin/bitcoin/pull/22586
12:23 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
12:24 -!- jessebarton85 [~jessebart@ip72-203-188-10.tu.ok.cox.net] has joined #bitcoin-core-dev
12:25 -!- raj [~raj_@2409:4061:28c:fa97:22d0:ec36:363c:bb08] has joined #bitcoin-core-dev
12:26 -!- jessebarton [~jessebart@184.179.34.210] has quit [Ping timeout: 240 seconds]
12:27 -!- muhblockchain [~muhblockc@user/muhblockchain] has quit [Ping timeout: 272 seconds]
13:31 -!- raj [~raj_@2409:4061:28c:fa97:22d0:ec36:363c:bb08] has quit [Read error: Connection reset by peer]
13:42 -!- maria_elis [~iskra@2804:14d:78c3:a3c0:1a3d:a2ff:fe09:cec4] has joined #bitcoin-core-dev
13:47 -!- Talkless [~Talkless@mail.dargis.net] has quit [Quit: Konversation terminated!]
13:52 -!- notmandatory [~notmandat@shindig.notmandatory.org] has quit [Ping timeout: 240 seconds]
13:52 -!- notmandatory [~notmandat@shindig.notmandatory.org] has joined #bitcoin-core-dev
13:53 -!- Guyver2_ [Guyver@guyver2.xs4all.nl] has quit [Quit: Going offline, see ya! (www.adiirc.com)]
13:56 -!- grettke [~grettke@cpe-65-29-228-30.wi.res.rr.com] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
14:06 -!- Ananta-shesha [~pjetcetal@2.95.210.188] has quit [Ping timeout: 268 seconds]
14:59 -!- jnewbery [~john@user/jnewbery] has quit [Ping timeout: 276 seconds]
15:00 -!- jnewbery [~john@user/jnewbery] has joined #bitcoin-core-dev
15:06 -!- grettke [~grettke@cpe-65-29-228-30.wi.res.rr.com] has joined #bitcoin-core-dev
15:20 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has quit [Ping timeout: 240 seconds]
15:44 -!- vysn [~vysn@user/vysn] has quit [Ping timeout: 240 seconds]
15:46 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has joined #bitcoin-core-dev
16:23 -!- vnogueira [~vnogueira@user/vnogueira] has quit [Ping timeout: 244 seconds]
16:26 -!- lightlike [~lightlike@user/lightlike] has quit [Quit: Leaving]
16:38 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has quit [Ping timeout: 245 seconds]
16:42 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #bitcoin-core-dev
17:20 -!- gene [~gene@gateway/tor-sasl/gene] has quit [Quit: gene]
17:32 -!- b10c [uid500648@id-500648.charlton.irccloud.com] has quit [Quit: Connection closed for inactivity]
17:39 -!- vnogueira [~vnogueira@user/vnogueira] has joined #bitcoin-core-dev
17:43 -!- bomb-on [~bomb-on@194.144.47.113] has quit [Quit: aллилѹіа!]
17:49 -!- contrapumpkin [~woohoo@user/copumpkin] has joined #bitcoin-core-dev
17:50 -!- copumpkin [~woohoo@user/copumpkin] has quit [Ping timeout: 248 seconds]
17:56 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
17:56 < bitcoin-git> [bitcoin] fanquake pushed 3 commits to master: https://github.com/bitcoin/bitcoin/compare/8a40b227a61b...df30375788ef
17:56 < bitcoin-git> bitcoin/master 14b4802 fanquake: wallet: use FormatFullVersion instead of CLIENT_BUILD in rpcdump
17:56 < bitcoin-git> bitcoin/master 2d7534b fanquake: wallet: use PACKAGE_NAME instead of "Bitcoin" in rpcdump
17:56 < bitcoin-git> bitcoin/master df30375 fanquake: Merge bitcoin/bitcoin#22715: wallet: use `FormatFullVersion()` & `PACKAGE_...
17:56 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
17:57 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
17:57 < bitcoin-git> [bitcoin] fanquake merged pull request #22715: wallet: use `FormatFullVersion()` & `PACKAGE_NAME` in dumpwallet (master...rpcdump_use_formatfullversion) https://github.com/bitcoin/bitcoin/pull/22715
17:57 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
18:17 -!- gambpang [~ian@207.181.230.156] has quit [Ping timeout: 258 seconds]
18:17 -!- belcher_ [~belcher@user/belcher] has joined #bitcoin-core-dev
18:21 -!- belcher [~belcher@user/belcher] has quit [Ping timeout: 256 seconds]
18:43 -!- BUSY [~BUSY@user/busy] has joined #bitcoin-core-dev
19:05 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
19:05 < bitcoin-git> [bitcoin] fanquake pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/df30375788ef...f3dbd1c2b2bc
19:05 < bitcoin-git> bitcoin/master 60e0cbd Amiti Uttarwar: [addrman] Merge the two Add() functions
19:05 < bitcoin-git> bitcoin/master f3dbd1c fanquake: Merge bitcoin/bitcoin#22627: [addrman] De-duplicate Add() function
19:05 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
19:08 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
19:08 < bitcoin-git> [bitcoin] fanquake closed pull request #22627: [addrman] De-duplicate Add() function (master...2021-08-merge-add) https://github.com/bitcoin/bitcoin/pull/22627
19:08 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
19:13 -!- earnestly [~earnest@user/earnestly] has quit [Ping timeout: 240 seconds]
19:21 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Ping timeout: 245 seconds]
19:25 -!- luke-jr [~luke-jr@user/luke-jr] has joined #bitcoin-core-dev
20:12 -!- Ananta-shesha [~pjetcetal@2.95.210.196] has joined #bitcoin-core-dev
20:25 -!- gambpang [~ian@207.181.230.156] has joined #bitcoin-core-dev
20:48 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Remote host closed the connection]
20:48 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #bitcoin-core-dev
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:03 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Remote host closed the connection]
21:03 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #bitcoin-core-dev
21:24 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
21:25 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #bitcoin-core-dev
21:38 -!- AaronvanW [~AaronvanW@190.150.148.22] has quit [Remote host closed the connection]
21:46 -!- gambpang [~ian@207.181.230.156] has quit [Ping timeout: 248 seconds]
21:47 -!- gambpang [~ian@207.181.230.156] has joined #bitcoin-core-dev
22:10 -!- reallll [~belcher@user/belcher] has joined #bitcoin-core-dev
22:11 -!- belcher_ [~belcher@user/belcher] has quit [Ping timeout: 245 seconds]
22:24 -!- AaronvanW [~AaronvanW@190.150.148.22] has joined #bitcoin-core-dev
22:26 -!- vysn [~vysn@user/vysn] has joined #bitcoin-core-dev
22:54 -!- AaronvanW [~AaronvanW@190.150.148.22] has quit [Ping timeout: 248 seconds]
22:58 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
22:58 < bitcoin-git> [bitcoin] fanquake opened pull request #22721: doc: add inital PR and author list to 0.21.2 release notes (0.21...0_21_2rc1_prelim_relnotes) https://github.com/bitcoin/bitcoin/pull/22721
22:58 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
22:58 -!- gambpang [~ian@207.181.230.156] has quit [Ping timeout: 268 seconds]
22:58 -!- gambpang [~ian@207.181.230.156] has joined #bitcoin-core-dev
23:10 -!- reallll is now known as belcher
23:23 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
23:23 < bitcoin-git> [bitcoin] pranabp-bit closed pull request #22673: rpc: Add function walletestimatefee (master...walletestimatefee) https://github.com/bitcoin/bitcoin/pull/22673
23:23 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
23:26 -!- gambpang [~ian@207.181.230.156] has quit [Ping timeout: 258 seconds]
23:26 -!- gambpang [~ian@207.181.230.156] has joined #bitcoin-core-dev
23:32 -!- AaronvanW [~AaronvanW@190.150.148.22] has joined #bitcoin-core-dev
23:45 -!- goatpig [~goat@blocksettle-gw.cust.31173.se] has joined #bitcoin-core-dev
23:51 -!- raj [~raj_@2409:4061:28c:fa97:1397:4171:6289:f64] has joined #bitcoin-core-dev
23:51 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
23:51 < bitcoin-git> [bitcoin] pranabp-bit opened pull request #22722: rpc: update estimatesmartfee (master...estimatesmartfee) https://github.com/bitcoin/bitcoin/pull/22722
23:51 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
23:59 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has joined #bitcoin-core-dev
--- Log closed Tue Aug 17 00:00:40 2021