19:00:08 <laanwj> #startmeeting 
19:00:08 <core-meetingbot> Meeting started Thu May 27 19:00:08 2021 UTC.  The chair is laanwj. Information about MeetBot at https://bitcoin.jonasschnelli.ch/ircmeetings.
19:00:08 <core-meetingbot> Available commands: action commands idea info link nick
19:00:14 <jamesob> hi
19:00:19 <achow101> hi
19:00:22 <michaelfolkson> hi
19:00:25 <provoostenator> hi
19:00:27 <meshcollider> hi
19:00:28 <hebasto> hi
19:00:31 <ariard> hi
19:00:39 <fjahr> hi
19:01:02 <laanwj> last week was a bit hectic on IRC due to the server transition, but i don't think we have proposed meeting topics (if we do, please correct me)
19:01:25 <laanwj> #bitcoin -core-dev Meeting: achow101 aj amiti ariard bluematt cfields Chris_Stewart_5 digi_james dongcarl elichai2 emilengler fanquake fjahr gleb glozow gmaxwell gwillen hebasto instagibbs jamesob jb55 jeremyrubin jl2012 jnewbery jonasschnelli jonatack jtimon kallewoof kanzure kvaciral lightlike luke-jr maaku marcofalke meshcollider michagogo moneyball morcos nehan NicolasDorier paveljanik
19:01:27 <sipa> hi
19:01:27 <laanwj> petertodd phantomcircuit promag provoostenator ryanofsky sdaftuar sipa vasild wumpus
19:01:33 <jonatack> hi
19:01:42 <laanwj> also if you have any last minute meeting topic, of course
19:01:55 <jamesob> if we have nothing else, here's a quick update on assumeutxo: I'm towards the end of a (pretty involved) rebase and will be pushing that up soon. afterwards I'll run manual tests and start on writing some functional tests.
19:01:56 <achow101> proposed topic: which versions to re-release with new windows code signing cert?
19:02:01 <ariard> laanwj: you might need to update the meeting ping with few nicknames upgrade :)
19:02:09 <jarolrod> hi
19:02:31 <laanwj> ariard: if there's any you'd like to add let me know
19:02:47 <ariard> laanwj: yours is changed at least
19:02:49 <jonatack> _aj_: s/aj/_aj_/
19:03:25 <jonatack> s/bluematt/BlueMatt/
19:03:33 <laanwj> ariard: jonatack  good point
19:03:46 <darosior> hi
19:04:36 <laanwj> #topic High priority for review
19:04:36 <core-meetingbot> topic: High priority for review
19:04:53 <laanwj> https://github.com/bitcoin/bitcoin/projects/8 11 blockers, no bugfixes, nothing chasing Concept ACK
19:05:04 <achow101> couple things were merged
19:05:05 <laanwj> anything to add/remove, or that is almost ready for merge?
19:05:19 <sipa> can i have #22051 ?
19:05:21 <gribble> https://github.com/bitcoin/bitcoin/issues/22051 | Basic Taproot derivation support for descriptors by sipa · Pull Request #22051 · bitcoin/bitcoin · GitHub
19:05:36 <laanwj> i suppose #20833 is
19:05:40 <gribble> https://github.com/bitcoin/bitcoin/issues/20833 | rpc/validation: enable packages through testmempoolaccept by glozow · Pull Request #20833 · bitcoin/bitcoin · GitHub
19:05:45 <achow101> #22008 for me
19:05:48 <gribble> https://github.com/bitcoin/bitcoin/issues/22008 | An error has occurred and has been logged. Please contact this bot's administrator for more information.
19:05:51 <jamesob> can I have #21526?
19:05:53 <gribble> https://github.com/bitcoin/bitcoin/issues/21526 | validation: UpdateTip/CheckBlockIndex assumeutxo support by jamesob · Pull Request #21526 · bitcoin/bitcoin · GitHub
19:06:15 <sipa> #22008 again, bot?
19:06:17 <gribble> https://github.com/bitcoin/bitcoin/issues/22008 | An error has occurred and has been logged. Please contact this bot's administrator for more information.
19:06:19 <ariard> yes 20833 is pretty mature, would be glad to have few last eyes on it
19:06:42 <achow101> sipa: I guess the bot just hates me
19:07:35 <darosior> ariard: looking at it, currently getting up to date with all the precedent comments
19:08:06 <laanwj> achow101: sipa jamesob  added
19:08:12 <jamesob> thanks
19:08:24 <ariard> darosior: thanks
19:09:26 <laanwj> #topic Versions to re-release with new windows code signing cert (achow101)
19:09:26 <core-meetingbot> topic: Versions to re-release with new windows code signing cert (achow101)
19:09:49 <achow101> I finally got a new windows code signing cert
19:10:08 <laanwj> imo don't re-release anything, just use the cert for new versions
19:10:16 <achow101> the versions that were affected by the previous cert being revoked are 0.21.1, 0.21.0, 0.20.1, 0.20.0, and 0.19.2
19:10:31 <achow101> the question is which should we do a x.x.x.1 release for with the new cert
19:10:39 <achow101> 0.21.1.1 I think is obvious
19:10:40 <laanwj> people can always use the zip for installation on windows if they want
19:11:07 <laanwj> yes
19:11:25 <achow101> it would be nice of each major version had a version that didn't fail to install on windows
19:11:30 <laanwj> 0.21 needs a new release anyway, why not 0.21.2 though
19:11:34 <sipa> do we things queued up for 0.21.2?
19:11:39 <sipa> right, that
19:11:41 <laanwj> i saw MarcoFalke  already did bafckports
19:11:43 <achow101> provoostenator suggested making a 0.20.2 since there's stuff for it too
19:12:00 <jonasschnelli> hi
19:12:40 <laanwj> #22022 
19:12:42 <gribble> https://github.com/bitcoin/bitcoin/issues/22022 | Final backports for 0.21.2rc1 by MarcoFalke · Pull Request #22022 · bitcoin/bitcoin · GitHub
19:12:58 <laanwj> clearly the certificate change needs to be backported too
19:13:16 <laanwj> oh, thats in there
19:13:46 <achow101> are there enough things to be backported for 0.21.2? We did 0.21.1 only 4 weeks ago
19:14:22 <laanwj> i mean, we're going to do a release anyway right
19:14:38 <laanwj> normally i'd say no
19:14:57 <achow101> true
19:15:21 <sipa> right, given that there are repo changes for the new cert anyway, it'd necessitate doing the full build process over, and just the codesigning step?
19:15:41 <laanwj> yeah! if it was a matter of simply attaching the signature (no rebuild) it would be different
19:16:16 <achow101> I could just attach the signature.. it just wouldn't fit within gitian
19:16:19 <jonasschnelli> does the new codesigning LLC obtains apple code signing certificates already?
19:16:23 <achow101> jonasschnelli: no
19:16:59 <laanwj> achow101: so it would need a different script than the normal signature attachment
19:17:00 <jonasschnelli> They might want to see a D.U.N.S number (which could take a few days to get).
19:17:22 <achow101> jonasschnelli: we have a duns number
19:17:37 <achow101> laanwj: yes, and future gitian builds would get a different result
19:17:37 <jonasschnelli> good... then a matter of minutes (and 99$) to get one
19:17:56 <achow101> new release is the path of least resistance still I think
19:18:06 <laanwj> yes
19:18:16 <achow101> What about for the 0.19 branch then?
19:18:33 <achow101> there haven't been any other backports
19:20:22 <laanwj> no strong opinion on that, we could do a 0.19.2.1 if anyone really wants one, i'm not sure it's the effort just for a certificate update
19:20:42 <achow101> oh, we never finished releasing 0.20.2, the latest tag there is for 0.20.2rc1. I guess now's the time to do that.
19:20:43 <sipa> how many 0.19 are there on the network?
19:21:18 <laanwj> achow101: hah we didn't finish the 0.20 release ... no one complained
19:21:35 <laanwj> achow101: yes
19:21:44 <sipa> that's going to be a *big* 0.20.2rc2 i guess
19:22:01 <sipa> or just 0.20.3
19:22:04 <laanwj> sipa: but people already on the network with 0.19 don't need to upgrade just to get a different codesigning cert :)
19:22:30 <laanwj> after all, the certificate is for the installer only not the binary that is run
19:22:41 <jonasschnelli> sipa: cat dnsseed.dump | grep "  100.00% 100.00% 100.00%" | grep "/Satoshi:0.19" | wc -l      --> 38
19:22:44 <laanwj> that would have been *much* worse
19:23:02 <achow101> https://luke.dashjr.org/programs/bitcoin/files/charts/software.html says ~4500 0.19.x
19:23:22 <sipa> laanwj: of course; just to get an idea of popularity, however bogus the measurement is
19:23:50 <achow101> I'm fine with leaving 0.19 as it is. it's almost eol anyways
19:24:02 <laanwj> i think i stick with my original response, use the cert for new releases if they are needed anyuway
19:24:05 <emzy> sipa: $ cat dnsseed.dump | grep "  100.00% 100.00% 100.00%" | grep "/Satoshi:0.19" | wc -l  --> 56
19:24:12 <jonasschnelli> 518 "good" 0.19 nodes on my seeder
19:24:25 <laanwj> then do a 0.21.2 soon
19:24:46 <achow101> laanwj: sgtm
19:25:29 <achow101> #22017 is the pr
19:25:30 <gribble> https://github.com/bitcoin/bitcoin/issues/22017 | Update Windows code signing certificate by achow101 · Pull Request #22017 · bitcoin/bitcoin · GitHub
19:25:30 <laanwj> and 0.20.2 i guess which has been in rc for too long
19:26:48 <laanwj> #topic Assumeutxo update (jamesob)
19:26:48 <core-meetingbot> topic: Assumeutxo update (jamesob)
19:27:16 <jamesob> As stated early, just finishing up a big rebase and will push that today, to be followed shortly with manual/functional tests
19:27:20 <jamesob> *earlier
19:27:36 <jamesob> thanks for everyone's patience and help so far
19:27:37 <laanwj> jamesob: thanks for the update
19:28:39 <jamesob> anytime
19:28:51 <laanwj> any other topics for today?
19:28:54 <ariard> jamesob: quite awesome to hear progress on assumeutxo :)
19:29:09 <jamesob> thanks ariard! I'm excited
19:29:44 <laanwj> #endmeeting