12026-02-12T00:08:13 *** midnight_ is now known as midnight
22026-02-12T00:10:57 *** w0xlt <w0xlt!~w0xlt@103.251.26.187> has joined #bitcoin-core-dev
32026-02-12T00:25:06 *** tarotfied <tarotfied!~tarotfied@user/tarotfied> has joined #bitcoin-core-dev
42026-02-12T00:27:06 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has quit IRC (Read error: Connection reset by peer)
52026-02-12T00:27:19 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has joined #bitcoin-core-dev
62026-02-12T00:28:36 *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has joined #bitcoin-core-dev
72026-02-12T00:57:11 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has quit IRC (Read error: Connection reset by peer)
82026-02-12T00:57:26 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has joined #bitcoin-core-dev
92026-02-12T01:29:01 *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has quit IRC (Ping timeout: 252 seconds)
102026-02-12T01:32:00 *** dzxzg2 <dzxzg2!~dzxzg@user/dzxzg> has quit IRC (Remote host closed the connection)
112026-02-12T01:53:05 *** Cory30 <Cory30!~Cory30@user/pasha> has quit IRC (Quit: Client closed)
122026-02-12T01:53:20 *** Cory30 <Cory30!~Cory30@user/pasha> has joined #bitcoin-core-dev
132026-02-12T01:57:05 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has quit IRC (Read error: Connection reset by peer)
142026-02-12T01:59:43 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has joined #bitcoin-core-dev
152026-02-12T02:11:25 *** luke-jr <luke-jr!~luke-jr@user/luke-jr> has quit IRC (Read error: Connection reset by peer)
162026-02-12T02:11:59 *** luke-jr <luke-jr!~luke-jr@user/luke-jr> has joined #bitcoin-core-dev
172026-02-12T02:13:47 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has quit IRC (Quit: l0rinc)
182026-02-12T02:16:05 *** kevkevin_ <kevkevin_!~kevkevin@209.242.60.195> has quit IRC (Remote host closed the connection)
192026-02-12T02:22:46 <bitcoin-git> [bitcoin] ryanofsky pushed 4 commits to master: https://github.com/bitcoin/bitcoin/compare/55c49ff8f4b1...0b4cd08fcd22
202026-02-12T02:22:47 <bitcoin-git> bitcoin/master 418b799 Sjors Provoost: test: have mining template helpers return None
212026-02-12T02:22:47 <bitcoin-git> bitcoin/master d3e4952 Sjors Provoost: mining: fix -blockreservedweight shadows IPC option
222026-02-12T02:22:47 <bitcoin-git> bitcoin/master b623fab Sjors Provoost: mining: enforce minimum reserved weight for IPC
232026-02-12T02:22:50 <bitcoin-git> [bitcoin] ryanofsky merged pull request #33965: mining: fix -blockreservedweight shadows IPC option (master...2025/11/ipc-reserve) https://github.com/bitcoin/bitcoin/pull/33965
242026-02-12T02:32:45 *** kevkevin <kevkevin!~kevkevin@209.242.60.195> has joined #bitcoin-core-dev
252026-02-12T02:37:49 *** kevkevin <kevkevin!~kevkevin@209.242.60.195> has quit IRC (Ping timeout: 264 seconds)
262026-02-12T02:49:49 *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has joined #bitcoin-core-dev
272026-02-12T02:52:51 *** kevkevin <kevkevin!~kevkevin@209.242.60.195> has joined #bitcoin-core-dev
282026-02-12T03:00:34 *** adil <adil!~Thunderbi@2402:4000:b142:8d92:1912:fc74:769c:a72c> has joined #bitcoin-core-dev
292026-02-12T03:10:08 *** adil <adil!~Thunderbi@2402:4000:b142:8d92:1912:fc74:769c:a72c> has quit IRC (Quit: adil)
302026-02-12T03:21:47 *** robszarka <robszarka!~szarka@2603:3003:4eac:100:7d09:f20d:f463:cb9f> has quit IRC (Quit: Leaving)
312026-02-12T03:27:13 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has quit IRC (Read error: Connection reset by peer)
322026-02-12T03:29:40 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has joined #bitcoin-core-dev
332026-02-12T03:53:23 *** kevkevin <kevkevin!~kevkevin@209.242.60.195> has quit IRC (Ping timeout: 252 seconds)
342026-02-12T03:53:58 *** memset <memset!~memset@gateway/tor-sasl/memset> has quit IRC (Remote host closed the connection)
352026-02-12T03:54:19 *** memset <memset!~memset@gateway/tor-sasl/memset> has joined #bitcoin-core-dev
362026-02-12T04:00:16 *** memset <memset!~memset@gateway/tor-sasl/memset> has quit IRC (Remote host closed the connection)
372026-02-12T04:00:34 *** memset <memset!~memset@gateway/tor-sasl/memset> has joined #bitcoin-core-dev
382026-02-12T04:05:34 *** kevkevin <kevkevin!~kevkevin@209.242.60.195> has joined #bitcoin-core-dev
392026-02-12T04:10:27 *** szarka <szarka!~szarka@2603:3003:4eac:100:dd8f:e484:7450:c23> has joined #bitcoin-core-dev
402026-02-12T04:10:30 <bitcoin-git> [bitcoin] ryanofsky opened pull request #34568: mining: Break compatibility with existing IPC mining clients (master...pr/mbreak) https://github.com/bitcoin/bitcoin/pull/34568
412026-02-12T04:16:31 *** svanstaa <svanstaa!~quassel@149.50.42.105> has quit IRC (Ping timeout: 264 seconds)
422026-02-12T04:16:33 *** svanstaa_ <svanstaa_!~quassel@149.50.46.195> has joined #bitcoin-core-dev
432026-02-12T04:17:01 *** memset <memset!~memset@gateway/tor-sasl/memset> has quit IRC (Remote host closed the connection)
442026-02-12T04:17:17 *** memset <memset!~memset@gateway/tor-sasl/memset> has joined #bitcoin-core-dev
452026-02-12T04:29:47 *** kevkevin <kevkevin!~kevkevin@209.242.60.195> has quit IRC (Remote host closed the connection)
462026-02-12T04:30:19 *** kevkevin <kevkevin!~kevkevin@209.242.60.195> has joined #bitcoin-core-dev
472026-02-12T04:57:06 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has quit IRC (Read error: Connection reset by peer)
482026-02-12T04:59:37 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has joined #bitcoin-core-dev
492026-02-12T04:59:47 *** kevkevin <kevkevin!~kevkevin@209.242.60.195> has quit IRC (Remote host closed the connection)
502026-02-12T05:00:19 *** kevkevin <kevkevin!~kevkevin@209.242.60.195> has joined #bitcoin-core-dev
512026-02-12T05:01:01 *** cmirror <cmirror!~cmirror@4.53.92.114> has quit IRC (Remote host closed the connection)
522026-02-12T05:01:32 *** cmirror <cmirror!~cmirror@4.53.92.114> has joined #bitcoin-core-dev
532026-02-12T05:08:44 *** kevkevin <kevkevin!~kevkevin@209.242.60.195> has quit IRC (Ping timeout: 252 seconds)
542026-02-12T05:22:29 *** kevkevin <kevkevin!~kevkevin@209.242.60.195> has joined #bitcoin-core-dev
552026-02-12T05:29:47 *** kevkevin <kevkevin!~kevkevin@209.242.60.195> has quit IRC (Remote host closed the connection)
562026-02-12T05:30:19 *** kevkevin <kevkevin!~kevkevin@209.242.60.195> has joined #bitcoin-core-dev
572026-02-12T05:44:25 *** adil <adil!~Thunderbi@2402:4000:b142:8d92:45e4:f3ba:7c4a:ddbb> has joined #bitcoin-core-dev
582026-02-12T05:44:27 *** adil <adil!~Thunderbi@2402:4000:b142:8d92:45e4:f3ba:7c4a:ddbb> has quit IRC (Client Quit)
592026-02-12T05:59:47 *** kevkevin <kevkevin!~kevkevin@209.242.60.195> has quit IRC (Remote host closed the connection)
602026-02-12T06:00:19 *** kevkevin <kevkevin!~kevkevin@209.242.60.195> has joined #bitcoin-core-dev
612026-02-12T06:16:06 *** drenalizea <drenalizea!uid740952@id-740952.hampstead.irccloud.com> has joined #bitcoin-core-dev
622026-02-12T06:24:29 *** kevkevin <kevkevin!~kevkevin@209.242.60.195> has quit IRC (Ping timeout: 245 seconds)
632026-02-12T06:38:34 *** kevkevin <kevkevin!~kevkevin@209.242.60.195> has joined #bitcoin-core-dev
642026-02-12T06:42:28 *** luke-jr <luke-jr!~luke-jr@user/luke-jr> has quit IRC (Read error: Connection reset by peer)
652026-02-12T06:43:29 *** luke-jr <luke-jr!~luke-jr@user/luke-jr> has joined #bitcoin-core-dev
662026-02-12T06:57:09 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has quit IRC (Read error: Connection reset by peer)
672026-02-12T06:59:46 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has joined #bitcoin-core-dev
682026-02-12T06:59:47 *** kevkevin <kevkevin!~kevkevin@209.242.60.195> has quit IRC (Remote host closed the connection)
692026-02-12T07:00:20 *** kevkevin <kevkevin!~kevkevin@209.242.60.195> has joined #bitcoin-core-dev
702026-02-12T07:03:25 *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has quit IRC (Ping timeout: 252 seconds)
712026-02-12T07:07:00 *** Cory30 <Cory30!~Cory30@user/pasha> has quit IRC (Quit: Client closed)
722026-02-12T07:07:18 *** Cory30 <Cory30!~Cory30@user/pasha> has joined #bitcoin-core-dev
732026-02-12T07:14:37 *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has joined #bitcoin-core-dev
742026-02-12T07:20:15 *** Cory30 <Cory30!~Cory30@user/pasha> has quit IRC (Quit: Client closed)
752026-02-12T07:29:47 *** kevkevin <kevkevin!~kevkevin@209.242.60.195> has quit IRC (Remote host closed the connection)
762026-02-12T07:30:19 *** kevkevin <kevkevin!~kevkevin@209.242.60.195> has joined #bitcoin-core-dev
772026-02-12T08:04:19 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has joined #bitcoin-core-dev
782026-02-12T08:10:10 *** memset <memset!~memset@gateway/tor-sasl/memset> has quit IRC (Remote host closed the connection)
792026-02-12T08:10:34 *** memset <memset!~memset@gateway/tor-sasl/memset> has joined #bitcoin-core-dev
802026-02-12T08:11:36 *** adil <adil!~Thunderbi@2402:4000:b142:8d92:4c8:1c42:b91d:c91a> has joined #bitcoin-core-dev
812026-02-12T08:24:11 *** neonrooks <neonrooks!~neonrooks@2600:1700:9f50:b4e0:9065:196d:94c9:94b5> has joined #bitcoin-core-dev
822026-02-12T08:27:18 *** Guyver2 <Guyver2!~Guyver@77.174.98.73> has joined #bitcoin-core-dev
832026-02-12T08:30:36 *** Guyver2 <Guyver2!~Guyver@77.174.98.73> has left #bitcoin-core-dev
842026-02-12T08:33:53 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has quit IRC (Quit: l0rinc)
852026-02-12T08:37:06 *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has quit IRC (Remote host closed the connection)
862026-02-12T08:37:06 *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has quit IRC (Read error: Connection reset by peer)
872026-02-12T08:37:06 *** memset <memset!~memset@gateway/tor-sasl/memset> has quit IRC (Read error: Connection reset by peer)
882026-02-12T08:37:37 *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has joined #bitcoin-core-dev
892026-02-12T08:37:48 *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has joined #bitcoin-core-dev
902026-02-12T08:39:53 *** durandal__ <durandal__!~durandal@94.196.72.217.threembb.co.uk> has quit IRC (Remote host closed the connection)
912026-02-12T08:40:16 *** durandal__ <durandal__!~durandal@94.196.72.217.threembb.co.uk> has joined #bitcoin-core-dev
922026-02-12T08:47:32 *** memset <memset!~memset@gateway/tor-sasl/memset> has joined #bitcoin-core-dev
932026-02-12T08:53:32 *** durandal_ <durandal_!~durandal@92.41.57.161.threembb.co.uk> has joined #bitcoin-core-dev
942026-02-12T08:53:53 *** durandal_ <durandal_!~durandal@92.41.57.161.threembb.co.uk> has quit IRC (Remote host closed the connection)
952026-02-12T08:54:15 *** durandal_ <durandal_!~durandal@92.41.57.161.threembb.co.uk> has joined #bitcoin-core-dev
962026-02-12T08:55:18 *** dongcarl0002 <dongcarl0002!~dongcarl@66.65.169.19> has joined #bitcoin-core-dev
972026-02-12T08:55:22 *** neonrooks <neonrooks!~neonrooks@user/neonrooks> has quit IRC (Quit: Client closed)
982026-02-12T08:56:09 *** durandal__ <durandal__!~durandal@94.196.72.217.threembb.co.uk> has quit IRC (Ping timeout: 245 seconds)
992026-02-12T08:56:18 *** neonrooks <neonrooks!~neonrooks@user/neonrooks> has joined #bitcoin-core-dev
1002026-02-12T08:56:52 *** dongcarl000 <dongcarl000!~dongcarl@66.65.169.19> has quit IRC (Ping timeout: 246 seconds)
1012026-02-12T08:58:53 *** neonrooks <neonrooks!~neonrooks@user/neonrooks> has quit IRC (Client Quit)
1022026-02-12T09:16:49 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has joined #bitcoin-core-dev
1032026-02-12T09:31:56 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
1042026-02-12T09:32:07 *** jon_atack <jon_atack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 264 seconds)
1052026-02-12T09:41:34 *** kevkevin <kevkevin!~kevkevin@209.242.60.195> has quit IRC (Ping timeout: 245 seconds)
1062026-02-12T09:43:43 <bitcoin-git> [bitcoin] fanquake pushed 3 commits to master: https://github.com/bitcoin/bitcoin/compare/0b4cd08fcd22...07b924775e4f
1072026-02-12T09:43:44 <bitcoin-git> bitcoin/master 1111fff MarcoFalke: lint: Add missing --platform=linux to docker build command
1082026-02-12T09:43:44 <bitcoin-git> bitcoin/master faba426 MarcoFalke: lint: Flatten lint image entry points
1092026-02-12T09:43:45 <bitcoin-git> bitcoin/master 07b9247 merge-script: Merge bitcoin/bitcoin#34427: lint: Flatten lint image entry points
1102026-02-12T09:43:46 <bitcoin-git> [bitcoin] fanquake merged pull request #34427: lint: Flatten lint image entry points (master...2601-lint-entry) https://github.com/bitcoin/bitcoin/pull/34427
1112026-02-12T09:56:31 *** kevkevin <kevkevin!~kevkevin@209.242.60.195> has joined #bitcoin-core-dev
1122026-02-12T10:01:09 *** kevkevin <kevkevin!~kevkevin@209.242.60.195> has quit IRC (Ping timeout: 245 seconds)
1132026-02-12T10:05:10 *** adil <adil!~Thunderbi@2402:4000:b142:8d92:4c8:1c42:b91d:c91a> has quit IRC (Quit: adil)
1142026-02-12T10:08:16 *** adil <adil!~Thunderbi@2402:4000:b142:8d92:4c8:1c42:b91d:c91a> has joined #bitcoin-core-dev
1152026-02-12T10:10:13 *** kevkevin <kevkevin!~kevkevin@209.242.60.195> has joined #bitcoin-core-dev
1162026-02-12T10:23:49 <bitcoin-git> [bitcoin] janb84 opened pull request #34570: doc: update Windows MSVC build guide to utilize winget to install build requirements (master...windows-msvc-update) https://github.com/bitcoin/bitcoin/pull/34570
1172026-02-12T10:27:08 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has quit IRC (Read error: Connection reset by peer)
1182026-02-12T10:27:19 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has joined #bitcoin-core-dev
1192026-02-12T10:29:30 *** adil <adil!~Thunderbi@2402:4000:b142:8d92:4c8:1c42:b91d:c91a> has quit IRC (Quit: adil)
1202026-02-12T10:29:49 <bitcoin-git> [bitcoin] maflcko opened pull request #34571: test: Fix intermittent issues in feature_assumevalid.py (master...2602-test-av-int-fail) https://github.com/bitcoin/bitcoin/pull/34571
1212026-02-12T10:31:37 *** adil <adil!~Thunderbi@2402:4000:b142:8d92:4c8:1c42:b91d:c91a> has joined #bitcoin-core-dev
1222026-02-12T10:54:52 <bitcoin-git> [bitcoin] maflcko closed pull request #34544: wallet: Disallow wallet names that are paths including `..` and `.` elements (master...wallet-no-relative-paths) https://github.com/bitcoin/bitcoin/pull/34544
1232026-02-12T10:55:02 <bitcoin-git> [bitcoin] maflcko reopened pull request #34544: wallet: Disallow wallet names that are paths including `..` and `.` elements (master...wallet-no-relative-paths) https://github.com/bitcoin/bitcoin/pull/34544
1242026-02-12T11:05:20 <bitcoin-git> [bitcoin] DrahtBot closed pull request #34075: fees: Introduce Mempool Based Fee Estimation to reduce overestimation (master...12-2025-fee-estimation-improvement) https://github.com/bitcoin/bitcoin/pull/34075
1252026-02-12T11:05:25 <bitcoin-git> [bitcoin] DrahtBot closed pull request #27052: test: rpc: add last block announcement time to getpeerinfo result (master...2023-02-getpeerinfo) https://github.com/bitcoin/bitcoin/pull/27052
1262026-02-12T11:05:35 <bitcoin-git> [bitcoin] DrahtBot reopened pull request #34075: fees: Introduce Mempool Based Fee Estimation to reduce overestimation (master...12-2025-fee-estimation-improvement) https://github.com/bitcoin/bitcoin/pull/34075
1272026-02-12T11:05:37 <bitcoin-git> [bitcoin] DrahtBot reopened pull request #27052: test: rpc: add last block announcement time to getpeerinfo result (master...2023-02-getpeerinfo) https://github.com/bitcoin/bitcoin/pull/27052
1282026-02-12T11:06:14 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has quit IRC (Quit: l0rinc)
1292026-02-12T11:12:50 *** kevkevin <kevkevin!~kevkevin@209.242.60.195> has quit IRC (Ping timeout: 252 seconds)
1302026-02-12T11:24:59 *** kevkevin <kevkevin!~kevkevin@209.242.60.195> has joined #bitcoin-core-dev
1312026-02-12T11:27:07 <bitcoin-git> [bitcoin] hebasto opened pull request #34572: cmake: Fix NetBSD-specific workaround for Boost (master...260212-netbsd-boost) https://github.com/bitcoin/bitcoin/pull/34572
1322026-02-12T11:30:01 *** kevkevin <kevkevin!~kevkevin@209.242.60.195> has quit IRC (Ping timeout: 264 seconds)
1332026-02-12T11:30:55 *** adil <adil!~Thunderbi@2402:4000:b142:8d92:4c8:1c42:b91d:c91a> has quit IRC (Quit: adil)
1342026-02-12T11:42:05 *** kevkevin <kevkevin!~kevkevin@209.242.60.195> has joined #bitcoin-core-dev
1352026-02-12T11:57:18 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has quit IRC (Read error: Connection reset by peer)
1362026-02-12T11:58:36 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has joined #bitcoin-core-dev
1372026-02-12T11:58:44 *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has quit IRC (Remote host closed the connection)
1382026-02-12T11:59:07 *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has joined #bitcoin-core-dev
1392026-02-12T11:59:47 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has joined #bitcoin-core-dev
1402026-02-12T12:20:32 *** eugenesiegel <eugenesiegel!~eugenesie@user/eugenesiegel> has joined #bitcoin-core-dev
1412026-02-12T12:27:05 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has quit IRC (Read error: Connection reset by peer)
1422026-02-12T12:29:41 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has joined #bitcoin-core-dev
1432026-02-12T12:45:14 *** kevkevin <kevkevin!~kevkevin@209.242.60.195> has quit IRC (Ping timeout: 252 seconds)
1442026-02-12T12:52:42 *** memset <memset!~memset@gateway/tor-sasl/memset> has quit IRC (Remote host closed the connection)
1452026-02-12T12:53:04 *** memset <memset!~memset@gateway/tor-sasl/memset> has joined #bitcoin-core-dev
1462026-02-12T12:58:55 *** kevkevin <kevkevin!~kevkevin@209.242.60.195> has joined #bitcoin-core-dev
1472026-02-12T13:01:13 *** twistedline <twistedline!~bitcoin@1tbit.com> has quit IRC (Ping timeout: 264 seconds)
1482026-02-12T13:10:40 *** twistedline <twistedline!~bitcoin@1tbit.com> has joined #bitcoin-core-dev
1492026-02-12T13:22:49 *** twistedline <twistedline!~bitcoin@1tbit.com> has quit IRC (Ping timeout: 264 seconds)
1502026-02-12T13:27:04 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has quit IRC (Read error: Connection reset by peer)
1512026-02-12T13:27:18 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has joined #bitcoin-core-dev
1522026-02-12T13:30:30 *** kevkevin <kevkevin!~kevkevin@209.242.60.195> has quit IRC (Remote host closed the connection)
1532026-02-12T13:31:02 *** kevkevin <kevkevin!~kevkevin@209.242.60.195> has joined #bitcoin-core-dev
1542026-02-12T13:36:30 *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has quit IRC (Quit: = "")
1552026-02-12T13:45:30 *** kevkevin <kevkevin!~kevkevin@209.242.60.195> has quit IRC (Remote host closed the connection)
1562026-02-12T13:46:02 *** kevkevin <kevkevin!~kevkevin@209.242.60.195> has joined #bitcoin-core-dev
1572026-02-12T13:53:54 *** abubakarsadiq <abubakarsadiq!uid602234@id-602234.hampstead.irccloud.com> has joined #bitcoin-core-dev
1582026-02-12T13:57:07 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has quit IRC (Read error: Connection reset by peer)
1592026-02-12T13:57:18 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has joined #bitcoin-core-dev
1602026-02-12T13:57:23 *** sr_gi[m] <sr_gi[m]!~srgimatri@2620:6e:a000:ce11::2a> has quit IRC (Quit: issued !quit command)
1612026-02-12T13:58:23 *** sr_gi <sr_gi!~sr_gi@46.231.244.218> has joined #bitcoin-core-dev
1622026-02-12T14:01:09 *** kevkevin <kevkevin!~kevkevin@209.242.60.195> has quit IRC (Ping timeout: 245 seconds)
1632026-02-12T14:01:18 *** durandal_ <durandal_!~durandal@92.41.57.161.threembb.co.uk> has quit IRC (Read error: Connection reset by peer)
1642026-02-12T14:02:00 *** durandal_ <durandal_!~durandal@92.41.57.161.threembb.co.uk> has joined #bitcoin-core-dev
1652026-02-12T14:02:23 *** durandal_ <durandal_!~durandal@92.41.57.161.threembb.co.uk> has quit IRC (Remote host closed the connection)
1662026-02-12T14:02:23 *** kevkevin <kevkevin!~kevkevin@209.242.60.195> has joined #bitcoin-core-dev
1672026-02-12T14:07:49 <bitcoin-git> [bitcoin] m3dwards closed pull request #32672: ci: update pwsh to use custom shell that fails-fast (master...250603-pwsh-fail-fast) https://github.com/bitcoin/bitcoin/pull/32672
1682026-02-12T14:08:53 *** twistedline <twistedline!~bitcoin@1tbit.com> has joined #bitcoin-core-dev
1692026-02-12T14:10:54 *** eugenesiegel <eugenesiegel!~eugenesie@user/eugenesiegel> has quit IRC (Quit: Client closed)
1702026-02-12T14:13:34 *** twistedline <twistedline!~bitcoin@1tbit.com> has quit IRC (Ping timeout: 255 seconds)
1712026-02-12T14:17:40 *** twistedline <twistedline!~bitcoin@1tbit.com> has joined #bitcoin-core-dev
1722026-02-12T14:22:41 *** memset <memset!~memset@gateway/tor-sasl/memset> has quit IRC (Remote host closed the connection)
1732026-02-12T14:23:25 *** memset <memset!~memset@gateway/tor-sasl/memset> has joined #bitcoin-core-dev
1742026-02-12T14:44:20 *** eugenesiegel <eugenesiegel!~eugenesie@user/eugenesiegel> has joined #bitcoin-core-dev
1752026-02-12T14:44:59 <bitcoin-git> [bitcoin] maflcko closed pull request #34557: test: fix intermittent failure in interface_zmq.py (master...master) https://github.com/bitcoin/bitcoin/pull/34557
1762026-02-12T14:46:40 <bitcoin-git> [bitcoin] andrewtoth closed pull request #34329: rpc,net: Add private broadcast RPCs (master...private_broadcast_rpcs) https://github.com/bitcoin/bitcoin/pull/34329
1772026-02-12T14:46:44 <bitcoin-git> [bitcoin] andrewtoth reopened pull request #34329: rpc,net: Add private broadcast RPCs (master...private_broadcast_rpcs) https://github.com/bitcoin/bitcoin/pull/34329
1782026-02-12T14:52:04 <bitcoin-git> [bitcoin] Hijanhv opened pull request #34574: test: fix intermittent failure in interface_zmq.py (master...fix-interface-zmq-test) https://github.com/bitcoin/bitcoin/pull/34574
1792026-02-12T14:57:06 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has quit IRC (Read error: Connection reset by peer)
1802026-02-12T14:59:44 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has joined #bitcoin-core-dev
1812026-02-12T15:10:45 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has quit IRC (Quit: l0rinc)
1822026-02-12T15:11:29 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has joined #bitcoin-core-dev
1832026-02-12T15:27:06 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has quit IRC (Read error: Connection reset by peer)
1842026-02-12T15:29:41 *** twistedline <twistedline!~bitcoin@1tbit.com> has quit IRC (Ping timeout: 252 seconds)
1852026-02-12T15:29:43 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has joined #bitcoin-core-dev
1862026-02-12T15:30:23 *** durandal_ <durandal_!~durandal@92.41.58.139.threembb.co.uk> has joined #bitcoin-core-dev
1872026-02-12T15:33:33 *** twistedline <twistedline!~bitcoin@1tbit.com> has joined #bitcoin-core-dev
1882026-02-12T15:40:55 *** Guyver2 <Guyver2!~Guyver@77-174-98-73.fixed.kpn.net> has joined #bitcoin-core-dev
1892026-02-12T15:41:17 *** Guyver2 <Guyver2!~Guyver@77-174-98-73.fixed.kpn.net> has left #bitcoin-core-dev
1902026-02-12T15:43:24 *** bugs_ <bugs_!~bugs@user/bugs/x-5128603> has joined #bitcoin-core-dev
1912026-02-12T15:46:04 *** memset <memset!~memset@gateway/tor-sasl/memset> has quit IRC (Remote host closed the connection)
1922026-02-12T15:46:22 *** memset <memset!~memset@gateway/tor-sasl/memset> has joined #bitcoin-core-dev
1932026-02-12T15:59:56 *** twistedline <twistedline!~bitcoin@1tbit.com> has quit IRC (Ping timeout: 252 seconds)
1942026-02-12T16:00:10 *** musaHaruna <musaHaruna!uid732742@id-732742.hampstead.irccloud.com> has joined #bitcoin-core-dev
1952026-02-12T16:00:19 <fjahr> #startmeeting
1962026-02-12T16:00:19 <corebot> fjahr: Meeting started at 2026-02-12T16:00+0000
1972026-02-12T16:00:20 <corebot> fjahr: Current chairs: fjahr
1982026-02-12T16:00:21 <corebot> fjahr: Useful commands: #action #info #idea #link #topic #motion #vote #close #endmeeting
1992026-02-12T16:00:22 <corebot> fjahr: See also: https://hcoop-meetbot.readthedocs.io/en/stable/
2002026-02-12T16:00:23 <corebot> fjahr: Participants should now identify themselves with '#here' or with an alias like '#here FirstLast'
2012026-02-12T16:00:24 <hodlinator> hi
2022026-02-12T16:00:26 <eugenesiegel> hi
2032026-02-12T16:00:27 <fjahr> #bitcoin-core-dev Meeting: abubakarsadiq achow101 _aj_ ajonas b10c brunoerg cfields darosior dergoegge dzxzg eugenesiegel fanquake fjahr furszy gleb glozow hebasto hodlinator instagibbs janb84 jarolrod jonatack josibake kanzure kevkevin laanwj LarryRuane lightlike l0rinc luke-jr maflcko marcofleon maxedw Murch pinheadmz provoostenator ryanofsky sdaftuar S3RK stickies-v sipa sliv3r__ sr_gi tdb3 theStack TheCharlatan vasild
2042026-02-12T16:00:27 <fjahr> willcl-ark
2052026-02-12T16:00:29 <pinheadmz_> yo
2062026-02-12T16:00:30 <achow101> hi
2072026-02-12T16:00:30 <dergoegge> hi
2082026-02-12T16:00:30 <janb84> hi
2092026-02-12T16:00:32 <hebasto> hi
2102026-02-12T16:00:33 <furszy> hi
2112026-02-12T16:00:33 <brunoerg> hi
2122026-02-12T16:00:34 <abubakarsadiq> hi
2132026-02-12T16:00:37 <stringintech> hi
2142026-02-12T16:00:38 <Sjors[m]1> Hi
2152026-02-12T16:00:39 <sliv3r__> hi
2162026-02-12T16:00:41 <fjahr> There is one pre-proposed meeting topic this week. Any last minute ones to add?
2172026-02-12T16:00:43 <sr_gi> hi
2182026-02-12T16:00:54 <lightlike> Hi
2192026-02-12T16:00:56 <johnny9dev> hi
2202026-02-12T16:01:03 <stickies-v> hi
2212026-02-12T16:01:14 <sipa_> hi
2222026-02-12T16:01:19 *** sipa_ is now known as sipa
2232026-02-12T16:01:28 <sipa> hi
2242026-02-12T16:01:29 *** Emc99 <Emc99!~Emc99@212.129.77.67> has joined #bitcoin-core-dev
2252026-02-12T16:01:38 <fjahr> We'll get started with the WGs!
2262026-02-12T16:01:41 <fjahr> #topic Fuzzing WG Update (dergoegge)
2272026-02-12T16:01:52 <dergoegge> nothing from my side
2282026-02-12T16:02:00 <cfields_> hi
2292026-02-12T16:02:21 <fjahr> #topic Cluster Mempool WG Update (sdaftuar, sipa)
2302026-02-12T16:02:39 <sipa> Hi!
2312026-02-12T16:03:26 <sipa> We're getting very close to the finish line. #34257 was merged. Next to review is #34023 which would be good to get into the first release still.
2322026-02-12T16:03:28 <corebot> https://github.com/bitcoin/bitcoin/issues/34257 | txgraph: deterministic optimal transaction order by sipa · Pull Request #34257 · bitcoin/bitcoin · GitHub
2332026-02-12T16:03:30 <corebot> https://github.com/bitcoin/bitcoin/issues/34023 | Optimized SFL cluster linearization by sipa · Pull Request #34023 · bitcoin/bitcoin · GitHub
2342026-02-12T16:03:42 <sipa> I've removed some parts of the latter that are less critical, so ready for review now.
2352026-02-12T16:04:02 <sipa> That's it for me.
2362026-02-12T16:04:14 <fjahr> #topic Net Split WG Update (cfields)
2372026-02-12T16:05:12 <cfields_> nothing to report this week
2382026-02-12T16:05:36 <fjahr> I guess we are skipping kernel, silent payments and benchmarking unless I missed someone or they forgot to say hi...
2392026-02-12T16:05:57 <fjahr> #topic unbundling the GUI (https://gist.github.com/stickies-v/c871439db3ac93269d370905323820a8) (hebasto, stickies-v)
2402026-02-12T16:06:04 <hebasto> hi
2412026-02-12T16:06:07 <hebasto> I'm presenting this topic alone.
2422026-02-12T16:06:12 <hebasto> the updated is here: https://gist.github.com/hebasto/478910dc16239d17c8bfdfd61a53a5dd
2432026-02-12T16:06:18 <hebasto> it's a common opinion that the GUI development stuck.
2442026-02-12T16:06:23 <hebasto> but I see it a bit differently; it's in stalemate.
2452026-02-12T16:06:29 <hebasto> the current monolithic approach in the codebase, build system, release process, and publishing makes it infeasible to move forward neither in the current GUI (like adding Wayland support for release binaries) nor in new QML-based GUI.
2462026-02-12T16:06:34 <hebasto> this crisis stems from the natural antagonism between security (less dependencies) and functionality (more dependencies).
2472026-02-12T16:06:41 <hebasto> the problem with Bitcoin Core GUI has been known for quite a long time, and this attempt to find a solution isn't the first.
2482026-02-12T16:06:46 <hebasto> furthermore, the long-standing nature of this issue, combined with the separate GUI repository, led to a decline in developer focus on the GUI.
2492026-02-12T16:06:53 <hebasto> I strongly believe that it is in best interest of the current and _future_ users to shift focus on developing the GUI based on a public API (IPC, RPC etc).
2502026-02-12T16:06:59 <hebasto> of course, we have to pledge to develop and maintain such APIs basing on the best engineering practices.
2512026-02-12T16:07:04 <hebasto> as a side effect, it opens a free market for alternative GUI implementations.
2522026-02-12T16:07:08 <hebasto> the immediate action I propose is to deprecate the GUI binaries in v31.0
2532026-02-12T16:07:14 <hebasto> in light of the above, I will be shifting my personal focus accordingly.
2542026-02-12T16:07:18 <hebasto> that's all from me
2552026-02-12T16:07:54 <achow101> The gist states that the eventual goal is to abandon the GUI, which I wholeheartedly disagree with
2562026-02-12T16:08:56 <achow101> I think the project must ship an official GUI. That can still be done even if we have IPC
2572026-02-12T16:08:57 <johnny9dev> I would also like to add that from someone on the edge. The gui doesnt look abandoned at all. There are PRs and issues flowing. Its certainly slow but it appears infinitely more healthy than a majority of open source projects.
2582026-02-12T16:09:37 <hebasto> achow101: I hope you can propose an alternative to move away from the current stalemate?
2592026-02-12T16:09:40 <furszy> I think we should monitor the GUI's downloads in some way, and see if we do have users for it.
2602026-02-12T16:10:04 <pinheadmz_> furszy i suggested that before, no one wants to track bitcoin users tho
2612026-02-12T16:10:19 <furszy> not even the download count?
2622026-02-12T16:10:22 <pinheadmz_> also suggested we intentionally break the gui and see if anyone complains ;-)
2632026-02-12T16:10:30 <janb84> I like the free market idea
2642026-02-12T16:10:31 <pinheadmz_> furszy ask BlueMatt[m] hell refuse
2652026-02-12T16:10:35 <l0rinc> hi
2662026-02-12T16:10:36 <instagibbs> pinheadmz_ lol
2672026-02-12T16:10:55 <achow101> hebasto: I don't disagree with moving towards having a stable IPC interface that the GUI can use, but that does not mean that we shouldn't ship a GUI
2682026-02-12T16:11:01 <pinheadmz_> johnny9dev IIRC you have a branch of QML that is pretty good - but its like 1000 commits
2692026-02-12T16:11:02 <johnny9dev> there are plenty of people that I believe would be interested in taking ownership of the old gui as well. I wouldnt use the term deprecation but maybe migrating it is an idea.
2702026-02-12T16:11:06 <instagibbs> I'm a marginal GUI user, but I'd just as easily use an alterantive dashboard for the same purposes
2712026-02-12T16:11:10 <pinheadmz_> so if we want a gui we need review
2722026-02-12T16:11:10 <furszy> pinheadmz_: I had a few easy crash fixes in the gui open for a while, and no one complained about them.
2732026-02-12T16:11:27 <achow101> furszy: all access logs on the website are disabled so we currently can't get any stats
2742026-02-12T16:11:51 <dergoegge> Who ever wants us to keep shipping the gui will need to take care of it
2752026-02-12T16:11:52 <sliv3r__> @pinheadmz_ lol
2762026-02-12T16:12:15 <pinheadmz_> it does seem very useful to find out if anyone uses a thing before we dedicate work to it
2772026-02-12T16:12:15 <bitcoin-git> [bitcoin] maflcko opened pull request #34575: test: Avoid empty errmsg in JSONRPCException (master...2602-test-proper-JSONRPCException-error) https://github.com/bitcoin/bitcoin/pull/34575
2782026-02-12T16:12:17 <BlueMatt[m]> @libera_irc_pinheadmz_:bitcoin.ninja i mean, i think the gui is great to have, but also i dont really have an opinion that counts here cause I don't work on core
2792026-02-12T16:12:21 <fanquake> pinheadz: the issue with the current QML (which iirc hasn't had a commit for 6 months), is that is inherits the same architectural problems as the current gui, but somewhat worse, given the subtree.
2802026-02-12T16:12:23 <pinheadmz_> achow101 why do you think we must ship a gui ?
2812026-02-12T16:12:40 <fjahr> I can agree with the issue stated but by hebasto/stickies but if we don't have any official GUI at all I fear a flood of vibe coded malicious GUIs that will cause us more pain than maintaining an official gui, which could be very minimal
2822026-02-12T16:12:49 <pinheadmz_> BlueMatt[m] do you have an opinion about tracking downloads ?
2832026-02-12T16:12:53 <BlueMatt[m]> if bitcoin core is gonna ship a wallet, it seems reasonable that it should also ship a gui to access that wallet
2842026-02-12T16:12:57 <achow101> pinheadmz_: because users expect us to provide one. I think everyone severely underestimates how many people actually use the gui
2852026-02-12T16:13:02 <BlueMatt[m]> pinheadmz_: yes, we shouldn't do it.
2862026-02-12T16:13:11 *** twistedline <twistedline!~bitcoin@1tbit.com> has joined #bitcoin-core-dev
2872026-02-12T16:13:21 <sipa> hebasto: i don't think the dependencies problem is core to the issue here; we can move towards a more-static-linked binary for bitcoind, and simultaneously toward a more runtime-dependency rich bitcoin-qt binary... because GUI users naturally depend on more dependencies (no pun intended)
2882026-02-12T16:13:30 <achow101> just for example, the default windows and macos downloads install and provide access to the gui by default. Using bitcoind on windows is a pain in the ass. and the macos app installer doesn't even provide bitcoind or the utilities
2892026-02-12T16:13:32 <pinheadmz_> fanquake all the commits are, i belive, on johnny9dev branch and need lots of PRs and reviews
2902026-02-12T16:14:03 <fanquake> pinheadz: is the subtreeing solved, and is it using IPC now?
2912026-02-12T16:14:15 <furszy> BlueMatt[m]: not even download count? nothing else.
2922026-02-12T16:14:34 <hebasto> fanquake: wdyt about sipa's suggestion?
2932026-02-12T16:14:37 <pinheadmz_> fanquake not using IPC yet
2942026-02-12T16:14:41 <eugenesiegel> to second fjahr comment, I also worry about malicious GUIs takings the official ones place
2952026-02-12T16:14:42 <fanquake> It would be good to get some clarity around if we are implementing new features (silent payments, pay dns, privatebroadcast, assumeutxo etc) in the current gui, and who might implement those
2962026-02-12T16:14:52 <achow101> something else to consider is that we already have a bunch of loud people who claim we hate users. killing the gui in the short term will add fuel to that fire
2972026-02-12T16:15:00 <pinheadmz_> i just wanted to stop core codebase changes in the qml repo, so forcing bitcoin as a subtree
2982026-02-12T16:15:05 <johnny9dev> I bet we could recruit people to work on those things if its a manpower issue
2992026-02-12T16:15:07 <dergoegge> there's nothing stopping anyone from building malicious GUIs right now
3002026-02-12T16:15:23 <sipa> hebasto, fanquake: to be clear, i'm not saying that this is a trivial thing to do - i'm saying the issue isn't dependencies, it's reviewer interest (if anything)
3012026-02-12T16:15:23 <hebasto> achow101: it's not about "killing the gui"
3022026-02-12T16:15:39 <ryanofsky> i'm curious about problems with the subtree. it seems like a read-only subtree could be a good way to support a group of external developers making a gui
3032026-02-12T16:15:40 <BlueMatt[m]> furszy: im not aware of a way to do counts trivially without logs on a static site. i mean you can log to tmpfs and then have a script that converts that to count, but then you do have logs...
3042026-02-12T16:15:46 <fjahr> dergoegge: but people are not actively looking for a replacement right now so the incentives are much lower
3052026-02-12T16:15:58 <pinheadmz_> johnny9dev -- your branch -- how is it going. feature complete? enough for most users to send and receive?
3062026-02-12T16:15:59 <achow101> dergoegge: the only people who would be affected by a malicious gui right now are those who seek a 3rd party gui. killing the official one requires every gui user to find one
3072026-02-12T16:16:33 <fanquake> ryanofsky: it doesn't decouple the gui from our repo, and doesn't properly exercise the interface, like an external user would have to
3082026-02-12T16:16:45 <fanquake> we can't clean up any code, we need to keep sharing depends in some awkward way etc
3092026-02-12T16:16:58 <fanquake> basically the current situation except worse, because now you have a sync / versioning problem
3102026-02-12T16:17:20 <johnny9dev> The branch is still in the demo state. I had personal things come up and other project take priority. I think conceptually your refactor works and it is a route to build the gui independantly but there is a lot of work to make qml a reality still
3112026-02-12T16:17:41 <fanquake> (also unclear if the CI framework would be shared, of the gui repo would have it's own)
3122026-02-12T16:17:46 <ryanofsky> fanquake, thanks. i feel like those issues might be fixable? like we could delete all gui code & depends stuff from core repo and move it to an external repo includeing core as a read-only subtree
3132026-02-12T16:17:50 <fanquake> which would retain further coupling
3142026-02-12T16:18:25 <fanquake> ryanofsky: how about all the settings code, util code etc?
3152026-02-12T16:18:55 <sipa> ryanofsky: i like that as something we could try, but i'm not sure it'll change much
3162026-02-12T16:18:57 <ryanofsky> it is includedin core. if gui developers need to change it (hopefully not frequently) they submit a pr
3172026-02-12T16:18:58 <johnny9dev> I do agree that the subtree refactor pinheadz did to the qml project is a viable alternative. Release process/ownership would need to be understood
3182026-02-12T16:19:09 <johnny9dev> doing that adds more process
3192026-02-12T16:19:22 <fanquake> Somebody should be able to take out IPC interface, and build a GUI essentially without seeing our repo, and we aren't dogfooding that by having a subtree with tonnes of shared code
3202026-02-12T16:19:39 <johnny9dev> agree there too. it would be a step in the right direction though
3212026-02-12T16:19:40 <ryanofsky> sipa, yes. i think the real question is just whether external developers want to continue maintaining the gui, but developers here who are currently maintaining it do not want to
3222026-02-12T16:19:43 <fanquake> and I assume would not build out the interfaces properly, because we can just cheat
3232026-02-12T16:19:48 *** eugenesiegel <eugenesiegel!~eugenesie@user/eugenesiegel> has quit IRC (Quit: Client closed)
3242026-02-12T16:19:51 <ryanofsky> s/but/because/
3252026-02-12T16:20:20 <dergoegge> achow101 fjahr: they've managed to download and run bitcoin-qt I think they'll be fine. Seems like very paternalistic thinking. They might also (more likely) find a better alternative
3262026-02-12T16:20:21 <achow101> I strongly prefer that we still have the gui in the main repo, shipped along with our normal release process. it can still use IPC and does not need to be so tightly coupled, other than in doing releases
3272026-02-12T16:20:23 <johnny9dev> I'm skeptical that the gui is in such a dire state, though. I know its been a friction point, but I don't fully understand why.
3282026-02-12T16:20:31 <fanquake> This just seems to create more friction, and repos to track, that non-gui devs (majority) have to deal with?
3292026-02-12T16:20:54 *** eugenesiegel <eugenesiegel!~eugenesie@user/eugenesiegel> has joined #bitcoin-core-dev
3302026-02-12T16:21:00 <BlueMatt[m]> yea, i mean the gui works fine. just because its not super actively maintained doesn't mean that it has noticeable bugs that impact the average user
3312026-02-12T16:21:01 <sipa> fanquake: that's fair - and cleaning up the interface to make it even possible to have an IPC-only GUI will probably require significant changes to the interface on the core side, so would be easier to do before such a subtree move
3322026-02-12T16:21:25 <ryanofsky> fanquake, moving gui code out of core into a separate repo would seem to create more friction for (theoretical) gui developers but not core developers
3332026-02-12T16:21:31 <Sjors[m]1> My hot take would be: we should keep offering a GUI, but it can a separate download. Designing a fresh IPC for this, rather than sticking to the current GUI interface, would make the most sense to me.
3342026-02-12T16:21:43 <fjahr> dergoegge: It will look much better and then maybe steal their coins
3352026-02-12T16:21:50 <Sjors[m]1> And I would probably feel more motivated to work on such an IPC interface than on the current GUI code.
3362026-02-12T16:22:23 <fjahr> dergoegge: And the users won't know which project stole them, core or the gui
3372026-02-12T16:22:33 <fanquake> ryanofsky: yea, the reason the separated repos seem to have worked so far, is because 95% of core devs aren't touching any gui code
3382026-02-12T16:22:37 *** memset <memset!~memset@gateway/tor-sasl/memset> has quit IRC (Remote host closed the connection)
3392026-02-12T16:22:51 <fanquake> (also why none of the GUI side of features we've shipped has been implemented)
3402026-02-12T16:23:02 <dergoegge> fjahr: if your core node is a hot wallet then any piece of software you download runs that risk
3412026-02-12T16:23:08 <fanquake> A non-technical user still can't use AssumeUTXO
3422026-02-12T16:23:11 <achow101> I would argue that separate repos has not worked so far, and is in fact what has caused the GUI to get into this stalemate situation
3432026-02-12T16:23:12 *** memset <memset!~memset@gateway/tor-sasl/memset> has joined #bitcoin-core-dev
3442026-02-12T16:23:29 <sipa> achow101: i agree
3452026-02-12T16:23:39 <furszy> fanquake: would argue that a technical one neither.
3462026-02-12T16:23:45 <furszy> but that is a different subject
3472026-02-12T16:23:52 <fanquake> I think the key point here, is that hebasto has decided he's focussing on different things, so it sounds like somebody(s) need to step up here
3482026-02-12T16:23:57 *** sr_gi <sr_gi!~sr_gi@46.231.244.218> has quit IRC (Quit: Client closed)
3492026-02-12T16:24:06 <achow101> in fact, I would entirely propose that something we should try to unstick the gui is to remove the separate repo and bring it back into the main repo
3502026-02-12T16:24:30 <fanquake> As of today there are new (non-)GUI issues that needs solving, i.e #34569
3512026-02-12T16:24:31 <corebot> https://github.com/bitcoin/bitcoin/issues/34569 | build: Qt depends build broken with GCC 16 · Issue #34569 · bitcoin/bitcoin · GitHub
3522026-02-12T16:25:06 *** sr_gi <sr_gi!~sr_gi@46.231.244.218> has joined #bitcoin-core-dev
3532026-02-12T16:25:07 <cfields_> Oh, heh, I have fixes for that :)
3542026-02-12T16:25:14 <dergoegge> the proposal was abandonment in v34, all of you who are so in favor of having a gui have enough time until then to build an alternative we can ship that solves the current issues
3552026-02-12T16:25:20 <cfields_> I built wit gcc16 this week and have some patches to PR.
3562026-02-12T16:25:39 <cfields_> (I realize that's not the point you're making though.. )
3572026-02-12T16:25:47 <pinheadmz_> fanquake is right the real lede here is hebasto's priorities
3582026-02-12T16:25:58 <sliv3r__> achow101 I agree, it's so anoying if you try to do stuff on the gui to have another repo with a bunch of duplicated code
3592026-02-12T16:26:31 <fanquake> Yea. Someone else needs to be responsible for release prep, translations, implenting new GUI features, making a decision about QML, deciding what new GUI features we might implement, make a decision about a wayland migration or not, etc
3602026-02-12T16:26:32 <hebasto> fanquake: pinheadmz_: I don't think its about my personal priorities
3612026-02-12T16:26:37 *** memset <memset!~memset@gateway/tor-sasl/memset> has quit IRC (Remote host closed the connection)
3622026-02-12T16:26:41 <achow101> dergoegge: I am doubtful that we can do all of multiprocess in that time, which seems like a hard requirement for alternative guis
3632026-02-12T16:26:49 <johnny9dev> To the point of bitcoin-core/gui being not create. I still don't actually know the relationship between bitcoin-core/gui and bitcoin/bitcoin. I've been on the edge but I think it probably be obvious to someone like me by now.
3642026-02-12T16:26:57 <johnny9dev> being not great*
3652026-02-12T16:27:32 <dergoegge> The RPCs work as well, there's no hard requirement on IPC afaict
3662026-02-12T16:27:56 <dergoegge> Alternative decoupled GUIs exist today without IPC
3672026-02-12T16:28:00 <achow101> dergoegge: there absolutely is, in order to get signals/notifications
3682026-02-12T16:28:01 <Sjors[m]1> RPC is much too slow for a UI, all of the web based UI's have demonstrated that
3692026-02-12T16:28:08 <achow101> dergoegge: provide an example
3702026-02-12T16:28:15 *** memset <memset!~memset@gateway/tor-sasl/memset> has joined #bitcoin-core-dev
3712026-02-12T16:28:23 <dergoegge> liana, specter, sparrow
3722026-02-12T16:28:31 <achow101> none of those are guis. those are whole ass separate wallets
3732026-02-12T16:28:51 <sliv3r__> those does not allow you to control your node
3742026-02-12T16:28:56 <achow101> they do very different things from what our gui does
3752026-02-12T16:29:08 <hebasto> re "Yea. Someone else needs to be responsible for release prep, translations, implenting new GUI features, making a decision about QML, deciding what new GUI features we might implement, make a decision about a wayland migration or not, etc" -- okay, if you say so
3762026-02-12T16:29:32 <fanquake> ? Isn't that what you're proposing by focussing on other things?
3772026-02-12T16:29:35 <johnny9dev> yeah if you're serious i think you need to champion a new owner and mentor
3782026-02-12T16:29:38 <dergoegge> RPCs can be polled
3792026-02-12T16:29:38 <johnny9dev> it will be a lot of work
3802026-02-12T16:29:45 <pinheadmz_> boy it sure would be great is we knew any users wanted a bitcoin core gui
3812026-02-12T16:29:51 <pinheadmz_> how can we set our agenda without that info
3822026-02-12T16:30:01 <BlueMatt[m]> I mean people definitely use it
3832026-02-12T16:30:06 <sipa> agreed, achow101; and importantly: there is no way to convert/import/load Bitcoin Core wallets into them - they have an entirely different idea of what a wallet is, so that's no viable migration path for current GUI wallet users
3842026-02-12T16:30:15 <Sjors[m]1> I use it :-)
3852026-02-12T16:30:17 <BlueMatt[m]> how man i dunno, but its very far from zero, and with a wallet its the most important part
3862026-02-12T16:30:42 <pinheadmz_> good point - abandon the wallet !
3872026-02-12T16:30:47 <achow101> pinheadmz_: here's data from the survey I ran 5 years ago, never really processed it to the point that something could be written up, but there were questiosn about how users use Bitcoin Core https://github.com/achow101/2021-core-survey/
3882026-02-12T16:31:19 <sliv3r__> if we kill the gui we kill the posibility for non-tech users to run nodes easily without relaying on something like umbrel, etc.
3892026-02-12T16:31:50 <achow101> of the 342 people who responded to the question "How do you currently use Bitcoin Core?", 176 of them said "the GUI"
3902026-02-12T16:32:02 <pinheadmz_> interesting !
3912026-02-12T16:32:03 <sliv3r__> people should be able to run a node only with core, and not needing other's "frontend" software
3922026-02-12T16:32:24 <achow101> of the 387 people who responded to the question "how did you previously use Bitcoin Core?", 246 responded "the GUI"
3932026-02-12T16:32:52 <sliv3r__> achow101 would be a lot of work to run that survey again?
3942026-02-12T16:33:11 <dergoegge> So the only data we have is a 5 year old survey of ~400 users?
3952026-02-12T16:33:15 <sipa> sliv3r__: i worry that the current social media climate is not conducive to getting honest answers
3962026-02-12T16:33:18 <achow101> sliv3r__: kinda yeah, and also the questions need major work to get more useful info out
3972026-02-12T16:34:08 <sliv3r__> true :/
3982026-02-12T16:34:21 <achow101> dergoegge: the survey itself had ~3000 responses, just those ~400 who answered those specific questions
3992026-02-12T16:35:22 <ryanofsky> i think it'd be good to have a more specific idea of current problems. if hebasto, fanquake others are currently spending time on the gui and want to work on other things, deleting src/qt/ may be one solution but there may be others
4002026-02-12T16:35:23 <pinheadmz_> well could we start releasing a QML-beta within a year that had MVP functinality
4012026-02-12T16:35:27 <pinheadmz_> along with deprecating Qt
4022026-02-12T16:36:03 <dergoegge> Who will work on the qml gui?
4032026-02-12T16:36:34 <johnny9dev> as the last remaining QML guy. I actually think the Qt widgets serves a really important role and I have grown to really like it.
4042026-02-12T16:36:50 <hebasto> I will
4052026-02-12T16:36:52 <johnny9dev> I would rather keep Qt widgets alive than try to replace it.
4062026-02-12T16:36:52 <pinheadmz_> well. i can take on some of the review to get jonnys work into a beta release.
4072026-02-12T16:37:39 <pinheadmz_> the qml ui looks slick and modern, i think it is something bitcoin should have
4082026-02-12T16:37:41 <sipa> johnny9dev: just for someone not familiar with the terminology... does "Qt widgets" mean the current non-QML gui?
4092026-02-12T16:38:00 <hebasto> ^ right
4102026-02-12T16:38:01 <furszy> sipa: the current widgets
4112026-02-12T16:38:05 <johnny9dev> yeah qml serves a different purpose that the widgets one for sure and there is a lot of opportunity if it can be realised
4122026-02-12T16:38:20 <sipa> furszy: you have not provided an answer that is useful to someone unfamiliar with technology :p
4132026-02-12T16:38:23 <johnny9dev> Qt widgets is old-school desktop gui
4142026-02-12T16:38:27 <sipa> *terminology
4152026-02-12T16:38:31 <johnny9dev> think tables, gray buttons, and tabs
4162026-02-12T16:38:35 <furszy> sipa: :)
4172026-02-12T16:38:52 <achow101> sipa: QT widgets is what the current gui we ship uses
4182026-02-12T16:38:55 <johnny9dev> but its still perfect for data software. Sparrow is widgets based
4192026-02-12T16:38:58 <sipa> achow101: thanks
4202026-02-12T16:39:15 <pinheadmz_> isnt Qt deprecating widgets? like isnt there some dependency-reason we have to migrate ?
4212026-02-12T16:39:19 <johnny9dev> no they are not
4222026-02-12T16:39:28 <johnny9dev> there was a misconception but it will never be deprecated
4232026-02-12T16:39:36 <pinheadmz_> ah i was misconcieved
4242026-02-12T16:39:47 <johnny9dev> its not getting new features but it is supported. Consider it "solved"
4252026-02-12T16:39:56 <hebasto> Qt stopped developing Qt Widgets actively, but not deprecated them
4262026-02-12T16:40:43 <furszy> so, hebasto, you are interested in working on the new GUI, but not in maintaining the current one anymore?
4272026-02-12T16:41:25 <Sjors[m]1> If QML is easier to work with and we have a working prototype, that's still better(tm), no?
4282026-02-12T16:41:45 <fanquake> ryanofsky: 1 issue is that because the QML gui was being built, no new features were added to the current GUI, but that has also stalled, so now new features are being added anywhere
4292026-02-12T16:41:55 <sipa> it is not just a question of what technology is best, but also what people want to work on, sadly
4302026-02-12T16:42:11 *** Emc53 <Emc53!~Emc99@212.129.80.131> has joined #bitcoin-core-dev
4312026-02-12T16:42:15 <sliv3r__> Is there any tracking issue or resource that lists the implemented and missing features for both new and old GUI?
4322026-02-12T16:42:20 <fjahr> sipa: so rust gui?
4332026-02-12T16:42:34 <sipa> fjahr: can you vibecode that?
4342026-02-12T16:42:53 <fjahr> sipa: consider it done
4352026-02-12T16:43:07 <achow101> fjahr: if it can work over ipc, i don't see why not
4362026-02-12T16:43:14 <cfields_> fjahr: that becomes an actual possibility if good ipc api emerges...
4372026-02-12T16:43:34 <johnny9dev> it would also be good to get an understanding of what would make developing the current gui more manageable or why it feels like its such a burden
4382026-02-12T16:43:37 <achow101> as long as others are okay with us shipping it under the bitcoin core banner
4392026-02-12T16:43:51 <dergoegge> is the need for IPC actually documented somewhere? don't see why that is such a hard requirement
4402026-02-12T16:43:57 <hebasto> furszy: I was saying not about my intetntion but about what I believe is good for the users and developers
4412026-02-12T16:44:36 <hebasto> important detail that QML-based GUI was designed by designers
4422026-02-12T16:44:43 <achow101> dergoegge: I don't believe so
4432026-02-12T16:45:07 <dergoegge> Can it summarized quickly here?
4442026-02-12T16:45:19 <Sjors[m]1> dergoegge: IPC has the potential of actually being acceptably fast for a UI
4452026-02-12T16:45:48 <Sjors[m]1> Although we probably won't get 120 frames per second on mobile :-)
4462026-02-12T16:45:51 <achow101> but just as a (very) old example, armory resorted to reading the blocksdir rather than relying on rpc
4472026-02-12T16:46:02 <sipa> i think the IPC relevance here is just that if we'd force our own GUI to use the IPC, we'll necessarily also make it easier for external projects to build their own GUI against the same interface
4482026-02-12T16:46:05 <achow101> because rpc was slow to respond
4492026-02-12T16:46:15 <Sjors[m]1> Regarding rust and IPC: that's being very actively tested for the Mining interface.
4502026-02-12T16:46:22 <achow101> and rpc polling just kinda sucks
4512026-02-12T16:46:39 *** Emc99 <Emc99!~Emc99@212.129.77.67> has quit IRC (Ping timeout: 272 seconds)
4522026-02-12T16:46:50 <sipa> i don't think RPC for a GUI is all that interesting; it's not great for it - and making a good RPC GUI interface is probably harder than creating an IPC interface from scratch + GUI from scratch that uses it
4532026-02-12T16:46:51 <Sjors[m]1> And with libmultiprocess using IPC for a c++ client is a piece of cake.
4542026-02-12T16:46:52 <dergoegge> RPC is not slow anymore
4552026-02-12T16:47:09 <dergoegge> as in the json-rpc overhead is not noticeable if you click a button
4562026-02-12T16:47:17 <achow101> and rpc did not (does not?) provide all of the necessary data
4572026-02-12T16:47:21 <furszy> hebasto: I think we are in a similar spot to when we were doing the projects board and voting for them. Everyone who feel this is important should sign up to work on it. Otherwise we will stall again.
4582026-02-12T16:47:29 <dergoegge> what data is missing
4592026-02-12T16:47:43 <dergoegge> we can add that and it'd be less work than all of IPC
4602026-02-12T16:47:48 <Sjors[m]1> Adding data to RPC shouldn't be the bottleneck.
4612026-02-12T16:48:13 <achow101> don't remember off the top of my head, it's been 10 years
4622026-02-12T16:48:16 <fjahr> johnny9dev: Would it be fair to say that the QML project is suffering from too high expectations and that is hindering it getting towards the finish line? E.g. if you were not trying to achieve everything exactly as in the design docs would you be done quicker?
4632026-02-12T16:48:34 <Sjors[m]1> But in the UI you often need push based stuff, like a notification when a transaction confirms. You can do that with multiple long poll RPC requests, but it's cleaner with IPC.
4642026-02-12T16:49:34 <dergoegge> Why does polling suck? because it's not optimal from a eng perspective? I don't think users would care
4652026-02-12T16:50:04 <fanquake> fjahr: I think the expectations are just to implement the features we currently have, so it'd be a drop-in replacement?
4662026-02-12T16:50:15 <hebasto> fjahr: once we agreed on the including more dependencies guix scripts without sacrificing security of bitcoind, the QML-based GUI could be released in v32.0
4672026-02-12T16:50:47 <dergoegge> achow101: so perhaps it's not even an issue? the wallet and node work just fine through the cli, so I don't see how RPCs wouldn't be good enough for a gui
4682026-02-12T16:51:04 <achow101> but the general issue is that the gui wants to be notified/get a signal when things like a block or transaction arrive to the wallet that needs to be shown to the user. for something like transactions, there's no way to ask rpc essentially "what has changed since I last polled", but rather it has to be "give me all of the wallet transactions and then I need to diff this response with the last one"
4692026-02-12T16:51:33 <hebasto> ^ right
4702026-02-12T16:51:34 <sipa> dergoegge: i think these are questions that need to be answered by people working on the GUI, not in this meeting
4712026-02-12T16:51:36 <achow101> and then we also run into limitations like listtransactions doesn't return all tranasctions, and asking it to do that every time can actually be quite slow
4722026-02-12T16:51:36 <fjahr> fanquake: but it also has this beautiful UI that was designed and I guess that adds overhead
4732026-02-12T16:51:47 <dergoegge> All I'm saying is that if people want to build a nice gui today, it is possible. It's just that almost no one wants to actually do the work
4742026-02-12T16:52:02 <fanquake> fjahr: sure. It has also been 4 or 5 years though?
4752026-02-12T16:52:27 *** aleggg <aleggg!~aleggg@189.110.152.194> has quit IRC (Remote host closed the connection)
4762026-02-12T16:52:28 <achow101> dergoegge: probably because there is currently a gui, so why work to create something that's worse
4772026-02-12T16:52:29 <fjahr> fanquake: yeah, just looking for potential shortcuts to the finish line ;)
4782026-02-12T16:52:36 <sipa> dergoegge: it's possible, but i think that's an unfair conclusion
4792026-02-12T16:53:35 <fjahr> (I also don't know if the original design get's further changes, the design community is quite active)
4802026-02-12T16:53:39 <fanquake> I guess if there's a heap of devs here who haven't contributed to QML in the last 4-5 years, but would like to actively work on it now, and that means we ship it in 32, and replace that current widgets based GUI, that is some clarity. Is that possible?
4812026-02-12T16:54:05 <achow101> fanquake: does it need to use IPC?
4822026-02-12T16:55:15 <fanquake> I think that would be best (even if that means it takes longer), otherwise we haven't improved things architectural, or started building what is needed for external applications to build the same type of applications
4832026-02-12T16:55:22 <hebasto> QML GUI for 32.0 may be based on internal interfaces only
4842026-02-12T16:56:04 <Sjors[m]1> What hebasto says makes sense to me. Once we have QML, we can redesign the interface and then later make it public facing.
4852026-02-12T16:56:11 <achow101> fanquake: sure, but doing that requires us to actually finish doing multiprocess
4862026-02-12T16:56:30 <achow101> which seems to be currently focused a lot more on supporting mining
4872026-02-12T16:56:34 <fanquake> achow101: only to the extent that we have done for the mining interface right? Given that is currently shipped and useable
4882026-02-12T16:57:02 <fjahr> 3 minutes left...
4892026-02-12T16:57:20 <Sjors[m]1> We've made quite a bit of progress on fine-tuning libmultiprocess since v30.
4902026-02-12T16:57:28 *** luke-jr <luke-jr!~luke-jr@user/luke-jr> has quit IRC (Read error: Connection reset by peer)
4912026-02-12T16:57:36 <sipa> i think being restricted to clean internal interfaces is 90% of the work of making it IPC-capable?
4922026-02-12T16:58:03 *** luke-jr <luke-jr!~luke-jr@user/luke-jr> has joined #bitcoin-core-dev
4932026-02-12T16:58:06 *** sr_gi <sr_gi!~sr_gi@46.231.244.218> has quit IRC (Quit: Client closed)
4942026-02-12T16:58:19 <Sjors[m]1> sipa: not necessarily, IIRC there's some stuff that doesn't perform well with the IPC overhead.
4952026-02-12T16:58:25 <Sjors[m]1> So that needs to be redesigned.
4962026-02-12T16:58:41 <achow101> fanquake: I think it'll be more complicated? it will have to launch bitcoind in the background and do process management stuff?
4972026-02-12T16:58:46 *** sr_gi <sr_gi!~sr_gi@46.231.244.218> has joined #bitcoin-core-dev
4982026-02-12T16:58:51 <hebasto> Sjors[m]1: due to latency?
4992026-02-12T16:58:52 *** aleggg <aleggg!~aleggg@189.110.152.194> has joined #bitcoin-core-dev
5002026-02-12T16:59:12 <Sjors[m]1> hebasto: probably due to going back and forth too much. But this hasn't been tested recently.
5012026-02-12T16:59:20 <sipa> ok fair
5022026-02-12T16:59:28 *** furszy <furszy!~furszy@user/furszy> has quit IRC (Ping timeout: 265 seconds)
5032026-02-12T16:59:35 <fjahr> Anything else that needs to be shared? Feature freeze is in 2 weeks.
5042026-02-12T16:59:36 <Sjors[m]1> We also left out process spawning for mining, so that's not battletested.
5052026-02-12T16:59:58 <achow101> I think we should defer the action of deprecation to after we can yell at each other in person
5062026-02-12T17:00:06 <fjahr> (feel free to continue the GUI discussion of course but I will finish the meeting)
5072026-02-12T17:00:18 <pinheadmz_> The gui discussion will never end
5082026-02-12T17:00:24 <fjahr> #endmeeting
5092026-02-12T17:00:24 <corebot> fjahr: Meeting ended at 2026-02-12T17:00+0000
5102026-02-12T17:00:25 <corebot> fjahr: Raw log: https://achow101.com/ircmeetings/2026/bitcoin-core-dev.2026-02-12_16_00.log.json
5112026-02-12T17:00:26 <corebot> fjahr: Formatted log: https://achow101.com/ircmeetings/2026/bitcoin-core-dev.2026-02-12_16_00.log.html
5122026-02-12T17:00:27 <corebot> fjahr: Minutes: https://achow101.com/ircmeetings/2026/bitcoin-core-dev.2026-02-12_16_00.html
5132026-02-12T17:00:28 <fjahr> but this meeting does
5142026-02-12T17:00:49 *** Emc53 <Emc53!~Emc99@212.129.80.131> has quit IRC (Quit: Client closed)
5152026-02-12T17:01:06 <Sjors[m]1> I made a note to take QML GUI for a spin, probably after the branch-off. Keep it freshly rebased :-)
5162026-02-12T17:01:10 *** andytoshi <andytoshi!~apoelstra@user/andytoshi> has quit IRC (Ping timeout: 245 seconds)
5172026-02-12T17:01:16 <hodlinator> (not sure if it was a serious suggestion, but starting to mix in Rust for the GUI would risk eventually leading to a Frankenstein monster with BDK and Bitcoin Core Kernel dependencies both pulled in and duplicating functionality in incompatible ways, or building/maintaining our own Rust-Bitcoin-Core lib).
5182026-02-12T17:01:22 *** andytoshi <andytoshi!~apoelstra@user/andytoshi> has joined #bitcoin-core-dev
5192026-02-12T17:01:39 <hebasto> cfields_: did I understand you correctly that you have a solution for #34569?
5202026-02-12T17:01:40 <corebot> https://github.com/bitcoin/bitcoin/issues/34569 | build: Qt depends build broken with GCC 16 · Issue #34569 · bitcoin/bitcoin · GitHub
5212026-02-12T17:01:44 <pinheadmz_> Sjors[m]1: the thing is if you wanna take it for a spin you have to pull Johnny's branch
5222026-02-12T17:01:56 <pinheadmz_> Main branch doesn't even display addresses
5232026-02-12T17:02:08 <Sjors[m]1> hodlinator: we'll probably stick to QML, but I could imagine said Frankenstein to be less total code than all of QT that we pull in now
5242026-02-12T17:02:28 <pinheadmz_> https://github.com/bitcoin-core/gui-qml/issues/496
5252026-02-12T17:02:44 <fjahr> hodlinator: it was tongue in cheek of course but it would attract contributors. That doesn't mean it would give up the goal of the bitcoin core project to keep dependencies to a minimum if that were to be seriously considered.
5262026-02-12T17:02:44 <cfields_> hebasto: I have a few patches for qt. Can't remember if I had it totally fixed or not. Looking at them now.
5272026-02-12T17:02:45 *** furszy <furszy!~furszy@104.128.239.93> has joined #bitcoin-core-dev
5282026-02-12T17:03:11 *** twistedline <twistedline!~bitcoin@1tbit.com> has quit IRC (Ping timeout: 252 seconds)
5292026-02-12T17:03:21 <cfields_> hebasto: one reason I didn't PR is because a few of the patches are just backports and another reasonable solution would be to just bump qt in depends. Is there a reason we're still on such an old release?
5302026-02-12T17:03:56 <hebasto> yes, I was going to push my branch for Qt 6.10
5312026-02-12T17:04:28 <hebasto> the only reason was compiler requirements for Windows binaries
5322026-02-12T17:04:47 *** arejula27 <arejula27!~arejula27@user/arejula27> has joined #bitcoin-core-dev
5332026-02-12T17:04:55 <cfields_> Yeah, I think that has the fixes for gcc as well. Most of them anyway.
5342026-02-12T17:05:47 <hebasto> I'll test gcc 16 with Qt 6.10 then
5352026-02-12T17:05:56 <cfields_> Either way, bumping would mean carrying fewer patches. So +1 for doing that first.
5362026-02-12T17:07:55 <hebasto> okay, let me brush it up and push
5372026-02-12T17:08:09 *** memset <memset!~memset@gateway/tor-sasl/memset> has quit IRC (Remote host closed the connection)
5382026-02-12T17:08:27 *** memset <memset!~memset@gateway/tor-sasl/memset> has joined #bitcoin-core-dev
5392026-02-12T17:08:50 <cfields_> hebasto: I can easily test now if you have a commit to bump. IIRC it meant fixing/dropping some of our existing patches as well.
5402026-02-12T17:09:37 *** memset <memset!~memset@gateway/tor-sasl/memset> has quit IRC (Remote host closed the connection)
5412026-02-12T17:11:21 *** arejula27 <arejula27!~arejula27@user/arejula27> has quit IRC (Ping timeout: 272 seconds)
5422026-02-12T17:13:33 *** memset <memset!~memset@gateway/tor-sasl/memset> has joined #bitcoin-core-dev
5432026-02-12T17:22:33 *** sr_gi <sr_gi!~sr_gi@46.231.244.218> has quit IRC (Quit: Client closed)
5442026-02-12T17:27:05 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has quit IRC (Read error: Connection reset by peer)
5452026-02-12T17:29:34 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has quit IRC (Quit: l0rinc)
5462026-02-12T17:29:44 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has joined #bitcoin-core-dev
5472026-02-12T17:33:37 *** dzxzg <dzxzg!~dzxzg@user/dzxzg> has quit IRC (Ping timeout: 264 seconds)
5482026-02-12T17:33:48 <bitcoin-git> [qa-assets] murchandamus opened pull request #255: Add initial corpus for bnb_finds_min_waste (main...2026-02-initial-bnb_finds_min_waste) https://github.com/bitcoin-core/qa-assets/pull/255
5492026-02-12T17:38:07 *** eugenesiegel <eugenesiegel!~eugenesie@user/eugenesiegel> has quit IRC (Quit: Client closed)
5502026-02-12T17:39:45 <bitcoin-git> [bitcoin] andrewtoth opened pull request #34576: threadpool: add SubmitMany (master...threadpool_submitmany) https://github.com/bitcoin/bitcoin/pull/34576
5512026-02-12T17:40:16 *** twistedline <twistedline!~bitcoin@1tbit.com> has joined #bitcoin-core-dev
5522026-02-12T17:43:41 *** eugenesiegel <eugenesiegel!~eugenesie@user/eugenesiegel> has joined #bitcoin-core-dev
5532026-02-12T17:45:52 *** twistedline <twistedline!~bitcoin@1tbit.com> has quit IRC (Remote host closed the connection)
5542026-02-12T17:46:53 *** Guest35 <Guest35!~Guest35@102.90.117.94> has joined #bitcoin-core-dev
5552026-02-12T17:47:04 *** twistedline <twistedline!~bitcoin@1tbit.com> has joined #bitcoin-core-dev
5562026-02-12T17:51:25 *** Guest35 <Guest35!~Guest35@102.90.117.94> has quit IRC (Client Quit)
5572026-02-12T17:57:07 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has quit IRC (Read error: Connection reset by peer)
5582026-02-12T17:59:45 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has joined #bitcoin-core-dev
5592026-02-12T18:23:25 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has joined #bitcoin-core-dev
5602026-02-12T18:34:51 *** musaHaruna <musaHaruna!uid732742@id-732742.hampstead.irccloud.com> has quit IRC (Quit: Connection closed for inactivity)
5612026-02-12T18:40:45 *** neonrooks <neonrooks!~neonrooks@user/neonrooks> has joined #bitcoin-core-dev
5622026-02-12T18:41:52 *** neonrooks <neonrooks!~neonrooks@user/neonrooks> has quit IRC (Client Quit)
5632026-02-12T18:57:11 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has quit IRC (Read error: Connection reset by peer)
5642026-02-12T18:57:26 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has joined #bitcoin-core-dev
5652026-02-12T18:57:32 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has quit IRC (Quit: l0rinc)
5662026-02-12T18:58:15 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has joined #bitcoin-core-dev
5672026-02-12T19:02:51 <darosior4> For the record, i'd like to say that IPC is in no way a requirement for a decent GUI. Using RPC is just fine, despite the inconsistent and often-breaking API (and even that is easier to fix than trying to come up with yet another moonshot IPC interface). I don't know how it came to be considered as such, and it frankly shows a clear disconnect with
5682026-02-12T19:02:52 <darosior4> how Bitcoin is actually being used today. Better, less laggy, GUIs than the Bitcoin Core GUI exist today that use RPC! This is incredibly disingenuous to try and claim otherwise.
5692026-02-12T19:02:52 <darosior4> That is not to say i am unilaterally in favour of removing the GUI, i think it's a more complicated topic, in particular with regards to interactions with the wallet and migration of existing users. I have more thoughts i will share, but just wanted to say i hope we can do better as a group at having discussions on the directions of the project
5702026-02-12T19:02:52 <darosior4> than camping on pre-conceived positions and trying to uncritically accept any semblance of argument that justifies our position.
5712026-02-12T19:07:13 <sipa> darosior4: i wasn't aware that any RPC-based GUIs for the Bitcoin Core wallet existed?
5722026-02-12T19:07:40 <sipa> (or any non-Bitcoin-Core GUIs at all, for that matter)
5732026-02-12T19:08:32 *** dzxzg <dzxzg!~dzxzg@user/dzxzg> has joined #bitcoin-core-dev
5742026-02-12T19:09:47 <sipa> if you're referring to other *wallets* that use RPC to communicate with Bitcoin Core, which include their own GUI, that's not a fair comparison i think
5752026-02-12T19:09:53 <jarolrod> ð
5762026-02-12T19:10:16 <darosior4> Liana is an example using the Bitcoin Core wallet, Sparrow is an example using a separate wallet but a direct RPC connection, virtually any other wallet in common use today is an example using an Electrum server as middleware (sometimes even locally, see for instance BWT).
5772026-02-12T19:10:50 <darosior4> sipa: what is the expectation for a Bitcoin Core GUI other than being able to use Bitcoin through a graphical user interface?
5782026-02-12T19:11:01 *** laanwj <laanwj!~laanwj@user/laanwj> has quit IRC (Ping timeout: 255 seconds)
5792026-02-12T19:11:09 *** b10c[m] <b10c[m]!~b10cmatri@2620:6e:a000:ce11::4d> has quit IRC (Ping timeout: 260 seconds)
5802026-02-12T19:11:09 *** BlueMattTest1 <BlueMattTest1!~test-acct@2620:6e:a000:ce11::c> has quit IRC (Ping timeout: 260 seconds)
5812026-02-12T19:11:09 *** bitcoin-git <bitcoin-git!~bitcoin-g@2620:6e:a000:ce11::21> has quit IRC (Ping timeout: 260 seconds)
5822026-02-12T19:11:34 *** BlueMattMtrxBot <BlueMattMtrxBot!~bluemattm@2620:6e:a000:ce11::44> has quit IRC (Ping timeout: 256 seconds)
5832026-02-12T19:11:44 *** Murch[m] <Murch[m]!~murch@2620:6e:a000:ce11::1b> has quit IRC (Ping timeout: 260 seconds)
5842026-02-12T19:11:53 <sipa> darosior4: being able to use/manage a Bitcoin Core wallet
5852026-02-12T19:12:00 <sipa> if not, you can just use other wallet software
5862026-02-12T19:13:21 <darosior4> I think the line is blurry because common other wallet software use a Bitcoin Core watchonly wallet in the background, but i agree backward-compatibility with the Bitcoin Core wallet format is the actual torny issue here.
5872026-02-12T19:13:43 <_aj_> being able to observe/control the node state? (connected to peers, how many blocks synced)
5882026-02-12T19:13:54 <sliv3r__> not only wallet, node control through a gui is important
5892026-02-12T19:14:06 <darosior4> sliv3r__: control of what for instance?
5902026-02-12T19:14:29 <darosior4> I think changing technical configurations of the node should not be a priority for a GUI targetting non-technical users.
5912026-02-12T19:15:10 <darosior4> sipa: To eliminate those cases of people merely using watchonly wallet, would you think it's fair to reduce the scope to "being able to use/manage a Bitcoin Core hot wallet"?
5922026-02-12T19:16:22 <sipa> i feel like we're missing a distinction between "a GUI that is a wallet" and "a GUI to control the Bitcoin Core wallet"
5932026-02-12T19:16:35 <sliv3r__> darosior4: even shutting down the node, changing the network, changing net config like ports, pruning, etc.
5942026-02-12T19:17:14 <sliv3r__> we cannot ask all users to go and play with a config file
5952026-02-12T19:17:16 <darosior4> sliv3r__: that falls under wallet configuration to be honest
5962026-02-12T19:17:44 <sliv3r__> darosior4: pruning your node falls under wallet configuration? I fail to see how
5972026-02-12T19:17:48 <sipa> darosior4: i'm not very familiar with sparrow, but from what i understand, i would call it a separatey wallet - which happens to delegate some tasks to a bitcoin core wallet which it uses in a limited manner
5982026-02-12T19:18:14 <sipa> it's not something you can use to manage an existing bitcoin core wallet.dat file, i believe?
5992026-02-12T19:18:27 <sipa> and it's not something a bitcoin core wallet.dat file could be converted/migrated to
6002026-02-12T19:18:43 <darosior4> sliv3r__: this "we cannot" language i think is a big hindrance to having a proper discussion. Of course everybody think that good things are desirable, duh, there is just disagreement about priorities and it appears that people that do eat the cost of those decisions (not me, to be clear) aren't happy bearing those anymore
6012026-02-12T19:19:04 <darosior4> sipa: that is correct, yes
6022026-02-12T19:19:23 <sipa> right, so i don't think that it using RPC is relevant in this discussion
6032026-02-12T19:19:39 <darosior4> Some migration paths were discussed, but i don't think there is anything that could be reasonably considered a "recommended migration path out of Bitcoin Core"
6042026-02-12T19:19:44 <sipa> it's a separate wallet, not a GUI for the Bitcoin Core wallet
6052026-02-12T19:25:20 <darosior4> sipa: i don't think this is irrelevant to the discussion, because one way people have discussed this topic in the past is the intention behind the Bitcoin Core GUI is to "make Bitcoin accessible to non-technical users". You go to bitcoincore.org, download bitcoin, run bitcoin and it just works without moving parts. However i don't think this
6062026-02-12T19:25:20 <darosior4> position is really compelling anymore in 2026, and i think what you point to is the real important part of the discussion. But the fact that there exists other simple ways (really, superior ways) of using Bitcoin (as in having a wallet) backed by a Bitcoin Core full node is not irrelevant to this discussion.
6072026-02-12T19:27:07 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has quit IRC (Read error: Connection reset by peer)
6082026-02-12T19:27:35 <sipa> I really feel that's a separate discussion.
6092026-02-12T19:28:10 <sipa> Not an irrelevant one, but a largely orthogonal one, because you're really talking about creating what I'd say is a new, more modern, possibly simpler, wallet - with its own GUI.
6102026-02-12T19:28:53 <sliv3r__> darosior4: so to understand your position, you think that the best approach is to get rid of the gui and let non-tech users use some other software to interact with their node? I feel we are mixing wallet gui and node gui
6112026-02-12T19:29:03 <sipa> My concern w.r.t. deprecating the GUI is that it leaves people who _want to use the Bitcoin Core wallet_, for whatever reason - without a migration path.
6122026-02-12T19:29:41 <darosior4> It is indeed a separate discussion, because the argument of keeping the Bitcoin Core GUI as the sole accessible way of using the Bitcoin network has not much to it, and now the real remaining question is: quid of existing users of the Bitcoin Core wallet?
6132026-02-12T19:29:43 <sipa> If the goal is not that, but "providing non-technical users with a GUI to manage their BTC backed by Bitcoin Core", just use Sparrow?
6142026-02-12T19:29:45 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has joined #bitcoin-core-dev
6152026-02-12T19:29:55 <sipa> they seem to be better at it
6162026-02-12T19:30:00 *** BlueMattMtrxBot <BlueMattMtrxBot!~bluemattm@2620:6e:a000:ce11::44> has joined #bitcoin-core-dev
6172026-02-12T19:30:08 *** bitcoin-git <bitcoin-git!~bitcoin-g@2620:6e:a000:ce11::21> has joined #bitcoin-core-dev
6182026-02-12T19:30:19 *** BlueMattTest1 <BlueMattTest1!~test-acct@2620:6e:a000:ce11::c> has joined #bitcoin-core-dev
6192026-02-12T19:30:45 *** Murch[m] <Murch[m]!~murch@2620:6e:a000:ce11::1b> has joined #bitcoin-core-dev
6202026-02-12T19:30:49 <darosior4> sliv3r__: i have not said that. In fact i explicitly stated that i was not signaling in favour of removing the GUI in my last message.
6212026-02-12T19:31:31 <sliv3r__> I missunderstood then sry
6222026-02-12T19:32:26 <darosior4> No worries. I started writing down my thought in an editor to share here, but it's turning into an essay, so i think i'll open a Delving thread about this and hopefully people will chime in
6232026-02-12T19:33:35 *** eugenesiegel <eugenesiegel!~eugenesie@user/eugenesiegel> has quit IRC (Quit: Client closed)
6242026-02-12T19:34:15 <hodlinator> Sjors[m]1 & fjahr: I can really see the appeal to devs of doing the official GUI in Rust. Again, I'm concerned about duplicating effort with BDK or using the actual BDK / rust bitcoin and running into a bunch of inconsistencies. But it might be worth the mess in order to get real traction. Time to fork Liana. ;)
6252026-02-12T19:34:16 *** laanwj <laanwj!~laanwj@user/laanwj> has joined #bitcoin-core-dev
6262026-02-12T19:36:54 *** b10c[m] <b10c[m]!~b10cmatri@2620:6e:a000:ce11::4d> has joined #bitcoin-core-dev
6272026-02-12T19:44:18 *** memset <memset!~memset@gateway/tor-sasl/memset> has quit IRC (Remote host closed the connection)
6282026-02-12T19:44:49 *** memset <memset!~memset@gateway/tor-sasl/memset> has joined #bitcoin-core-dev
6292026-02-12T19:52:31 *** twistedline <twistedline!~bitcoin@1tbit.com> has quit IRC (Ping timeout: 264 seconds)
6302026-02-12T19:52:42 <bitcoin-git> [bitcoin] furszy opened pull request #34577: http: fix submission during shutdown race (master...2026_http_submission_error) https://github.com/bitcoin/bitcoin/pull/34577
6312026-02-12T19:56:24 *** twistedline <twistedline!~bitcoin@1tbit.com> has joined #bitcoin-core-dev
6322026-02-12T20:00:30 *** dodo <dodo!~dodo@user/dodo> has quit IRC (Quit: dodo)
6332026-02-12T20:01:31 *** dodo <dodo!~dodo@user/dodo> has joined #bitcoin-core-dev
6342026-02-12T20:27:05 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has quit IRC (Read error: Connection reset by peer)
6352026-02-12T20:44:36 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has joined #bitcoin-core-dev
6362026-02-12T20:53:39 *** abubakarsadiq <abubakarsadiq!uid602234@id-602234.hampstead.irccloud.com> has quit IRC (Quit: Connection closed for inactivity)
6372026-02-12T20:57:06 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has quit IRC (Read error: Connection reset by peer)
6382026-02-12T20:57:27 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has joined #bitcoin-core-dev
6392026-02-12T21:26:52 *** w0xlt <w0xlt!~w0xlt@103.251.26.187> has quit IRC (Ping timeout: 244 seconds)
6402026-02-12T21:41:30 *** kevkevin <kevkevin!~kevkevin@209.242.60.195> has quit IRC (Remote host closed the connection)
6412026-02-12T21:46:14 *** w0xlt <w0xlt!~w0xlt@198.44.129.110> has joined #bitcoin-core-dev
6422026-02-12T21:55:01 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has quit IRC (Quit: l0rinc)
6432026-02-12T21:56:08 *** luke-jr <luke-jr!~luke-jr@user/luke-jr> has quit IRC (Read error: Connection reset by peer)
6442026-02-12T21:56:14 *** luke-jr_ <luke-jr_!~luke-jr@user/luke-jr> has joined #bitcoin-core-dev
6452026-02-12T21:57:03 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has quit IRC (Read error: Connection reset by peer)
6462026-02-12T21:57:19 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has joined #bitcoin-core-dev
6472026-02-12T22:11:05 <yancy> Just catching up on the meeting discussion. Like 20 years ago, a large C project I worked on just surfaced a REST API, so any web coders could make APIs. That was a long time ago, but I'm surprised that there isn't a discussion about how to make a webpage GUI. I think keeping an abstraction of the API vs the GUI is nice since it could potentially be agnostic to how the GUI is built, and by who.
6482026-02-12T22:12:49 *** memset <memset!~memset@gateway/tor-sasl/memset> has quit IRC (Remote host closed the connection)
6492026-02-12T22:13:24 *** memset <memset!~memset@gateway/tor-sasl/memset> has joined #bitcoin-core-dev
6502026-02-12T22:14:34 *** bugs_ <bugs_!~bugs@user/bugs/x-5128603> has quit IRC (Quit: Leaving)
6512026-02-12T22:18:45 <yancy> I guess that was like 2012 or something so maybe not "20 years" :P
6522026-02-12T22:21:33 <_aj_> yancy: that seems kind-of appealing
6532026-02-12T22:27:07 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has quit IRC (Read error: Connection reset by peer)
6542026-02-12T22:27:21 <darosior4> Given who we'd care about supporting (afaiu) are users with private key enabled Bitcoin Core wallets, on the contrary that seems to be an unnecessary increase in the attack surface compared to a standalone software?
6552026-02-12T22:27:25 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has joined #bitcoin-core-dev
6562026-02-12T22:28:17 <_aj_> if you have a private key on the node that you're running a gui from already, i don't think so?
6572026-02-12T22:28:25 *** darosior4 is now known as darosior
6582026-02-12T22:28:58 <darosior> Presumably you are doing other things than managing your money on this web browser
6592026-02-12T22:31:25 <_aj_> i don't feel like shooting down an idea while it's still being brainstormed is very helpful. there are half a dozen different ways you could manage that risk.
6602026-02-12T22:32:19 <darosior> Fair enough, i think it's a concern worth being raised but i didn't mean to shoot down the idea
6612026-02-12T22:35:08 <_aj_> (a) don't run your wallet on a mixed-use system; (b) bundle a dedicated broweser engine with the app; (c) use a dedicated browser for interfacing with bitcoin; (d) use a dedicated wallet gui like sparrow for the wallet, and use the bitcoin gui for managing the node; (e) rely on XSS/etc protections -- if your system as a whole is compromised, you're screwed no matter what anyway
6622026-02-12T22:36:06 <_aj_> "would that even work in a way that doesn't just completely suck for both devs and users"
6632026-02-12T22:41:00 <bitcoin-git> [bitcoin] hebasto opened pull request #34578: depends: Update Qt to version 6.10.2 (master...260212-qt6.10) https://github.com/bitcoin/bitcoin/pull/34578
6642026-02-12T22:56:58 *** memset <memset!~memset@gateway/tor-sasl/memset> has quit IRC (Remote host closed the connection)
6652026-02-12T22:57:17 *** memset <memset!~memset@gateway/tor-sasl/memset> has joined #bitcoin-core-dev
6662026-02-12T23:22:43 *** kevkevin <kevkevin!~kevkevin@2607:fb90:9b11:93c:347e:2e7c:64b:8532> has joined #bitcoin-core-dev
6672026-02-12T23:27:03 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has quit IRC (Read error: Connection reset by peer)
6682026-02-12T23:29:41 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has joined #bitcoin-core-dev
6692026-02-12T23:32:44 *** PaperSword <PaperSword!~Thunderbi@securemail.qrsnap.io> has quit IRC (Quit: PaperSword)
6702026-02-12T23:41:34 *** kevkevin <kevkevin!~kevkevin@2607:fb90:9b11:93c:347e:2e7c:64b:8532> has quit IRC (Remote host closed the connection)
6712026-02-12T23:50:40 *** kevkevin <kevkevin!~kevkevin@2607:fb90:9b11:93c:347e:2e7c:64b:8532> has joined #bitcoin-core-dev
6722026-02-12T23:54:54 *** kevkevin <kevkevin!~kevkevin@2607:fb90:9b11:93c:347e:2e7c:64b:8532> has quit IRC (Ping timeout: 245 seconds)
6732026-02-12T23:57:05 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has quit IRC (Read error: Connection reset by peer)
6742026-02-12T23:59:43 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has joined #bitcoin-core-dev