--- Log opened Fri Apr 19 00:00:26 2024
--- Day changed Fri Apr 19 2024
00:00 -!- the_mariner [~Thunderbi@2804:29b8:518d:a89:5c14:d15d:bf33:e0ae] has joined #bitcoin-core-dev
00:04 -!- the_mariner [~Thunderbi@2804:29b8:518d:a89:5c14:d15d:bf33:e0ae] has quit [Ping timeout: 255 seconds]
00:09 -!- ion- [ion-@user/ion-] has joined #bitcoin-core-dev
00:11 -!- jon_atack [~jonatack@user/jonatack] has joined #bitcoin-core-dev
00:13 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 264 seconds]
00:24 -!- Guyver2 [~Guyver@77-174-98-73.fixed.kpn.net] has joined #bitcoin-core-dev
00:28 -!- gribble [~gribble@bitcoin/bot/gribble] has quit [Remote host closed the connection]
00:28 -!- salvatoshi [~salvatosh@genymobile-2-6-86.fib.nerim.net] has joined #bitcoin-core-dev
00:35 -!- gribble [~gribble@bitcoin/bot/gribble] has joined #bitcoin-core-dev
00:35 -!- mode/#bitcoin-core-dev [+o gribble] by ChanServ
00:47 -!- javi404 [~quassel@2601:582:0:2c41:91ca:6895:2072:3474] has quit [Ping timeout: 260 seconds]
00:48 -!- javi404 [~quassel@2601:582:0:2c41:91ca:6895:2072:3474] has joined #bitcoin-core-dev
01:26 -!- ion- [ion-@user/ion-] has quit [Remote host closed the connection]
01:26 -!- ion- [ion-@user/ion-] has joined #bitcoin-core-dev
01:31 -!- Guest98 [~Guest98@178-143-34-211.static.orange.sk] has quit [Quit: Client closed]
01:44 -!- aleggg [~aleggg@189.58.252.13] has quit [Ping timeout: 256 seconds]
01:44 -!- aleggg [~aleggg@189.114.91.124] has joined #bitcoin-core-dev
01:47 -!- ion- [ion-@user/ion-] has quit [Remote host closed the connection]
01:55 -!- ion- [ion-@user/ion-] has joined #bitcoin-core-dev
01:56 -!- ion- [ion-@user/ion-] has quit [Remote host closed the connection]
02:01 -!- Guyver2 [~Guyver@77-174-98-73.fixed.kpn.net] has left #bitcoin-core-dev [Closing Window]
02:04 -!- ion- [ion-@user/ion-] has joined #bitcoin-core-dev
02:07 -!- salvatoshi [~salvatosh@genymobile-2-6-86.fib.nerim.net] has quit [Remote host closed the connection]
02:28 -!- BrandonOdiwuor [~BrandonOd@41.80.118.16] has joined #bitcoin-core-dev
02:45 -!- Chris_Stewart_5 [~Chris_Ste@185.141.119.176] has quit [Ping timeout: 268 seconds]
02:46 -!- Chris_Stewart_5 [~Chris_Ste@185.141.119.135] has joined #bitcoin-core-dev
02:48 -!- jon_atack [~jonatack@user/jonatack] has quit [Ping timeout: 264 seconds]
02:49 < bitcoin-git> [bitcoin] hebasto opened pull request #29910: Refactor `subprocess.hpp` to follow our conventions (master...240419-sp-win32) https://github.com/bitcoin/bitcoin/pull/29910
03:32 -!- the_mariner [~Thunderbi@179.180.142.244] has joined #bitcoin-core-dev
03:37 -!- the_mariner [~Thunderbi@179.180.142.244] has quit [Ping timeout: 264 seconds]
04:08 -!- furszy [~furszy@user/furszy] has changed host
04:16 -!- brunoerg [~brunoerg@2804:14c:3bfb:37:3d3f:a9ab:eacd:b52c] has quit [Remote host closed the connection]
04:20 -!- the_mariner [~Thunderbi@2804:7f7:e082:64b0:49cd:fbd8:38e3:46f4] has joined #bitcoin-core-dev
04:24 -!- Chris_Stewart_5 [~Chris_Ste@185.141.119.135] has quit [Ping timeout: 252 seconds]
04:26 -!- Chris_Stewart_5 [~Chris_Ste@185.141.119.165] has joined #bitcoin-core-dev
04:28 -!- ion- [ion-@user/ion-] has quit [Remote host closed the connection]
04:42 -!- ion- [ion-@user/ion-] has joined #bitcoin-core-dev
04:46 -!- ion- [ion-@user/ion-] has quit [Ping timeout: 256 seconds]
04:50 < fanquake> https://github.com/bitcoin-core/packaging/issues/226 - bitcoin-core 27.0 snap crashed on start
05:00 -!- ion- [ion-@user/ion-] has joined #bitcoin-core-dev
05:20 < bitcoin-git> [bitcoin] furszy opened pull request #29913: bugfix: update chainman best_header after block reconsideration (master...2024_fix_reconsiderblock_bestheader) https://github.com/bitcoin/bitcoin/pull/29913
05:24 -!- VonNaturAustreVe [~ne0h_@user/vonnaturaustreve] has joined #bitcoin-core-dev
05:26 -!- VonNaturAustreVe [~ne0h_@user/vonnaturaustreve] has quit [Client Quit]
05:27 -!- VonNaturAustreVe [~ne0h_@2804:14c:65d7:8ea5:1f:9d89:eb02:47a5] has joined #bitcoin-core-dev
05:27 -!- VonNaturAustreVe [~ne0h_@user/vonnaturaustreve] has changed host
05:44 -!- brunoerg [~brunoerg@2804:18:131:839f:d424:5843:4d1e:4706] has joined #bitcoin-core-dev
05:45 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 260 seconds]
05:54 -!- brunoerg_ [~brunoerg@2804:18:131:839f:ad80:f620:8607:7aca] has joined #bitcoin-core-dev
05:58 -!- brunoerg [~brunoerg@2804:18:131:839f:d424:5843:4d1e:4706] has quit [Ping timeout: 268 seconds]
06:18 -!- VonNaturAustreVe [~ne0h_@user/vonnaturaustreve] has quit [Quit: Leaving]
06:18 -!- BrandonOdiwuor [~BrandonOd@41.80.118.16] has quit [Ping timeout: 250 seconds]
06:37 -!- brunoerg_ [~brunoerg@2804:18:131:839f:ad80:f620:8607:7aca] has quit [Ping timeout: 268 seconds]
06:41 -!- abubakarsadiq [uid602234@id-602234.hampstead.irccloud.com] has joined #bitcoin-core-dev
06:43 -!- ion- [ion-@user/ion-] has quit [Remote host closed the connection]
06:43 -!- ion- [ion-@user/ion-] has joined #bitcoin-core-dev
06:59 -!- ion- [ion-@user/ion-] has quit [Remote host closed the connection]
07:11 < josie> git status 
07:12 < fanquake> nothing to commit, working tree clean
07:13 < josie> if only that were true... 
07:14 < sipa> git push upstream -d master
07:14 -!- preimage [~halosghos@user/halosghost] has joined #bitcoin-core-dev
07:15 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-dev
07:15 -!- ion- [ion-@user/ion-] has joined #bitcoin-core-dev
07:32 < josie> sipa: that's certainly one way to fix all the bugs
07:38 -!- brunoerg [~brunoerg@2804:14c:3bfb:37:18e:94af:4f47:207a] has joined #bitcoin-core-dev
07:39 -!- bugs_ [~bugs@user/bugs/x-5128603] has joined #bitcoin-core-dev
07:42 -!- brunoerg [~brunoerg@2804:14c:3bfb:37:18e:94af:4f47:207a] has quit [Remote host closed the connection]
07:43 -!- brunoerg [~brunoerg@2804:14c:3bfb:37:18e:94af:4f47:207a] has joined #bitcoin-core-dev
07:43 < _aj_> mightn't fix all the bugs, but should remove any merge conflicts?
07:43 -!- ion- [ion-@user/ion-] has quit [Ping timeout: 260 seconds]
07:55 -!- ion- [ion-@user/ion-] has joined #bitcoin-core-dev
08:02 -!- ion- [ion-@user/ion-] has quit [Ping timeout: 268 seconds]
08:15 -!- ion- [ion-@user/ion-] has joined #bitcoin-core-dev
08:20 -!- BrandonOdiwuor [~BrandonOd@41.80.117.179] has joined #bitcoin-core-dev
08:20 -!- ion- [ion-@user/ion-] has quit [Ping timeout: 268 seconds]
08:33 -!- ion- [ion-@user/ion-] has joined #bitcoin-core-dev
08:36 -!- ion- [ion-@user/ion-] has quit [Remote host closed the connection]
08:36 -!- ion- [ion-@user/ion-] has joined #bitcoin-core-dev
08:37 -!- ion- [ion-@user/ion-] has quit [Remote host closed the connection]
08:38 -!- ion- [ion-@user/ion-] has joined #bitcoin-core-dev
08:54 -!- ion- [ion-@user/ion-] has quit [Remote host closed the connection]
09:00 -!- preimage [~halosghos@user/halosghost] has quit [Ping timeout: 240 seconds]
09:12 -!- preimage [~halosghos@user/halosghost] has joined #bitcoin-core-dev
09:44 < bitcoin-git> [bitcoin] glozow closed pull request #29827: test: p2p: add test for rejected tx request logic (`m_recent_rejects` filter) (master...202404-test-p2p-check_rejected_tx_requests) https://github.com/bitcoin/bitcoin/pull/29827
10:15 -!- the_mariner [~Thunderbi@2804:7f7:e082:64b0:49cd:fbd8:38e3:46f4] has quit [Ping timeout: 256 seconds]
10:16 -!- the_mariner [~Thunderbi@2804:7f7:e082:64b0:49cd:fbd8:38e3:46f4] has joined #bitcoin-core-dev
10:26 < bitcoin-git> [bitcoin] instagibbs opened pull request #29915: test: Don't fetch orphan parent when parent is in orphanage (master...2024-04-parent_orphan_orphan_nofetch) https://github.com/bitcoin/bitcoin/pull/29915
10:29 -!- the_mariner [~Thunderbi@2804:7f7:e082:64b0:49cd:fbd8:38e3:46f4] has quit [Ping timeout: 268 seconds]
10:49 -!- ___nick___ [~quassel@cpc68290-cdif17-2-0-cust24.5-1.cable.virginm.net] has joined #bitcoin-core-dev
11:20 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 260 seconds]
11:21 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-dev
11:25 -!- the_mariner [~Thunderbi@2804:29b8:518d:a89:253a:a0fe:e49e:387b] has joined #bitcoin-core-dev
11:29 -!- the_mariner [~Thunderbi@2804:29b8:518d:a89:253a:a0fe:e49e:387b] has quit [Ping timeout: 256 seconds]
11:49 -!- jon_atack [~jonatack@user/jonatack] has joined #bitcoin-core-dev
11:49 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 268 seconds]
12:00 -!- preimage [~halosghos@user/halosghost] has quit [Quit: WeeChat 4.2.2]
12:08 < roasbeef> so we're seeing some weird behavior on testnet with bitcoin nodes, iiuc ppl are mining a ton of empty blocks, and occasionally we get an error that: ConnectBlock(): coinbase pays too much (actual=26389831 vs limit=26389830)
12:08 < roasbeef> searched the tracker, and closest I could find was: https://github.com/bitcoin/bitcoin/issues/7301 
12:09 < roasbeef> this ends up leading to a segfault 
12:10 < sipa> bitcoind segfaults?
12:10 < roasbeef> we've tried to reindex (mentioned as a solution in that issue), but then it still ends up choking on blocks later
12:11 < roasbeef> yes
12:11 < roasbeef> this is bitciond 26 
12:11 < achow101> Try 27?
12:12 < sipa> without a way to reproduce this is hard to investigate
12:12 < roasbeef> hehe these are connected to lnd nodes, and bitcoind 27 added breaking behavior in sendrawtransaction so we can't update those yet (we have v0.17.5 staged, should drop shortly), but thought this was exceptional enough that I should dig into it 
12:13 < roasbeef> eg it doesn't like this block: https://mempool.space/testnet/block/000000000000000f5fbf42eb4f16952c8dabc0282a63baee5f69fc6d4bdfb44d 
12:15 < roasbeef> sec pulling logs
12:15 < achow101> that looks valid
12:16 < Murch[m]> Is this v26.0 or v26.1?
12:17 < roasbeef> https://zerobin.org/?60bc7ed80b55cc3b#2whp4Kw9djngt62qNUmjqMNRxmt62XFb4qbLinbVhrad
12:17 <@gribble> https://github.com/bitcoin/bitcoin/issues/2 | Long-term, safe, store-of-value · Issue #2 · bitcoin/bitcoin · GitHub
12:18 -!- jarthur [~jarthur@user/jarthur] has joined #bitcoin-core-dev
12:18 < roasbeef> better one that shows the restart afterwards: https://zerobin.org/?979a92e4bc5edfae#k9Gsq8Yo1dQrUhEGkHfuHXxqYTCmBXPgojqkb9AiPGy
12:18 < roasbeef> Bitcoin Core version v26.0.0 (release build)
12:19 < achow101> that looks like it was a clean shut down, not a segfault?
12:19 < roasbeef> the logs don't capture it here, but we see a SIGSEGV
12:20 < roasbeef> this also isn't happening to all the nodes 
12:21 < roasbeef> another instance: https://zerobin.org/?3953ea1b17b89cef#8UBfbBX3iiinrTVRz3KG6XFBZzj8oqtX5b3pkFGbBmn3 
12:21 < sipa> last line is about loading block index, so it's segfaulting during startup?
12:21 <@gribble> https://github.com/bitcoin/bitcoin/issues/8 | RPC command to sign text with wallet private key · Issue #8 · bitcoin/bitcoin · GitHub
12:21 < achow101> my testnet node handled that block fine
12:22 < achow101> but it is 27.99
12:22 < sipa> i'm spinning up a 26.0 on testnet
12:26 < achow101> roasbeef: any chance of a coredump?
12:26 < roasbeef> lemmie see
12:27 < sipa> if it's reproducible after a restart, perhaps the datadir is useful to have
12:27 < achow101> (may contain keys and other private data, blah blah, share privately if you care)
12:27 < roasbeef> they're running in k8s, so the container can be wiped/re-created pretty quickly (re obtaining a core dump), can try to extract the state to run it on a normal host also 
12:27 < roasbeef> the datadir is persistent tho 
12:27 < roasbeef> just testnet, no wallet instance 
12:28 < sipa> roasbeef: if you restart bitcoind, does it immediately/quickly segfault again?
12:30 < roasbeef> after restart it'll go back to processing blocks to catch up, then will hit a problematic block and repeat the cycle 
12:33 < roasbeef> more logs that better show the crash loop: https://zerobin.org/?6106751e48551dca#4R5JJw4914MvxeL2Hyp67nnXoJt1c2ANweiapzigLR1R
12:33 <@gribble> https://github.com/bitcoin/bitcoin/issues/4 | Export/Import wallet in a human readable, future-proof format · Issue #4 · bitcoin/bitcoin · GitHub
12:34 < roasbeef> we're reindexing another instance, that one is nearly done
12:38 < sdaftuar> i appear to be seeing some of the same issues as roasbeef on my 23.0 testnet node
12:39 < roasbeef> ok we were able to get the core dump file
12:40 < sdaftuar> (no crashes on my node though, just seeing some of the same invalid blocks)
12:40 < sipa> sdaftuar: i'm thinking the invalid blocks may be legit
12:41 < sipa> (as in, someone is actually creating invalid blocks)
12:41 < achow101> I think the invalid blocks are expected
12:41 < instagibbs> right are we sure any of these blocks are actually valid?
12:41 < sdaftuar> oh i thought achow was saying that the block linked above looked valid? my node also thought it was invalid
12:43 < sdaftuar> sorry -- i misread my log, a block building on that one was invalid, never mind me
12:44 < achow101> roasbeef: post that somewhere, or email it?
12:47 -!- flooded [flooded@gateway/vpn/protonvpn/flood/x-43489060] has joined #bitcoin-core-dev
12:51 < Murch[m]> Could have something to do with this: https://twitter.com/0xB10C/status/1780212733805301931
12:51 -!- test_ [flooded@gateway/vpn/protonvpn/flood/x-43489060] has joined #bitcoin-core-dev
12:53 -!- flooded [flooded@gateway/vpn/protonvpn/flood/x-43489060] has quit [Ping timeout: 252 seconds]
12:53 < roasbeef> achow101: uploading to gdrive rn
12:55 < jon_atack> at first look git blaming the related code not seeing any recent (v26 era or later) relevant changes 
12:58 -!- szkl [uid110435@id-110435.uxbridge.irccloud.com] has joined #bitcoin-core-dev
12:58 < roasbeef> here's the core dump: https://drive.google.com/file/d/1N-0FZb4OG6nXLKE6DfgbDOUDi426XozM/view
12:59 < sipa> roasbeef: is this a release binary?
13:00 < roasbeef> yeah should be, we see this on start up: 2024-04-19T19:08:24Z Bitcoin Core version v26.0.0 (release build)
13:05 -!- ___nick___ [~quassel@cpc68290-cdif17-2-0-cust24.5-1.cable.virginm.net] has quit [Ping timeout: 260 seconds]
13:05 -!- hirish [~hirish@ip251.ip-178-33-19.eu] has quit [Ping timeout: 256 seconds]
13:06 -!- twistedline [~bitcoin@185.193.125.44] has quit [Remote host closed the connection]
13:06 -!- hirish [~hirish@ip251.ip-178-33-19.eu] has joined #bitcoin-core-dev
13:07 -!- twistedline [~bitcoin@c-73-172-209-62.hsd1.md.comcast.net] has joined #bitcoin-core-dev
13:13 -!- Talkless [~Talkless@mail.dargis.net] has joined #bitcoin-core-dev
13:13 -!- chungus [~chungus@130.44.132.180] has joined #bitcoin-core-dev
13:14 -!- chungus [~chungus@130.44.132.180] has quit [Client Quit]
13:15 -!- djkazic [~djkazic@130.44.132.180] has joined #bitcoin-core-dev
13:19 -!- djkazic [~djkazic@130.44.132.180] has quit [Client Quit]
13:23 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-dev
13:24 -!- jon_atack [~jonatack@user/jonatack] has quit [Ping timeout: 264 seconds]
13:26 < sipa> roasbeef: is there any chance you can share the whole datadir?
13:32 -!- BrandonOdiwuor [~BrandonOd@41.80.117.179] has quit [Ping timeout: 250 seconds]
13:51 -!- puchka [~puchka@185.203.122.229] has quit [Quit: leaving]
13:52 < roasbeef> sipa: sure
13:56 < roasbeef> have the cp command running, will take a bit testnet is like 40 GB now and I haz slow internet
14:00 < sipa> ok
14:02 -!- the_mariner [~Thunderbi@177.37.233.155] has joined #bitcoin-core-dev
14:13 -!- SpellChecker [~SpellChec@user/SpellChecker] has quit [Remote host closed the connection]
14:13 -!- SpellChecker [~SpellChec@user/SpellChecker] has joined #bitcoin-core-dev
14:26 -!- drnet [~drnet@185.89.163.206] has joined #bitcoin-core-dev
14:29 -!- the_mariner [~Thunderbi@177.37.233.155] has quit [Ping timeout: 252 seconds]
14:32 -!- Talkless [~Talkless@mail.dargis.net] has quit [Quit: Konversation terminated!]
14:35 < roasbeef> ok uploading to gdrive now 
14:38 < roasbeef> might take a few hours...
14:41 < achow101> Well that coredump was less than helpful
14:43 < achow101> Just to double check, what's the hash of the bitcoind you're using?
14:45 -!- Guest78 [~Guest78@77.68.55.89] has joined #bitcoin-core-dev
14:46 -!- Guest78 [~Guest78@77.68.55.89] has quit [Client Quit]
14:53 < roasbeef> achow101: binary hash?
14:54 < roasbeef> seeing if someone else on the team can upload the data dir, with my upload speed it'll take like 10 hrs at this rate 
14:55 < achow101> roasbeef: Yes, of the binary itself
14:57 < roasbeef> # sha256sum /opt/bitcoin-26.0/bin/bitcoind
14:57 < roasbeef> 6f33b7daa95984eb2d4cbf32070c28da66165d02da9997ce1264fcdd0820030a  /opt/bitcoin-26.0/bin/bitcoind
15:00 -!- jon_atack [~jonatack@user/jonatack] has joined #bitcoin-core-dev
15:01 < sipa> hmm, doesn't match my binary hash
15:01 < sipa> for the 26.0 release
15:02 < sipa> ab06620aadcf814c0ef8274566631a0428119f1f7e218566c689d535cb515f75  bitcoind
15:02 < achow101> Same
15:02 < achow101> That would explain why the coredump was useless
15:02 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 252 seconds]
15:03 < roasbeef> hmm was built off of: https://github.com/lightninglabs/docker-bitcoin-core/blob/master/26/Dockerfile
15:04 < roasbeef> there's someone else on the team that hit it with thier personal bitcoind nodes, which they claim to be just the binary from the release
15:08 < sipa> roasbeef: a coredump from them would be useful then
15:16 -!- blockdyor [~blockdyor@dynamic-adsl-94-34-196-193.clienti.tiscali.it] has quit [Quit: My iMac has gone to sleep. ZZZzzz…]
15:33 -!- Chris_Stewart_5 [~Chris_Ste@185.141.119.165] has quit [Ping timeout: 272 seconds]
15:35 -!- Chris_Stewart_5 [~Chris_Ste@185.141.119.135] has joined #bitcoin-core-dev
15:54 -!- Guest74 [~Guest29@137.59.223.170] has joined #bitcoin-core-dev
15:55 -!- Guest74 [~Guest29@137.59.223.170] has quit [Client Quit]
17:06 -!- jon_atack [~jonatack@user/jonatack] has quit [Ping timeout: 268 seconds]
17:07 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-dev
17:13 -!- bugs_ [~bugs@user/bugs/x-5128603] has quit [Quit: Leaving]
17:17 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Quit: Leaving]
17:17 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #bitcoin-core-dev
17:18 < bitcoin-git> [bitcoin] JonathanTylerCombs opened pull request #29919: Codespace laughing carnival g44xqwpj7jj9367w (master...codespace-laughing-carnival-g44xqwpj7jj9367w) https://github.com/bitcoin/bitcoin/pull/29919
17:26 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Ping timeout: 260 seconds]
17:28 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #bitcoin-core-dev
17:42 -!- drnet [~drnet@185.89.163.206] has quit [Quit: Leaving]
17:49 -!- Mousticke [~Mousticke@2001:7e8:c01c:e000:49ce:a854:9690:2336] has joined #bitcoin-core-dev
18:00 < bitcoin-git> [bitcoin] achow101 closed pull request #29919: Codespace laughing carnival g44xqwpj7jj9367w (master...codespace-laughing-carnival-g44xqwpj7jj9367w) https://github.com/bitcoin/bitcoin/pull/29919
18:00 < bitcoin-git> [bitcoin] JonathanTylerCombs opened pull request #29921: Check this out (master...master) https://github.com/bitcoin/bitcoin/pull/29921
18:03 < bitcoin-git> [bitcoin] achow101 closed pull request #29921: Check this out (master...master) https://github.com/bitcoin/bitcoin/pull/29921
18:29 -!- Mousticke [~Mousticke@2001:7e8:c01c:e000:49ce:a854:9690:2336] has quit [Quit: Client closed]
18:57 -!- abubakarsadiq [uid602234@id-602234.hampstead.irccloud.com] has quit [Quit: Connection closed for inactivity]
19:41 -!- luke-jr_ is now known as luke-jr
20:19 -!- pablomartin4btc [~pablomart@89.35.25.94] has quit [Ping timeout: 264 seconds]
21:01 -!- cmirror [~cmirror@4.53.92.114] has quit [Remote host closed the connection]
21:01 -!- cmirror [~cmirror@4.53.92.114] has joined #bitcoin-core-dev
21:06 -!- jarthur [~jarthur@user/jarthur] has quit [Quit: jarthur]
23:11 < willcl-ark> > hmm was built off of: https://github.com/lightninglabs/docker-bitcoin-core/blob/master/26/Dockerfile -- I just build this dockerfile and got hash: ab06620aadcf814c0ef8274566631a0428119f1f7e218566c689d535cb515f75  /opt/bitcoin-26.0/bin/bitcoind
23:12 < willcl-ark> I'm syncing it now on testnet, but I'm guessing I won't hit the same errors you're seeing roasbeef...
23:17 < willcl-ark> Also possibly of interest to you, I am going to be maintaining **unofficial** docker images --which will actually be updated in a timely fashion-- of supported versions (i.e. not EoL), here: https://hub.docker.com/r/bitcoin/bitcoin I've modernised both alpine and debian builds a bit too. Possibly of note, there is no bdb wallet support -- only migration to sqlite (as BDB is going away
23:17 < willcl-ark> very soon). But everything else should match those unmaintained ruimarinho images.
--- Log closed Sat Apr 20 00:00:32 2024