12024-09-26T01:05:54 *** mudsip <mudsip!~mudsip@user/mudsip> has joined #bitcoin-core-dev
22024-09-26T01:08:29 *** mudsip <mudsip!~mudsip@user/mudsip> has quit IRC (Client Quit)
32024-09-26T01:30:57 *** __DuBPiRaTe__ <__DuBPiRaTe__!~E_bomb@2600:6c50:7f7f:d89a:2ecf:67ff:fe08:b362> has quit IRC (Quit: Leaving)
42024-09-26T01:34:09 *** dviola <dviola!~diego@user/dviola> has quit IRC (Ping timeout: 248 seconds)
52024-09-26T01:47:35 *** diego <diego!~diego@186.207.245.11> has joined #bitcoin-core-dev
62024-09-26T01:48:05 *** diego is now known as Guest7518
72024-09-26T02:36:25 *** pablomartin4btc <pablomartin4btc!~pablomart@91.196.223.101> has quit IRC (Ping timeout: 272 seconds)
82024-09-26T03:06:32 *** eval-exec <eval-exec!~Thunderbi@104.160.45.106.16clouds.com> has joined #bitcoin-core-dev
92024-09-26T03:29:56 *** _andrewtoth_ <_andrewtoth_!~andrewtot@gateway/tor-sasl/andrewtoth> has quit IRC (Ping timeout: 260 seconds)
102024-09-26T03:34:39 *** achow101 <achow101!~achow101@user/achow101> has quit IRC (Quit: Bye)
112024-09-26T03:35:00 *** achow101 <achow101!~achow101@user/achow101> has joined #bitcoin-core-dev
122024-09-26T03:35:12 *** achow101 <achow101!~achow101@user/achow101> has quit IRC (Client Quit)
132024-09-26T03:35:44 *** achow101 <achow101!~achow101@user/achow101> has joined #bitcoin-core-dev
142024-09-26T04:01:01 *** cmirror <cmirror!~cmirror@4.53.92.114> has quit IRC (Remote host closed the connection)
152024-09-26T04:01:33 *** cmirror <cmirror!~cmirror@4.53.92.114> has joined #bitcoin-core-dev
162024-09-26T04:28:32 *** kevkevin_ <kevkevin_!~kevkevin@209-242-39-30.rev.dls.net> has joined #bitcoin-core-dev
172024-09-26T04:31:14 *** kevkevin <kevkevin!~kevkevin@209-242-39-30.rev.dls.net> has quit IRC (Ping timeout: 260 seconds)
182024-09-26T04:46:20 *** szkl <szkl!uid110435@id-110435.uxbridge.irccloud.com> has quit IRC (Quit: Connection closed for inactivity)
192024-09-26T04:54:39 *** Guest18 <Guest18!~Guest18@2001:fb1:11b:b0e9:d2d5:760f:fe93:2d22> has joined #bitcoin-core-dev
202024-09-26T04:55:05 *** Guest18 <Guest18!~Guest18@2001:fb1:11b:b0e9:d2d5:760f:fe93:2d22> has quit IRC (Client Quit)
212024-09-26T05:01:32 *** mcey_ <mcey_!~emcy@148.252.145.21> has joined #bitcoin-core-dev
222024-09-26T05:01:33 *** mcey <mcey!~emcy@148.252.145.21> has quit IRC (Remote host closed the connection)
232024-09-26T05:08:31 *** BrandonOdiwuor <BrandonOdiwuor!~BrandonOd@105.163.2.94> has joined #bitcoin-core-dev
242024-09-26T05:12:32 *** zeropoint <zeropoint!~alex@45-28-139-114.lightspeed.sntcca.sbcglobal.net> has quit IRC (Quit: leaving)
252024-09-26T05:20:17 *** l0rinc <l0rinc!~l0rinc@94.44.108.19> has joined #bitcoin-core-dev
262024-09-26T05:27:41 *** l0rinc <l0rinc!~l0rinc@94.44.108.19> has quit IRC (Quit: Client closed)
272024-09-26T06:37:41 *** ion- <ion-!ion-@user/ion-> has quit IRC (Remote host closed the connection)
282024-09-26T06:37:56 *** ion- <ion-!ion-@user/ion-> has joined #bitcoin-core-dev
292024-09-26T06:39:17 *** oneeyedalien <oneeyedalien!~oneeyedal@user/oneeyedalien> has joined #bitcoin-core-dev
302024-09-26T06:40:34 *** ion- <ion-!ion-@user/ion-> has quit IRC (Remote host closed the connection)
312024-09-26T06:53:59 *** ion- <ion-!ion-@user/ion-> has joined #bitcoin-core-dev
322024-09-26T06:55:05 *** PatBoy <PatBoy!xyz@cryption.cn> has quit IRC (Quit: ZNC 1.8.2 - https://znc.in)
332024-09-26T06:55:10 *** P8tBoy <P8tBoy!xyz@cryption.cn> has joined #bitcoin-core-dev
342024-09-26T06:58:48 *** ion- <ion-!ion-@user/ion-> has quit IRC (Ping timeout: 276 seconds)
352024-09-26T06:58:51 *** ion-_ <ion-_!ion-@user/ion-> has joined #bitcoin-core-dev
362024-09-26T07:57:56 *** Guyver2 <Guyver2!~Guyver@77-174-98-73.fixed.kpn.net> has joined #bitcoin-core-dev
372024-09-26T08:02:08 *** oneeyedalien <oneeyedalien!~oneeyedal@user/oneeyedalien> has quit IRC (Quit: Leaving)
382024-09-26T08:23:30 *** ion-_ <ion-_!ion-@user/ion-> has quit IRC (Remote host closed the connection)
392024-09-26T08:32:28 *** ___nick___ <___nick___!~quassel@82-132-215-132.dab.02.net> has joined #bitcoin-core-dev
402024-09-26T08:40:02 *** ion- <ion-!ion-@user/ion-> has joined #bitcoin-core-dev
412024-09-26T08:45:11 <bitcoin-git> [bitcoin] fanquake opened pull request #30973: doc: fix `loadtxoutset` example (master...loadtxoutset_help) https://github.com/bitcoin/bitcoin/pull/30973
422024-09-26T08:55:16 *** Guest10 <Guest10!~Guest10@176.40.247.132> has joined #bitcoin-core-dev
432024-09-26T08:56:15 *** ion- <ion-!ion-@user/ion-> has quit IRC (Remote host closed the connection)
442024-09-26T08:56:30 *** ion- <ion-!ion-@user/ion-> has joined #bitcoin-core-dev
452024-09-26T08:59:06 <bitcoin-git> [bitcoin] fanquake pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/65f6e7078b17...513b7136c798
462024-09-26T08:59:07 <bitcoin-git> bitcoin/master c183258 fanquake: ci: add LLVM_SYMBOLIZER_PATH to Valgrind fuzz job
472024-09-26T08:59:07 <bitcoin-git> bitcoin/master 513b713 merge-script: Merge bitcoin/bitcoin#30961: ci: add `LLVM_SYMBOLIZER_PATH` to Valgrind fu...
482024-09-26T08:59:10 <bitcoin-git> [bitcoin] fanquake merged pull request #30961: ci: add `LLVM_SYMBOLIZER_PATH` to Valgrind fuzz job (master...valgrind_symbolizer) https://github.com/bitcoin/bitcoin/pull/30961
492024-09-26T09:01:45 *** ion- <ion-!ion-@user/ion-> has quit IRC (Remote host closed the connection)
502024-09-26T09:03:24 *** l0rinc <l0rinc!~l0rinc@94.44.108.19> has joined #bitcoin-core-dev
512024-09-26T09:04:13 *** l0rinc <l0rinc!~l0rinc@94.44.108.19> has quit IRC (Client Quit)
522024-09-26T09:05:07 *** l0rinc <l0rinc!~l0rinc@94.44.108.19> has joined #bitcoin-core-dev
532024-09-26T09:06:48 *** ___nick___ <___nick___!~quassel@82-132-215-132.dab.02.net> has quit IRC (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.)
542024-09-26T09:08:29 *** ion- <ion-!ion-@user/ion-> has joined #bitcoin-core-dev
552024-09-26T09:08:59 *** ___nick___ <___nick___!~quassel@82-132-215-132.dab.02.net> has joined #bitcoin-core-dev
562024-09-26T09:11:11 *** ___nick___ <___nick___!~quassel@82-132-215-132.dab.02.net> has quit IRC (Client Quit)
572024-09-26T09:13:21 *** ___nick___ <___nick___!~quassel@82-132-215-132.dab.02.net> has joined #bitcoin-core-dev
582024-09-26T09:17:09 *** szkl <szkl!uid110435@id-110435.uxbridge.irccloud.com> has joined #bitcoin-core-dev
592024-09-26T09:59:59 *** Guest10 <Guest10!~Guest10@176.40.247.132> has quit IRC (Ping timeout: 256 seconds)
602024-09-26T10:05:40 *** l0rinc <l0rinc!~l0rinc@94.44.108.19> has quit IRC (Quit: Client closed)
612024-09-26T10:05:46 *** cold <cold!~cold@user/cold> has quit IRC (Ping timeout: 252 seconds)
622024-09-26T10:06:09 *** midnight <midnight!~midnight@user/midnight> has quit IRC (Ping timeout: 248 seconds)
632024-09-26T10:06:19 *** midnight_ <midnight_!~midnight@user/midnight> has joined #bitcoin-core-dev
642024-09-26T10:06:48 *** cold <cold!~cold@user/cold> has joined #bitcoin-core-dev
652024-09-26T10:09:22 <bitcoin-git> [bitcoin] maflcko opened pull request #30974: ci: Require git to be installed on workers (master...2409-ci-git) https://github.com/bitcoin/bitcoin/pull/30974
662024-09-26T10:22:51 *** ion- <ion-!ion-@user/ion-> has quit IRC (Remote host closed the connection)
672024-09-26T10:26:58 <bitcoin-git> [bitcoin] fanquake pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/513b7136c798...e13da501db9e
682024-09-26T10:26:59 <bitcoin-git> bitcoin/master 2867251 fanquake: doc: fix loadtxoutset example
692024-09-26T10:26:59 <bitcoin-git> bitcoin/master e13da50 merge-script: Merge bitcoin/bitcoin#30973: doc: fix `loadtxoutset` example
702024-09-26T10:27:01 <bitcoin-git> [bitcoin] fanquake merged pull request #30973: doc: fix `loadtxoutset` example (master...loadtxoutset_help) https://github.com/bitcoin/bitcoin/pull/30973
712024-09-26T10:29:43 <bitcoin-git> [bitcoin] Sjors opened pull request #30975: guix: add multiprocess binaries (master...2024/09/multiprocess-guix) https://github.com/bitcoin/bitcoin/pull/30975
722024-09-26T10:38:30 *** ion- <ion-!ion-@user/ion-> has joined #bitcoin-core-dev
732024-09-26T10:48:39 *** __DuBPiRaTe__ <__DuBPiRaTe__!~E_bomb@2600:6c50:7f7f:d89a:2ecf:67ff:fe08:b362> has joined #bitcoin-core-dev
742024-09-26T11:00:05 <bitcoin-git> [bitcoin] hebasto opened pull request #30976: depends, doc: Drop package-specific note about CMake (master...240926-mp-deps) https://github.com/bitcoin/bitcoin/pull/30976
752024-09-26T11:01:55 *** ion- <ion-!ion-@user/ion-> has quit IRC (Remote host closed the connection)
762024-09-26T11:02:11 *** ion- <ion-!ion-@user/ion-> has joined #bitcoin-core-dev
772024-09-26T11:21:02 *** midnight_ is now known as midnight
782024-09-26T11:23:20 <bitcoin-git> [bitcoin] fanquake pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/e13da501db9e...d5af7d28f475
792024-09-26T11:23:21 <bitcoin-git> bitcoin/master 4cf84b3 Hennadii Stepanov: depends, doc: No need to specify general requirement
802024-09-26T11:23:21 <bitcoin-git> bitcoin/master d5af7d2 merge-script: Merge bitcoin/bitcoin#30976: depends, doc: Drop package-specific note abou...
812024-09-26T11:23:23 <bitcoin-git> [bitcoin] fanquake merged pull request #30976: depends, doc: Drop package-specific note about CMake (master...240926-mp-deps) https://github.com/bitcoin/bitcoin/pull/30976
822024-09-26T11:24:07 *** Guest7518 <Guest7518!~diego@186.207.245.11> has quit IRC (Quit: WeeChat 4.4.2)
832024-09-26T11:24:43 *** dviola <dviola!~diego@user/dviola> has joined #bitcoin-core-dev
842024-09-26T11:38:44 *** abubakarsadiq <abubakarsadiq!uid602234@id-602234.hampstead.irccloud.com> has joined #bitcoin-core-dev
852024-09-26T11:43:54 *** ion- <ion-!ion-@user/ion-> has quit IRC (Remote host closed the connection)
862024-09-26T11:50:24 *** ion- <ion-!ion-@user/ion-> has joined #bitcoin-core-dev
872024-09-26T11:51:34 *** ion-_ <ion-_!ion-@user/ion-> has joined #bitcoin-core-dev
882024-09-26T11:52:49 *** ion-_ <ion-_!ion-@user/ion-> has quit IRC (Remote host closed the connection)
892024-09-26T11:53:32 *** aleggg <aleggg!~aleggg@187.113.241.88> has quit IRC (Ping timeout: 264 seconds)
902024-09-26T11:54:34 *** ion- <ion-!ion-@user/ion-> has quit IRC (Ping timeout: 245 seconds)
912024-09-26T12:09:29 *** ion- <ion-!ion-@user/ion-> has joined #bitcoin-core-dev
922024-09-26T12:12:31 *** ion- <ion-!ion-@user/ion-> has quit IRC (Remote host closed the connection)
932024-09-26T12:12:47 *** ion- <ion-!ion-@user/ion-> has joined #bitcoin-core-dev
942024-09-26T12:21:44 *** ion- <ion-!ion-@user/ion-> has quit IRC (Remote host closed the connection)
952024-09-26T12:22:24 *** pablomartin4btc <pablomartin4btc!~pablomart@91.196.223.101> has joined #bitcoin-core-dev
962024-09-26T12:38:28 *** ion- <ion-!ion-@user/ion-> has joined #bitcoin-core-dev
972024-09-26T12:42:53 *** ion- <ion-!ion-@user/ion-> has quit IRC (Ping timeout: 255 seconds)
982024-09-26T12:44:05 *** Guyver2 <Guyver2!~Guyver@77-174-98-73.fixed.kpn.net> has left #bitcoin-core-dev (Closing Window)
992024-09-26T12:56:07 *** ion- <ion-!ion-@user/ion-> has joined #bitcoin-core-dev
1002024-09-26T13:13:54 *** _andrewtoth_ <_andrewtoth_!~andrewtot@gateway/tor-sasl/andrewtoth> has joined #bitcoin-core-dev
1012024-09-26T13:25:58 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 252 seconds)
1022024-09-26T13:33:37 *** Chris_Stewart_5 <Chris_Stewart_5!~Chris_Ste@static-68-235-44-41.cust.tzulo.com> has joined #bitcoin-core-dev
1032024-09-26T13:37:49 *** eval-exec <eval-exec!~Thunderbi@104.160.45.106.16clouds.com> has quit IRC (Ping timeout: 260 seconds)
1042024-09-26T13:58:01 <bitcoin-git> [bitcoin] fjahr opened pull request #30979: contrib: Update asmap link in seeds readme (master...2024-09-asmap-seed-link) https://github.com/bitcoin/bitcoin/pull/30979
1052024-09-26T14:00:33 <achow101> #startmeeting
1062024-09-26T14:00:33 *** Emc99 <Emc99!~Emc99@212.129.84.59> has joined #bitcoin-core-dev
1072024-09-26T14:00:36 <tdb3> hi
1082024-09-26T14:00:38 <achow101> #bitcoin-core-dev Meeting: achow101 _aj_ amiti ariard aureleoules b10c BlueMatt brunoerg cfields darosior dergoegge dongcarl fanquake fjahr furszy gleb glozow hebasto instagibbs jamesob jarolrod jonatack josibake kallewoof kanzure kouloumos kvaciral laanwj LarryRuane lightlike luke-jr MacroFake Murch phantomcircuit pinheadmz promag provoostenator ryanofsky sdaftuar S3RK stickies-v sipa sr_gi theStack TheCharlatan vasild
1092024-09-26T14:00:46 <pinheadmz> hi
1102024-09-26T14:00:47 <willcl-ark> hi
1112024-09-26T14:00:47 <vasild> hi
1122024-09-26T14:00:48 <kanzure> hi
1132024-09-26T14:00:52 <achow101> There are no pre-proposed meeting topics this week. Any last minute ones to add?
1142024-09-26T14:00:56 <bitcoin-git> [bitcoin] marcofleon opened pull request #30980: fuzz: fix bug in p2p_headers_presync harness (master...2024/09/headers-presync-fuzz-bugfix) https://github.com/bitcoin/bitcoin/pull/30980
1152024-09-26T14:01:02 <dergoegge> hi
1162024-09-26T14:01:05 <fjahr> hi
1172024-09-26T14:01:40 <hebasto> hi
1182024-09-26T14:01:52 <achow101> #topic Ad-hoc high priority for review
1192024-09-26T14:01:53 <achow101> Anything to add or remove from https://github.com/orgs/bitcoin/projects/1/views/4
1202024-09-26T14:03:10 *** kvaciral[m] <kvaciral[m]!~kvaciralx@2620:6e:a000:ce11::27> has joined #bitcoin-core-dev
1212024-09-26T14:03:18 <achow101> #topic 28.0
1222024-09-26T14:03:30 <achow101> Any new issues in 28.0rc2?
1232024-09-26T14:04:31 <achow101> Current backports PR is #30959. Since the 2 fixes being backported are trivial, I'm plannin on skipping rc3 and tagging final once that is merged
1242024-09-26T14:04:32 <gribble> https://github.com/bitcoin/bitcoin/issues/30959 | [28.x] backports and finalize (or rc3) by achow101 · Pull Request #30959 · bitcoin/bitcoin · GitHub
1252024-09-26T14:04:56 <willcl-ark> That sounds reasonable :)
1262024-09-26T14:05:19 <achow101> Please also review the draft release notes https://github.com/bitcoin-core/bitcoin-devwiki/wiki/28.0-Release-Notes-Draft
1272024-09-26T14:06:02 <sipa> hi
1282024-09-26T14:06:11 <achow101> anything else to discuss?
1292024-09-26T14:06:15 <fjahr> Just a quick PSA: I have moved all my ASMap related repos to a dedicated org (https://github.com/asmap) to make collaboration easier. Old links should still work via redirect but if you see an outdated link please update because GH says they don't maintain those redirects forever.
1302024-09-26T14:06:20 <willcl-ark> (reading first bit of that): perhaps we should discuss macos notarization? i.e. #15774
1312024-09-26T14:06:21 <gribble> https://github.com/bitcoin/bitcoin/issues/15774 | macOS App Notarization & Stapling · Issue #15774 · bitcoin/bitcoin · GitHub
1322024-09-26T14:06:46 <willcl-ark> is the plan to give in to Apple's requirements and fully Notarize and staple?
1332024-09-26T14:07:14 <pinheadmz> piggy back #29749 on that >
1342024-09-26T14:07:14 <gribble> https://github.com/bitcoin/bitcoin/issues/29749 | release: ship codesigned MacOS arm64 binaries · Issue #29749 · bitcoin/bitcoin · GitHub
1352024-09-26T14:07:27 *** b10c[m] <b10c[m]!~b10cb10cm@2620:6e:a000:ce11::1c> has joined #bitcoin-core-dev
1362024-09-26T14:07:36 <achow101> fjahr: good to know. IIRC github does keep redirects for a long time, at least I've had a redirect that's been working for 5 years now
1372024-09-26T14:07:46 <achow101> #topic MacOS notarization
1382024-09-26T14:08:04 <achow101> willcl-ark: I don't think there's really been a plan yet?
1392024-09-26T14:08:13 <achow101> but it does seem like we should probably figure it out for the next release
1402024-09-26T14:08:36 <fjahr> achow101: yeah, that's just what I read, I guess they want to have the option to remove them at some point
1412024-09-26T14:08:47 <sipa> if macos is phoning home regardless of stapling/notarization, there seems to be little downside to doing it
1422024-09-26T14:08:48 <willcl-ark> Exactly THe current requirement is that a user must generate a codesigning cert, then codesign, and remove the quarantine bit. We can't really get around it AFAIK
1432024-09-26T14:10:10 <Chris_Stewart_5> Seems like a note about this in the release notes would be a good first step? I've run into this multiple times at this point and its a PITA finding the exact commands that need to be run to make bitcoind work on mac
1442024-09-26T14:11:08 <Chris_Stewart_5> a quick glance of the 28.0 release notes doesn't contain anything AFAICT. Seems like putting this in the 'How to upgrade' section would make sense? :man_shrugging:
1452024-09-26T14:11:08 <gmaxwell> If OSX phones home the software users run it might be worth a persistant note on that too in the docs for running on OSX.
1462024-09-26T14:11:22 <achow101> I've moved #15774 to the 29.0 milestone
1472024-09-26T14:11:24 <gribble> https://github.com/bitcoin/bitcoin/issues/15774 | macOS App Notarization & Stapling · Issue #15774 · bitcoin/bitcoin · GitHub
1482024-09-26T14:11:34 <sipa> gmaxwell: right
1492024-09-26T14:11:45 <achow101> Chris_Stewart_5: if you know what the commands are, feel free to add it yourself
1502024-09-26T14:11:57 <Chris_Stewart_5> Can do assuming everyone is on board
1512024-09-26T14:12:34 <sipa> Chris_Stewart_5: does the software actually not work if you don't?
1522024-09-26T14:12:38 <fanquake> My understanding is that our binaries just wont work at all on the latest macos release, and there's no-longer workarounds available
1532024-09-26T14:12:43 <willcl-ark> It does not work at all
1542024-09-26T14:12:44 <sipa> oh wow
1552024-09-26T14:12:46 <Chris_Stewart_5> sipa: it doesn't start and gives a cryptic error
1562024-09-26T14:13:01 <sipa> i assumed it was just a "warning unverified software" popup or so
1572024-09-26T14:13:03 <fanquake> so we are basically shipping no-ops for the latest version of macos
1582024-09-26T14:13:07 <Chris_Stewart_5> I don't have it handy atm.... i'll dig up the commands again. I haven't done it since the 27.1 release iirc.
1592024-09-26T14:13:23 <hebasto> is ad-hoc self signing no longer works as a workaround?
1602024-09-26T14:13:24 <Chris_Stewart_5> sipa: This also applies to bitcoind, bitcoin-cli
1612024-09-26T14:13:36 <willcl-ark> I had a think about adding an "auto-sign" script for macos: https://github.com/bitcoin/bitcoin/compare/master...willcl-ark:bitcoin:codesign-script but you still need a self-signed signing certificate
1622024-09-26T14:13:39 <achow101> sipa: it started that way
1632024-09-26T14:13:43 <vasild> well, if macos is phoning home and bitcoind does not work on macos, then even better. Why do we need to do anything?
1642024-09-26T14:13:44 <Chris_Stewart_5> hebasto: it does, but where are the commands? How are people suppose to find them?
1652024-09-26T14:13:45 <emzy> AFAIK it is this: xattr -rd com.apple.quarantine /path/to/applicationname.app
1662024-09-26T14:13:56 <willcl-ark> fanquake: no, I'm pretty sure the self signing and removing quarantine bit still works?
1672024-09-26T14:14:11 <Chris_Stewart_5> to be clear, this is probably a stop gap, things should probably just work :tm: ? But giving people instructions as a workaround for now seems appropriate?
1682024-09-26T14:14:19 <sipa> Chris_Stewart_5: agreed
1692024-09-26T14:14:23 <achow101> Chris_Stewart_5: yes
1702024-09-26T14:14:34 <fanquake> willcl-ark: not sure, but anyone using bitcoin-qt, which is primarily what we ship on macos, isn't doing any of that
1712024-09-26T14:14:43 <willcl-ark> fanquake: agree
1722024-09-26T14:14:48 <sipa> vasild: the world would be a lot better place if all humans were reasonable, but if that were the case, we probably wouldn't need bitcoin at all?
1732024-09-26T14:15:17 <willcl-ark> (but I have for sure run bitcoind 28rc2 after self-signing)
1742024-09-26T14:15:19 <vasild> sipa: yeah, I was half-joking ;-)
1752024-09-26T14:16:15 <sipa> to self-sign, you need a self-signing certificate? can you do that without apple's involvement?
1762024-09-26T14:16:16 <achow101> Any other topics to discuss?
1772024-09-26T14:16:22 <sipa> are there workarounds besides that?
1782024-09-26T14:16:38 <achow101> sipa: there's "ad-hoc signing" which doesn't actually require a certificate
1792024-09-26T14:16:38 <willcl-ark> sipa: not that I'm aware of. {Perhaps disable the entire SIP mechanism?
1802024-09-26T14:16:40 <Chris_Stewart_5> sipa: No need to involve apple, you self sign and the cert gets stored locally iirc
1812024-09-26T14:16:48 <glozow> re topics, I was wondering about cluster mempool / TxGraph status? If sipa has an update on that?
1822024-09-26T14:17:07 <sipa> glozow: happy to give an update
1832024-09-26T14:17:27 <achow101> #topic cluster mempool update
1842024-09-26T14:17:32 <glozow> :D
1852024-09-26T14:18:01 <sipa> so, we're currently imagining something like 3 layers for the cluster mempool code
1862024-09-26T14:18:26 <Chris_Stewart_5> One last comment on the notarization problem on mac, here is a bitcoin stack exchange question detailing the problem and solution: https://bitcoin.stackexchange.com/a/117101
1872024-09-26T14:18:40 <gmaxwell> vasild: considering how easy it is to enumerate people running bitcoin from the p2p network the fact that it phones home isn't hard incompatible with bitcoin I think. But perhaps it would be a very unwelcome surprise to people using bitcoin behind tor.
1882024-09-26T14:19:21 <sipa> * the bottom layer (depgraph) is pretty much done, apart from 30857 (which i don't plan to change anymore barring significant review comments). It deals with individual transaction clusters in a very abstract way, but contains all the computationally-hard stuff.
1892024-09-26T14:20:51 <vasild> gmaxwell: yeah, and it depends on what it phones home - maybe it would automatically backup important files to the cloud (like wallet.dat). A friend of mine complained that some anti virus moved his wallet.dat (!) I wouldn't be surprised if it sent it to the anti virus company for an analysis, if it treated it as a virus.
1902024-09-26T14:20:54 <sipa> * the middle layer (txgraph) is sort of a barebones mempool, knowing just about all transaction fees/sizes and dependencies between them (but has no concept of txids, outputs, inputs, prioritization, ...), clusters of them, and linearizations for them...; i have been working on fleshing the design for this out, but i don't have anything to show yet, sorry
1912024-09-26T14:21:58 <sipa> txgraph would also have a notion of "changesets", proposed sets of transaction additions/removals/dependencies to add to the mempool, so a rbfs can be staged (create a changeset for a proposed RBF, inspect the feerate diagram changes it would make, and then decide to throw it away or commit it)
1922024-09-26T14:22:27 <sipa> * the top layer is the mempool/validation code, which would use txgraph but add actual transactions, policy rules, validation
1932024-09-26T14:22:47 <sipa> the point of txgraph is that being more abstract it can be tested in isolation much more easily
1942024-09-26T14:23:48 <sipa> suhas' current PR (28676) contains a prototype for txgraph, but i'm working on rewriting it as a separate PR, after which 28676 would be rebased on that
1952024-09-26T14:24:17 <glozow> This sounds really cool!
1962024-09-26T14:25:32 <glozow> Thanks for the update sipa
1972024-09-26T14:25:49 <tdb3> thanks sipa!
1982024-09-26T14:26:34 <achow101> anything else to discuss?
1992024-09-26T14:26:49 <Chris_Stewart_5> sipa: Perhaps cart before the horse, but what do we think the deployment story looks like?
2002024-09-26T14:27:21 <Chris_Stewart_5> last I heard, the idea would be the totally replace existing mempool code with the new cluster mempool code, is that still the plan (presumably in 29.0)?
2012024-09-26T14:27:55 <sipa> Chris_Stewart_5: i think everything up to txgraph (which may well end up becoming multiple PRs) can be staged in, as in merged without actually changing any observable behavior, as it's just new data structures and algorithms that can be tested in isolation
2022024-09-26T14:28:49 <sipa> but the introduction of cluster-based mempool will be a hard switch; i don't think we realistically want both the old and new code ever simultaneously in production (it'd involve the worst of both worlds: the memory and CPU costs related to having both, plus the policy rules that are necessitated by both).
2032024-09-26T14:29:21 <sipa> i could imagine the introduction of cluster mempool, and the removal of the old mempool data structures to be in separate PRs only if the intent is for both to go in in the same release.
2042024-09-26T14:29:54 <Chris_Stewart_5> I guess I was thinking more along the lines of a -clustermempool flag in 29.0 and then assuming everything goes good, default to -clustermempool in 30.0 and remove old code in 31.0? Perhaps this a bit too conservative though?
2052024-09-26T14:30:06 <sipa> there is no way we can do that
2062024-09-26T14:30:11 <bitcoin-git> [bitcoin] willcl-ark opened pull request #30981: ci: add timestamps to cirrus jobs (master...cirrus-timestamps) https://github.com/bitcoin/bitcoin/pull/30981
2072024-09-26T14:30:47 <Chris_Stewart_5> Is this written about anywhere why its not possible? Or just have to read through code?
2082024-09-26T14:30:53 <sipa> i just told you :)
2092024-09-26T14:31:07 <sipa> it would involve the worst of both worlds
2102024-09-26T14:31:35 <Chris_Stewart_5> Yeah, and I guess I assumed only 1 of the mempool implementations would be running (-clustermempool or legacy mempool). Not both.
2112024-09-26T14:31:56 <sipa> they're just data structures that need to be maintained - if they're compiled in, they will be used
2122024-09-26T14:31:59 *** Emc99 <Emc99!~Emc99@212.129.84.59> has quit IRC (Ping timeout: 256 seconds)
2132024-09-26T14:32:09 <sipa> at the very least you'd get the memory usage from both
2142024-09-26T14:32:30 <sipa> it's not like we're creating a completely new mempool and can decide at runtime which of the two you're using
2152024-09-26T14:32:59 <_aj_> if you're nervous about the new mempool code in 29.x you'd just keep running 28.x anyway?
2162024-09-26T14:33:21 <Chris_Stewart_5> Runtime performance and code maintenance are different topics. I agree there will be maintenance burden for awhile. Idk if i'm so convinced on runtime performance, but you have more experience than i do on the topic so i'll defer to you
2172024-09-26T14:33:24 <sipa> we do have simulations based on replays of all mempool data to get an idea of what would be impacted by the policy changes that cluster mempool entails
2182024-09-26T14:33:58 <Chris_Stewart_5> _aj_: Yeah, and then we give people another reason not to upgrade with the latest and greatest stuff and get them stuck on 28.x.
2192024-09-26T14:34:17 *** Wronsk <Wronsk!~Wronsk@cust-west-par-46-193-0-235.cust.wifirst.net> has joined #bitcoin-core-dev
2202024-09-26T14:34:26 <_aj_> Chris_Stewart_5: if they don't upgrade from 28.x until 30.x is out, that's already fine and supported
2212024-09-26T14:34:38 <Chris_Stewart_5> Any way, perhaps i'm concern trolling at this point so i'll keep quiet. I am excited about clustermempool and think its great!
2222024-09-26T14:35:30 <sipa> Chris_Stewart_5: i think the biggest issue is the policy rules... the current mempool has certain policy rules that are necessitated by its implementation (primarily the ancestor and descendant set limits); cluster mempool has different policy rules (cluster size limit, which isn't exactly the same as ancestor or descendant limits, but supports higher numbers)
2232024-09-26T14:35:42 <sipa> if we keep the old mempool data structures, we need to keep the old policy rules
2242024-09-26T14:35:55 <sipa> if we introduce the new mempool data structures, we need to introduce the new policy rules
2252024-09-26T14:36:28 <sipa> so having a release that supports both would effectively entail having the combination of both policy rules (neither ancestor/descendant limits can be violated, nor cluster size limits).
2262024-09-26T14:36:56 <glozow> I imagine it would be even more invasive to add code everywhere (validation, policy, mining, etc) to have 2 mempools. And they'd have different transactions in them... sounds like a nightmare
2272024-09-26T14:37:30 <glozow> (And I can't think of another way to support both)
2282024-09-26T14:37:46 <Chris_Stewart_5> I'll think about this more. We can move on
2292024-09-26T14:37:46 <sipa> Chris_Stewart_5: yeah i understand the concern; it will be a nontrivial and abrubt change - but i don't think the alternative is very realistic
2302024-09-26T14:37:55 <vasild> "I guess I assumed only 1 of the mempool implementations would be running"
2312024-09-26T14:38:25 <sipa> a compile-time switch between them may be vaguely possible
2322024-09-26T14:38:34 <sipa> but even that is pretty hard
2332024-09-26T14:39:36 <achow101> anything else to discuss?
2342024-09-26T14:39:54 <tdb3> Sounds like the probability of bugs would be higher in a conjoined/transition implementation than with a clean update. And an end goal is minimizing bugs
2352024-09-26T14:40:11 *** bugs_ <bugs_!~bugs@user/bugs/x-5128603> has joined #bitcoin-core-dev
2362024-09-26T14:41:56 *** b10c_ <b10c_!~quassel@static.33.106.217.95.clients.your-server.de> has quit IRC (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.)
2372024-09-26T14:42:01 <achow101> #endmeeting
2382024-09-26T14:42:09 *** b10c <b10c!~quassel@static.33.106.217.95.clients.your-server.de> has joined #bitcoin-core-dev
2392024-09-26T14:42:50 <sipa> Chris_Stewart_5: re apple... if you self-sign, do you still have the phoning home?
2402024-09-26T14:43:02 <b10c> would love to have a few more eyes on #25832. I've been using the connection tracepoints for >2 years now. They've helped learning out about LinkingLion and us dropping connections due to high CPU usage elsewhere
2412024-09-26T14:43:05 <gribble> https://github.com/bitcoin/bitcoin/issues/25832 | tracing: network connection tracepoints by 0xB10C · Pull Request #25832 · bitcoin/bitcoin · GitHub
2422024-09-26T14:43:21 <b10c> I'm frequently rebasing these commits on master and e.g. RCs that I monitor - hope to run plain master at some point
2432024-09-26T14:45:30 *** twistedline <twistedline!~bitcoin@185.193.125.44> has quit IRC (Ping timeout: 276 seconds)
2442024-09-26T14:47:04 <Chris_Stewart_5> sipa: i'm not sure what you mean by phoning home, and I'll need to investigate regardless. Do you mean contacting apple ?
2452024-09-26T14:47:13 <sipa> Chris_Stewart_5: yes
2462024-09-26T14:47:32 <Chris_Stewart_5> i don't believe so, but i'm going to go investigate now. Be back in awhile with a PR
2472024-09-26T14:47:37 <fanquake> by default any codesigning may involve timestamping, which i'd assume apple would use it's own servers for
2482024-09-26T14:47:58 <sipa> my understanding is that we've previously held off on doing these things because apple would phone home to verify the certificate in some way or so
2492024-09-26T14:48:05 <achow101> ad-hoc signing doesn't actually sign though
2502024-09-26T14:48:22 <achow101> it actually tells gatekeeper that the binary is safe to not verify
2512024-09-26T14:48:28 <sipa> but given recent reports that this contacting of apple servers happens regardless, it may be time to bite the bullet
2522024-09-26T14:49:00 <fanquake> has anyone checked if the codesigning tool actually ships on a vanilla, non-dev mac
2532024-09-26T14:49:13 <fanquake> or will we also need to tell people to download and install the command line tools (from apple)
2542024-09-26T14:49:26 <fanquake> to actually do any signing in the first place
2552024-09-26T14:50:04 <achow101> fanquake: i believe it does as it's part of the security utils. haven't checked on a mac though
2562024-09-26T14:50:16 <sipa> Chris_Stewart_5: i ask, because if somehow the phoning home can be prevented by self-signing, then perhaps self-signing should remain the primary recommendation, even if we do the stapling
2572024-09-26T14:51:26 *** twistedline <twistedline!~bitcoin@185.193.125.44> has joined #bitcoin-core-dev
2582024-09-26T15:01:04 <fanquake> Can someone share whatever command they are using for adhoc codesigning? I just downloaded bins from bitcoincore.org, ran codesign --force --options runtime -s - bitcoind, which shows, Signature=adhoc, but the bins still don't run
2592024-09-26T15:03:10 *** twistedline <twistedline!~bitcoin@185.193.125.44> has quit IRC (Ping timeout: 260 seconds)
2602024-09-26T15:03:36 *** twistedline <twistedline!~bitcoin@185.193.125.44> has joined #bitcoin-core-dev
2612024-09-26T15:08:15 *** Wronsk <Wronsk!~Wronsk@cust-west-par-46-193-0-235.cust.wifirst.net> has quit IRC (Remote host closed the connection)
2622024-09-26T15:11:20 *** twistedline <twistedline!~bitcoin@185.193.125.44> has quit IRC (Ping timeout: 260 seconds)
2632024-09-26T15:11:45 *** twistedline <twistedline!~bitcoin@185.193.125.44> has joined #bitcoin-core-dev
2642024-09-26T15:23:53 *** Emc99 <Emc99!~Emc99@212.129.84.59> has joined #bitcoin-core-dev
2652024-09-26T15:25:09 *** Emc99 <Emc99!~Emc99@212.129.84.59> has quit IRC (Client Quit)
2662024-09-26T15:29:26 <bitcoin-git> [bitcoin] Christewart opened pull request #30982: docs: Add instructions on how to self-sign bitcoin-core binaries for macOS (master...2024-09-26-selfsign-mac-instructions) https://github.com/bitcoin/bitcoin/pull/30982
2672024-09-26T15:29:55 *** twistedline <twistedline!~bitcoin@185.193.125.44> has quit IRC (Ping timeout: 244 seconds)
2682024-09-26T15:30:17 <Chris_Stewart_5> fanquake: ^ is what works for me. Give it a try. It appears that the xattr -d com.apple.quarantine is only required if you download via a web browser (rather than command line) AFAICT
2692024-09-26T15:31:40 *** twistedline <twistedline!~bitcoin@185.193.125.44> has joined #bitcoin-core-dev
2702024-09-26T15:32:04 <Chris_Stewart_5> and i don't believe it requires phoning home. I disconnected from my network connection and was still able to sign and run commands like ./bitcoin-cli --help
2712024-09-26T15:34:40 <Chris_Stewart_5> fanquake: Also according to chatGPT 'codesign' ships by default on macOS ;).
2722024-09-26T15:35:19 <fanquake> Chris_Stewart_5: cool. Note that we'll want to inline the instructions into the readme, rather than linking to one thing, that then links to something else
2732024-09-26T15:35:35 <fanquake> as far as I'm aware, it's also not required to create a cert, as claimed in the second linked post
2742024-09-26T15:36:38 <Chris_Stewart_5> I"ll just remove the link as I don't think it provides much value
2752024-09-26T15:36:48 *** szkl <szkl!uid110435@id-110435.uxbridge.irccloud.com> has quit IRC (Quit: Connection closed for inactivity)
2762024-09-26T15:37:08 <bitcoin-git> [bitcoin] fanquake pushed 3 commits to master: https://github.com/bitcoin/bitcoin/compare/d5af7d28f475...fa7c2838a5f3
2772024-09-26T15:37:09 <bitcoin-git> bitcoin/master fa48be6 MarcoFalke: test: Refactor fill_mempool to extract send_batch helper
2782024-09-26T15:37:09 <bitcoin-git> bitcoin/master faf8015 MarcoFalke: test: Add missing sync_mempools() to fill_mempool()
2792024-09-26T15:37:09 <bitcoin-git> bitcoin/master fa7c283 merge-script: Merge bitcoin/bitcoin#30948: test: Add missing sync_mempools() to fill_mem...
2802024-09-26T15:37:12 <bitcoin-git> [bitcoin] fanquake merged pull request #30948: test: Add missing sync_mempools() to fill_mempool() (master...2409-test-fix-tx-mem) https://github.com/bitcoin/bitcoin/pull/30948
2812024-09-26T15:40:33 *** twistedline <twistedline!~bitcoin@185.193.125.44> has quit IRC (Ping timeout: 248 seconds)
2822024-09-26T15:40:48 *** twistedline <twistedline!~bitcoin@185.193.125.44> has joined #bitcoin-core-dev
2832024-09-26T15:45:42 *** twistedline <twistedline!~bitcoin@185.193.125.44> has quit IRC (Ping timeout: 246 seconds)
2842024-09-26T15:45:58 *** twistedline <twistedline!~bitcoin@185.193.125.44> has joined #bitcoin-core-dev
2852024-09-26T15:47:45 *** szkl <szkl!uid110435@id-110435.uxbridge.irccloud.com> has joined #bitcoin-core-dev
2862024-09-26T15:51:38 <bitcoin-git> [bitcoin] fanquake pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/fa7c2838a5f3...36ad9516dbd6
2872024-09-26T15:51:39 <bitcoin-git> bitcoin/master f951f1f willcl-ark: ci: add timestamps to cirrus jobs
2882024-09-26T15:51:39 <bitcoin-git> bitcoin/master 36ad951 merge-script: Merge bitcoin/bitcoin#30981: ci: add timestamps to cirrus jobs
2892024-09-26T15:51:42 <bitcoin-git> [bitcoin] fanquake merged pull request #30981: ci: add timestamps to cirrus jobs (master...cirrus-timestamps) https://github.com/bitcoin/bitcoin/pull/30981
2902024-09-26T15:59:42 *** twistedline <twistedline!~bitcoin@185.193.125.44> has quit IRC (Ping timeout: 246 seconds)
2912024-09-26T16:00:38 *** twistedline <twistedline!~bitcoin@185.193.125.44> has joined #bitcoin-core-dev
2922024-09-26T16:09:42 *** zeropoint <zeropoint!~alex@45-28-139-114.lightspeed.sntcca.sbcglobal.net> has joined #bitcoin-core-dev
2932024-09-26T16:12:33 *** BrandonOdiwuor <BrandonOdiwuor!~BrandonOd@105.163.2.94> has quit IRC (Quit: Client closed)
2942024-09-26T16:18:38 *** ion- <ion-!ion-@user/ion-> has quit IRC (Remote host closed the connection)
2952024-09-26T16:18:54 *** ion- <ion-!ion-@user/ion-> has joined #bitcoin-core-dev
2962024-09-26T16:19:45 *** twistedline <twistedline!~bitcoin@185.193.125.44> has quit IRC (Ping timeout: 252 seconds)
2972024-09-26T16:20:20 *** twistedline <twistedline!~bitcoin@185.193.125.44> has joined #bitcoin-core-dev
2982024-09-26T16:52:04 *** ___nick___ <___nick___!~quassel@82-132-215-132.dab.02.net> has quit IRC (Ping timeout: 245 seconds)
2992024-09-26T16:52:46 *** ion- <ion-!ion-@user/ion-> has quit IRC (Remote host closed the connection)
3002024-09-26T17:04:45 *** ___nick___ <___nick___!~quassel@82-132-215-31.dab.02.net> has joined #bitcoin-core-dev
3012024-09-26T17:08:41 *** ion- <ion-!ion-@user/ion-> has joined #bitcoin-core-dev
3022024-09-26T17:13:22 *** emcy__ <emcy__!~emcy@85.255.235.25> has joined #bitcoin-core-dev
3032024-09-26T17:16:21 *** mcey_ <mcey_!~emcy@148.252.145.21> has quit IRC (Ping timeout: 246 seconds)
3042024-09-26T17:22:46 *** brunoerg <brunoerg!~brunoerg@187.183.60.117> has joined #bitcoin-core-dev
3052024-09-26T17:47:36 *** Talkless <Talkless!~Talkless@mail.dargis.net> has joined #bitcoin-core-dev
3062024-09-26T18:01:44 <pinheadmz> does anyone still have the testnet4 block that was reorged out?
3072024-09-26T18:01:46 <pinheadmz> 00000000000000263393ce5f648afd53676f13d360cc9f264b89351623bf1242
3082024-09-26T18:33:22 *** ion- <ion-!ion-@user/ion-> has quit IRC (Remote host closed the connection)
3092024-09-26T18:33:37 *** ion- <ion-!ion-@user/ion-> has joined #bitcoin-core-dev
3102024-09-26T18:34:32 *** dviola <dviola!~diego@user/dviola> has quit IRC (Quit: WeeChat 4.4.2)
3112024-09-26T19:00:06 *** ion- <ion-!ion-@user/ion-> has quit IRC (Remote host closed the connection)
3122024-09-26T19:06:39 *** dviola <dviola!~diego@user/dviola> has joined #bitcoin-core-dev
3132024-09-26T19:11:06 *** dongcarl3 <dongcarl3!~dongcarl@syn-066-065-169-019.res.spectrum.com> has joined #bitcoin-core-dev
3142024-09-26T19:11:25 *** _andrewtoth_ <_andrewtoth_!~andrewtot@gateway/tor-sasl/andrewtoth> has quit IRC (Remote host closed the connection)
3152024-09-26T19:12:19 *** dermoth_ <dermoth_!~dermoth@user/dermoth> has joined #bitcoin-core-dev
3162024-09-26T19:13:39 *** andrewtoth <andrewtoth!~andrewtot@gateway/tor-sasl/andrewtoth> has joined #bitcoin-core-dev
3172024-09-26T19:16:38 *** theStack_ <theStack_!~theStack@95.179.145.232> has joined #bitcoin-core-dev
3182024-09-26T19:18:06 *** theStack_ <theStack_!~theStack@95.179.145.232> has quit IRC (Client Quit)
3192024-09-26T19:18:53 *** ion- <ion-!ion-@user/ion-> has joined #bitcoin-core-dev
3202024-09-26T19:19:31 *** shesek <shesek!~shesek@user/shesek> has quit IRC (*.net *.split)
3212024-09-26T19:19:31 *** dermoth <dermoth!~dermoth@user/dermoth> has quit IRC (*.net *.split)
3222024-09-26T19:19:31 *** dongcarl <dongcarl!~dongcarl@syn-066-065-169-019.res.spectrum.com> has quit IRC (*.net *.split)
3232024-09-26T19:19:31 *** robobub <robobub!uid248673@id-248673.uxbridge.irccloud.com> has quit IRC (*.net *.split)
3242024-09-26T19:19:31 *** theStack <theStack!~theStack@95.179.145.232> has quit IRC (*.net *.split)
3252024-09-26T19:19:31 *** dergoegge <dergoegge!sid453889@id-453889.lymington.irccloud.com> has quit IRC (*.net *.split)
3262024-09-26T19:19:32 *** rodarmor <rodarmor!sid210835@id-210835.helmsley.irccloud.com> has quit IRC (*.net *.split)
3272024-09-26T19:19:32 *** ajonas <ajonas!sid385278@2a03:5180:f:1::5:e0fe> has quit IRC (*.net *.split)
3282024-09-26T19:19:32 *** moneyball_____ <moneyball_____!sid299869@2a03:5180:f:1::4:935d> has quit IRC (*.net *.split)
3292024-09-26T19:19:32 *** valwal__ <valwal__!sid570092@2a03:5180:f::8:b2ec> has quit IRC (*.net *.split)
3302024-09-26T19:19:32 *** Flow <Flow!~none@gentoo/developer/flow> has quit IRC (*.net *.split)
3312024-09-26T19:19:32 *** Ara <Ara!~Ara@user/ara> has quit IRC (*.net *.split)
3322024-09-26T19:19:32 *** dongcarl3 is now known as dongcarl
3332024-09-26T19:20:19 *** shesek <shesek!~shesek@user/shesek> has joined #bitcoin-core-dev
3342024-09-26T19:20:19 *** robobub <robobub!uid248673@id-248673.uxbridge.irccloud.com> has joined #bitcoin-core-dev
3352024-09-26T19:20:19 *** dergoegge <dergoegge!sid453889@id-453889.lymington.irccloud.com> has joined #bitcoin-core-dev
3362024-09-26T19:20:19 *** rodarmor <rodarmor!sid210835@id-210835.helmsley.irccloud.com> has joined #bitcoin-core-dev
3372024-09-26T19:20:19 *** ajonas <ajonas!sid385278@2a03:5180:f:1::5:e0fe> has joined #bitcoin-core-dev
3382024-09-26T19:20:19 *** moneyball_____ <moneyball_____!sid299869@2a03:5180:f:1::4:935d> has joined #bitcoin-core-dev
3392024-09-26T19:20:19 *** valwal__ <valwal__!sid570092@2a03:5180:f::8:b2ec> has joined #bitcoin-core-dev
3402024-09-26T19:20:19 *** Flow <Flow!~none@gentoo/developer/flow> has joined #bitcoin-core-dev
3412024-09-26T19:20:19 *** Ara <Ara!~Ara@user/ara> has joined #bitcoin-core-dev
3422024-09-26T19:22:11 *** dermoth_ is now known as dermoth
3432024-09-26T19:23:58 *** ion- <ion-!ion-@user/ion-> has quit IRC (Ping timeout: 244 seconds)
3442024-09-26T19:26:06 *** robobub <robobub!uid248673@id-248673.uxbridge.irccloud.com> has quit IRC (Ping timeout: 265 seconds)
3452024-09-26T19:30:06 *** theStack <theStack!~theStack@95.179.145.232> has joined #bitcoin-core-dev
3462024-09-26T19:31:53 *** robobub <robobub!uid248673@id-248673.uxbridge.irccloud.com> has joined #bitcoin-core-dev
3472024-09-26T19:36:32 *** Talkless <Talkless!~Talkless@mail.dargis.net> has quit IRC (Remote host closed the connection)
3482024-09-26T19:38:58 *** ion- <ion-!ion-@user/ion-> has joined #bitcoin-core-dev
3492024-09-26T19:41:05 *** ___nick___ <___nick___!~quassel@82-132-215-31.dab.02.net> has quit IRC (Ping timeout: 248 seconds)
3502024-09-26T20:01:53 *** brunoerg <brunoerg!~brunoerg@187.183.60.117> has quit IRC (Remote host closed the connection)
3512024-09-26T20:02:05 *** Chris_Stewart_5 <Chris_Stewart_5!~Chris_Ste@static-68-235-44-41.cust.tzulo.com> has quit IRC (Ping timeout: 255 seconds)
3522024-09-26T20:02:29 *** Chris_Stewart_5 <Chris_Stewart_5!~Chris_Ste@static-68-235-44-41.cust.tzulo.com> has joined #bitcoin-core-dev
3532024-09-26T20:25:59 *** arminsdev <arminsdev!~arminsdev@2601:184:4181:ba20:71cc:1923:57a:fa69> has joined #bitcoin-core-dev
3542024-09-26T21:07:29 *** ion- <ion-!ion-@user/ion-> has quit IRC (Ping timeout: 248 seconds)
3552024-09-26T21:12:27 *** VonNaturAustreVe <VonNaturAustreVe!~natur@user/vonnaturaustreve> has joined #bitcoin-core-dev
3562024-09-26T21:21:54 *** achow101 <achow101!~achow101@user/achow101> has quit IRC (Ping timeout: 252 seconds)
3572024-09-26T21:21:56 *** ion- <ion-!ion-@user/ion-> has joined #bitcoin-core-dev
3582024-09-26T21:22:23 *** VonNaturAustreVe <VonNaturAustreVe!~natur@user/vonnaturaustreve> has quit IRC (Quit: Leaving)
3592024-09-26T21:27:53 *** brunoerg <brunoerg!~brunoerg@2804:1600:100:1f00:9d6b:24db:99c4:546e> has joined #bitcoin-core-dev
3602024-09-26T21:32:03 <bitcoin-git> [bitcoin] brunoerg opened pull request #30984: p2p: rpc: add `tx_reconciliation` to `getpeerinfo` (master...2024-09-erlay-getpeerinfo) https://github.com/bitcoin/bitcoin/pull/30984
3612024-09-26T21:34:51 *** achow101 <achow101!~achow101@user/achow101> has joined #bitcoin-core-dev
3622024-09-26T21:38:02 <bitcoin-git> [bitcoin] andremralves opened pull request #30986: contrib: skip missing binaries in gen-manpages (master...fix-gen-manpages) https://github.com/bitcoin/bitcoin/pull/30986
3632024-09-26T21:40:01 *** achow101 <achow101!~achow101@user/achow101> has quit IRC (Ping timeout: 248 seconds)
3642024-09-26T21:45:33 *** achow101 <achow101!~achow101@user/achow101> has joined #bitcoin-core-dev
3652024-09-26T21:46:16 *** brunoerg <brunoerg!~brunoerg@2804:1600:100:1f00:9d6b:24db:99c4:546e> has quit IRC (Ping timeout: 265 seconds)
3662024-09-26T21:53:20 *** bugs_ <bugs_!~bugs@user/bugs/x-5128603> has quit IRC (Quit: Leaving)
3672024-09-26T21:56:33 *** brunoerg <brunoerg!~brunoerg@2804:1600:100:1f00:9d6b:24db:99c4:546e> has joined #bitcoin-core-dev
3682024-09-26T22:11:45 *** arminsdev <arminsdev!~arminsdev@2601:184:4181:ba20:71cc:1923:57a:fa69> has quit IRC (Quit: Client closed)
3692024-09-26T22:13:20 *** brunoerg <brunoerg!~brunoerg@2804:1600:100:1f00:9d6b:24db:99c4:546e> has quit IRC (Remote host closed the connection)
3702024-09-26T22:23:11 *** brunoerg <brunoerg!~brunoerg@2804:1600:100:1f00:9d6b:24db:99c4:546e> has joined #bitcoin-core-dev
3712024-09-26T22:40:36 <bitcoin-git> [bitcoin] davidgumberg opened pull request #30987: Don't zero-after-free `DataStream`: ~25% faster IBD (master...zero_after_free_allocator_change) https://github.com/bitcoin/bitcoin/pull/30987
3722024-09-26T22:42:20 *** brunoerg <brunoerg!~brunoerg@2804:1600:100:1f00:9d6b:24db:99c4:546e> has quit IRC (Remote host closed the connection)
3732024-09-26T22:45:23 *** brunoerg <brunoerg!~brunoerg@2804:1600:100:1f00:9d6b:24db:99c4:546e> has joined #bitcoin-core-dev
3742024-09-26T23:24:52 *** brunoerg <brunoerg!~brunoerg@2804:1600:100:1f00:9d6b:24db:99c4:546e> has quit IRC (Remote host closed the connection)
3752024-09-26T23:27:35 *** brunoerg <brunoerg!~brunoerg@2804:1600:100:1f00:9d6b:24db:99c4:546e> has joined #bitcoin-core-dev
3762024-09-26T23:27:51 *** brunoerg <brunoerg!~brunoerg@2804:1600:100:1f00:9d6b:24db:99c4:546e> has quit IRC (Remote host closed the connection)
3772024-09-26T23:29:52 *** brunoerg <brunoerg!~brunoerg@2804:1600:100:1f00:9d6b:24db:99c4:546e> has joined #bitcoin-core-dev
3782024-09-26T23:31:40 *** brunoerg <brunoerg!~brunoerg@2804:1600:100:1f00:9d6b:24db:99c4:546e> has quit IRC (Remote host closed the connection)
3792024-09-26T23:48:22 *** zeropoint <zeropoint!~alex@45-28-139-114.lightspeed.sntcca.sbcglobal.net> has quit IRC (Quit: leaving)
3802024-09-26T23:54:19 *** VonNaturAustreVe <VonNaturAustreVe!~natur@2804:14c:65d7:8f6e:d016:5a64:247c:5e04> has joined #bitcoin-core-dev