<bitcoin-git>
bitcoin/master 70a55c0 Andrew Chow: psbt: Avoid unsigned int overflow in PSBT_IN_TAP_BIP32_DERIVATION
<bitcoin-git>
bitcoin/master 0094ff3 fanquake: Merge bitcoin/bitcoin#25812: psbt: Avoid unsigned int overflow in PSBT_IN_...
<bitcoin-git>
[bitcoin] fanquake merged pull request #25812: psbt: Avoid unsigned int overflow in PSBT_IN_TAP_BIP32_DERIVATION (master...psbt-hd-path-int-overflow) https://github.com/bitcoin/bitcoin/pull/25812
brunoerg has quit [Ping timeout: 268 seconds]
brunoerg has joined #bitcoin-core-dev
andrewtoth_ has joined #bitcoin-core-dev
_andrewtoth_ has quit [Remote host closed the connection]
AaronvanW has quit [Remote host closed the connection]
AaronvanW has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 268 seconds]
mudsip has joined #bitcoin-core-dev
brunoerg has joined #bitcoin-core-dev
AaronvanW has quit [Remote host closed the connection]
<bitcoin-git>
[bitcoin] glozow opened pull request #25820: [test] make tx6 child of tx5, not tx3, in rbf_tests (master...2022-08-rbf-test-fix) https://github.com/bitcoin/bitcoin/pull/25820
<bitcoin-git>
bitcoin/master 49db42c glozow: [test] make tx6 child of tx5, not tx3, in rbf_tests
<bitcoin-git>
bitcoin/master dd62721 fanquake: Merge bitcoin/bitcoin#25820: [test] make tx6 child of tx5, not tx3, in rbf...
<bitcoin-git>
[bitcoin] fanquake merged pull request #25820: [test] make tx6 child of tx5, not tx3, in rbf_tests (master...2022-08-rbf-test-fix) https://github.com/bitcoin/bitcoin/pull/25820
mudsip has joined #bitcoin-core-dev
Kaizen_Kintsugi_ has quit [Ping timeout: 268 seconds]
yanmaani has quit [Ping timeout: 268 seconds]
yanmaani has joined #bitcoin-core-dev
Kaizen_Kintsugi_ has joined #bitcoin-core-dev
mudsip has quit []
SpellChecker has quit [Remote host closed the connection]
<laanwj>
kanzure: i'm not sure yet; to start, i'll not merge anything anymore and not do the releases anymore
<sipa>
laanwj: It's not a surprise, and I very much understand where you're coming from - but I'm still sad to see you go. Thank you so much for carrying the project all this time; it certainly wasn't easy. Good luck, with whatever comes next.
<laanwj>
i'm not planning to completely disappear
<cfields>
laanwj: thanks for those 10 years. what an amazing legacy!
<kanzure>
glad you're not disappearing, and thank you for all the hard work
<stickies-v>
thank you for all those years of dedication and great work, sad I wasn't part of it for longer but very much appreciated!
<josie[m]>
laanwj: feels a bit trite to just say thanks for 10 years of work, but seriously, thank you. not only for your contributions but for also being welcoming to new contributors (like myself)
Talkless has quit [Quit: Konversation terminated!]
<laanwj>
it makes me sad too, but, i'm having burnout and health issues, i just cannot do this anymore
<laanwj>
thank you!
<cold>
thank you for being excellent.
<laanwj>
we have some great and enthousiastic maintainers who are already doing most of the work right now, so i'm confident the project will carry on being great
<achow101>
that does bring up a few logistical questions though. like management of the github orgs and the bitcoincore.org website
<kanzure>
are you planning to attend the october meeting
<laanwj>
kanzure: probably
livestradamus has joined #bitcoin-core-dev
<instagibbs>
retirement party, with cake
<instagibbs>
jk
<kanzure>
yes
<cfields>
:)
<laanwj>
achow101: yes
<laanwj>
instagibbs: lol!
<laanwj>
ok, that was my announcement, we don't need to figure out every single detail in the meeting
<cold>
(with a person inside who bursts out and distributes high-quality sbc that use ecc and have lots of ram on them for everyone)
<cold>
(sorry)
<laanwj>
cold: lol
<laanwj>
i don't think there were any pre-proposed meetings this week (you can propose them with #proposedmeetingtopic)
<laanwj>
any last minute ones?
<jarolrod>
a note of appreciation for people like fanquake and MacroFake who do so much, and will surely do a great job on high level project organization in laanwj absence
<sipa>
Indeed, jarolrod!
<laanwj>
jarolrod: +1!
<laanwj>
they have already been doing that, i have been less involved over time
<laanwj>
#topic High priority for review
<core-meetingbot>
topic: High priority for review
<instagibbs>
4 days from feature freeze, yes?
<glozow>
thank you for everything you’ve done laanwj 🙏
<MacroFake>
laanwj: Sad to see you go (and the reason for your departure), but I can relate. Thank you for all your work and all the best for your health and whatever is ahead.
<fanquake>
I think we could get both of those in. Even if it meant pushing feature freeze back slight. Both worthwhile. Would be good to help the wallet migration on.
<laanwj>
if everyone wants those two PRs to make it in i'm sure we can get some review
<MacroFake>
Are there any non-bugfix features that would be good in 24.0? Maybe #19602 ? If it looks like they'll receive enough review in a week or so, we could postpone the feature freeze by that much?
<laanwj>
though wallet migration is kind of risky, maybe it could be added as experimental, not as something recommended
<instagibbs>
or just longer seasoning in master post-split?
<achow101>
it could be marked experimental
<laanwj>
it's something that needs testing with a wide variety of wallets, probably best way to get that is to put it in a rc
<achow101>
it's also rpc only, and no mention of it anywhere else, so the only people who would use it are those seeking it out
<laanwj>
but as experimental, and easy to roll back if it doesn't work as expected
<laanwj>
right
<luke-jr>
-experimentalrpc= perhaps in the most extreme case
<achow101>
I don't think that will be necessary
<laanwj>
that would be more extreme, i think just not recommending it yet, and mentioining it in the help that it is experimental, is enough in practice
Kaizen_Kintsugi_ has quit [Remote host closed the connection]
Kaizen_Kintsugi_ has joined #bitcoin-core-dev
<laanwj>
MacroFake: right
<laanwj>
ok, any other proposed features? any other topics?
<laanwj>
if not, closing the meeting, see you next time, well i guess we'll need to find someone else to do the meeting too, though no hurry
<sipa>
Do you have `chain=X` in your bitcoin.cinf?
<sipa>
conf
<Kaizen_Kintsugi_>
i bet I do
<Kaizen_Kintsugi_>
yup
<Kaizen_Kintsugi_>
I sure do
<sipa>
It's combining the config entries from the file and the command line.
<Kaizen_Kintsugi_>
Is this worthy of a bug or just my miss use of the software?
<sipa>
It is functioning exactly as intended. You're giving it two distinct contradictory instructions.
<Kaizen_Kintsugi_>
Cool
<Kaizen_Kintsugi_>
Would the error message benefit from stating that a chain argument is coming from conf and the commandline?
<sipa>
Maybe. I'm not sure if our config logic currently even tracks where things come from.
<Kaizen_Kintsugi_>
Ah sounds a bit more complicated than I thought.
Guest56 has quit [Ping timeout: 252 seconds]
denise[m] has joined #bitcoin-core-dev
vysn has joined #bitcoin-core-dev
Kaizen_Kintsugi_ has quit [Remote host closed the connection]
Kaizen_Kintsugi_ has joined #bitcoin-core-dev
Kaizen_Kintsugi_ has quit [Ping timeout: 252 seconds]
Kaizen_Kintsugi_ has joined #bitcoin-core-dev
Kaizen_Kintsugi_ has quit [Ping timeout: 268 seconds]
evanlinjin has quit [Remote host closed the connection]
evanlinjin has joined #bitcoin-core-dev
Intdtti has joined #bitcoin-core-dev
Kaizen_Kintsugi_ has joined #bitcoin-core-dev
yanmaani has quit [Remote host closed the connection]
yanmaani has joined #bitcoin-core-dev
_apex2_ has joined #bitcoin-core-dev
Kaizen_Kintsugi_ has quit [Remote host closed the connection]
Kaizen_Kintsugi_ has joined #bitcoin-core-dev
_andrewtoth_ has quit [Remote host closed the connection]
_andrewtoth_ has joined #bitcoin-core-dev
yanmaani has quit [Ping timeout: 268 seconds]
jonatack has quit [Ping timeout: 252 seconds]
_andrewtoth_ has quit [Remote host closed the connection]
_andrewtoth_ has joined #bitcoin-core-dev
brunoerg has quit [Remote host closed the connection]
brunoerg has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 264 seconds]
yanmaani has joined #bitcoin-core-dev
brunoerg has joined #bitcoin-core-dev
<Kaizen_Kintsugi_>
Is there any guidance or resources on debugging bitcoin, Ideally I would like to run it through vscode, run a command and go through each of the steps of the software
bomb-on has quit [Read error: Connection reset by peer]
bomb-on has joined #bitcoin-core-dev
<Kaizen_Kintsugi_>
Some odd differences between signet and main, I'm running two different bitcoind nodes(is this the way? or can one node operate across many chains?) getnewaddress is requesting an rpcwallet filename