Kaizen_Kintsugi_ has quit [Ping timeout: 244 seconds]
Kaizen_Kintsugi_ has joined #bitcoin-core-dev
Kaizen_K_ has joined #bitcoin-core-dev
Kaizen_Kintsugi_ has quit [Ping timeout: 240 seconds]
evanlinjin has quit [Remote host closed the connection]
ghost43 has quit [Remote host closed the connection]
yanmaani has quit [Remote host closed the connection]
vasild has quit [Remote host closed the connection]
vasild has joined #bitcoin-core-dev
evanlinjin has joined #bitcoin-core-dev
ghost43 has joined #bitcoin-core-dev
Kaizen_Kintsugi_ has joined #bitcoin-core-dev
Kaizen_K_ has quit [Ping timeout: 240 seconds]
yanmaani has joined #bitcoin-core-dev
Kaizen_Kintsugi_ has quit [Ping timeout: 272 seconds]
<bitcoin-git>
[bitcoin] JeremyRubin opened pull request #25560: [WIP] Add a MAINTAINERS.md file and desribe the role of maintainer more directly (master...maintainer-role) https://github.com/bitcoin/bitcoin/pull/25560
Kaizen_Kintsugi_ has joined #bitcoin-core-dev
Kaizen_Kintsugi_ has quit [Ping timeout: 244 seconds]
Kaizen_Kintsugi_ has joined #bitcoin-core-dev
Kaizen_K_ has joined #bitcoin-core-dev
Kaizen___ has joined #bitcoin-core-dev
Kaizen_Kintsugi_ has quit [Ping timeout: 244 seconds]
Kaizen_K_ has quit [Ping timeout: 240 seconds]
Kaizen___ has quit [Ping timeout: 240 seconds]
Kaizen_Kintsugi_ has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 255 seconds]
Kaizen_Kintsugi_ has quit [Ping timeout: 244 seconds]
brunoerg has joined #bitcoin-core-dev
Kaizen_Kintsugi_ has joined #bitcoin-core-dev
Kaizen_Kintsugi_ has quit [Read error: Connection reset by peer]
Zenton has joined #bitcoin-core-dev
Kaizen_Kintsugi_ has joined #bitcoin-core-dev
Kaizen_Kintsugi_ has quit [Ping timeout: 240 seconds]
Kaizen_Kintsugi_ has joined #bitcoin-core-dev
Kaizen_Kintsugi_ has quit [Ping timeout: 264 seconds]
Kaizen_Kintsugi_ has joined #bitcoin-core-dev
Kaizen_K_ has joined #bitcoin-core-dev
Kaizen_Kintsugi_ has quit [Ping timeout: 244 seconds]
Kaizen_K_ has quit [Ping timeout: 276 seconds]
Kaizen_Kintsugi_ has joined #bitcoin-core-dev
Kaizen_Kintsugi_ has quit [Ping timeout: 244 seconds]
brunoerg has quit [Ping timeout: 276 seconds]
brunoerg has joined #bitcoin-core-dev
Kaizen_Kintsugi_ has joined #bitcoin-core-dev
Kaizen_Kintsugi_ has quit [Ping timeout: 240 seconds]
Kaizen_Kintsugi_ has joined #bitcoin-core-dev
Kaizen_Kintsugi_ has quit [Read error: Connection reset by peer]
Kaizen_Kintsugi_ has joined #bitcoin-core-dev
Kaizen_K_ has joined #bitcoin-core-dev
Kaizen_Kintsugi_ has quit [Ping timeout: 240 seconds]
Kaizen_K_ has quit [Ping timeout: 244 seconds]
Kaizen_Kintsugi_ has joined #bitcoin-core-dev
greypw254600 has quit [Remote host closed the connection]
greypw254600 has joined #bitcoin-core-dev
Kaizen_K_ has joined #bitcoin-core-dev
Kaizen_Kintsugi_ has quit [Ping timeout: 276 seconds]
greypw254600 has quit [Remote host closed the connection]
greypw254600 has joined #bitcoin-core-dev
Kaizen_K_ has quit [Ping timeout: 244 seconds]
greypw254600 has quit [Remote host closed the connection]
greypw254600 has joined #bitcoin-core-dev
bitdex has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 244 seconds]
Kaizen_Kintsugi_ has joined #bitcoin-core-dev
Kaizen_Kintsugi_ has quit [Ping timeout: 256 seconds]
Guest65 has joined #bitcoin-core-dev
Guest65 has quit [Client Quit]
brunoerg has joined #bitcoin-core-dev
Kaizen_Kintsugi_ has joined #bitcoin-core-dev
Kaizen_Kintsugi_ has quit [Ping timeout: 244 seconds]
Kaizen_Kintsugi_ has joined #bitcoin-core-dev
ishaanam[m] has joined #bitcoin-core-dev
Kaizen_Kintsugi_ has quit [Ping timeout: 244 seconds]
sudoforge has joined #bitcoin-core-dev
Kaizen_Kintsugi_ has joined #bitcoin-core-dev
cmirror has quit [Remote host closed the connection]
cmirror has joined #bitcoin-core-dev
Kaizen_K_ has joined #bitcoin-core-dev
Kaizen_Kintsugi_ has quit [Ping timeout: 276 seconds]
Kaizen_K_ has quit [Ping timeout: 244 seconds]
Kaizen_Kintsugi_ has joined #bitcoin-core-dev
test_ has joined #bitcoin-core-dev
Guest0 has joined #bitcoin-core-dev
Guest0 has quit [Client Quit]
_flood has quit [Read error: Connection reset by peer]
javi404 has quit [Remote host closed the connection]
javi404 has joined #bitcoin-core-dev
Kaizen_Kintsugi_ has quit [Ping timeout: 240 seconds]
brunoerg has quit [Ping timeout: 276 seconds]
Kaizen_Kintsugi_ has joined #bitcoin-core-dev
Kaizen_Kintsugi_ has quit [Ping timeout: 272 seconds]
brunoerg has joined #bitcoin-core-dev
Kaizen_Kintsugi_ has joined #bitcoin-core-dev
Kaizen_Kintsugi_ has quit [Ping timeout: 244 seconds]
test_ has quit [Read error: Connection reset by peer]
Kaizen_Kintsugi_ has joined #bitcoin-core-dev
flooded has joined #bitcoin-core-dev
Kaizen_Kintsugi_ has quit [Ping timeout: 256 seconds]
jarthur_ has quit [Quit: jarthur_]
sudoforge has quit [Ping timeout: 244 seconds]
Kaizen_Kintsugi_ has joined #bitcoin-core-dev
Kaizen_Kintsugi_ has quit [Ping timeout: 240 seconds]
<bitcoin-git>
[bitcoin] MarcoFalke closed pull request #24183: test: use MiniWallet for mempool_updatefromblock.py (master...mempool-updatefromblock-miniwallet) https://github.com/bitcoin/bitcoin/pull/24183
<willcl_ark>
hebasto and ryanofsky did one of you have a gist/issue describing the threads of Bitcoin Core in some detail (sorry if I'm misremembering)?
<bitcoin-git>
bitcoin/master 42aa5d5 dergoegge: [net] Add NoBan status to NodeEvictionCandidate
<bitcoin-git>
bitcoin/master a3c2707 dergoegge: [net] Add connection type to NodeEvictionCandidate
<bitcoin-git>
bitcoin/master c741d74 Cory Fields: [net] Move ConnectionType to its own file
<bitcoin-git>
[bitcoin] fanquake merged pull request #25500: refactor: Move inbound eviction logic to its own translation unit (master...2022-06-evictionman-1ofN) https://github.com/bitcoin/bitcoin/pull/25500
<laanwj>
one proposed meeting topic this week: two short announcements (sipa)
___nick___ has joined #bitcoin-core-dev
<glozow>
hi
<jeremyrubin>
hi
<b10c>
hi
<instagibbs>
hi
<laanwj>
any last minute topics?
<Murch>
hi
<kanzure>
hi
craigderington17 has quit [Client Quit]
<jamesob>
hi
<dongcarl>
hi
<willcl_ark>
Hi
<laanwj>
hi
<laanwj>
okay, let's start with the announcements
<laanwj>
#topic Two short announcements
<core-meetingbot>
topic: Two short announcements
<sipa>
ok
<sipa>
the first is that i've come to realize it's time for me to step down as maintainer
vasild has quit [Ping timeout: 268 seconds]
Kaizen_Kintsugi_ has joined #bitcoin-core-dev
<sipa>
i'm not intending to change anything about what i do or work on, but the reality is that i haven't used my maintainer privileged for almost two years, but also more in general my interests have shifted and i'm not as closely involved with the codebase anymore
<laanwj>
sad to see you go
vasild has joined #bitcoin-core-dev
<laanwj>
but if you're hardly using commit access it definitely makes sense to drop it
<kanzure>
will you still be a contributor even if periodic or incidentally?
<gleb745438685291>
hi
gleb745438685291 is now known as gleb1
<sipa>
and with the discussions the past week i realized there is no need to keep my privileges if i don't use them
<dunxen>
Thanks, Pieter! glad to know you’ll continue working on what you do now!
<laanwj>
yes!
<sipa>
kanzure: Yes, definitely - nothing changes there. Though lately the projects I work on are more research-oriented, like miniscript, bip324, and various other things. I plan to keep writing code and reviewing.
<jeremyrubin>
Thanks for all the hard work over the years sipa!
<jeremyrubin>
Do you intend to stay a maintainer of libsecp256k1?
<brunoerg>
thanks, pieter!
<sipa>
jeremyrubin: yes!
<josibake___>
hi
<willcl_ark>
Thanks for your noteworthy and numerous contributions Pieter!
<jeremyrubin>
sipa: fantastic :)
<sipa>
In fact that's the second short announcement: libsecp256k1 now has IRC meetings too, every two weeks, 15:00 UTC on mondays; the next one is the 18th.
<jarolrod>
sipa: on this channel or another channel?
Kaizen_K_ has joined #bitcoin-core-dev
Kaizen_Kintsugi_ has quit [Ping timeout: 256 seconds]
<luke-jr>
this one is quiet enough I'd almost suggest combining it in ;)
<sipa>
I've had this lingering guilt about not being to spend as much time with the codebase and doing review... and I still plan to at some point get back to doing more of that, but I also have lots of other things going on.
<sipa>
jarolrod: on the #secp256k1 channel
<jarolrod>
sipa: don't think you have anything to apologize for :D
<josibake___>
sipa: thanks for your work as a maintainer and glad to hear you will still be coding/reviewing :)
___nick___ has quit [Ping timeout: 256 seconds]
<cfields_>
late hi
<jeremyrubin>
luke-jr: personally I think separate channels are really great as they make logs much more easily searched
<luke-jr>
jeremyrubin: "almost" ;)
<sipa>
That's it for me, unless people have more questions.
<cfields_>
sipa: thanks for your time as maintainer, glad to hear that your contributions won't be changing much :)
<jeremyrubin>
oh one other q
<jeremyrubin>
do you intend to retain status as PoC for security issues?
<ariard>
i think PoC for security issues can be dissociated from maintenance, at least we do that for LDK
<instagibbs>
point of contact(tried for 5 seconeds to figure out what that was)
<jarolrod>
^^^ i guess on that note, there's also the question on elevated privileges, such as being able to ban spammers
Kaizen_K_ has quit [Ping timeout: 276 seconds]
<jeremyrubin>
jarolrod: i think a lot of people have those github bits as a convenience, already separate from maintainership
<gleb1>
from some brief interactions with those security communication channels, i remember sipa did good job at handling them
<achow101>
iirc the security email has multiple non-maintainers on it
<instagibbs>
banning is only done for egregious spamming afaik
<achow101>
jeremyrubin: banning requires admin perms, which only a few of the maintainers have
<sipa>
I'm in no rush to change anything, so if it's helpful to stay on as security PoC, or even keep privileges to ban people, I'm happy to do that.
<jeremyrubin>
achow101: i don't send to the security email precisely because I don't know who is on it, prefer to communicate to a particular developer about an issue with encryption if there is a problem
<jeremyrubin>
gleb1: +1 :)
<luke-jr>
jeremyrubin: encryption works in email too ;)
<jeremyrubin>
sipa: thanks for clairfying, just wanted to be sure such communications were still welcome
<sipa>
But I also think over time those functions should move to others.
<laanwj>
tbh the security email mostly only gets spam and support requests anyway
<jeremyrubin>
luke-jr: yes, but there's not a key for the security email so it's not clear who i should encrypt it to for that list
<kanzure>
jeremy do you have something you're holding
<jeremyrubin>
kanzure?
<luke-jr>
jeremyrubin: see real_or_random's link
<jeremyrubin>
yes im familiar with the link, sipa is listed there, that's all i'm asking about
<real_or_random>
you could encrypt to any subset of those three people
<sipa>
any non-empty subset
<achow101>
encrypting to any of the keys listed for the security email is fine, I expect it get forwarded/put in contact with the appropriate people
<real_or_random>
maybe this could be made clearer
<real_or_random>
sipa: well, if you don't want to report the vulnerability...
<sipa>
it's a bit strange to send a mail to the security list, not knowing who's on it, but then encrypt it to just specific people (for which it's not even explicit that they're on that list)
<jeremyrubin>
sipa: yes, exactly. but it's an aside, someone can clean that up out of band of the meeting
<sipa>
the security list does indeed mostly get spam ("the email on bitcoincore.org is not properly configured!")
<laanwj>
yes, or 'i lost my wallet' or other vague requests like 'i want my spam article to be featured on the site'
Talkless has quit [Quit: Konversation terminated!]
<real_or_random>
yeah, most of the strangest emails I have received in my life were sent to secp256k1-security@bitcoincore.org
Kaizen_Kintsugi_ has joined #bitcoin-core-dev
<real_or_random>
(for example, a link to a google doc containing nothing but the developer documentation of libjpeg)
<real_or_random>
sorry, I don't want to disrupt the meeting here ^^
<luke-jr>
real_or_random: perhaps malware intended to exploit a browser 0day ;)
<laanwj>
another announcement: welcome glozow as mempool/relay policy maintainer!
<sipa>
\o/
<josibake___>
glozow: congrats!
<gleb1>
great news
<cfields_>
🚀
<jarolrod>
glozow: 🎉
<laanwj>
congrats glozow
Kaizen_K_ has joined #bitcoin-core-dev
Kaizen_Kintsugi_ has quit [Ping timeout: 256 seconds]
<ariard>
thanks again sipa for the years of maintenance!
<laanwj>
yes! thanks sipa
<instagibbs>
hear hear
<sipa>
:)
Kaizen_Kintsugi_ has joined #bitcoin-core-dev
sipsorcery has joined #bitcoin-core-dev
Kaizen_Kintsugi_ has quit [Ping timeout: 256 seconds]
Kaizen_Kintsugi_ has joined #bitcoin-core-dev
<glozow>
thank you sipa for everything you do!
<glozow>
and thanks laanwj darosior josibake___ gleb1 jarolrod cfields_ and everyone :)
Kaizen_Kintsugi_ has quit [Ping timeout: 244 seconds]
Kaizen_Kintsugi_ has joined #bitcoin-core-dev
furszy has quit []
Kaizen_Kintsugi_ has quit [Ping timeout: 240 seconds]
<dongcarl>
Hi all, I'm wondering how we commit to the RPC output, like if I wanted to change a field name in getmempoolinfo, is there a deprecation period or something?
<laanwj>
dongcarl: depends really on a case by case basis, but i'd say at least one major release deprecation period
<MacroFake>
sipa: Thanks for what you have done so far and good to hear that you keep doing what you do :)
<MacroFake>
dongcarl: If the field was added in the master branch, then no period is needed
<dongcarl>
Okay I see!
Kaizen_Kintsugi_ has joined #bitcoin-core-dev
Kaizen_Kintsugi_ has quit [Read error: Connection reset by peer]
mudsip has quit []
nanotube has quit [Ping timeout: 246 seconds]
Kaizen_Kintsugi_ has joined #bitcoin-core-dev
gnaf has quit [Quit: Konversation terminated!]
Kaizen_Kintsugi_ has quit [Ping timeout: 240 seconds]
Kaizen_Kintsugi_ has joined #bitcoin-core-dev
Kaizen_K_ has joined #bitcoin-core-dev
Kaizen_Kintsugi_ has quit [Ping timeout: 244 seconds]