09:07 <Sjors[m]> "rogue calls in mining functions" - ominous

14:06 <bitcoin-git> [bitcoin] krishpranav opened pull request #31735: Fix compilation errors in blockchain.cpp related to serialization, UTXO dumping, and path conversion (master...master) https://github.com/bitcoin/bitcoin/pull/31735

14:15 <sipa> glozow: a random idea about orphan memory accounting, to get the best of both worlds (guaranteed per-peer orphan space, but higher global limit while not under attack): every peer has an orphan reservation size (e.g. 4MW per outbound, 400kW per inbound), and the global orphan limit is the sum of the reservations (which is thus dynamic). Orphans are accounted for for *each* peer (regardless of

14:15 <sipa> however many peers announced jt). Orphan evictions only happen...

14:15 <sipa> when the global limit is exceeded, and find the peer whose usage/reservatiom ratio is the highest (and only removes the orphan from that peer, others may remain, and thus more evictiond may be needed).

14:16 <sipa> as long as no peer goes above their reservation, no evictions can happen, so it is at least as good in that regard as the alternative of just having strict per-peer accounting

14:18 <sipa> I don't know if any of this is necessary though, I think strict per-peer accounting is fine, and is more categorically safe in the sense that attackers cannot even influence eviction decisions for other peers

19:41 <bitcoin-git> [bitcoin] espi3 opened pull request #31736: .github/workflows/ci.yml link hygiene (master...minor-ci-doc-updates) https://github.com/bitcoin/bitcoin/pull/31736

21:19 <fjahr> darosior: We should keep having this conversation but it does feel like we are going in circles a bit. I don't remember if you were in Dublin!? We had two discussions around this topic and the prio projects came out of that meeting. See https://btctranscripts.com/bitcoin-core-dev-tech/2023-04/2023-04-26-meta-discussion and https://btctranscripts.com/bitcoin-core-dev-tech/2023-04/2023-04-25-refactors While not everyone was

21:19 <fjahr> there, I think a good starting point would be to discuss how people reflect on the discussions back then ~2 years later. But I don't know if that happened as part of what kicked off the WGs because I wasn't there for that one and thus feel a bit out of the loop on this front at the moment.

21:37 <fjahr> Sharing my slides from back with you directly to give more context, if anyone else is interested let me know.

23:50 <achow101> #31622 gui#850 bips#1695 bitcoincore.org#1100

23:50 <corebot> https://github.com/bitcoin/bitcoin/issues/31622 | psbt: add non-default sighash types to PSBTs and unify sighash type match checking by achow101 · Pull Request #31622 · bitcoin/bitcoin · GitHub

23:50 <corebot> https://github.com/bitcoin/bips/issues/1695 | BIP373: Clarify where keys in MuSig fields may appear in the Taproot output by achow101 · Pull Request #1695 · bitcoin/bips · GitHub

23:50 <corebot> https://github.com/bitcoin-core/gui/issues/850 | gui, psbt: Use SIGHASH_DEFAULT when signing PSBTs by achow101 · Pull Request #850 · bitcoin-core/gui · GitHub

23:50 <corebot> https://github.com/bitcoin-core/bitcoincore.org/issues/1100 | Bitcoin Core 28.1 by achow101 · Pull Request #1100 · bitcoin-core/bitcoincore.org · GitHub

23:50 <achow101> yay new irc bot

23:56 <sipa> secp256k1#1519

23:56 <sipa> :(

23:56 <achow101> try again

23:57 <achow101> secp256k1#1519

23:57 <corebot> https://github.com/bitcoin-core/secp256k1/issues/1519 | Add BIP352 `silentpayments` module by josibake · Pull Request #1519 · bitcoin-core/secp256k1 · GitHub

23:57 <achow101> :)

23:58 <sipa> dank

23:58 <achow101> I can have the bot join #secp256k1 too, if that's useful

23:58 <achow101> and have the default for #<numbers> be the secp repo

23:59 <sipa> yeah, i think that would be nice