00:08 <dzxzg> What is the rationale for marking peers as Misbehaving() as opposed to dropping malformed messages on the ground? if we (the royal node) know something is harmful and we are not processing it anyways, then why also disprefer the peer? It would make more sense to me to impose some cost on peers that ask us to do things that are expensive but which we do anyways, but I'm not sure I follow why we should discourage peers that act out-of-protocol in ways we

00:08 <dzxzg> already ignore. e.g. sending us invalid cmpct blocks

00:10 <dzxzg> if the peer is malicious, why send the invalid message that we ignore at all? it mainly seems to punish peers whose software is buggy / not strictly protocol conforming rather than peers that are deliberately causing harm

00:10 <dzxzg> *it mainly -> Marking as Misbehaving()

00:12 <dzxzg> (I am thinking about this in the context of #35321 which is totally consistent with how Misbehaving() is used in general, and how it's already being used for the happy-path compact blocks, so given status quo seems a reasonable change, but looking at it I felt uncertain that I understood Misbehaving clearly)

00:12 <corebot> https://github.com/bitcoin/bitcoin/issues/35321 | p2p: Misbehave on invalid compact block in optimistic reconstruction by ViniciusCestarii · Pull Request #35321 · bitcoin/bitcoin · GitHub

05:28 <bitcoin-git> [bitcoin] HusseinAdeiza opened pull request #35364: doc: Fix command in build-unix.md example (master...fix-typo-build-unix-docs) https://github.com/bitcoin/bitcoin/pull/35364

05:31 <bitcoin-git> [bitcoin] HusseinAdeiza opened pull request #35365: Fix typo in IPC code comments (master...fix-typo-dededup-comments) https://github.com/bitcoin/bitcoin/pull/35365

06:55 <bitcoin-git> [bitcoin] sedited closed pull request #35365: Fix typo in IPC code comments (master...fix-typo-dededup-comments) https://github.com/bitcoin/bitcoin/pull/35365

08:01 <bitcoin-git> [bitcoin] fanquake closed pull request #35364: doc: Fix command in build-unix.md example (master...fix-typo-build-unix-docs) https://github.com/bitcoin/bitcoin/pull/35364

11:12 <bitcoin-git> [bitcoin] sedited pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/9f7b08c61ca0...de925455c802

11:12 <bitcoin-git> bitcoin/master dfe5d6a frankomosh: fuzz: apply node context reset pattern to p2p_handshake

11:12 <bitcoin-git> bitcoin/master de92545 merge-script: Merge bitcoin/bitcoin#35141: fuzz: apply node context reset pattern to p2p...

11:12 <bitcoin-git> [bitcoin] sedited merged pull request #35141: fuzz: apply node context reset pattern to p2p_handshake (master...fuzz-p2p-handshake-node-context) https://github.com/bitcoin/bitcoin/pull/35141

14:56 <bitcoin-git> [gui-qml] johnny9 opened pull request #724: Node startup and runtime feedback (Errors/Warnings) (qt6...qml-node-runtime-feedback) https://github.com/bitcoin-core/gui-qml/pull/724

15:01 <bitcoin-git> [gui-qml] johnny9 closed pull request #697: Have -disablewallet remove all walletmodels and validate node-only mode with a functional test (qt6...issue-691-disablewallet) https://github.com/bitcoin-core/gui-qml/pull/697

15:02 <bitcoin-git> [gui-qml] johnny9 closed pull request #558: Add MiniBlockClock to the Navigation Bar (qt6...miniblockclock) https://github.com/bitcoin-core/gui-qml/pull/558

15:19 <bitcoin-git> [gui-qml] johnny9 closed pull request #716: Language and Units Functional Test Fix (qt6...lang-functional-test-fix) https://github.com/bitcoin-core/gui-qml/pull/716