<Zaidan>
I'm looking for configuration options to add a suffix to the pid name so I can run multiple nodes from different branches and know which one is which, any suggestions?
<jarthur>
I don't know of anything out of the box, but there are some runtime tricks. Assuming you give your branch instances different datadirs, you'll get a separate bitcoind.pid in each.
<sipa>
You can't run two instances out of the same datadir anyway, so I don't think it's useful (and likely problematic) to make them use distinct pidfiles.
<sipa>
Though you can provide the -pidfile=FILE command line argument if you really want to.
<laanwj>
i doubt it's useful but it's not going to give problems because the mechanism to lock datadir is independent from the pid file
<provoostenator>
achow101: that RPC is marked experimental anyway, so it might be good to get it in to see if any wallets in the wild don't work with it.
PaperSwordAlt has quit [Ping timeout: 252 seconds]
emcy has quit [Ping timeout: 252 seconds]
<laanwj>
ok, so it seems the answer is 'feature freeze needs to be postponed further', as i've heard mention of three PRs now
Talkless has quit [Quit: Konversation terminated!]
<provoostenator>
Seems so, unless there's any reason we want to ship 24.0 real soon?
<laanwj>
not that i know of
<laanwj>
it is a slightly uncommon way of working, we've never really delayed the feature freeze for non critical features, it was 'what makes it in makes it in'
<luke-jr>
maybe make 1 week from today a hard deadline for enforcing that then?
<vasild>
I am ok to drop #25355 from 24 if people think it is rushed or needs more time/review.
<laanwj>
those PRs have been close to merge for quite a time now and there has to be a cut-off point, bu there's no reason why it'd need to be today
<glozow>
+1 25717 is my priority rn
<laanwj>
luke-jr: sgtm, if others agree
<vasild>
the i2p one is a "nice to have", not "must have"
<luke-jr>
arguably features are always "nice to have" - there's always 25.x :P
<vasild>
:P
<laanwj>
fwiw i'll be traveling next week so i'll not be here
<luke-jr>
o
<laanwj>
not that it matters someone else can easily pick up the meeting
<dongcarl>
last minute topic: libbitcoinkernel update
<laanwj>
dongcarl: noted
<laanwj>
#topic full-rbf maximalism vs gentle phase-out of opt-in RBF (ariard)
<core-meetingbot>
topic: full-rbf maximalism vs gentle phase-out of opt-in RBF (ariard)
sipsorcery has joined #bitcoin-core-dev
<lightlike>
when suggesting that topic, ariard added he wasn't sure if he could make it to the meeting.
<laanwj>
ok, that seems the case
<laanwj>
let's postpone it for another meeting then?
<vasild>
is there a problem with the current state of rbf?
toumbot has joined #bitcoin-core-dev
<luke-jr>
devs need to stop trying to dictate policies for users. if some users want "full RBF", they should be able to have it. Likewise, opt-in RBF.
<glozow>
this is a signaling question, though the answer to your question is yes, there’s room for improvement
<lightlike>
Can't speak for him, but I think he probably wanted to discuss different possibilities to transition to full-rbf:
<lightlike>
Support for preferential peering (#25600) vs changing the default vs doing nothing (having it as an option that is off per default)
<gribble>
https://github.com/bitcoin/bitcoin/issues/25600 | p2p: Advertise `NODE_REPLACE_BY_FEE` and connect to 1 outbound full-rbf peer if `mempoolfullrbf` sets by ariard · Pull Request #25600 · bitcoin/bitcoin · GitHub
<glozow>
sure, i run a full rbf node, 🤷🏻♀️ but merging full rbf default or preferential peering is a different question. agree to postpone this topic for when ariard is here.
<dongcarl>
Hi all, I’ll be leaving Chaincode Labs next week and will no longer be contributing full time to Bitcoin Core. I won’t be entirely gone, just contributing within the restriction of my leftover bandwidth (IIRC fjahr has been doing this).
<dongcarl>
I’ve tapped TheCharlatan as the point person for driving forward libbitcoinkernel (although I see all contributors, reviewers, and PR authors whose PRs we depend on as part of the libbitcoinkernel effort).
<dongcarl>
I strongly believe that he has the right skillset and drive for completing what’s left of phase 1 of libbitcoinkernel and making phase 2 happen. I’m currently ramping him up, and he is set to be able to devote full-time attention starting November and I will assist in helping him find full-time sponsors (there are parties who have indicated
<dongcarl>
interest already).
<dongcarl>
TheCharlatan: Perhaps you’d like to introduce yourself, what you’ve done in the past, what your interest is in libbitcoinkernel?
brunoerg has quit [Ping timeout: 268 seconds]
<vasild>
:(
<Zaidan>
well thank you for your contributions carl
mudsip has joined #bitcoin-core-dev
brunoerg has joined #bitcoin-core-dev
<glozow>
😭
toumbot has quit [Ping timeout: 248 seconds]
<dongcarl>
I will still be an alive human though! (at least I expect to be)
* dongcarl
nudges TheCharlatan
<laanwj>
phew!
<TheCharlatan>
carl's are big shoes to fill, but he's been super helpful in getting men up to speed so far
<sipa>
I was hoping for a bit more than "alive".
<luke-jr>
lol
<luke-jr>
libbitcoinkernel aside, is anyone going to be actively maintaining the guix stuff? :x
<fanquake>
yes?
<dongcarl>
luke-jr: Oh I think fanquake and hebasto have been doing more than an excellent job
<luke-jr>
ok, sorry, I don't mean to downplay their work, I don't pay close attention to the "who" on PRs
<laanwj>
but yes it was a bit of a shock to me as well to hear you're moving to something else, I fully understand of course. Hopefully TheCharlatan can take it over the finish line.
<dongcarl>
TheCharlatan: Perhaps you can speak a bit about your past work?
<sipa>
Will he turn into TheCarlatan?
<dongcarl>
OH NO
<TheCharlatan>
I've been lurking here since a long time, and am keen to keep carl's work alive. Im also a guix user, so over time I hope to keep at it as well. I'll slowly ramp up my contributions over the next months.
<dongcarl>
You have uncovered my ploy
<dongcarl>
The current plan is to have TheCharlatan do chainparams<->ArgsManager circular dependency decoupling as the first PR, we'll see as we go along!
<cfields>
I intend to step up and help TheCharlatan out with the libkernel work/review as well. I've fallen off a bit lately (again) but am trying to find my way back (again) :)
brunoerg has joined #bitcoin-core-dev
toumbot has joined #bitcoin-core-dev
Zaidan has quit [Remote host closed the connection]
sipsorcery has quit [Read error: Connection reset by peer]
SpellChecker_ has quit [Remote host closed the connection]
SpellChecker has joined #bitcoin-core-dev
<jnewbery>
dongcarl: thanks for all of your contributions and good luck in your next adventure :)
sipsorcery has joined #bitcoin-core-dev
Zaidan has joined #bitcoin-core-dev
<cfields>
+1
Zaidan has quit [Ping timeout: 260 seconds]
mudsip has quit []
_apex_ has joined #bitcoin-core-dev
<dongcarl>
Thanks jnewbery! :-)
_apex_ has quit [Ping timeout: 252 seconds]
Zaidan has joined #bitcoin-core-dev
<bitcoin-git>
[bitcoin] furszy opened pull request #25933: wallet: AvailableCoins, simplify output script type acquisition (master...2022_wallet_availablecoins_type_cleanup) https://github.com/bitcoin/bitcoin/pull/25933
<bitcoin-git>
[bitcoin] brunoerg opened pull request #25934: wallet, rpc: add `label` to `listsinceblock` (master...2022-08-add-label-listsinceblock) https://github.com/bitcoin/bitcoin/pull/25934
Zaidan has joined #bitcoin-core-dev
toumbot has joined #bitcoin-core-dev
bytes1440000 has joined #bitcoin-core-dev
<bytes1440000>
luke-jr: agree with you devs need to stop trying to dictate policies for users. if some users want "full RBF", they should be able to have it. Likewise, opt-in RBF.
<bytes1440000>
i have a default nack for such changes
bytes1440000 has left #bitcoin-core-dev [#bitcoin-core-dev]
toumbot has quit [Ping timeout: 248 seconds]
Guest74 has quit [Quit: Client closed]
Zaidan has quit [Remote host closed the connection]
Zaidan has joined #bitcoin-core-dev
brunoerg has quit []
Guest5524 has joined #bitcoin-core-dev
Guest5524 has quit [Client Quit]
Flipster has quit [Quit: Client closed]
toumbot has joined #bitcoin-core-dev
Zaidan has quit [Read error: Connection reset by peer]
Zaidan has joined #bitcoin-core-dev
sipsorcery has quit [Ping timeout: 268 seconds]
toumbot has quit [Ping timeout: 244 seconds]
Zaidan has quit [Remote host closed the connection]