12024-12-05T00:01:10 <bitcoin-git> [bitcoin-detached-sigs] achow101 pushed 1 commit to 28.x: https://github.com/bitcoin-core/bitcoin-detached-sigs/compare/ee8cb49df8f6...f79e2ce472db
22024-12-05T00:01:11 <bitcoin-git> bitcoin-detached-sigs/28.x f79e2ce Ava Chow: 28.1: win signature for rc1
32024-12-05T00:01:41 <bitcoin-git> [bitcoin-detached-sigs] achow101 pushed tag v28.1rc1: https://github.com/bitcoin-core/bitcoin-detached-sigs/compare/v28.1rc1
42024-12-05T00:43:40 *** Zenton__ <Zenton__!~Zenton@user/zenton> has quit IRC (Remote host closed the connection)
52024-12-05T00:43:58 *** Zenton__ <Zenton__!~Zenton@user/zenton> has joined #bitcoin-core-dev
62024-12-05T00:45:40 *** ioannis <ioannis!ion-@user/ion-> has quit IRC (Ping timeout: 260 seconds)
72024-12-05T00:47:27 *** adil <adil!~Thunderbi@2402:d000:8134:9818:a574:e458:13a6:f6f7> has joined #bitcoin-core-dev
82024-12-05T00:48:10 *** Zenton__ <Zenton__!~Zenton@user/zenton> has quit IRC (Remote host closed the connection)
92024-12-05T00:49:45 *** Zenton <Zenton!~Zenton@user/zenton> has joined #bitcoin-core-dev
102024-12-05T00:57:42 *** ioannis <ioannis!ion-@user/ion-> has joined #bitcoin-core-dev
112024-12-05T01:02:16 *** ioannis <ioannis!ion-@user/ion-> has quit IRC (Ping timeout: 252 seconds)
122024-12-05T01:15:08 *** ioannis <ioannis!ion-@user/ion-> has joined #bitcoin-core-dev
132024-12-05T01:19:37 *** ioannis <ioannis!ion-@user/ion-> has quit IRC (Ping timeout: 244 seconds)
142024-12-05T01:19:52 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Remote host closed the connection)
152024-12-05T01:20:50 *** zeropoint <zeropoint!~alex@45-28-139-114.lightspeed.sntcca.sbcglobal.net> has quit IRC (Quit: leaving)
162024-12-05T01:22:36 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
172024-12-05T01:24:50 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Excess Flood)
182024-12-05T01:25:50 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
192024-12-05T01:27:40 *** adil <adil!~Thunderbi@2402:d000:8134:9818:a574:e458:13a6:f6f7> has quit IRC (Quit: adil)
202024-12-05T01:29:59 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 245 seconds)
212024-12-05T01:31:46 *** ioannis <ioannis!ion-@user/ion-> has joined #bitcoin-core-dev
222024-12-05T01:36:00 *** brad_ <brad_!~brad@200.68.141.10> has joined #bitcoin-core-dev
232024-12-05T01:36:25 *** ioannis <ioannis!ion-@user/ion-> has quit IRC (Ping timeout: 260 seconds)
242024-12-05T01:46:31 *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has joined #bitcoin-core-dev
252024-12-05T01:49:24 *** ioannis <ioannis!ion-@user/ion-> has joined #bitcoin-core-dev
262024-12-05T01:53:53 *** ioannis <ioannis!ion-@user/ion-> has quit IRC (Ping timeout: 248 seconds)
272024-12-05T01:54:09 *** eval-exec <eval-exec!~Thunderbi@107.182.187.217.16clouds.com> has joined #bitcoin-core-dev
282024-12-05T01:58:10 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
292024-12-05T02:04:03 *** spynxic <spynxic!~spynxic@spynxic.powered.by.lunarbnc.net> has quit IRC (Ping timeout: 244 seconds)
302024-12-05T02:04:09 *** spynx <spynx!~spynxic@spynxic.powered.by.lunarbnc.net> has joined #bitcoin-core-dev
312024-12-05T02:06:16 *** ioannis <ioannis!ion-@user/ion-> has joined #bitcoin-core-dev
322024-12-05T02:10:39 *** spynx <spynx!~spynxic@spynxic.powered.by.lunarbnc.net> has quit IRC (Ping timeout: 260 seconds)
332024-12-05T02:11:14 *** ioannis <ioannis!ion-@user/ion-> has quit IRC (Ping timeout: 260 seconds)
342024-12-05T02:15:12 *** ioannis <ioannis!ion-@user/ion-> has joined #bitcoin-core-dev
352024-12-05T02:18:42 *** tripleslash <tripleslash!~triplesla@user/tripleslash> has quit IRC (Ping timeout: 276 seconds)
362024-12-05T02:20:36 *** vasild <vasild!~vd@user/vasild> has quit IRC (Ping timeout: 264 seconds)
372024-12-05T02:20:48 *** vasild <vasild!~vd@user/vasild> has joined #bitcoin-core-dev
382024-12-05T02:43:26 *** spynxic <spynxic!~spynxic@spynxic.powered.by.lunarbnc.net> has joined #bitcoin-core-dev
392024-12-05T02:46:25 *** Murch[m] <Murch[m]!~murch@2620:6e:a000:ce11::1b> has quit IRC (Ping timeout: 260 seconds)
402024-12-05T02:47:00 *** sr_gi[m] <sr_gi[m]!~srgimatri@2620:6e:a000:ce11::2a> has quit IRC (Ping timeout: 260 seconds)
412024-12-05T02:47:00 *** kvaciral[m] <kvaciral[m]!~kvaciralx@2620:6e:a000:ce11::27> has quit IRC (Ping timeout: 260 seconds)
422024-12-05T02:55:45 *** spynxic <spynxic!~spynxic@spynxic.powered.by.lunarbnc.net> has quit IRC (Ping timeout: 276 seconds)
432024-12-05T02:59:38 *** Murch[m] <Murch[m]!~murch@2620:6e:a000:ce11::1b> has joined #bitcoin-core-dev
442024-12-05T03:00:12 *** kvaciral[m] <kvaciral[m]!~kvaciralx@2620:6e:a000:ce11::27> has joined #bitcoin-core-dev
452024-12-05T03:00:49 *** sr_gi[m] <sr_gi[m]!~srgimatri@2620:6e:a000:ce11::2a> has joined #bitcoin-core-dev
462024-12-05T03:14:25 *** Zenton <Zenton!~Zenton@user/zenton> has quit IRC (Read error: Connection reset by peer)
472024-12-05T03:14:57 *** Zenton <Zenton!~Zenton@user/zenton> has joined #bitcoin-core-dev
482024-12-05T03:20:49 *** ioannis <ioannis!ion-@user/ion-> has quit IRC (Ping timeout: 272 seconds)
492024-12-05T03:25:16 *** spynxic <spynxic!~spynxic@spynxic.powered.by.lunarbnc.net> has joined #bitcoin-core-dev
502024-12-05T03:32:33 *** ioannis <ioannis!ion-@user/ion-> has joined #bitcoin-core-dev
512024-12-05T04:03:44 *** Zenton_ <Zenton_!~Zenton@user/zenton> has joined #bitcoin-core-dev
522024-12-05T04:06:20 *** Zenton <Zenton!~Zenton@user/zenton> has quit IRC (Ping timeout: 260 seconds)
532024-12-05T04:10:10 *** Zenton_ <Zenton_!~Zenton@user/zenton> has quit IRC (Remote host closed the connection)
542024-12-05T04:10:28 *** Zenton_ <Zenton_!~Zenton@user/zenton> has joined #bitcoin-core-dev
552024-12-05T04:16:09 *** Zenton_ <Zenton_!~Zenton@user/zenton> has quit IRC (Remote host closed the connection)
562024-12-05T04:17:34 *** Zenton <Zenton!~Zenton@user/zenton> has joined #bitcoin-core-dev
572024-12-05T04:35:57 *** ioannis <ioannis!ion-@user/ion-> has quit IRC (Ping timeout: 265 seconds)
582024-12-05T04:41:21 *** itsarjn <itsarjn!~itsarjn@user/itsarjn> has joined #bitcoin-core-dev
592024-12-05T04:48:14 *** ioannis <ioannis!ion-@user/ion-> has joined #bitcoin-core-dev
602024-12-05T04:51:27 *** itsarjn <itsarjn!~itsarjn@user/itsarjn> has quit IRC (Remote host closed the connection)
612024-12-05T04:54:43 *** itsarjn <itsarjn!~itsarjn@user/itsarjn> has joined #bitcoin-core-dev
622024-12-05T04:54:44 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Read error: Connection reset by peer)
632024-12-05T04:58:09 *** kevkevin <kevkevin!~kevkevin@2601:243:197e:8f10:3581:7920:80d9:4fec> has joined #bitcoin-core-dev
642024-12-05T05:01:01 *** cmirror <cmirror!~cmirror@4.53.92.114> has quit IRC (Remote host closed the connection)
652024-12-05T05:03:21 *** kerm|t <kerm|t!sid393220@user/kermit4> has quit IRC (Read error: Connection reset by peer)
662024-12-05T05:03:25 *** FelixWeis__ <FelixWeis__!sid154231@id-154231.hampstead.irccloud.com> has quit IRC (Ping timeout: 272 seconds)
672024-12-05T05:03:25 *** arik__ <arik__!sid402902@id-402902.lymington.irccloud.com> has quit IRC (Ping timeout: 272 seconds)
682024-12-05T05:03:34 *** kerm|t <kerm|t!sid393220@user/kermit4> has joined #bitcoin-core-dev
692024-12-05T05:03:44 *** rodarmor <rodarmor!sid210835@id-210835.helmsley.irccloud.com> has quit IRC (Ping timeout: 264 seconds)
702024-12-05T05:03:44 *** fanquake <fanquake!sid369002@user/fanquake> has quit IRC (Ping timeout: 264 seconds)
712024-12-05T05:03:44 *** zone117x <zone117x!sid117212@id-117212.tinside.irccloud.com> has quit IRC (Ping timeout: 264 seconds)
722024-12-05T05:03:44 *** amiti___ <amiti___!sid373138@id-373138.lymington.irccloud.com> has quit IRC (Ping timeout: 264 seconds)
732024-12-05T05:03:53 *** johnny9dev584508 <johnny9dev584508!~johnny9de@136.56.172.142> has quit IRC (Read error: Connection reset by peer)
742024-12-05T05:03:54 *** rodarmor <rodarmor!sid210835@id-210835.helmsley.irccloud.com> has joined #bitcoin-core-dev
752024-12-05T05:04:03 *** maxedw <maxedw!sid625334@id-625334.uxbridge.irccloud.com> has quit IRC (Ping timeout: 272 seconds)
762024-12-05T05:04:09 *** gribble <gribble!~gribble@bitcoin/bot/gribble> has quit IRC (Ping timeout: 246 seconds)
772024-12-05T05:04:43 *** cmirror <cmirror!~cmirror@4.53.92.114> has joined #bitcoin-core-dev
782024-12-05T05:04:52 *** _aj_ <_aj_!aj@user/aj/x-5857768> has quit IRC (Ping timeout: 246 seconds)
792024-12-05T05:05:07 *** FelixWeis__ <FelixWeis__!sid154231@id-154231.hampstead.irccloud.com> has joined #bitcoin-core-dev
802024-12-05T05:05:59 *** gribble` <gribble`!~gribble@bitcoin/bot/gribble> has joined #bitcoin-core-dev
812024-12-05T05:06:00 *** ChanServ sets mode: +o gribble`
822024-12-05T05:06:47 *** _aj_ <_aj_!aj@azure.erisian.com.au> has joined #bitcoin-core-dev
832024-12-05T05:06:52 *** maxedw <maxedw!sid625334@id-625334.uxbridge.irccloud.com> has joined #bitcoin-core-dev
842024-12-05T05:06:53 *** amiti___ <amiti___!sid373138@id-373138.lymington.irccloud.com> has joined #bitcoin-core-dev
852024-12-05T05:06:55 *** fanquake <fanquake!sid369002@user/fanquake> has joined #bitcoin-core-dev
862024-12-05T05:06:56 *** zone117x <zone117x!sid117212@id-117212.tinside.irccloud.com> has joined #bitcoin-core-dev
872024-12-05T05:07:09 *** arik__ <arik__!sid402902@id-402902.lymington.irccloud.com> has joined #bitcoin-core-dev
882024-12-05T05:08:33 *** kevkevin <kevkevin!~kevkevin@2601:243:197e:8f10:3581:7920:80d9:4fec> has quit IRC (Ping timeout: 248 seconds)
892024-12-05T06:01:08 *** mcey_ <mcey_!~emcy@148.252.146.200> has quit IRC (Remote host closed the connection)
902024-12-05T06:01:36 *** mcey_ <mcey_!~emcy@148.252.146.200> has joined #bitcoin-core-dev
912024-12-05T06:14:49 *** kevkevin <kevkevin!~kevkevin@2601:243:197e:8f10:3581:7920:80d9:4fec> has joined #bitcoin-core-dev
922024-12-05T06:18:36 <bitcoin-git> [bitcoin] vasild opened pull request #31424: build: enable libc++ and libstdc++ hardening (master...libc_hardening) https://github.com/bitcoin/bitcoin/pull/31424
932024-12-05T06:19:25 *** kevkevin <kevkevin!~kevkevin@2601:243:197e:8f10:3581:7920:80d9:4fec> has quit IRC (Ping timeout: 272 seconds)
942024-12-05T06:22:08 *** dongcarl <dongcarl!~dongcarl@syn-066-065-169-019.res.spectrum.com> has quit IRC (Quit: Ping timeout (120 seconds))
952024-12-05T06:23:30 *** dongcarl <dongcarl!~dongcarl@syn-066-065-169-019.res.spectrum.com> has joined #bitcoin-core-dev
962024-12-05T06:25:39 *** itsarjn_ <itsarjn_!~itsarjn@user/itsarjn> has joined #bitcoin-core-dev
972024-12-05T06:28:39 *** ioannis <ioannis!ion-@user/ion-> has quit IRC (Ping timeout: 252 seconds)
982024-12-05T06:29:01 *** itsarjn <itsarjn!~itsarjn@user/itsarjn> has quit IRC (Ping timeout: 252 seconds)
992024-12-05T06:39:12 *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has quit IRC (Ping timeout: 264 seconds)
1002024-12-05T06:40:42 *** kevkevin <kevkevin!~kevkevin@2601:243:197e:8f10:3581:7920:80d9:4fec> has joined #bitcoin-core-dev
1012024-12-05T06:40:49 *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has joined #bitcoin-core-dev
1022024-12-05T06:42:39 *** ioannis <ioannis!ion-@user/ion-> has joined #bitcoin-core-dev
1032024-12-05T06:54:58 *** itsarjn <itsarjn!~itsarjn@user/itsarjn> has joined #bitcoin-core-dev
1042024-12-05T06:55:31 *** kevkevin <kevkevin!~kevkevin@2601:243:197e:8f10:3581:7920:80d9:4fec> has quit IRC (Ping timeout: 272 seconds)
1052024-12-05T06:57:57 *** itsarjn_ <itsarjn_!~itsarjn@user/itsarjn> has quit IRC (Ping timeout: 248 seconds)
1062024-12-05T07:08:41 *** kevkevin <kevkevin!~kevkevin@2601:243:197e:8f10:3581:7920:80d9:4fec> has joined #bitcoin-core-dev
1072024-12-05T07:15:49 *** ioannis <ioannis!ion-@user/ion-> has quit IRC (Ping timeout: 245 seconds)
1082024-12-05T07:19:09 *** Zenton <Zenton!~Zenton@user/zenton> has quit IRC (Remote host closed the connection)
1092024-12-05T07:19:28 *** Zenton <Zenton!~Zenton@user/zenton> has joined #bitcoin-core-dev
1102024-12-05T07:22:49 *** ioannis <ioannis!ion-@user/ion-> has joined #bitcoin-core-dev
1112024-12-05T07:25:04 *** kevkevin <kevkevin!~kevkevin@2601:243:197e:8f10:3581:7920:80d9:4fec> has quit IRC (Ping timeout: 260 seconds)
1122024-12-05T08:01:11 *** aleggg <aleggg!~aleggg@189.114.82.114> has quit IRC (Ping timeout: 255 seconds)
1132024-12-05T08:20:18 *** Zenton <Zenton!~Zenton@user/zenton> has quit IRC (Read error: Connection reset by peer)
1142024-12-05T08:20:37 *** Zenton <Zenton!~Zenton@user/zenton> has joined #bitcoin-core-dev
1152024-12-05T08:30:11 <bitcoin-git> [bitcoin] TheCharlatan opened pull request #31425: RFC: Riscv bare metal CI job (master...bare_metal_support) https://github.com/bitcoin/bitcoin/pull/31425
1162024-12-05T08:37:40 *** Zenton <Zenton!~Zenton@user/zenton> has quit IRC (Remote host closed the connection)
1172024-12-05T08:37:59 *** Zenton <Zenton!~Zenton@user/zenton> has joined #bitcoin-core-dev
1182024-12-05T08:41:53 *** otoburb <otoburb!~otoburb@user/otoburb> has quit IRC (Ping timeout: 248 seconds)
1192024-12-05T08:42:09 *** otoburb <otoburb!~otoburb@user/otoburb> has joined #bitcoin-core-dev
1202024-12-05T08:42:31 *** itsarjn <itsarjn!~itsarjn@user/itsarjn> has quit IRC (Remote host closed the connection)
1212024-12-05T08:43:36 *** itsarjn <itsarjn!~itsarjn@user/itsarjn> has joined #bitcoin-core-dev
1222024-12-05T08:44:09 *** Guyver2 <Guyver2!Guyver@77-174-98-73.fixed.kpn.net> has joined #bitcoin-core-dev
1232024-12-05T09:02:50 *** Guyver2 <Guyver2!Guyver@77-174-98-73.fixed.kpn.net> has left #bitcoin-core-dev (Closing Window)
1242024-12-05T09:14:10 *** Zenton <Zenton!~Zenton@user/zenton> has quit IRC (Remote host closed the connection)
1252024-12-05T09:14:29 *** Zenton <Zenton!~Zenton@user/zenton> has joined #bitcoin-core-dev
1262024-12-05T09:25:13 *** sebastianvstaa <sebastianvstaa!~sebastian@dsl-212-100-46-253.pool.bitel.net> has joined #bitcoin-core-dev
1272024-12-05T09:41:54 *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has quit IRC (Remote host closed the connection)
1282024-12-05T09:42:15 *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has joined #bitcoin-core-dev
1292024-12-05T09:45:15 *** Flow <Flow!~none@gentoo/developer/flow> has quit IRC (Ping timeout: 272 seconds)
1302024-12-05T09:55:53 *** sliv3r__ <sliv3r__!~sliv3r__@user/sliv3r-:76883> has joined #bitcoin-core-dev
1312024-12-05T09:56:11 *** sliv3r__ <sliv3r__!~sliv3r__@user/sliv3r-:76883> has quit IRC (Client Quit)
1322024-12-05T10:02:45 *** brad_ <brad_!~brad@200.68.141.10> has quit IRC (Ping timeout: 260 seconds)
1332024-12-05T10:05:39 *** Zenton <Zenton!~Zenton@user/zenton> has quit IRC (Remote host closed the connection)
1342024-12-05T10:05:58 *** Zenton <Zenton!~Zenton@user/zenton> has joined #bitcoin-core-dev
1352024-12-05T10:11:41 *** itsarjn <itsarjn!~itsarjn@user/itsarjn> has quit IRC (Remote host closed the connection)
1362024-12-05T10:12:22 *** itsarjn <itsarjn!~itsarjn@user/itsarjn> has joined #bitcoin-core-dev
1372024-12-05T10:18:42 *** Zenton_ <Zenton_!~Zenton@user/zenton> has joined #bitcoin-core-dev
1382024-12-05T10:21:09 *** Zenton <Zenton!~Zenton@user/zenton> has quit IRC (Ping timeout: 248 seconds)
1392024-12-05T10:37:10 *** Zenton_ <Zenton_!~Zenton@user/zenton> has quit IRC (Remote host closed the connection)
1402024-12-05T10:37:29 *** Zenton_ <Zenton_!~Zenton@user/zenton> has joined #bitcoin-core-dev
1412024-12-05T10:41:13 *** Zenton_ <Zenton_!~Zenton@user/zenton> has quit IRC (Read error: Connection reset by peer)
1422024-12-05T10:41:22 *** Zenton__ <Zenton__!~Zenton@user/zenton> has joined #bitcoin-core-dev
1432024-12-05T10:49:52 *** Flow <Flow!~none@gentoo/developer/flow> has joined #bitcoin-core-dev
1442024-12-05T10:59:10 *** Zenton__ <Zenton__!~Zenton@user/zenton> has quit IRC (Remote host closed the connection)
1452024-12-05T10:59:28 *** Zenton__ <Zenton__!~Zenton@user/zenton> has joined #bitcoin-core-dev
1462024-12-05T11:15:39 *** Zenton__ <Zenton__!~Zenton@user/zenton> has quit IRC (Remote host closed the connection)
1472024-12-05T11:15:59 *** Zenton__ <Zenton__!~Zenton@user/zenton> has joined #bitcoin-core-dev
1482024-12-05T11:27:16 <bitcoin-git> [bitcoin] willcl-ark opened pull request #31427: lint: bump MLC to v0.19.0 (master...bump-mlc) https://github.com/bitcoin/bitcoin/pull/31427
1492024-12-05T11:36:32 *** Zenton <Zenton!~Zenton@user/zenton> has joined #bitcoin-core-dev
1502024-12-05T11:37:13 *** Zenton__ <Zenton__!~Zenton@user/zenton> has quit IRC (Ping timeout: 246 seconds)
1512024-12-05T11:40:36 *** chinggg <chinggg!~chinggg@141.5.46.6> has joined #bitcoin-core-dev
1522024-12-05T11:45:11 *** kevkevin <kevkevin!~kevkevin@2601:243:197e:8f10:3581:7920:80d9:4fec> has joined #bitcoin-core-dev
1532024-12-05T11:49:54 *** kevkevin <kevkevin!~kevkevin@2601:243:197e:8f10:3581:7920:80d9:4fec> has quit IRC (Ping timeout: 260 seconds)
1542024-12-05T11:53:44 *** SpellChecker_ <SpellChecker_!~SpellChec@user/SpellChecker> has joined #bitcoin-core-dev
1552024-12-05T11:56:36 *** SpellChecker <SpellChecker!~SpellChec@user/SpellChecker> has quit IRC (Ping timeout: 264 seconds)
1562024-12-05T12:23:35 *** AlHqz <AlHqz!~AlHqz@190.57.84.236> has joined #bitcoin-core-dev
1572024-12-05T12:24:20 *** AlHqz <AlHqz!~AlHqz@190.57.84.236> has quit IRC (Client Quit)
1582024-12-05T12:28:39 *** Zenton <Zenton!~Zenton@user/zenton> has quit IRC (Remote host closed the connection)
1592024-12-05T12:28:59 *** Zenton <Zenton!~Zenton@user/zenton> has joined #bitcoin-core-dev
1602024-12-05T12:36:11 *** chinggg <chinggg!~chinggg@141.5.46.6> has quit IRC (Ping timeout: 240 seconds)
1612024-12-05T12:41:41 *** ioannis <ioannis!ion-@user/ion-> has quit IRC (Remote host closed the connection)
1622024-12-05T12:49:27 <bitcoin-git> [bitcoin] glozow pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/e8cc790fe2a2...083770adbe7d
1632024-12-05T12:49:28 <bitcoin-git> bitcoin/master 0f84cdd Greg Sanders: func: test orphan parent is re-requested from 2nd peer
1642024-12-05T12:49:28 <bitcoin-git> bitcoin/master 083770a glozow: Merge bitcoin/bitcoin#31414: test: orphan parent is re-requested from 2nd ...
1652024-12-05T12:49:32 <bitcoin-git> [bitcoin] glozow merged pull request #31414: test: orphan parent is re-requested from 2nd peer (master...2024-12-double-request-orphan-parent) https://github.com/bitcoin/bitcoin/pull/31414
1662024-12-05T12:51:07 *** sebastianvstaa <sebastianvstaa!~sebastian@dsl-212-100-46-253.pool.bitel.net> has quit IRC (Quit: Client closed)
1672024-12-05T13:00:51 *** Zenton_ <Zenton_!~Zenton@user/zenton> has joined #bitcoin-core-dev
1682024-12-05T13:03:29 *** Zenton <Zenton!~Zenton@user/zenton> has quit IRC (Ping timeout: 272 seconds)
1692024-12-05T13:07:27 *** kevkevin <kevkevin!~kevkevin@2601:243:197e:8f10:9e2:4262:46ee:c0d> has joined #bitcoin-core-dev
1702024-12-05T13:12:09 *** kevkevin <kevkevin!~kevkevin@2601:243:197e:8f10:9e2:4262:46ee:c0d> has quit IRC (Ping timeout: 260 seconds)
1712024-12-05T13:18:47 *** ioannis <ioannis!ion-@user/ion-> has joined #bitcoin-core-dev
1722024-12-05T13:23:22 *** ioannis <ioannis!ion-@user/ion-> has quit IRC (Ping timeout: 252 seconds)
1732024-12-05T13:24:05 *** emcy__ <emcy__!~emcy@148.252.129.219> has joined #bitcoin-core-dev
1742024-12-05T13:27:17 *** mcey_ <mcey_!~emcy@148.252.146.200> has quit IRC (Ping timeout: 248 seconds)
1752024-12-05T13:29:03 *** greypw14 <greypw14!~greypw@user/greypw> has quit IRC (Remote host closed the connection)
1762024-12-05T13:34:41 *** ioannis <ioannis!ion-@user/ion-> has joined #bitcoin-core-dev
1772024-12-05T13:43:01 *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has quit IRC (Quit: = "")
1782024-12-05T13:45:58 *** kevkevin <kevkevin!~kevkevin@2601:243:197e:8f10:80b1:579f:79ae:fda2> has joined #bitcoin-core-dev
1792024-12-05T13:50:09 *** kevkevin <kevkevin!~kevkevin@2601:243:197e:8f10:80b1:579f:79ae:fda2> has quit IRC (Ping timeout: 248 seconds)
1802024-12-05T13:52:15 *** ioannis <ioannis!ion-@user/ion-> has quit IRC (Ping timeout: 276 seconds)
1812024-12-05T13:56:27 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
1822024-12-05T13:57:52 *** Emc99 <Emc99!~Emc99@212.129.73.228> has joined #bitcoin-core-dev
1832024-12-05T13:59:00 *** nymius <nymius!~nymius@user/nymius> has joined #bitcoin-core-dev
1842024-12-05T13:59:10 *** Zenton_ <Zenton_!~Zenton@user/zenton> has quit IRC (Remote host closed the connection)
1852024-12-05T13:59:19 *** nymius <nymius!~nymius@user/nymius> has quit IRC (Client Quit)
1862024-12-05T13:59:37 *** Zenton_ <Zenton_!~Zenton@user/zenton> has joined #bitcoin-core-dev
1872024-12-05T13:59:44 *** nymius <nymius!~nymius@user/nymius> has joined #bitcoin-core-dev
1882024-12-05T14:00:24 <achow101> #startmeeting
1892024-12-05T14:00:28 <b10c> hi
1902024-12-05T14:00:30 <achow101> #bitcoin-core-dev Meeting: abubakarsadiq achow101 _aj_ ajonas b10c brunoerg cfields darosior dergoegge fanquake fjahr furszy gleb glozow hebasto instagibbs jarolrod jonatack josibake kanzure laanwj LarryRuane lightlike luke-jr maflcko maxedw Murch pinheadmz provoostenator ryanofsky sdaftuar S3RK stickies-v sipa sr_gi tdb3 theStack TheCharlatan vasild willcl-ark
1912024-12-05T14:00:31 <hodlinator> hi
1922024-12-05T14:00:33 <sipa> hi
1932024-12-05T14:00:39 <nymius> hi
1942024-12-05T14:00:40 <vasild> hi
1952024-12-05T14:00:40 <jonatack> hi
1962024-12-05T14:00:43 <tdb3> hi
1972024-12-05T14:00:44 <brunoerg> hi
1982024-12-05T14:00:45 <instagibbs> hi
1992024-12-05T14:00:58 *** sebastianvstaa <sebastianvstaa!~sebastian@212.100.46.253> has joined #bitcoin-core-dev
2002024-12-05T14:01:09 <achow101> There are no pre-proposed meeting topics this week. Any last minute ones to add?
2012024-12-05T14:01:10 *** Zenton_ <Zenton_!~Zenton@user/zenton> has quit IRC (Remote host closed the connection)
2022024-12-05T14:01:20 <jarolrod> Hi
2032024-12-05T14:01:26 <theStack> hi
2042024-12-05T14:01:32 <dergoegge> can we get marcofleon added to the meeting ping list?
2052024-12-05T14:01:34 *** Zenton_ <Zenton_!~Zenton@user/zenton> has joined #bitcoin-core-dev
2062024-12-05T14:01:36 <fjahr> hi
2072024-12-05T14:01:45 <marcofleon> hi
2082024-12-05T14:02:10 <hebasto> hi
2092024-12-05T14:02:14 <achow101> dergoegge: marcofleon: added
2102024-12-05T14:02:22 <marcofleon> thanks
2112024-12-05T14:02:23 <dergoegge> cheers
2122024-12-05T14:02:52 <achow101> For future reference, I just copy-paste from https://github.com/bitcoin-core/bitcoin-devwiki/wiki/IRC-Meeting-Cheat-Sheet which should be editable by everyone in the org
2132024-12-05T14:03:12 <dergoegge> ah i see, thanks
2142024-12-05T14:03:22 <achow101> #topic Erlay WG Update (sr_gi, gleb, marcofleon)
2152024-12-05T14:03:42 <gleb> Hi
2162024-12-05T14:03:48 <willcl-ark> hi
2172024-12-05T14:03:57 *** ioannis <ioannis!ion-@user/ion-> has joined #bitcoin-core-dev
2182024-12-05T14:04:20 <gleb> On erlay we currently have a list of design questions weâre discussing in the WG
2192024-12-05T14:05:06 <gleb> Im personally spending a bunch of time rebasing the full implementation
2202024-12-05T14:05:14 <gleb> Sergi is working on the simulations
2212024-12-05T14:05:20 <gleb> Thatâs it
2222024-12-05T14:05:27 <maxedw> hi
2232024-12-05T14:05:52 <achow101> #topic Fuzzing WG Update (dergoegge)
2242024-12-05T14:06:10 <glozow> hi. sorry iâm late
2252024-12-05T14:06:33 <dergoegge> no real update
2262024-12-05T14:06:33 <dergoegge> https://github.com/guidovranken/cryptofuzz/ was deleted 1 or 2 weeks ago and i'm not sure how we're gonna replace that wrt fuzzing secp
2272024-12-05T14:06:51 <instagibbs> oof
2282024-12-05T14:07:02 <achow101> why was it deleted?
2292024-12-05T14:07:26 <sipa> we had a student work on writing a libfuzzer-based harness for libsecp256k1 some time ago, which would be able to do more low-level things
2302024-12-05T14:07:33 <fanquake> the crypto fuzz maintainer nuked all his repos
2312024-12-05T14:07:34 <dergoegge> not entirely sure this is all we know: https://github.com/google/oss-fuzz/pull/12746
2322024-12-05T14:07:50 <sipa> it never progressed past being a prototype, but it'd be nice if someone picked it up
2332024-12-05T14:08:15 <dergoegge> sipa: cool! i think the cool thing about cryptofuzz was the differential oracle
2342024-12-05T14:08:25 <sipa> dergoegge: yeah, i'm aware
2352024-12-05T14:08:46 *** ioannis <ioannis!ion-@user/ion-> has quit IRC (Ping timeout: 252 seconds)
2362024-12-05T14:08:51 <dergoegge> we have a fork of cryptofuzz (latest commit afaik) but i would assume it's not trivial to maintain
2372024-12-05T14:08:52 <vasild> "In light of the EU Product Liability Directive and other speech criminalizations I am ceasing all my publications including FOSS contributions."
2382024-12-05T14:08:54 <furszy> hi
2392024-12-05T14:09:29 <achow101> yeesh
2402024-12-05T14:09:35 <fanquake> dergoegge: itâs missing my last upstream fix but otherwise up to date yea
2412024-12-05T14:09:43 <sipa> some portion of the kinds of things cryptofuzz could catch are also covered by wycheproof
2422024-12-05T14:09:54 <fjahr> dergoegge: does it make sense to put it under a core org?
2432024-12-05T14:10:16 <fanquake> not unless someone is planning to maintain it
2442024-12-05T14:10:17 <fjahr> at least until another, better maintained for emerges
2452024-12-05T14:10:49 <fjahr> for someone to start it needs to be available somewhere
2462024-12-05T14:11:34 <dergoegge> https://github.com/fanquake/cryptofuzz
2472024-12-05T14:11:46 <fjahr> that works
2482024-12-05T14:11:48 <cfields> hi
2492024-12-05T14:11:58 <dergoegge> fanquake: you're the maintainer now
2502024-12-05T14:12:19 <achow101> There appear to be other forks too:https://github.com/google/oss-fuzz/pull/12765#issuecomment-2520199032
2512024-12-05T14:12:26 <fanquake> If also suggest that if someone wants to re-add it to oss-fuzz, to bot re-add it to the bitcoin-core project, but keep it separate
2522024-12-05T14:13:02 <fanquake> As the majority of our build failures came from crypto-fuzz, but that isnât needed for core, so would just break out build
2532024-12-05T14:13:06 <brunoerg> the MozillaSecurity fork seems active
2542024-12-05T14:13:37 <fanquake> So keeping it separate means our fuzzers donât break when the secp cryptofuzz build does
2552024-12-05T14:14:16 *** abubakarsadiq <abubakarsadiq!uid602234@id-602234.hampstead.irccloud.com> has joined #bitcoin-core-dev
2562024-12-05T14:14:27 <achow101> it seems like the libsecp folks are looking into it
2572024-12-05T14:14:29 <achow101> let's move on
2582024-12-05T14:14:42 <achow101> #topic Cluster Mempool WG Update (sdaftuar, sipa)
2592024-12-05T14:14:51 <sipa> hi
2602024-12-05T14:15:13 <sipa> since last meeting i have opened #31363
2612024-12-05T14:15:14 <gribble`> https://github.com/bitcoin/bitcoin/issues/31363 | cluster mempool: introduce TxGraph by sipa · Pull Request #31363 · bitcoin/bitcoin · GitHub
2622024-12-05T14:15:44 <instagibbs> how much work remains to get a glimpse of end to end usage
2632024-12-05T14:16:25 <sipa> it implements (part of) the "medium level" layer: sort of a whole-mempool representation of the transaction graph, but very stripped down in functionality (it knows only fees, sizes, dependencies, and represents transactions as abstract handle "Ref" objects, no txids, no ctransaction, ...)
2642024-12-05T14:17:06 <sipa> it's tested by a single simulation fuzz test, which compares the behavior of it with a naive reimplementation (mostly) which treats the entire mempool as a single depgraph
2652024-12-05T14:17:31 <sipa> instagibbs: you mean in terms of what is left to do at the txgraph level, or what is left for cluster mempool as a whole?
2662024-12-05T14:17:37 <instagibbs> latter
2672024-12-05T14:18:40 <sipa> so i'm working on extending txgraph to be fully featured (i have some non-pr'ed stuff that is ready already) so it provides enough functionality (specifically, it needs mining/eviction, and a way to deal with reorgs that might otherwise violate policy limits)
2682024-12-05T14:19:04 <sipa> after that, i think sdaftuar is planning to rebase #28676 on txgraph
2692024-12-05T14:19:08 <gribble`> https://github.com/bitcoin/bitcoin/issues/28676 | [WIP] Cluster mempool implementation by sdaftuar · Pull Request #28676 · bitcoin/bitcoin · GitHub
2702024-12-05T14:19:54 *** ioannis <ioannis!ion-@user/ion-> has joined #bitcoin-core-dev
2712024-12-05T14:20:06 <sipa> then there are a few "optimizations" that we'll probably want soon, but aren't blockers for more progress on the mempool side (e.g. reducing memory usage for small clusters in txgraph, and a way to do background relinearization, ...)
2722024-12-05T14:20:13 <instagibbs> taking that as Two Weeks, thanks
2732024-12-05T14:20:20 <sipa> yeah, (tm)
2742024-12-05T14:20:39 <bitcoin-git> [bitcoin] maflcko opened pull request #31428: ci: Allow build dir on CI host (master...2412-ci-build) https://github.com/bitcoin/bitcoin/pull/31428
2752024-12-05T14:20:45 <sipa> in either case, 31363 is the thing to review now
2762024-12-05T14:21:06 <sipa> based on feedback, i'm happy to split off more parts, split off commits, ... whatever helps
2772024-12-05T14:22:24 <sipa> perhaps also an interesting update that won't affect things in the too near future: during bitcoin research week at chaincode, some researchers came up with an idea for how optimal cluster linearization may be doable in polynomial time
2782024-12-05T14:22:58 <glozow> sipa: do you think that algo would require a refactor? or could it just be an edit to cluster_linearize.h?
2792024-12-05T14:22:58 <sipa> depending on how things evolve there, the approach may end up being too slow to run inside our "relay-time" linearization logic, so it wouldn't really affect our guarantees or cluster size limit
2802024-12-05T14:23:08 <instagibbs> sipa interested to learn how th relaxation was shown to be optimal :)
2812024-12-05T14:23:23 <glozow> (assuming you want to incorporate it)
2822024-12-05T14:23:28 <sipa> but it may mean that a background relinearization can practically linearize everything optimally
2832024-12-05T14:23:35 <instagibbs> that's awesome
2842024-12-05T14:23:41 <sipa> glozow: it'd be pretty much a drop-in replacement for some code in cluster_linearize.h
2852024-12-05T14:23:51 <glozow> awesome! so it could be worked on in parallel
2862024-12-05T14:24:14 <sipa> instagibbs: i can give you a quick intuition, but let's do that after the meeting
2872024-12-05T14:24:18 <instagibbs> yeah offline
2882024-12-05T14:24:35 *** ioannis <ioannis!ion-@user/ion-> has quit IRC (Ping timeout: 252 seconds)
2892024-12-05T14:24:54 <sipa> that's it from me, unless sdaftuar still appears and has an update
2902024-12-05T14:24:54 *** ioannis <ioannis!ion-@user/ion-> has joined #bitcoin-core-dev
2912024-12-05T14:25:07 <achow101> #topic MuSig2 WG Update (achow101)
2922024-12-05T14:25:15 <achow101> No updates, waiting for further review of #31242 and #31243
2932024-12-05T14:25:16 <gribble`> https://github.com/bitcoin/bitcoin/issues/31242 | wallet, desc spkm: Return SigningProvider only if we have the privkey by achow101 · Pull Request #31242 · bitcoin/bitcoin · GitHub
2942024-12-05T14:25:18 <gribble`> https://github.com/bitcoin/bitcoin/issues/31243 | descriptor: Move filling of keys from `DescriptorImpl::MakeScripts` to `PubkeyProvider::GetPubKey` by achow101 · Pull Request #31243 · bitcoin/bitcoin · GitHub
2952024-12-05T14:25:32 <achow101> #topic Legacy Wallet Removal WG Update (achow101)
2962024-12-05T14:25:44 <achow101> furszy found a few additional edge cases in migration and opened #31374 and #31378 to handle those. These are the current PRs to review.
2972024-12-05T14:25:46 <gribble`> https://github.com/bitcoin/bitcoin/issues/31374 | wallet: fix crash during watch-only wallet migration by furszy · Pull Request #31374 · bitcoin/bitcoin · GitHub
2982024-12-05T14:25:48 <gribble`> https://github.com/bitcoin/bitcoin/issues/31378 | wallet: fix crash during migration due to invalid multisig descriptors by furszy · Pull Request #31378 · bitcoin/bitcoin · GitHub
2992024-12-05T14:25:55 <achow101> #30328 has also gotten some review but is now waiting on 31374 and 31378 as those add tests that we want for 30328
3002024-12-05T14:25:58 <gribble`> https://github.com/bitcoin/bitcoin/issues/30328 | wallet: Remove IsMine from migration code by achow101 · Pull Request #30328 · bitcoin/bitcoin · GitHub
3012024-12-05T14:26:26 <achow101> #topic package relay WG Update (glozow)
3022024-12-05T14:27:03 <glozow> I've put up the next PR for making orphan resolution more robust by trying with all candidate peers, #31397. It is getting some review (thanks!!). We have a meeting 2h from now in #bitcoin-core-pr-reviews. I'm also happy to do a video call walkthrough if enough people are interested? lmk.
3032024-12-05T14:27:04 <gribble`> https://github.com/bitcoin/bitcoin/issues/31397 | p2p: track and use all potential peers for orphan resolution by glozow · Pull Request #31397 · bitcoin/bitcoin · GitHub
3042024-12-05T14:27:37 <glozow> #28031 is rebased, and it includes the next step which would be to make `TxDownloadManager` internally thread-safe
3052024-12-05T14:27:41 <gribble`> https://github.com/bitcoin/bitcoin/issues/28031 | Package Relay 1/3: Introduce TxDownloadManager and improve orphan-handling by glozow · Pull Request #28031 · bitcoin/bitcoin · GitHub
3062024-12-05T14:28:00 <glozow> The step after that would be orphanage protection and more thinking around how we can limit per-peer usage of orphanage
3072024-12-05T14:28:17 <glozow> Separately, #31385 may be of interest to mempool folks and users. It relaxes the "all unconf parents must be present" requirement for package validation.
3082024-12-05T14:28:18 <gribble`> https://github.com/bitcoin/bitcoin/issues/31385 | package validation: relax the package-not-child-with-unconfirmed-parents rule by glozow · Pull Request #31385 · bitcoin/bitcoin · GitHub
3092024-12-05T14:28:19 <sipa> glozow: i'm interested, but i've been quite out of the loop w.r.t. orphan handling... is there a writeup/pr/... that would help to get up to speed?
3102024-12-05T14:29:21 *** ioannis <ioannis!ion-@user/ion-> has quit IRC (Ping timeout: 252 seconds)
3112024-12-05T14:29:22 <glozow> sipa: I think https://github.com/bitcoin-core/bitcoin-devwiki/wiki/%5BP2P%5D-known-TxOrphanage-problems is the most comprehensive explainer for the problems we are looking at solving
3122024-12-05T14:29:32 <sipa> cool will have a look
3132024-12-05T14:29:55 *** ioannis <ioannis!ion-@user/ion-> has joined #bitcoin-core-dev
3142024-12-05T14:30:36 <glozow> We have a (very old and quiet) group chat as a WG for this stuff so anybody feel free to lmk if you want to join.
3152024-12-05T14:31:49 <sipa> sure you can add me
3162024-12-05T14:32:14 <glozow> Great!
3172024-12-05T14:32:27 <glozow> That's it from me I think
3182024-12-05T14:32:44 <achow101> Any other topics to discuss?
3192024-12-05T14:34:09 *** ioannis <ioannis!ion-@user/ion-> has quit IRC (Ping timeout: 245 seconds)
3202024-12-05T14:34:37 <stevenroose> Does Core allow for changing the 100-block coinbase maturity in regtest? It is 100 blocks in regtest, right?
3212024-12-05T14:34:46 <achow101> #endmeeting
3222024-12-05T14:34:56 *** ioannis <ioannis!ion-@user/ion-> has joined #bitcoin-core-dev
3232024-12-05T14:35:09 <stevenroose> Tired of so many years having to scroll by hundreds of getblock logs of my wallets syncing empty blocks in tests ..
3242024-12-05T14:35:17 <stevenroose> Ah, sorry to interrupt the meeting (almost)
3252024-12-05T14:35:23 <achow101> stevenroose: it's hardcoded
3262024-12-05T14:35:46 <sipa> it'd need to be made a consensus parameter
3272024-12-05T14:35:55 <jonatack> stevenroose: grep for the COINBASE_MATURITY constant
3282024-12-05T14:36:04 <sipa> which is doable i guess, but i'm not sure i see a pressing need
3292024-12-05T14:36:53 <jonatack> test/functional/test_framework/blocktools.py:59:COINBASE_MATURITY = 100
3302024-12-05T14:37:35 <jonatack> oops sorry, functional tests, different topic
3312024-12-05T14:37:41 <instagibbs> sipa ok you can try explaining like I haven't thought about QPs/LPs in like 15 years
3322024-12-05T14:38:23 <sipa> instagibbs: yeah!
3332024-12-05T14:38:27 <instagibbs> my naive thought would result in an exact MILP, or eps-close LP, but obviously we care about optimal linearizations, so I'll let ya give it a try
3342024-12-05T14:38:41 *** darosior <darosior!~darosior@109.205.214.46> has joined #bitcoin-core-dev
3352024-12-05T14:38:48 <instagibbs> (and MILP would probably be stupid slow)
3362024-12-05T14:39:03 <_aj_> stevenroose: test_framework/test_framework.py has code to generate and cache a 199-block-long chain which makes things faster, though i guess you might still see getblock entries in your logs
3372024-12-05T14:39:16 *** ioannis <ioannis!ion-@user/ion-> has quit IRC (Ping timeout: 252 seconds)
3382024-12-05T14:39:24 <sipa> so we start with the problem of trying to find the highest-feerate topologically-valid subset (if you can do that repeatedly, you can linearize, just move the highest-feerate subset to the front; *if* an optimal linearization exists, this must find it)
3392024-12-05T14:39:55 *** ioannis <ioannis!ion-@user/ion-> has joined #bitcoin-core-dev
3402024-12-05T14:40:28 <sipa> which is: given a number n of transaction with fees (fee_1, fee_2, ..., fee_n) and sizes (size_1, size_2, ..., size_n), and dependencies: (par_1, chl_1), (par_2, chl_2), ...
3412024-12-05T14:41:22 <sipa> we're looking for boolean variables x_1, x_2, x_3, such that sum(fee_i * x_i) / sum(size_i * x_i) is maximized (and the denominator is nonzero; zero would mean empty set)
3422024-12-05T14:41:56 <sipa> and the constraint that for every (par_i, chl_i) pair, (x_{chl_i} => x_{par_i})
3432024-12-05T14:42:04 <sipa> sounds right?
3442024-12-05T14:42:09 *** Zenton_ <Zenton_!~Zenton@user/zenton> has quit IRC (Remote host closed the connection)
3452024-12-05T14:42:26 <_aj_> ("=>" -- implies, not greater-or-equal?)
3462024-12-05T14:42:34 *** Zenton_ <Zenton_!~Zenton@user/zenton> has joined #bitcoin-core-dev
3472024-12-05T14:42:43 <sipa> _aj_: yeah, just taking x_i to be booleans, so => is implication
3482024-12-05T14:42:48 <instagibbs> ah, ok yeah
3492024-12-05T14:42:52 <instagibbs> think im tracking
3502024-12-05T14:43:09 <sipa> but (x_{par_i} >= x_{chl_i}) would be equivalent if you think of booleans as {0, 1} integers
3512024-12-05T14:44:03 <sipa> and as you already know, the first step is relaxing the domain of the x_i variables to be real non-negative numbers instead
3522024-12-05T14:44:28 <instagibbs> mhmm
3532024-12-05T14:44:41 <stevenroose> _aj_: yeah wallets will still parse them all to sync.
3542024-12-05T14:44:46 <stevenroose> But thanks :)
3552024-12-05T14:45:07 <sipa> it's clear that multiplying all x_i's by the same constant won't change the solution, but it's perhaps less clear that allowed *distinct* real numbers for each of the x_i (not all exactly 1.0) won't introduce solutions to the problem that don'
3562024-12-05T14:45:11 *** Emc99 <Emc99!~Emc99@212.129.73.228> has quit IRC (Ping timeout: 240 seconds)
3572024-12-05T14:45:19 <sipa> 't actually correspond to solutions of the optimal subset problem
3582024-12-05T14:45:26 <sipa> i'll get back to that, ok?
3592024-12-05T14:45:26 <stevenroose> sipa: yeah wouldn't want to mess with consensus parameters for this case. though there's so many other ones, that was my main question of it was one or not. thanks
3602024-12-05T14:45:36 <_aj_> stevenroose: use one wallet for mining and a different one for testing, and compact block filters so the wallets only look at relevant blocks?
3612024-12-05T14:46:24 <stevenroose> I'm talking about other wallets like BDK. If they don't support birthdays (or the granularity of the birthday support is not block based but rough time based) it will still sync the entire regtest chain.
3622024-12-05T14:47:37 <sipa> instagibbs: with me so far?
3632024-12-05T14:47:42 <_aj_> stevenroose: backdate the blocks on regtest, mine a few at current time, and time based birthdays shoud be fine?
3642024-12-05T14:48:21 <instagibbs> sipa think so! one step of the optimization we already do, how do bool relaxed get optimal results, you will tell me
3652024-12-05T14:48:43 <sipa> ok, one more step before we arrive at the LP problem
3662024-12-05T14:48:46 <stevenroose> _aj_: interesting suggestions :)
3672024-12-05T14:49:07 <sipa> because scaling all x_i by the same constant doesn't change the solution, we can choose a normalization constraint that (arbitrarily) picks one scaling for them
3682024-12-05T14:49:34 <stevenroose> _aj_: we use bdk and afaik it doesn't support birthdays yet
3692024-12-05T14:49:49 <stevenroose> I can just settle to love with the noise for another few years.
3702024-12-05T14:50:04 <sipa> and the key insight is that the normalization constaint can be: set the denominator of the goal to 1 (sum(x_i * size_i) = 1), because it makes the goal function (the only part of the problem that's nonlinear) linear
3712024-12-05T14:51:03 <sipa> it could also be something else, as long as it's linear; e.g. (sum(x_i * size_i) = sum(size_i)) which can be simplified to sum((x_i - 1) * size_i) = 0, for example... doesn't matter; but we'll continue with sum(x_i * size_i) = 1
3722024-12-05T14:51:32 <sipa> alright?
3732024-12-05T14:52:29 <instagibbs> this step will take me a minute
3742024-12-05T14:52:39 <stevenroose> Also, achow101, is it normal that the wallet is pretty slow? https://nitter.poast.org/stevenroose3/status/1864675671143743942
3752024-12-05T14:53:11 <sipa> observe that multiplying all x_i by say 2 doesn't change (a) the validity of any constraint and (b) doesn't change the goal function (numerator and denominator both double)
3762024-12-05T14:53:13 <stevenroose> Colleague tells me it takes over 15 seconds on his machine to generate 100 blocks and I couldn't believe it. It took 5 secs on my beefy workstation as well.
3772024-12-05T14:54:21 <_aj_> stevenroose: bdk apparently supports compact block filters though https://bitcoindevkit.org/blog/compact-filters-demo/
3782024-12-05T14:55:19 <sipa> so if we for example just said sum(x_i) = 1, nothing really changes - among all solutions which only differ by an (identical) scaling of all x_i values, it just picks one of them
3792024-12-05T14:55:20 <instagibbs> ah wait, the original formulation isn't a LP(or QP or whatever) at all yet, so you're working on turning it into one?
3802024-12-05T14:55:25 <instagibbs> im backtracking sorry lol
3812024-12-05T14:55:27 <sipa> indeed
3822024-12-05T14:55:38 <instagibbs> ho ho ho ok re-reading a third time
3832024-12-05T14:55:52 <sipa> ð
3842024-12-05T14:56:03 <achow101> stevenroose: try having a smaller wallet
3852024-12-05T14:56:29 *** preimage <preimage!~halosghos@user/halosghost> has joined #bitcoin-core-dev
3862024-12-05T14:56:37 *** Zenton_ <Zenton_!~Zenton@user/zenton> has quit IRC (Remote host closed the connection)
3872024-12-05T14:57:06 *** Zenton_ <Zenton_!~Zenton@user/zenton> has joined #bitcoin-core-dev
3882024-12-05T14:57:51 <sipa> instagibbs: sorry, maybe i started too far back and should just have jumped to showing how the LP problem matches optimal sets
3892024-12-05T14:58:09 <sipa> but maybe there are other people reading along who don't yet know what the LP formulation is
3902024-12-05T14:58:39 <instagibbs> how do you set the denominator to a value without solving the LP, clearly missing something heh
3912024-12-05T14:59:00 <stevenroose> achow101: it's empty. they're regtests wallet on an empty chain. just that all of them spam all the rpc interactions for the 100+ (104 generally) block we have to generate to get some coin. I miss elements' initialfreecoin :D
3922024-12-05T14:59:10 <instagibbs> maybe the final LP will be illuminating yeah
3932024-12-05T14:59:11 *** Zenton__ <Zenton__!~Zenton@user/zenton> has joined #bitcoin-core-dev
3942024-12-05T14:59:14 <sipa> instagibbs: we literally just add a constraint to the problem: sum(size_i * x_i) = 1
3952024-12-05T14:59:41 <instagibbs> ok, so this by itself isn't turning it into an LP, you're just stating the constraint
3962024-12-05T14:59:42 <instagibbs> ?
3972024-12-05T14:59:43 <sipa> adding that constraint doesn't affect the solution space, because all it does is pick among every set of equivalent solutions, one canonical one
3982024-12-05T14:59:46 <sipa> indeed
3992024-12-05T14:59:56 <sipa> you agree with that?
4002024-12-05T14:59:58 <instagibbs> got it, I keep jumping ahead it seems yes
4012024-12-05T15:00:02 <sipa> ok!
4022024-12-05T15:00:13 <instagibbs> are we an LP yet are we an LP yet etc
4032024-12-05T15:00:29 <sipa> last step: we can replace the goal function from max sum(fee_i * x_i)/sum(size_i * x_i) to just max sum(fee_i * xi)
4042024-12-05T15:00:39 *** Zenton__ <Zenton__!~Zenton@user/zenton> has quit IRC (Remote host closed the connection)
4052024-12-05T15:00:46 <sipa> because we *know* the denominator is 1 (that's a constraint of the problem, which we leave in place)
4062024-12-05T15:00:55 <instagibbs> mmmmmm
4072024-12-05T15:01:25 <_aj_> (VCs are going to be so excited that bitcoin-core-dev is finally focussed on LPs)
4082024-12-05T15:01:41 *** Zenton_ <Zenton_!~Zenton@user/zenton> has quit IRC (Ping timeout: 248 seconds)
4092024-12-05T15:01:43 <sipa> haha
4102024-12-05T15:02:02 <sipa> like, clearly dividing by something we know equals 1 doesn't change the result
4112024-12-05T15:02:05 <instagibbs> I'm persuaded
4122024-12-05T15:02:06 *** Zenton <Zenton!~Zenton@user/zenton> has joined #bitcoin-core-dev
4132024-12-05T15:02:09 <instagibbs> yeah that's teh trick I was missing
4142024-12-05T15:02:20 <instagibbs> shove it in as a linear constraint
4152024-12-05T15:02:44 <bitcoin-git> [bitcoin] hebasto opened pull request #31429: cmake: Support user-defined C++ standard (master...241205-standard) https://github.com/bitcoin/bitcoin/pull/31429
4162024-12-05T15:02:46 <sipa> we did of course skip one part: showing that the relaxation to real numbers doesn't introduce *additional* solutions to the problem which are *more* optimal, but don't correspond to our real problem
4172024-12-05T15:03:40 *** Zenton <Zenton!~Zenton@user/zenton> has quit IRC (Remote host closed the connection)
4182024-12-05T15:04:05 *** Zenton <Zenton!~Zenton@user/zenton> has joined #bitcoin-core-dev
4192024-12-05T15:04:09 <instagibbs> ð
4202024-12-05T15:04:38 <sipa> to convince you that we didn't, i'm going to show you that *every* solution the LP problem (optimal and non-optimal) corresponds to a convex combination (a linear combination, where all coefficients are being 0 and 1, and which sum up to 1) of topologically-valid subsets... and thus that the goal function applies to them will also be a convex combination of those subset's feerates, which thus
4212024-12-05T15:04:44 <sipa> cannot possibly be more than the highest feerate of any of them
4222024-12-05T15:05:12 <sipa> when i say "convex combination" you can also think "weighted average"
4232024-12-05T15:05:29 <sipa> which can't be more than the maximum of any of the values being averaged
4242024-12-05T15:06:06 <sipa> ok
4252024-12-05T15:07:10 <sipa> let's say T_1, T_2, T_3, ..., T_m are the non-empty topologically valid subsets of our graph (in the real problem space, not the LP one)... there are clearly only a finite number of them as the graph is finite, but it could be exponential
4262024-12-05T15:08:44 <sipa> and call v_1, v_2, v_3, ..., v_m the corresponding LP solutions: v_k is the vector of (x_1, x_2, ..., x_n) where x_i=0 if i is not in T_i, and x_i=1/sum(size_j for j in T_k) if i is in T_i
4272024-12-05T15:09:14 <sipa> so that's just the vector of the boolean solutions, but rescaled so that sum(x_i * size_i)=1 holds
4282024-12-05T15:10:47 <sipa> so all the v_k are solutions to the LP problem... not necessarily the only ones, but just the ones that correspond to a single topologically-valid set
4292024-12-05T15:11:18 *** Guest48 <Guest48!~Guest48@outit03.fbk.eu> has joined #bitcoin-core-dev
4302024-12-05T15:11:52 <sipa> sorry this part is slightly technical and maybe not that easy to convey over text, but i promise it gets better
4312024-12-05T15:12:21 <_aj_> every valid solution to the LP problem would correspond with one of those v_k's in some sense -- they'd have all the same x_i=0 values, but some of the non-zero x_i's might have different values, no?
4322024-12-05T15:12:37 <instagibbs> to retread a bit, your contention is that any solution that has x_i as 0 implies exclusion, and any non-0 x_i inclusion?
4332024-12-05T15:12:47 <instagibbs> or am I jumping ahead again
4342024-12-05T15:12:50 <sipa> yeah :)
4352024-12-05T15:13:17 <sipa> look at the set of all possible LP solutions (optimal and non-optimal)
4362024-12-05T15:13:23 <instagibbs> ok, not convinced, but I can understand the words separately :P
4372024-12-05T15:13:37 <sipa> do you agree that the v_k vectors i've given you are all part of that set?
4382024-12-05T15:13:39 *** Guest48 <Guest48!~Guest48@outit03.fbk.eu> has quit IRC (Client Quit)
4392024-12-05T15:13:55 <sipa> so every v_k consists of 0s and all-identical nonzeros
4402024-12-05T15:14:07 <sipa> they cannot have distinct non-zero values
4412024-12-05T15:14:53 <instagibbs> I can stipulate because you're saying it's true haha, this part might need full writeup and me staring at it
4422024-12-05T15:15:28 <sipa> say you have a graph {A,B,C} and B depends on C, so our T's are: T_1={A}, T_2={C}, T_3={B,C}, T_4={A,C}, T_5={A,B,C}
4432024-12-05T15:15:31 <sipa> all the same size
4442024-12-05T15:15:39 *** Zenton <Zenton!~Zenton@user/zenton> has quit IRC (Remote host closed the connection)
4452024-12-05T15:16:04 *** Zenton <Zenton!~Zenton@user/zenton> has joined #bitcoin-core-dev
4462024-12-05T15:16:12 <sipa> then the v's are: v_1=(1,0,0), v_2=(0,0,1), v_3=(0,1/2,1/2), v_4=(1/2,0,1/2), v_5=(1/3,1/3,1/3)
4472024-12-05T15:16:50 <sipa> do you see that these are all solutions of the LP problem?
4482024-12-05T15:16:56 <instagibbs> C depends on B* I presume
4492024-12-05T15:17:01 <instagibbs> or no
4502024-12-05T15:17:07 <sipa> B depends on C
4512024-12-05T15:17:19 <sipa> i'm never including B without also include C, but C can appear on its own
4522024-12-05T15:17:58 <_aj_> instagibbs: (he defined them to have all-identitcal nonzeros, x_i=1/divisor; and that satisfies all the constraints. since he defined them that way, they "cannot" have different values...)
4532024-12-05T15:18:25 <sipa> all i'm asking is: do you agree these are solutions to the LP problem
4542024-12-05T15:18:33 <sipa> i'm not asking to see that the optimal one is among them
4552024-12-05T15:18:55 <sipa> nor am i asking to see that they're the only solutions to the LP problem (which wouldn't be true, but that's jumping ahead)
4562024-12-05T15:18:59 *** bugs_ <bugs_!~bugs@user/bugs/x-5128603> has joined #bitcoin-core-dev
4572024-12-05T15:19:11 <instagibbs> probably yeah
4582024-12-05T15:19:50 <sipa> B depends on C, so one of the constraints is x_3 >= x_2, which is true for all of them
4592024-12-05T15:19:51 <instagibbs> I can re-read the argument later to fully convince, continue
4602024-12-05T15:20:08 <sipa> and the normalized constraint holds because all sizes are one so it's just sum(x_i)=1
4612024-12-05T15:20:11 <sipa> etc
4622024-12-05T15:20:51 <sipa> ok, for each of these v_k solutions, the goal function g(v) = sum(fee_i*v_i) equals the feerate of the corresponding T_k
4632024-12-05T15:21:43 <sipa> i should write g(x) = sum(fee_i*x_i), sorry for variable switch
4642024-12-05T15:21:59 <sipa> and each v_k is one possible x
4652024-12-05T15:24:38 <sipa> or put otherwise: among all these v_k's (and excluding any other LP solutions, which might be even better) the optimal one is the one corresponding to the highest-feerate topologically-valid subset (in the real problem)
4662024-12-05T15:24:45 <instagibbs> huh ok
4672024-12-05T15:25:24 <sipa> like these v_k's are just the corresponding solutions to the boolean problem we started with, but rescaled so that the sum(x_i size_i) = 1 constraint holds
4682024-12-05T15:25:43 <sipa> and we know rescaling doesn't change feerate
4692024-12-05T15:25:50 <instagibbs> claim seems clear, thanks
4702024-12-05T15:25:59 <sipa> OKAY
4712024-12-05T15:26:22 <sipa> the next step is showing that *every* LP solution can be written as a weighted average of one or more of these v_k's
4722024-12-05T15:27:41 <sipa> because of linearity, if that is true, then the goal function sum(fee_i * x_i) in each LP solution is also a weighted average of the goal function of some of these v_k's, which cannot exceed the feerate of the highest topologically-valid subset of the graph
4732024-12-05T15:27:47 *** kevkevin <kevkevin!~kevkevin@c-73-111-168-5.hsd1.il.comcast.net> has joined #bitcoin-core-dev
4742024-12-05T15:28:24 <sipa> that's jumping ahead, i haven't shown that every LP is a weighted average of v_k's yet, but do you see that if that's the case, we are done?
4752024-12-05T15:30:01 <instagibbs> sure
4762024-12-05T15:30:12 <sipa> okay
4772024-12-05T15:30:40 <sipa> given a solution x to the LP problem (any solution, optimal or not), which is a vector with components (x_1, x_2, ..., x_n)
4782024-12-05T15:30:51 <sipa> find the smallest nonzero x_i
4792024-12-05T15:31:19 <sipa> call that alpha
4802024-12-05T15:32:19 <sipa> observe that the set of nonzero x_i's must be topological: if a child x_i is included, the parent x_j must be nonzero too
4812024-12-05T15:32:56 <sipa> so this set of nonzero x_i's must correspond to some T_k, which has a correspond v_k, which we can subtract from x
4822024-12-05T15:33:55 <sipa> sorry, alpha is the ratio between the smallest nonzero x_i and the nonzero values in v_k
4832024-12-05T15:34:52 <sipa> so x' = x - alpha*v_k is nonnegative still, and also still topological (parents are higher than children, we've subtractedf the same amount from all parents and children, so parents are still higher than children)
4842024-12-05T15:35:45 <sipa> so we can keep repeating this... find the set of nonzero values in x', find the corresponding v_k, subtract a multiple of v_k from it, and continue until the whole x is 0
4852024-12-05T15:36:04 <sipa> every time we've subtracted a non-negative multiple of a v_k
4862024-12-05T15:37:13 <_aj_> x' is no longer an LP solution because it violates the sum(x'_i*size_i) = 1 constraint?
4872024-12-05T15:37:20 <sipa> _aj_: correct!
4882024-12-05T15:37:38 <sipa> it's a solution to the LP problem if you ignore the normalization constraint, though
4892024-12-05T15:38:23 <_aj_> so eg if i had (2/5, 1/5, 2/5) then B is the smallest; non-zeroes correspond to (1/3,1/3,1/3) in v_5, scale and subtract gives me (1/5,0,1/5), which matches v_4
4902024-12-05T15:38:41 *** nymius <nymius!~nymius@user/nymius> has quit IRC (Quit: nymius)
4912024-12-05T15:38:49 <sipa> exactly
4922024-12-05T15:39:49 <sipa> and the first alpha would be 3/5, the second alpha would be 2/5
4932024-12-05T15:40:20 <sipa> which form the coefficients of the weighted average
4942024-12-05T15:40:52 <sipa> i guess i don't really have a super tight argument why the alphas sum up to 1, but they have to
4952024-12-05T15:42:11 <instagibbs> _aj_ thanks for the example, was helpful
4962024-12-05T15:43:04 *** ioannis <ioannis!ion-@user/ion-> has quit IRC (Ping timeout: 252 seconds)
4972024-12-05T15:43:31 <_aj_> sipa: consider the highest value initially (either of the 2/5), it's reduced in each step, until it's eventually zero; i think that forces it to end up at 1? i don't have my head around the alphas though
4982024-12-05T15:44:31 <vasild> (lldb) p ~((unsigned)0)
4992024-12-05T15:44:31 <vasild> (unsigned int) 4294967295
5002024-12-05T15:44:34 <sipa> _aj_: the highest value is not necessarily reduced in every step
5012024-12-05T15:44:52 <vasild> as expected, but what is this:
5022024-12-05T15:44:54 <vasild> (lldb) p ~((unsigned short)0)
5032024-12-05T15:44:55 <vasild> (int) -1
5042024-12-05T15:44:59 <_aj_> sipa: huh?
5052024-12-05T15:45:42 <sipa> vasild: integer promotion; any operand argument smaller than int gets converted to int
5062024-12-05T15:45:44 <vasild> Why not 65535?
5072024-12-05T15:45:57 <sipa> vasild: the most nonsensical feature in C and C++, probably
5082024-12-05T15:46:22 <sipa> _aj_: oh, wait, yes!
5092024-12-05T15:46:31 <vasild> probably this is the reason for https://api.cirrus-ci.com/v1/task/5685829642747904/logs/ci.log
5102024-12-05T15:46:34 <vasild> [01:27:57.782] /ci_container_base/src/util/bitset.h:369:34: runtime error: implicit conversion from type 'int' of value -1 (32-bit, signed) to type 'value_type' (aka 'unsigned short') changed the value to 65535 (16-bit, unsigned)
5112024-12-05T15:47:05 <vasild> unsigned short variable = ~I{0}; // where I is unsigned short
5122024-12-05T15:47:12 <sipa> vasild: https://en.cppreference.com/w/c/language/conversion:
5132024-12-05T15:47:13 <sipa> Integer promotion is the implicit conversion of a value of any integer type with rank less or equal to rank of int or of a bit-field of type _Bool(until C23)bool(since C23), int, signed int, unsigned int, to the value of type int or unsigned int.
5142024-12-05T15:47:18 <sipa> If int can represent the entire range of values of the original type (or the range of values of the original bit-field), the value is converted to type int. Otherwise the value is converted to unsigned int.
5152024-12-05T15:48:08 <vasild> sipa: do you mind if I change that ~I{0} in bitset.h to std::numeric_limits<I>::max()?
5162024-12-05T15:48:24 <instagibbs> ok, so it cannot *exceed*, but since it's a relaxation, it cannot *underperform*?
5172024-12-05T15:48:28 <sipa> vasild: i'd prefer I(~I{0})
5182024-12-05T15:49:04 <vasild> ok, will PR it shortly to fix the fuzz CI (not sure why it failed now or whether it failed before)
5192024-12-05T15:49:25 <_aj_> what's the "relaxation"?
5202024-12-05T15:49:25 <sipa> instagibbs: all we're trying to get to is that every LP solution x can be written as sum(alpha_k * v_k), where all alphas are non-negative, and sum up to 1
5212024-12-05T15:49:40 <_aj_> from bools to reals?
5222024-12-05T15:50:16 <sipa> and if that's the case, then every LP's solution's goal function cannot exceed the highest-feerate topological subset, because the goal function on the v_k's cannot exceed that
5232024-12-05T15:50:24 *** preimage <preimage!~halosghos@user/halosghost> has quit IRC (Quit: WeeChat 4.4.4)
5242024-12-05T15:50:50 <sipa> and thus, the relaxation of allowing non-negative real x_i instead of booleans doesn't introduce any solutions that are *even better* than the highest-feerate topologically-valid subset one
5252024-12-05T15:52:08 <instagibbs> I was zooming out a bit to restate that LP relaxations theoretically do not result in worse objective values
5262024-12-05T15:52:15 <instagibbs> sorry if too obvious...
5272024-12-05T15:52:18 <dergoegge> vasild: i ran into the same issue on an early draft of #31093 (https://github.com/bitcoin/bitcoin/pull/31093#issuecomment-2416333030)
5282024-12-05T15:52:18 <dergoegge> and i fixed it with "I(~I{0})"
5292024-12-05T15:52:18 <dergoegge> in my case it was triggered by replacing the Assumes with asserts, and my guess was it had something to do with compiler optimizations (which might also be the case for you with the additional std library flags...)
5302024-12-05T15:52:20 <gribble`> https://github.com/bitcoin/bitcoin/issues/31093 | Introduce `g_fuzzing` global for fuzzing checks by dergoegge · Pull Request #31093 · bitcoin/bitcoin · GitHub
5312024-12-05T15:52:35 <_aj_> (no such thing as too obvious)
5322024-12-05T15:52:41 <sipa> instagibbs: that's indeed what we're trying to get to
5332024-12-05T15:53:40 <vasild> dergoegge: sounds feasible, but then I could reproduce locally on master without extra hardening flags, probably clang 20 (which I use locally) makes a difference
5342024-12-05T15:53:42 <sipa> vasild: i would also be ok with a suppression, because this isn't UB
5352024-12-05T15:54:31 <_aj_> sipa: that's a nice argument, much more constructive than i was thinking/expecting ("if they're unequal, some value is higher, which if it's a child vs a parent is invalid; if it's a parent vs a child, should drop the child to zero, blahblahhandwave")
5362024-12-05T15:54:50 *** itsarjn <itsarjn!~itsarjn@user/itsarjn> has quit IRC (Remote host closed the connection)
5372024-12-05T15:55:00 *** lucasbalieiro <lucasbalieiro!~lucasbali@187.99.228.77> has joined #bitcoin-core-dev
5382024-12-05T15:55:18 <sipa> instagibbs, _aj_: maybe an argument for why the alphas sum up to one: if instead of just subtracting alpha*v_k, you rescale: x' = (x - alpha*v_k) / (1 - alpha), you get an actual LP solution after every step
5392024-12-05T15:55:44 <sipa> and then you need not sum of alphas, but sum of partial products of alphas is 1
5402024-12-05T15:55:48 <instagibbs> sipa having trouble framing my point better, but I've convinced myself that trivially a relaxation cannot do what I was thinking of, excluding numerical fun
5412024-12-05T15:56:09 <sipa> _aj_: yeah, that's basically dongning's argument
5422024-12-05T15:56:27 <sipa> i found mine more constructive, but they're probably equivalent in some sense
5432024-12-05T15:56:45 *** ioannis <ioannis!ion-@user/ion-> has joined #bitcoin-core-dev
5442024-12-05T15:58:23 <sipa> _aj_: but to be clear, it *is* possible that the optimal LP solution consists of unique x_i's; however, this will imply it's a weighted average between distinct solutions, each of which corresponds to an optimal feerate topologically-valid subset, so the overall set of nonzero element is still optimal and topological
5452024-12-05T15:58:54 <sipa> e.g. A=2/1, B=2/1, C=1/1, A and B both depend on C
5462024-12-05T15:59:46 <sipa> it's possible your solution is a weighted average between (1/2,0,1/2) and (0,1/2,1/2), both of which are optimal-feerate topologically-valid subsets
5472024-12-05T15:59:53 <sipa> uhhhh
5482024-12-05T16:00:00 <sipa> i just realized this examples disproves me
5492024-12-05T16:00:12 <sipa> oh, no!
5502024-12-05T16:00:30 <sipa> {A,B,C} is actually better than {A,C} and {B,C}, this is a bad example, sorry
5512024-12-05T16:00:37 *** sebastianvstaa <sebastianvstaa!~sebastian@212.100.46.253> has quit IRC (Quit: Client closed)
5522024-12-05T16:01:21 <sipa> say the super simple example: {A,B}, no dependencies, both have fee and size 1
5532024-12-05T16:01:27 <bitcoin-git> [bitcoin] vasild opened pull request #31431: util: use explicit cast in MultiIntBitSet::Fill() (master...fuzz_bitset_silence_warning) https://github.com/bitcoin/bitcoin/pull/31431
5542024-12-05T16:02:21 <sipa> the v_ks are all optimal: (1,0), (0,1), and (1/2,1/2)... but it *is* possible that the optimal LP solution is say (1/3,2/3), which is a non-equal weighted average between (1,0) and (0,1)
5552024-12-05T16:02:40 <sipa> but that's fine because the set of nonzero elements is {A,B}, which is still a solution
5562024-12-05T16:03:57 <_aj_> for (1/3, 2/3) i'd be tempted to follow your proof approach and take the last set (0,1/3) as the LP's recommendation to try to get something smaller. doesn't help if the LP recommends (1/2, 1/2) though.
5572024-12-05T16:04:53 <sipa> since we want *minimal-size* highest-feerate topologically-valid subsets, you probably want the set of all the highest values, rather than just the nonzero ones
5582024-12-05T16:05:19 <sipa> and even that isn't enough, because of the (1/2,1/2) example... which can be improved by doing connected-component analysis on the solution
5592024-12-05T16:05:49 <sipa> sadly, even that is not enough, because the two sets which were (by a remarkable coincidence) exactly equally mixed could be dependent on one another
5602024-12-05T16:06:18 <sipa> if you want to fix even that, you need to do trial removals "can i forcibly set this x_i to 0, and find an equally-good solution?" for every nonzero x_i
5612024-12-05T16:08:37 <_aj_> could do it for the non-parents (of nonzero x_i's) only and get a first pass answer
5622024-12-05T16:09:18 <_aj_> i feel like the other cluster mempooly techniques will probably already deal with that in most cases too
5632024-12-05T16:09:47 *** Zenton_ <Zenton_!~Zenton@user/zenton> has joined #bitcoin-core-dev
5642024-12-05T16:09:55 <_aj_> though in most cases you probably don't have exact equality anyway, so...
5652024-12-05T16:10:00 <sipa> yeah
5662024-12-05T16:10:16 <sipa> i wonder if postlinearization + chunking doesn't suffice
5672024-12-05T16:10:47 <_aj_> there's probably some edge case where it doesn't
5682024-12-05T16:10:52 <sipa> probably
5692024-12-05T16:11:18 <_aj_> does suhas or someone have some super complicated cluster examples to throw at an LP implementation?
5702024-12-05T16:11:29 *** Zenton <Zenton!~Zenton@user/zenton> has quit IRC (Ping timeout: 248 seconds)
5712024-12-05T16:11:47 <sipa> he's working on a fuzzer that tests things through an LP-solving library
5722024-12-05T16:18:29 <_aj_> (oh, the alphas sum to one via scaling thing i like. you can argue that each step is taking a weighted average between two valid solutions, so if your original was the best, it must equal both the things you're averaging at each step, afaics)
5732024-12-05T16:19:13 *** Zenton_ <Zenton_!~Zenton@user/zenton> has quit IRC (Read error: Connection reset by peer)
5742024-12-05T16:19:16 *** __DuBPiRaTe__ <__DuBPiRaTe__!~E_bomb@2600:6c50:7f7f:d89a:bc1a:df18:b7c7:a7b5> has joined #bitcoin-core-dev
5752024-12-05T16:19:21 *** lucasbalieiro <lucasbalieiro!~lucasbali@187.99.228.77> has quit IRC (Ping timeout: 252 seconds)
5762024-12-05T16:19:33 *** Zenton_ <Zenton_!~Zenton@user/zenton> has joined #bitcoin-core-dev
5772024-12-05T16:19:33 <sipa> yup
5782024-12-05T16:19:42 <sipa> that's a nice way of explaining it
5792024-12-05T16:19:46 <_aj_> (so your original combined solution is equally good as the final v_k you ended up with that has equal weighting for all the elements that had the highest x_i values)
5802024-12-05T16:24:09 *** Zenton_ <Zenton_!~Zenton@user/zenton> has quit IRC (Remote host closed the connection)
5812024-12-05T16:24:29 *** Zenton_ <Zenton_!~Zenton@user/zenton> has joined #bitcoin-core-dev
5822024-12-05T16:31:25 *** gribble` is now known as gribble
5832024-12-05T16:32:15 <sipa> huh, this makes it much easier: https://en.wikipedia.org/wiki/Linear-fractional_programming
5842024-12-05T16:32:47 <sipa> one can generally convert a LFP problem (like LP, but the goal is the ratio of two linear expressions) to an LP problem
5852024-12-05T16:33:27 <sipa> so i think we can instead just reason about solutions to the LFP formulation
5862024-12-05T16:34:13 <bitcoin-git> [bitcoin] fanquake pushed 3 commits to master: https://github.com/bitcoin/bitcoin/compare/083770adbe7d...6a1e613e853d
5872024-12-05T16:34:13 <bitcoin-git> bitcoin/master 811a65d willcl-ark: lint: bump MLC to v0.19.0
5882024-12-05T16:34:14 <bitcoin-git> bitcoin/master f6afca4 willcl-ark: lint: use clearer wording on error message
5892024-12-05T16:34:14 <bitcoin-git> bitcoin/master 6a1e613 merge-script: Merge bitcoin/bitcoin#31427: lint: bump MLC to v0.19.0
5902024-12-05T16:34:18 <bitcoin-git> [bitcoin] fanquake merged pull request #31427: lint: bump MLC to v0.19.0 (master...bump-mlc) https://github.com/bitcoin/bitcoin/pull/31427
5912024-12-05T16:41:42 *** sebastianvstaa <sebastianvstaa!~sebastian@212.100.46.253> has joined #bitcoin-core-dev
5922024-12-05T16:46:11 *** chinggg <chinggg!~chinggg@cspsrv00-ext.mpi-sp.org> has joined #bitcoin-core-dev
5932024-12-05T16:47:59 *** zeropoint <zeropoint!~alex@45-28-139-114.lightspeed.sntcca.sbcglobal.net> has joined #bitcoin-core-dev
5942024-12-05T16:48:47 *** itsarjn <itsarjn!~itsarjn@user/itsarjn> has joined #bitcoin-core-dev
5952024-12-05T16:48:57 <sipa> because then you don't need the alphas to add up to 1
5962024-12-05T16:57:14 *** Zenton__ <Zenton__!~Zenton@user/zenton> has joined #bitcoin-core-dev
5972024-12-05T16:57:45 *** preimage <preimage!~halosghos@user/halosghost> has joined #bitcoin-core-dev
5982024-12-05T16:59:12 *** Zenton_ <Zenton_!~Zenton@user/zenton> has quit IRC (Ping timeout: 246 seconds)
5992024-12-05T16:59:19 *** Emc99 <Emc99!~Emc99@212.129.73.228> has joined #bitcoin-core-dev
6002024-12-05T17:01:22 *** monlovesmango <monlovesmango!monlovesma@gateway/vpn/protonvpn/monlovesmango> has joined #bitcoin-core-dev
6012024-12-05T17:11:26 *** eval-exec <eval-exec!~Thunderbi@107.182.187.217.16clouds.com> has quit IRC (Ping timeout: 252 seconds)
6022024-12-05T17:17:47 <bitcoin-git> [bitcoin] fanquake pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/6a1e613e853d...6d973f86f755
6032024-12-05T17:17:48 <bitcoin-git> bitcoin/master cccca8a MarcoFalke: test: Avoid logging error when logging error
6042024-12-05T17:17:48 <bitcoin-git> bitcoin/master 6d973f8 merge-script: Merge bitcoin/bitcoin#31408: test: Avoid logging error when logging error
6052024-12-05T17:17:50 <bitcoin-git> [bitcoin] fanquake merged pull request #31408: test: Avoid logging error when logging error (master...2412-test-log-err) https://github.com/bitcoin/bitcoin/pull/31408
6062024-12-05T17:20:33 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Read error: Connection reset by peer)
6072024-12-05T17:21:47 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
6082024-12-05T17:31:33 *** chinggg <chinggg!~chinggg@cspsrv00-ext.mpi-sp.org> has quit IRC (Quit: Client closed)
6092024-12-05T17:31:46 *** chinggg <chinggg!~chinggg@cspsrv00-ext.mpi-sp.org> has joined #bitcoin-core-dev
6102024-12-05T17:35:14 *** ioannis <ioannis!ion-@user/ion-> has quit IRC (Ping timeout: 260 seconds)
6112024-12-05T17:36:36 *** Zenton <Zenton!~Zenton@user/zenton> has joined #bitcoin-core-dev
6122024-12-05T17:38:25 *** Zenton__ <Zenton__!~Zenton@user/zenton> has quit IRC (Ping timeout: 248 seconds)
6132024-12-05T17:49:19 *** ioannis <ioannis!ion-@user/ion-> has joined #bitcoin-core-dev
6142024-12-05T17:53:17 *** abubakarsadiq <abubakarsadiq!uid602234@id-602234.hampstead.irccloud.com> has quit IRC (Quit: Connection closed for inactivity)
6152024-12-05T18:01:03 *** Emc99 <Emc99!~Emc99@212.129.73.228> has quit IRC (Quit: Client closed)
6162024-12-05T18:02:04 *** monlovesmango <monlovesmango!monlovesma@gateway/vpn/protonvpn/monlovesmango> has quit IRC ()
6172024-12-05T18:05:23 *** ioannis <ioannis!ion-@user/ion-> has quit IRC (Remote host closed the connection)
6182024-12-05T18:07:59 *** Talkless <Talkless!~Talkless@mail.dargis.net> has joined #bitcoin-core-dev
6192024-12-05T18:22:37 *** ioannis <ioannis!ion-@user/ion-> has joined #bitcoin-core-dev
6202024-12-05T18:25:53 *** Zenton <Zenton!~Zenton@user/zenton> has quit IRC (Read error: Connection reset by peer)
6212024-12-05T18:26:15 *** Zenton <Zenton!~Zenton@user/zenton> has joined #bitcoin-core-dev
6222024-12-05T18:27:09 *** ioannis <ioannis!ion-@user/ion-> has quit IRC (Ping timeout: 260 seconds)
6232024-12-05T18:38:16 *** Guest89 <Guest89!~Guest89@2a0a:ef40:db:2e01:794b:c586:7f44:b19d> has joined #bitcoin-core-dev
6242024-12-05T18:38:32 *** Guest89 <Guest89!~Guest89@2a0a:ef40:db:2e01:794b:c586:7f44:b19d> has quit IRC (Client Quit)
6252024-12-05T18:55:09 *** Zenton <Zenton!~Zenton@user/zenton> has quit IRC (Remote host closed the connection)
6262024-12-05T18:55:29 *** Zenton <Zenton!~Zenton@user/zenton> has joined #bitcoin-core-dev
6272024-12-05T18:55:52 *** dviola <dviola!~diego@user/dviola> has joined #bitcoin-core-dev
6282024-12-05T19:04:40 *** Zenton <Zenton!~Zenton@user/zenton> has quit IRC (Read error: Connection reset by peer)
6292024-12-05T19:04:59 *** Zenton <Zenton!~Zenton@user/zenton> has joined #bitcoin-core-dev
6302024-12-05T19:09:24 *** Zenton_ <Zenton_!~Zenton@user/zenton> has joined #bitcoin-core-dev
6312024-12-05T19:10:32 *** ioannis <ioannis!ion-@user/ion-> has joined #bitcoin-core-dev
6322024-12-05T19:11:13 *** Zenton <Zenton!~Zenton@user/zenton> has quit IRC (Ping timeout: 248 seconds)
6332024-12-05T19:16:43 *** ioannis <ioannis!ion-@user/ion-> has quit IRC (Remote host closed the connection)
6342024-12-05T19:20:41 *** chinggg <chinggg!~chinggg@cspsrv00-ext.mpi-sp.org> has quit IRC (Ping timeout: 240 seconds)
6352024-12-05T19:33:28 *** ioannis <ioannis!ion-@user/ion-> has joined #bitcoin-core-dev
6362024-12-05T19:38:06 *** ioannis <ioannis!ion-@user/ion-> has quit IRC (Ping timeout: 252 seconds)
6372024-12-05T19:44:57 *** ioannis <ioannis!ion-@user/ion-> has joined #bitcoin-core-dev
6382024-12-05T19:49:07 *** darosior <darosior!~darosior@109.205.214.46> has quit IRC (Ping timeout: 252 seconds)
6392024-12-05T19:50:46 *** darosior <darosior!~darosior@109.205.214.46> has joined #bitcoin-core-dev
6402024-12-05T19:54:18 *** ioannis <ioannis!ion-@user/ion-> has quit IRC (Remote host closed the connection)
6412024-12-05T20:05:38 *** Zenton_ <Zenton_!~Zenton@user/zenton> has quit IRC (Remote host closed the connection)
6422024-12-05T20:06:03 *** Zenton_ <Zenton_!~Zenton@user/zenton> has joined #bitcoin-core-dev
6432024-12-05T20:09:55 *** ioannis <ioannis!ion-@user/ion-> has joined #bitcoin-core-dev
6442024-12-05T20:15:06 *** ioannis <ioannis!ion-@user/ion-> has quit IRC (Ping timeout: 276 seconds)
6452024-12-05T20:22:20 *** ioannis <ioannis!ion-@user/ion-> has joined #bitcoin-core-dev
6462024-12-05T20:25:01 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 252 seconds)
6472024-12-05T20:26:59 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
6482024-12-05T20:28:35 *** ioannis <ioannis!ion-@user/ion-> has quit IRC (Remote host closed the connection)
6492024-12-05T20:31:25 *** itsarjn <itsarjn!~itsarjn@user/itsarjn> has quit IRC (Remote host closed the connection)
6502024-12-05T20:33:52 *** Talkless <Talkless!~Talkless@mail.dargis.net> has quit IRC (Remote host closed the connection)
6512024-12-05T20:45:03 *** ioannis <ioannis!ion-@user/ion-> has joined #bitcoin-core-dev
6522024-12-05T20:47:52 <bitcoin-git> [bitcoin] ryanofsky pushed 3 commits to master: https://github.com/bitcoin/bitcoin/compare/6d973f86f755...2eccb8bc5e22
6532024-12-05T20:47:52 <bitcoin-git> bitcoin/master f42ec0f Ava Chow: wallet: Check specified wallet exists before migration
6542024-12-05T20:47:53 <bitcoin-git> bitcoin/master 55347a5 Ava Chow: test: Rework migratewallet to use previous release (v28.0)
6552024-12-05T20:47:53 <bitcoin-git> bitcoin/master 2eccb8b Ryan Ofsky: Merge bitcoin/bitcoin#31248: test: Rework wallet_migration.py to use previ...
6562024-12-05T20:48:00 <bitcoin-git> [bitcoin] ryanofsky merged pull request #31248: test: Rework wallet_migration.py to use previous releases (master...migratewallet-prev-rels) https://github.com/bitcoin/bitcoin/pull/31248
6572024-12-05T20:49:35 *** ioannis <ioannis!ion-@user/ion-> has quit IRC (Ping timeout: 252 seconds)
6582024-12-05T20:51:22 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 252 seconds)
6592024-12-05T20:52:31 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
6602024-12-05T21:09:21 <achow101> 28.1rc1 bins posted
6612024-12-05T21:11:11 *** sebastianvstaa <sebastianvstaa!~sebastian@212.100.46.253> has quit IRC (Ping timeout: 240 seconds)
6622024-12-05T21:13:29 <dviola> the qt 5.x issue that I mentioned sometime back has been fixed by this commit apparently: https://invent.kde.org/qt/qt/qtbase/-/commit/2529f7f0c2333d437089c775c9c30f624d1fd5bc
6632024-12-05T21:14:02 <dviola> the one where fonts were getting vanished after turning my monitor off/on
6642024-12-05T21:27:40 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Read error: Connection reset by peer)
6652024-12-05T21:28:07 *** kevkevin <kevkevin!~kevkevin@c-73-111-168-5.hsd1.il.comcast.net> has quit IRC (Remote host closed the connection)
6662024-12-05T21:29:35 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
6672024-12-05T21:53:52 *** ioannis <ioannis!ion-@user/ion-> has joined #bitcoin-core-dev
6682024-12-05T21:58:30 *** ioannis <ioannis!ion-@user/ion-> has quit IRC (Ping timeout: 265 seconds)
6692024-12-05T22:32:21 *** preimage <preimage!~halosghos@user/halosghost> has quit IRC (Quit: WeeChat 4.4.4)
6702024-12-05T22:37:03 *** tinova4 <tinova4!~tinova@217.160.209.135> has quit IRC (Quit: Ping timeout (120 seconds))
6712024-12-05T22:37:20 *** tinova4 <tinova4!~tinova@217.160.209.135> has joined #bitcoin-core-dev
6722024-12-05T22:44:01 *** szkl <szkl!uid110435@id-110435.uxbridge.irccloud.com> has quit IRC (Quit: Connection closed for inactivity)
6732024-12-05T23:03:03 *** bugs_ <bugs_!~bugs@user/bugs/x-5128603> has quit IRC (Quit: Leaving)
6742024-12-05T23:04:25 *** ioannis <ioannis!ion-@user/ion-> has joined #bitcoin-core-dev
6752024-12-05T23:08:36 <bitcoin-git> [bitcoin] hodlinator opened pull request #31433: test: #31212 follow up (spelling, refactor) (master...2024/12/31212_follow_up) https://github.com/bitcoin/bitcoin/pull/31433
6762024-12-05T23:09:17 *** ioannis <ioannis!ion-@user/ion-> has quit IRC (Ping timeout: 255 seconds)
6772024-12-05T23:17:55 *** kevkevin <kevkevin!~kevkevin@2601:243:197e:8f10:9082:cc39:1f3a:b549> has joined #bitcoin-core-dev
6782024-12-05T23:26:51 *** kevkevin <kevkevin!~kevkevin@2601:243:197e:8f10:9082:cc39:1f3a:b549> has quit IRC (Ping timeout: 276 seconds)
6792024-12-05T23:54:55 *** twistedline <twistedline!~bitcoin@185.193.125.44> has quit IRC ()
6802024-12-05T23:59:28 *** twistedline <twistedline!~bitcoin@185.193.125.44> has joined #bitcoin-core-dev