<maflcko>
fanquake: Error: The action cirruslabs/cache/restore@v4 is not allowed in bitcoin-core/gui because all actions must be from a repository owned by bitcoin-core or match one of the patterns: actions/cache/restore@*, actions/cache/save@*, actions/cache@*, actions/checkout@*, actions/download-artifact@*, actions/upload-artifact@*, ilammy/msvc-dev-cmd@*.
<maflcko>
I guess the settings need to be copy-pasted from bitcoin/bitcoin to bitcoin-core/gui?
<bitcoin-git>
[bitcoin] jmoik opened pull request #33297: cmake: Inherit WERROR setting for secp256k1 build (master...cmake_inherit_Werror_secp256k1) https://github.com/bitcoin/bitcoin/pull/33297
<darosior>
Ugh, do we need to -stopatheight to be able to verify the utxo set hash in chainparams? (Through `dumptxoutset`)
<sipa>
isn't there an index that records the utxo hash at every height?
brunoerg has joined #bitcoin-core-dev
<darosior>
"2. hash_or_height (string or numeric, optional, default=the current best block) The block hash or height of the target height (only available with coinstatsindex)."
<darosior>
From gettxoutsetinfo
<lightlike>
coinstatsindex only saves muhash, assumeutxo uses serialized hash
<lightlike>
could also go back from a synced state ("rollback" parameter of dumptxoutset, or do invalidateblock by hand to stop at that block)
<darosior>
I ended up doing invalidateblock by hand
<sipa>
lightlike: ah, right
SSL has joined #bitcoin-core-dev
<SSL>
I noticed that a lot of you used to come to #bitcoin-pricetalk, please come back so we can actually have some convos.
SSL has left #bitcoin-core-dev [Leaving]
Saturday7 has quit [Ping timeout: 256 seconds]
<shiza>
what is the w icon replacing the bitcoin b on bitcoin-qt?
TallTim_ has quit [Read error: Connection reset by peer]
brunoerg has quit [Remote host closed the connection]
<sipa>
shiza: wayland
<sipa>
it probably means something is misconfigured and the proper icon cannot be found
<shiza>
aight, good
<instagibbs>
the long sought after bitcoin rebrand
<shiza>
instagibbs: sincerely I thought I was being pwned, but funds kept just being there so
<sipa>
if you need a quick way to lose your funds, that can be arranged
<shiza>
D:
TallTim has joined #bitcoin-core-dev
Cory27 has joined #bitcoin-core-dev
Talkless has quit [Quit: Konversation terminated!]
Cory11 has quit [Ping timeout: 250 seconds]
jerryf_ has joined #bitcoin-core-dev
jerryf has quit [Ping timeout: 272 seconds]
Cory27 has quit [Quit: Client closed]
Cory27 has joined #bitcoin-core-dev
jerryf_ has quit [Remote host closed the connection]
jerryf has joined #bitcoin-core-dev
brunoerg has joined #bitcoin-core-dev
<bitcoin-git>
[bitcoin] mzumsande opened pull request #33299: wallet: reduce unconditional logging during load (master...2025_wallet_log_less) https://github.com/bitcoin/bitcoin/pull/33299
brunoerg has quit [Ping timeout: 256 seconds]
dzxzg has quit [Ping timeout: 256 seconds]
dzxzg has joined #bitcoin-core-dev
jespada has joined #bitcoin-core-dev
jespada_ has quit [Ping timeout: 256 seconds]
dermoth has quit [Remote host closed the connection]
dermoth has joined #bitcoin-core-dev
jespada has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
Cory55 has joined #bitcoin-core-dev
Cory27 has quit [Ping timeout: 250 seconds]
LainIwakura has joined #bitcoin-core-dev
LainIwakura has quit [Client Quit]
brunoerg has joined #bitcoin-core-dev
LainIwakura has joined #bitcoin-core-dev
Cory62 has joined #bitcoin-core-dev
Cory55 has quit [Ping timeout: 250 seconds]
Cory46 has joined #bitcoin-core-dev
Cory45 has joined #bitcoin-core-dev
Cory62 has quit [Ping timeout: 250 seconds]
Cory46 has quit [Ping timeout: 250 seconds]
Cory66 has joined #bitcoin-core-dev
Cory45 has quit [Ping timeout: 250 seconds]
Cory91 has joined #bitcoin-core-dev
eugenesiegel has joined #bitcoin-core-dev
Cory66 has quit [Ping timeout: 250 seconds]
brunoerg has quit [*.net *.split]
dzxzg has quit [*.net *.split]
LainIwakura has quit [Quit: Client closed]
<sliv3r__>
Is there a reason why we don't use cmpctblocks with new blocks (recently mined) when doing background validation? I've been monitoring a node for a few hours and I cannot see any cmpctblock log.
<_aj_>
sliv3r__: ah, we won't do high bandwidth compact blocks if we have blocks in flight, which is probably a little buggy. likewise we'll only request as a compact block when mapBlocksInFlight == 1
jerryf_ has joined #bitcoin-core-dev
jerryf has quit [Remote host closed the connection]