--- Log opened Mon May 08 00:00:55 2023
00:05 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has joined #bitcoin-core-dev
00:10 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has quit [Ping timeout: 264 seconds]
00:11 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has joined #bitcoin-core-dev
00:16 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has quit [Ping timeout: 260 seconds]
00:18 -!- AaronvanW [~AaronvanW@user/AaronvanW] has joined #bitcoin-core-dev
00:22 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has joined #bitcoin-core-dev
00:27 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has quit [Ping timeout: 260 seconds]
00:37 -!- Guyver2 [~Guyver@77-174-98-73.fixed.kpn.net] has joined #bitcoin-core-dev
01:03 -!- flooded [~flooded@146.70.202.51] has joined #bitcoin-core-dev
01:07 -!- test_ [~flooded@146.70.174.163] has quit [Ping timeout: 240 seconds]
01:08 -!- Guest30 [~Guest30@202.134.8.142] has joined #bitcoin-core-dev
01:11 -!- Guest30 [~Guest30@202.134.8.142] has quit [Client Quit]
01:12 -!- Guest30 [~Guest30@202.134.8.142] has joined #bitcoin-core-dev
01:12 -!- Guest30 [~Guest30@202.134.8.142] has left #bitcoin-core-dev []
01:12 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has joined #bitcoin-core-dev
01:13 -!- Guest30 [~Guest30@202.134.8.142] has joined #bitcoin-core-dev
01:14 -!- Guest30 [~Guest30@202.134.8.142] has quit [Client Quit]
01:17 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has quit [Ping timeout: 265 seconds]
01:34 -!- AaronvanW [~AaronvanW@user/AaronvanW] has quit [Remote host closed the connection]
01:34 -!- puchka [~puchka@185.203.122.57] has quit [Ping timeout: 240 seconds]
01:36 -!- Guest98 [~Guest98@103.152.220.44] has joined #bitcoin-core-dev
01:40 -!- Guest98 [~Guest98@103.152.220.44] has quit [Client Quit]
01:40 -!- Guest98 [~Guest98@103.152.220.44] has joined #bitcoin-core-dev
01:44 -!- scg [~scg@84.252.114.5] has joined #bitcoin-core-dev
01:46 -!- szarka [~szarka@24-124-20-18-static.midco.net] has joined #bitcoin-core-dev
01:46 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has joined #bitcoin-core-dev
01:48 -!- robszarka [~szarka@24-124-20-18-static.midco.net] has quit [Ping timeout: 250 seconds]
01:51 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has quit [Ping timeout: 264 seconds]
01:53 -!- stevenwy37 [~stevenwy3@103.152.220.44] has joined #bitcoin-core-dev
02:05 -!- AaronvanW [~AaronvanW@user/AaronvanW] has joined #bitcoin-core-dev
02:11 -!- Guyver2 [~Guyver@77-174-98-73.fixed.kpn.net] has left #bitcoin-core-dev [Closing Window]
02:12 -!- puchka [~puchka@185.203.122.57] has joined #bitcoin-core-dev
02:19 -!- stevenwy37 [~stevenwy3@103.152.220.44] has quit [Remote host closed the connection]
02:19 -!- stevenwy37 [~stevenwy3@103.152.220.44] has joined #bitcoin-core-dev
02:19 -!- stevenwy37 [~stevenwy3@103.152.220.44] has quit [Remote host closed the connection]
02:20 -!- stevenwy37 [~stevenwy3@103.152.220.44] has joined #bitcoin-core-dev
02:27 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has joined #bitcoin-core-dev
02:32 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has quit [Ping timeout: 246 seconds]
02:39 -!- AaronvanW [~AaronvanW@user/AaronvanW] has quit [Ping timeout: 240 seconds]
02:44 -!- Guest98 [~Guest98@103.152.220.44] has quit [Quit: Client closed]
02:44 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has joined #bitcoin-core-dev
02:49 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has quit [Ping timeout: 265 seconds]
02:50 -!- puchka [~puchka@185.203.122.57] has quit [Ping timeout: 256 seconds]
02:55 -!- puchka [~puchka@185.203.122.42] has joined #bitcoin-core-dev
03:01 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 268 seconds]
03:01 -!- jon_atack [~jonatack@user/jonatack] has joined #bitcoin-core-dev
03:03 -!- Guest98 [~Guest98@103.152.220.44] has joined #bitcoin-core-dev
03:05 -!- Guest98 [~Guest98@103.152.220.44] has quit [Client Quit]
03:06 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has joined #bitcoin-core-dev
03:10 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has quit [Ping timeout: 248 seconds]
03:17 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has joined #bitcoin-core-dev
03:25 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has quit [Ping timeout: 240 seconds]
03:27 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has joined #bitcoin-core-dev
03:30 -!- vyHamii [~vyHamii@27.72.98.102] has quit [Remote host closed the connection]
03:32 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has quit [Ping timeout: 260 seconds]
03:43 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has joined #bitcoin-core-dev
03:43 < bitcoin-git> [bitcoin] MarcoFalke opened pull request #27594: refactor: Remove unused GetTimeMillis (master...2305-remove-GetTimeMillis-) https://github.com/bitcoin/bitcoin/pull/27594
03:48 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has quit [Ping timeout: 260 seconds]
03:49 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has joined #bitcoin-core-dev
03:53 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has quit [Ping timeout: 248 seconds]
03:54 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has joined #bitcoin-core-dev
03:57 -!- AaronvanW [~AaronvanW@user/AaronvanW] has joined #bitcoin-core-dev
04:00 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has quit [Ping timeout: 248 seconds]
04:06 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
04:06 -!- pablomartin4btc_ [~pablomart@217.146.83.239] has joined #bitcoin-core-dev
04:11 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 260 seconds]
04:13 -!- test_ [~flooded@146.70.195.83] has joined #bitcoin-core-dev
04:16 -!- flooded [~flooded@146.70.202.51] has quit [Ping timeout: 268 seconds]
04:21 -!- scg [~scg@84.252.114.5] has quit [Quit: Client closed]
04:28 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has joined #bitcoin-core-dev
04:30 -!- scg [~scg@84.252.114.5] has joined #bitcoin-core-dev
04:31 -!- AlexandreFerreir [~alex10ama@2001:470:69fc:105::1:1976] has joined #bitcoin-core-dev
04:34 < scg> Is my understanding correct?: parity encoded in TapLeaf version is only needed in witness? Seems to me that You do not need to care about it when constructing or signing PSBT. Only when one builds witness is properly encoded parity flag required in TapLeaf version.
04:35 -!- Guest36 [~Guest36@85.255.20.235] has joined #bitcoin-core-dev
04:35 -!- Guest36 [~Guest36@85.255.20.235] has quit [Client Quit]
04:37 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has quit [Ping timeout: 248 seconds]
04:49 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has joined #bitcoin-core-dev
04:53 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has quit [Ping timeout: 246 seconds]
04:57 -!- puchka [~puchka@185.203.122.42] has quit [Ping timeout: 256 seconds]
05:09 -!- b_101 [~robert@216.144.236.70] has quit [Ping timeout: 268 seconds]
05:12 -!- jon_atack [~jonatack@user/jonatack] has quit [Ping timeout: 240 seconds]
05:13 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
05:14 -!- jon_atack [~jonatack@user/jonatack] has joined #bitcoin-core-dev
05:19 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has joined #bitcoin-core-dev
05:20 -!- stevenwy37 [~stevenwy3@103.152.220.44] has quit [Remote host closed the connection]
05:20 -!- stevenwy37 [~stevenwy3@103.152.220.44] has joined #bitcoin-core-dev
05:37 -!- jon_atack [~jonatack@user/jonatack] has quit [Ping timeout: 240 seconds]
05:38 -!- jon_atack [~jonatack@user/jonatack] has joined #bitcoin-core-dev
05:44 -!- jon_atack [~jonatack@user/jonatack] has quit [Ping timeout: 268 seconds]
05:47 -!- pablomartin4btc_ [~pablomart@217.146.83.239] has quit [Quit: Leaving]
05:47 -!- pablomartin [~pablomart@217.146.83.239] has joined #bitcoin-core-dev
06:03 -!- puchka [~puchka@185.203.122.49] has joined #bitcoin-core-dev
06:05 -!- Guest98 [~Guest98@2a0d:6fc2:5420:6e00:4847:b953:71e7:61e4] has joined #bitcoin-core-dev
06:06 -!- Guest98 [~Guest98@2a0d:6fc2:5420:6e00:4847:b953:71e7:61e4] has quit [Client Quit]
06:32 -!- ZeroMaster_ [~webirc@87-126-6-81.ip.btc-net.bg] has quit [Read error: Connection reset by peer]
06:33 -!- ZeroMaster_ [~webirc@87-126-6-81.ip.btc-net.bg] has joined #bitcoin-core-dev
06:38 -!- scg [~scg@84.252.114.5] has quit [Quit: Client closed]
06:39 -!- scg [~scg@84.252.114.5] has joined #bitcoin-core-dev
06:39 -!- ZeroMaster_ [~webirc@87-126-6-81.ip.btc-net.bg] has quit [Read error: Connection reset by peer]
06:40 -!- ZeroMaster_ [~webirc@87-126-6-81.ip.btc-net.bg] has joined #bitcoin-core-dev
06:53 -!- Guest7550 [~Guest75@cpe-70-119-23-177.tx.res.rr.com] has joined #bitcoin-core-dev
06:54 -!- ZeroMaster_ [~webirc@87-126-6-81.ip.btc-net.bg] has quit [Ping timeout: 265 seconds]
07:01 -!- ZeroMaster_ [~webirc@87-126-6-81.ip.btc-net.bg] has joined #bitcoin-core-dev
07:11 -!- Guest7550 [~Guest75@cpe-70-119-23-177.tx.res.rr.com] has quit [Quit: Client closed]
07:13 < bitcoin-git> [bitcoin] fanquake pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/322ec63b0149...26cb32c02d76
07:13 < bitcoin-git> bitcoin/master d9b54c4 Hennadii Stepanov: msvc: Cleanup after upgrading libsecp256k1 up to 0.3.0
07:13 < bitcoin-git> bitcoin/master 26cb32c fanquake: Merge bitcoin/bitcoin#27580: msvc: Cleanup after upgrading libsecp256k1 up...
07:13 < bitcoin-git> [bitcoin] fanquake merged pull request #27580: msvc: Cleanup after upgrading libsecp256k1 up to 0.3.0 (master...230505-cleanup) https://github.com/bitcoin/bitcoin/pull/27580
07:21 -!- bugs_ [~bugs@user/bugs/x-5128603] has joined #bitcoin-core-dev
07:22 -!- flooded [~flooded@146.70.202.99] has joined #bitcoin-core-dev
07:26 -!- test_ [~flooded@146.70.195.83] has quit [Ping timeout: 260 seconds]
07:45 -!- scg [~scg@84.252.114.5] has quit [Quit: Client closed]
07:48 -!- preimage [~halosghos@user/halosghost] has joined #bitcoin-core-dev
07:53 -!- stevenwy37 [~stevenwy3@103.152.220.44] has quit [Quit: Leaving...]
07:56 < jamesob> hey, there's no way we can do Github access just to maintain a particular project is there? The assumeutxo board is out of date: https://github.com/bitcoin/bitcoin/projects/11
07:57 < achow101> jamesob: I can add just you to maintain that
07:58 < achow101> we can add individuals to each project board's access
07:58 < achow101> I think
07:58 < _aj_> need to convert to an org project first, i think?
07:59 < _aj_> or a non-classic project or whatever
07:59 < fanquake> yea a couple there we should probably migrate or close
08:02 -!- scg [~scg@84.252.114.5] has joined #bitcoin-core-dev
08:07 < achow101> migrated the project to https://github.com/orgs/bitcoin/projects/7 and added jamesob to write to it
08:08 < bitcoin-git> [bitcoin] jamesob opened pull request #27596: assumeutxo (2) (master...assumeutxo) https://github.com/bitcoin/bitcoin/pull/27596
08:09 < bitcoin-git> [bitcoin] jamesob closed pull request #15606: assumeutxo (master...utxo-dumpload-compressed) https://github.com/bitcoin/bitcoin/pull/15606
08:17 < instagibbs> https://github.com/bitcoin/bitcoin/issues/27555#issuecomment-1538504504 seems suboptimal, and partially my fault. Looks like fee estimator is returning obviously bogus rates(below min relay), then being over-ridden by mempoolminfee, which gets blown away on restart
08:17 < instagibbs> (I ack'd the PR  that changed the behavior that hid the issue)
08:17 < jamesob> achow101: thanks
08:17 -!- julien [~julien@2a01:e0a:ab1:22c0:8c06:1816:743f:e9f7] has joined #bitcoin-core-dev
08:17 < bitcoin-git> [bitcoin] hebasto opened pull request #27598: bench: Add `-sha-implementation` command-line option (master...230508-bench) https://github.com/bitcoin/bitcoin/pull/27598
08:18 -!- julien [~julien@2a01:e0a:ab1:22c0:8c06:1816:743f:e9f7] has quit [Client Quit]
08:21 -!- puchka [~puchka@185.203.122.49] has quit [Ping timeout: 250 seconds]
08:21 -!- infernix [nix@spirit.infernix.net] has quit [Quit: ZNC - http://znc.sourceforge.net]
08:33 -!- Talkless [~Talkless@mail.dargis.net] has joined #bitcoin-core-dev
08:51 -!- jb55 [~jb55@user/jb55] has joined #bitcoin-core-dev
08:53 < jb55> my core node was getting spammed with "Cache size (23509456) exceeds total space (15701232)" yesterday and then eventually just stopped working/got stale tip errors until I restarted. first time this has happened, has anyone experienced this?
08:57 < fjahr> jb55: What do you mean by getting spammed? The log message isn't a big issue by itself afaict. It just means that the cache will need to be flushed to disk. But that doesn't mean we shouldn't look into this of course. What disk do you run this node on?
08:59 < jb55> fjahr: means it was repeated 100 times or so. slow disk (HDD)
09:00 < jb55> then it just stopped and started to get stale tip warnings.
09:00 < jb55> a bit concerning if mempool activity could bring down my node :(
09:00 < jb55> I assumed that's what the message was about, not sure
09:00 -!- infernix [nix@spirit.infernix.net] has joined #bitcoin-core-dev
09:01 < instagibbs> it means it should flush to disk immediately, seeing it repeated that much is sketchy
09:02 < fjahr> Hmm, yeah, absolutely. Could it be that the cache is growing so fast that it fills up the memory and renders core unable to flush on a slow disk?
09:03 < ghost43> one of my nodes just got stuck, apparently, 3 blocks ago.  https://0bin.net/paste/ErHctHfs#yHXnmymeDKmBdLpqr7IYFZsV3IoX4vrV0UNiLQAB+Tu
09:05 < instagibbs> "bad-witness-nonce-size" ooh nice
09:05 < fjahr> summoning cache all stars jamesob, ryanofsky :)
09:07 < instagibbs> ghost43 looks like you're having repeated timeouts from peers. I've seen more lately, but nothing like that 3 times in a row
09:08 < provoostenator> ghost43: does getchaintips tell you which block triggered the bad-witness-nonce-size?
09:09 < ghost43> I have another node I am running addnoded bidirectionally with this one, which is not stuck. I would have hoped they can get blocks from each other :/
09:10 < ghost43> getchaintips: https://0bin.net/paste/ZmAGjdGW#RIakIpTB+qpdFnyHoxJ+gI2d7QvmvjfVtqH1nnekquI
09:10 < ghost43> that output looks weird, I doubt there is a branch of len=3
09:10 < instagibbs> no, your node is trying peers and not getting the block from any of them
09:10 < sipa> I have the 788807 block as active tio.
09:11 < sipa> So does forkmonitor.
09:11 < darosior> Same here. I'm at 78807 on multiple nodes
09:11 < fanquake> same
09:11 < darosior> 00000000000000000000f99758df6d2d29953344b4c52749f4b5d8442b4f5b36
09:11 < instagibbs> miner either made a stoopid block, or someone relayed a malleated block witness data for some reason
09:11 < sdaftuar> instagibbs: or hardware failure i think?
09:11 < instagibbs> sdaftuar always a possibility sure
09:12 < jb55> same
09:12 < sdaftuar> i'd have to guess hardware failure as most likely. can try to submitblock the hex of what we all think is valid and see if the node takes it
09:13 < instagibbs> ^ good idea, shove the next block in, see if it takes
09:14 < sipa> It says headers-only, not invalid.
09:14 < sdaftuar> malleation would cause that though
09:14 < sdaftuar> er, what was detected as malleation
09:14 < sipa> So it has never received the block (except perhaps malleated versions of it).
09:14 < instagibbs> MUTATED 
09:14 < darosior> I was trying to send you the output of getblock so you can submitblock but i can't find a paste site that accepts such large data
09:14 < instagibbs> "BLOCK_MUTATED,"
09:14 < sipa> Mutated.
09:14 < sipa> Yes.
09:14 < sipa> But why are all copies mutated?
09:15 < sipa> Of all the versions ghost43 is receiving?
09:15 -!- MatrixBot123456 [~matrixbot@2001:bc8:1824:bc3::1] has joined #bitcoin-core-dev
09:15 < provoostenator> So there's no recent invalid block in that getchaintips output. I guess we don't store failures related to maleation? 
09:15 < instagibbs> I'm seeing "Timeout" from his log, not rejection again
09:15 < provoostenator> (since we want to try again)
09:15 < instagibbs> provoostenator a peer could stuff logs/state cheaply with BLOCK_MUTATED I think
09:15 < sdaftuar> instagibbs: oops
09:16 < provoostenator> Sounds like we should add the block hash to log messages when this happens for easier debugging later.
09:16 < instagibbs> only behind verbose logging, otherwise it's free to trigger
09:17 < instagibbs> (IIUC)
09:17 < instagibbs> sdaftuar what's the oops
09:17 < sdaftuar> your logging observation!
09:17 < provoostenator> instagibbs: good poin
09:18 < provoostenator> But we're already logging this rejection, so adding the hash wouldn't make it worse :-)
09:19 < instagibbs> ruh roh
09:19 < instagibbs> ;P
09:19 < darosior> ghost43: so you can `submitblock`: http://download.darosior.ninja/blocks_for_ghost/
09:20 < provoostenator> I do not understand the code comment above that check by the way: "The malleation check is ignored; as the transaction tree itself already does not permit it, it is impossible to trigger in the witness tree."
09:21 < sdaftuar> we don't need to look for transaction duplicates there
09:21 < provoostenator> In particular what is being "ignored" here.
09:22 < provoostenator> Oh it's the malleated result from the previous call that we ignore.
09:23 < sdaftuar> provoostenator: right we don't have to worry about merkle root malleation like we do in CheckBlock, because we've already done those checks
09:25 < darosior> 2023-04-15T09:27:44Z ERROR: ProcessNewBlock: AcceptBlock FAILED (bad-witness-nonce-size, ContextualCheckBlock : invalid witness reserved value size)
09:27 < sdaftuar> jb55: how far apart (in timestamps) were you seeing those "cache size" log messages?
09:27 < jb55> https://jb55.com/s/58818ccccfb21d95.txt
09:27 < ghost43> can I get some shell help? :D        # bitcoin-cli submitblock $(cat block-788803-hex.txt)
09:27 < ghost43> bash: /usr/local/bin/bitcoin-cli: Argument list too long
09:28 < provoostenator> I get a couple of those per day too.
09:29 < sdaftuar> ghost43: oof, you might need to use a different rpc client? someone else here will know better than me
09:29 < ghost43> I will try curl
09:29 < instagibbs> ghost43 think the block is too chonky for your shell
09:29 < provoostenator> ghost43: cat block.txt | bitcoin-cli -stdin submitblock
09:30 < sipa> cat block | bitcoin-cli -stdin submitblock ?
09:30 < sipa> Or something like that
09:33 < ghost43> it accepted 788803 and ~instantly processed the next two blocks on top as well
09:33 < ghost43> but it is still only on 788805, not sure what it is doing atm
09:33 < ghost43> (as in it obtained 788804 and 788805 from the p2p network)
09:33 < provoostenator> I'm guessing we don't hold on to the non-witness part of the block when this happens?
09:34 < sdaftuar> provoostenator: we don't write the block to disk at all when this happens
09:34 < instagibbs> ghost43 "Timeout"s I think are mostly unrelated to that
09:34 < b10c> does it know the headers for the ones after 788805? (see getchaintips)
09:34 < provoostenator> So it wastes a bit of bandwidth (but so does ping) and a few (cheap) checks each time?
09:35 < cfields> sdaftuar: sure about that? By my read we would?
09:35 < sdaftuar> ghost43: did you submitblock for the later blocks as well?
09:35 < ghost43> oh wait, it is now stuck on the stale chain, the legit fork that happened at 788805
09:35 < ghost43> sdaftuar: no, I only did it for just 788803
09:35 < sdaftuar> cfields: hmm, checking
09:35 < cfields> sdaftuar: admittedly it's been a while since I've dug around in here though :)
09:36 < b10c> ghost34: on 0000000000000000000313dae7541b4c58e93832ddeaf96f8d6a5b5f8157d494?
09:36 < ghost43> b10c: yes
09:36 < ghost43> I can feed it the blocks on the other branch manually I guess
09:37 < b10c> do you have headers for the other branch?
09:37 < ghost43> # bitcoin-cli getchaintips
09:37 < ghost43> [    {      "height": 788809,      "hash": "00000000000000000003bd977a4ea6978a47d9a88e9adf8be244bc60ed7cd793",      "branchlen": 5,      "status": "headers-only"    },
09:37 < ghost43> {      "height": 788805,      "hash": "0000000000000000000313dae7541b4c58e93832ddeaf96f8d6a5b5f8157d494",      "branchlen": 0,      "status": "active"    },  
09:37 < instagibbs> it might fix itself on next block peers get
09:37 < ghost43> yes it has the headers
09:37 < instagibbs> oh
09:37 < instagibbs> check getpeerinfo for "inflight"s? would that be the place?
09:37 < provoostenator> cfields: SaveBlockToDisk is called after ContextualCheckBlock
09:38 < b10c> then I had the same issue. It knew the headers but kept timing out while downloading the blocks.
09:38 -!- Guest80 [~Guest80@86.121.142.207] has joined #bitcoin-core-dev
09:38 < sdaftuar> cfields: AcceptBlock is where we store to disk; in that function we invoke ContextualCheckBlock which is what reported the bad-witness-nonce-size error that ghost43 reported. so i don't see how the block could have been stored after that?
09:38 < fjahr> what, 788805 is still considered active?
09:38 < instagibbs> one of them is :)
09:38 < fjahr> ah, because it didn't get the blocks yet
09:38 < b10c> fjahr: see https://fork.observer/ maybe
09:40 < cfields> sdaftuar / provoostenator: yep,  you're right, I see.  thanks to both of you.
09:41 < fjahr> b10c: I misread "headers-only" for "valid-headers" and that would have been confusing
09:41 < instagibbs> b10c ghost43 are the stuck nodes listening nodes?
09:42 < ghost43> yes, it is listening on ipv4 and onion
09:43 < ghost43> "Timeout downloading block 00000000000000000001081dd49ade1108f0b5415605249804a0a95a8e63a3f6 from peer" in log :/
09:43 -!- Guest80 [~Guest80@86.121.142.207] has left #bitcoin-core-dev []
09:43 < instagibbs> I've had no timeouts on my non-listening nodes, anecdotally
09:43 < sdaftuar> jb55: do you have the last UpdateTip line your node saw before the cache size messages?  the end of those UpdateTip lines shows how big your coins cache was at the end of block validation
09:43 < b10c> instagibbs: yes
09:46 < ghost43> well, ok, I've restarted bitcoind and it instantly caught up to the tip
09:46 < sdaftuar> interesting!
09:47 < fjahr> jb55: do you have a custom maxmempool setting?
09:57 -!- puchka [~puchka@185.203.122.42] has joined #bitcoin-core-dev
09:59 < sdaftuar> i'll be afk for a bit, but if someone can open an issue and log some of this i think it's worth more investigation
10:02 < fjahr> jb55: also, I would be curious if this happened around the time when we had the 2 block reorg ~20h ago, i.e. around 788685-788688
10:02 < fjahr> I can open an issue if nobody else has started it already
10:02 < instagibbs> fjahr go ahead
10:16 -!- learner-monad [~ehanneken@user/learner-monad] has joined #bitcoin-core-dev
10:18 < fjahr> #27599, moving conversation there
10:18 <@gribble> https://github.com/bitcoin/bitcoin/issues/27599 | Node stuck with repeated "Cache size exceeds total space" log message · Issue #27599 · bitcoin/bitcoin · GitHub
10:29 < ghost43> my bitcoind got stuck again on 788809, due to "Timeout downloading block", so basically after the restart it caught up to tip fast and then it failed to download any subsequent blocks. (now tip is 788812) now I've restarted and again it caught up very fast to current tip...
10:31 -!- test_ [~flooded@146.70.195.35] has joined #bitcoin-core-dev
10:32 -!- b_101 [~robert@189.131.30.152] has joined #bitcoin-core-dev
10:32 < bitcoin-git> [bitcoin] achow101 pushed 3 commits to master: https://github.com/bitcoin/bitcoin/compare/26cb32c02d76...fa53611cf1b2
10:32 < bitcoin-git> bitcoin/master bd13dc2 Sjors Provoost: Switch hardened derivation marker to h in descriptors
10:32 < bitcoin-git> bitcoin/master fe49f06 Sjors Provoost: doc: clarify PR 26076 release note
10:32 < bitcoin-git> bitcoin/master fa53611 Andrew Chow: Merge bitcoin/bitcoin#26076: Switch hardened derivation marker to h
10:32 < bitcoin-git> [bitcoin] achow101 merged pull request #26076: Switch hardened derivation marker to h (master...2022/09/descriptors_h) https://github.com/bitcoin/bitcoin/pull/26076
10:32 < bugs_> hopefully its just network bandwidth problems and not a new sybil
10:34 < achow101> ghost43: are you seeing a lot of cpu usage?
10:34 -!- flooded [~flooded@146.70.202.99] has quit [Ping timeout: 240 seconds]
10:36 < fjahr> ghost43: please take note of the peers you are connected to. Have you tried to connect to a new, public node to see if that changes anything?
10:37 < ghost43> achow101: not really. server has 8 virtual cpus (I think 4 real cores, times two SMT), load averages below 2.0
10:38 < ghost43> bugs_: it cannot be sybilled in the naive sense because I have addnoded other nodes I control and they are running fine
10:38 < ghost43> btw it logged "ERROR: AcceptBlock: bad-witness-nonce-size, ContextualCheckBlock : invalid witness reserved value size"  again
10:38 < achow101> just on the block you got stuck on?
10:39 < bugs_> ah it might have gotten stuck on an ht core
10:40 < bugs_> ht core gets no cycles if the real cores are running sufficiently optimized code
10:40 < fjahr> ghost43: could it be that the server host or their providers are blocking bitcoin traffic? Or do you have other nodes on servers in the same infra that don't have the issue?
10:40 < ghost43> achow101: I think so because the tip was 788812 and it had header for 788813, and it logged that line then; however the log does not say which block height or hash the error is for
10:40 < bugs_> i always disable HT
10:41 < ghost43> this is a hetzner server with 1810 days uptime; I doubt its peering issues. last time I restarted it was when I dist-upgraded to ubuntu 18.04 when that got released :D
10:41 < instagibbs> that sounds like hardware failure or a sybil attacker which has figured out how to stall you out by mutating a tx (sounds like hardware ...)
10:41 < achow101> was it the same peer as before?
10:41 < instagibbs> mutating a block*
10:42 < bugs_> i had heard heztner decided to become crypto unfriendly a few months ago
10:43 < achow101> being able to see the block itself would also be interesting
10:43 < fjahr> ok, I mean hetzner has said that they don't want crypto stuff but if they had started to block traffic widely we would hear more complaints
10:43 < bugs_> but i'd definetly try turning off ht thats my bet
10:43 < bugs_> there is a way to do it in linux without rebooting
10:43 < sipa> @bugs_ That really seems unrelated.
10:43 < bugs_> but turning it off in the vbios is best
10:44 < bugs_> if something that owns a lock gets scheduled on an ht core bad things can happen
10:44 < bugs_> like an nfs lock
10:44 < ghost43> but it's been running like this for *years*, it cannot be ht :P
10:45 < ghost43> anyway, I am running the unreleased 24.0.0, if that matters; so I'll just upgrade to the v25.0rc1 tag, and also do a dist-upgrade from this ancient ubuntu (though that's only the host, the docker container running bitcoind is modern), and see if the hang reappears after that
10:46 < instagibbs> run in non-listening mode
10:46 < achow101> maybe also run tcpdump to catch the block data?
10:47 < jb55> sdaftuar: unfortunately no this is just a tmux backbuffer since I was rebuilding my utxo due to some kind of leveldb corruption. wasn't my main systemd logs. @fjahr: I don't have any custom maxmempool settings. This started happening 20hrs ago yes when mempool was hot
10:49 < jb55> sdaftuar: earliest log line I have of the cache spam thing is 2023-05-07T17:21:08Z
10:55 < fjahr> ghost43: I don't think the 24.0.1 fixes are related (#26616 if anyone else wants to check)
10:55 <@gribble> https://github.com/bitcoin/bitcoin/issues/26616 | [24.x] Backports for 24.0.1 by fanquake · Pull Request #26616 · bitcoin/bitcoin · GitHub
11:04 -!- aielima [~aielima@user/aielima] has joined #bitcoin-core-dev
11:13 -!- pablomartin [~pablomart@217.146.83.239] has quit [Ping timeout: 264 seconds]
11:44 < jamesob> One thought for jb55's issue: FlushStateToDisk ultimately issues the log he's getting spammed with, and the coins cache flush there is gated `by if (fDoFullFlush && !CoinsTip().GetBestBlock().IsNull())` (with no corresponding log in the `else`), so his coinstip's bestblock somehow got nullified, he'd be in a position where the cache gets critical
11:44 < jamesob> but doesn't get flushed 
11:44 < jamesob> *so if his coinstip's bestblock
11:46 < jamesob> but the only way I can see that happening is exceptionally unlucky memory fault?
11:51 < jamesob> I forgot that every ATMP call also calls FlushStateToDisk(..., PERIODIC)
12:02 -!- test_ [~flooded@146.70.195.35] has quit [Ping timeout: 256 seconds]
12:08 -!- vincenzopalazzo [~vincenzop@2001:470:69fc:105::a67] has joined #bitcoin-core-dev
12:25 -!- scg [~scg@84.252.114.5] has quit [Quit: Client closed]
12:33 -!- Dionysus [~dio_ny_su@c-24-34-165-90.hsd1.ma.comcast.net] has joined #bitcoin-core-dev
12:35 -!- Talkless [~Talkless@mail.dargis.net] has quit [Quit: Konversation terminated!]
12:39 -!- Dionysus [~dio_ny_su@c-24-34-165-90.hsd1.ma.comcast.net] has quit []
12:59 < bitcoin-git> [bitcoin] pinheadmz opened pull request #27600: Make peer eviction slightly more aggresive to make room for whitelisted inbound connections (master...whitebind-evict) https://github.com/bitcoin/bitcoin/pull/27600
13:16 -!- jarthur [~jarthur@user/jarthur] has joined #bitcoin-core-dev
13:59 < jb55> jamesob: what is ATMP
14:02 -!- chutner [~chutner@128-092-219-162.biz.spectrum.com] has joined #bitcoin-core-dev
14:02 < instagibbs> AcceptToMemPool
14:02 < jb55> ah k
14:03 < bitcoin-git> [bitcoin] furszy opened pull request #27601: wallet: don't duplicate change output if already exist (master...2023_wallet_double_change_output) https://github.com/bitcoin/bitcoin/pull/27601
14:06 -!- chutner [~chutner@128-092-219-162.biz.spectrum.com] has quit [Client Quit]
14:23 < bitcoin-git> [bitcoin] sr-gi opened pull request #27602: net: avoid serving non-announced txs as a result of a MEMPOOL message (master...mempool-not-inved) https://github.com/bitcoin/bitcoin/pull/27602
15:02 -!- preimage [~halosghos@user/halosghost] has quit [Quit: WeeChat 3.8]
15:09 -!- jackjack [~jack@31-209-196-73.dsl.dynamic.simnet.is] has joined #bitcoin-core-dev
15:16 -!- jackjack [~jack@31-209-196-73.dsl.dynamic.simnet.is] has quit [Ping timeout: 256 seconds]
15:26 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #bitcoin-core-dev
15:52 -!- bugs_ [~bugs@user/bugs/x-5128603] has quit [Quit: Leaving]
16:05 -!- andytosh1 [~apoelstra@user/andytoshi] has quit [Quit: leaving]
16:12 -!- Guest9 [~Guest9@2600:6c64:7e40:ee8:714d:231a:6207:3349] has joined #bitcoin-core-dev
16:12 -!- Guest9 [~Guest9@2600:6c64:7e40:ee8:714d:231a:6207:3349] has quit [Client Quit]
16:17 -!- aielima [~aielima@user/aielima] has quit [Quit: Ciao]
16:20 -!- SpellChecker_ [~SpellChec@user/SpellChecker] has quit [Remote host closed the connection]
16:20 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
16:20 -!- yanmaani1 [~yanmaani@gateway/tor-sasl/yanmaani] has quit [Remote host closed the connection]
16:21 -!- yanmaani1 [~yanmaani@gateway/tor-sasl/yanmaani] has joined #bitcoin-core-dev
16:21 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #bitcoin-core-dev
16:33 -!- andytoshi [~apoelstra@user/andytoshi] has joined #bitcoin-core-dev
17:05 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has quit [Remote host closed the connection]
17:05 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has joined #bitcoin-core-dev
17:10 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has quit [Ping timeout: 265 seconds]
17:11 -!- Guest21 [~Guest21@097-095-185-241.res.spectrum.com] has joined #bitcoin-core-dev
17:11 -!- Guest21 [~Guest21@097-095-185-241.res.spectrum.com] has quit [Client Quit]
17:57 -!- PaperSword [~Thunderbi@securemail.qrsnap.io] has quit [Quit: PaperSword]
18:03 -!- jarthur [~jarthur@user/jarthur] has quit [Quit: jarthur]
18:09 -!- kevkevin [~kevkevin@2601:241:8703:7b30:69bc:82a9:e070:345a] has joined #bitcoin-core-dev
18:14 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has joined #bitcoin-core-dev
18:18 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has quit [Ping timeout: 246 seconds]
18:37 -!- learner-monad [~ehanneken@user/learner-monad] has quit [Ping timeout: 260 seconds]
18:47 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has joined #bitcoin-core-dev
18:51 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has quit [Ping timeout: 265 seconds]
18:53 -!- vysn [~vysn@user/vysn] has quit [Remote host closed the connection]
18:54 < bitcoin-git> [bitcoin] kevkevinpal opened pull request #27603: test: added coverage to mining_basic.py (master...test/mining/emptyBlockVtx) https://github.com/bitcoin/bitcoin/pull/27603
18:56 -!- jarthur [~jarthur@user/jarthur] has joined #bitcoin-core-dev
19:13 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has joined #bitcoin-core-dev
19:18 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has quit [Ping timeout: 248 seconds]
19:19 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has joined #bitcoin-core-dev
19:26 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has quit [Ping timeout: 260 seconds]
19:26 -!- stevenwy37 [~stevenwy3@116.206.100.4] has joined #bitcoin-core-dev
19:49 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has joined #bitcoin-core-dev
19:55 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has quit [Ping timeout: 265 seconds]
19:57 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has joined #bitcoin-core-dev
20:02 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has quit [Ping timeout: 256 seconds]
20:03 -!- Guest8484 [~Guest84@74-194-76-48.montcmta01.res.dyn.suddenlink.net] has joined #bitcoin-core-dev
20:13 -!- Guest8484 [~Guest84@74-194-76-48.montcmta01.res.dyn.suddenlink.net] has quit [Ping timeout: 245 seconds]
20:20 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has joined #bitcoin-core-dev
20:24 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has quit [Ping timeout: 248 seconds]
20:31 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has joined #bitcoin-core-dev
20:33 < bitcoin-git> [bitcoin] ryanofsky opened pull request #27604: add ryanofsky to trusted-keys (master...pr/key) https://github.com/bitcoin/bitcoin/pull/27604
20:36 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has quit [Ping timeout: 260 seconds]
20:42 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
20:47 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 240 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:05 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has joined #bitcoin-core-dev
21:05 < BlueMatt[m]> huh, looks like if a transaction gets removed from the mempool bitcoin core just thinks your money disappeared? getbalance shows a reduction and listunspent shows neither the removed-from-mempool transaction nor the previous one.
21:06 < BlueMatt[m]> i know I'm supposed to abandon but that's a highly surprising and confusing result
21:10 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has quit [Ping timeout: 256 seconds]
21:27 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
21:32 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 248 seconds]
21:41 -!- Guest84 [~Guest84@74-194-76-48.montcmta01.res.dyn.suddenlink.net] has joined #bitcoin-core-dev
21:41 -!- Guest84 [~Guest84@74-194-76-48.montcmta01.res.dyn.suddenlink.net] has quit [Client Quit]
21:55 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has joined #bitcoin-core-dev
22:00 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has quit [Ping timeout: 260 seconds]
22:13 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
22:17 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 248 seconds]
22:47 -!- scg [~scg@84.252.114.5] has joined #bitcoin-core-dev
22:51 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
22:58 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 264 seconds]
23:02 < achow101> BlueMatt[m]: pretty sure there's an ancient open issue talking about that, although I can't be bothered to find it right now
23:03 < BlueMatt[m]> probably, i vaguely recall it, but now that fees are high again it smacked me in the face and I went "wow, that's confusing af" and only didnt panic because I recalled this behavior :p
23:03 < BlueMatt[m]> any other sensible user would have panicked :)
23:05 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has joined #bitcoin-core-dev
23:09 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb] has quit [Ping timeout: 264 seconds]
23:27 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
23:32 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 240 seconds]
--- Log closed Tue May 09 00:00:56 2023