🚀 fanquake merged a pull request: "test: perturb anchors.dat to test error during initialization"
(https://github.com/bitcoin/bitcoin/pull/26314)

💬 ismaelsadeeq commented on pull request "rpc: Add importmempool RPC":
(https://github.com/bitcoin/bitcoin/pull/27460#discussion_r1178919301)
Approach ACK
I think here since "apply_unbroadcast_set": True` option is added, we should test mempool unbroadcast set list, else there would be no need for the second option.
```suggestion
assert_equal({}, self.nodes[0].importmempool(mempooldat0, {"apply_fee_delta_priority": True, "apply_unbroadcast_set": True}))
assert_equal(2, self.nodes[0].getmempoolinfo()['unbroadcastcount'])
```

💬 pinheadmz commented on issue "Bitcoin Core v22.0.0 crashes while syncronizing the first local wallet transaction":
(https://github.com/bitcoin/bitcoin/issues/27533#issuecomment-1525343831)
Could you try again with the latest release? (24.0.1) Also, what is the story with this wallet? Was it created with Bitcoin Core back in 2018? How did you load it into your v22.0 node?

💬 adlai commented on issue "Improve transaction privacy / fungibility in Bitcoin Core and the Bitcoin system [meta tracking issues]":
(https://github.com/bitcoin/bitcoin/issues/6568#issuecomment-1525428723)
@pinheadmz could you please edit your closing comment to include links, reducing the amount of fingerprinting that must be suffered by folks reading along?

💬 pinheadmz commented on issue "Improve transaction privacy / fungibility in Bitcoin Core and the Bitcoin system [meta tracking issues]":
(https://github.com/bitcoin/bitcoin/issues/6568#issuecomment-1525459479)
@adlai https://en.bitcoin.it/wiki/Privacy

💬 adlai commented on issue "Improve transaction privacy / fungibility in Bitcoin Core and the Bitcoin system [meta tracking issues]":
(https://github.com/bitcoin/bitcoin/issues/6568#issuecomment-1525476600)
> @adlai https://en.bitcoin.it/wiki/Privacy

Why should I donate my metaphorical guano to the bitcoin-doteyetee domain?

💬 Sjors commented on pull request "assumeutxo: keep cache when flushing snapshot (#17487 followup)":
(https://github.com/bitcoin/bitcoin/pull/27008#issuecomment-1525621866)
@jamesob using the system monitor desktop app in Ubuntu, and I believe also based on the log messages. I'll double check this next time I run it.

💬 brunoerg commented on pull request "test: merge banning test from p2p_disconnect_ban to rpc_setban":
(https://github.com/bitcoin/bitcoin/pull/26863#issuecomment-1525636753)
Rebased

💬 fanquake commented on pull request "ci: use LLVM/clang-16 in native_asan job":
(https://github.com/bitcoin/bitcoin/pull/27360#discussion_r1179101061)
Added here.

💬 fanquake commented on pull request "ci: drop untrusted bpfcc tool usage":
(https://github.com/bitcoin/bitcoin/pull/27510#issuecomment-1525638406)
Combined into #27360. See https://github.com/bitcoin/bitcoin/pull/27360#discussion_r1174994067.

✅ fanquake closed a pull request: "ci: drop untrusted bpfcc tool usage"
(https://github.com/bitcoin/bitcoin/pull/27510)

💬 amitiuttarwar commented on pull request "Relay own transactions only via short-lived Tor or I2P connections":
(https://github.com/bitcoin/bitcoin/pull/27509#issuecomment-1525672113)
concept ACK

a high level question: the privacy benefit comes from the guarantees of using the altnets - the lifecycle of the connection is expected to reveal that the tx is an initial broadcast. if a spy is able to reliably fingerprint a node between networks, this mechanism could potentially degrade privacy. could it be worthwhile to mitigate this by occasionally broadcast non-wallet txs via the same short-lived connections? obv some big tradeoffs, just want to consider the possibility


...

💬 RandyMcMillan commented on pull request "Relay own transactions only via short-lived Tor or I2P connections":
(https://github.com/bitcoin/bitcoin/pull/27509#issuecomment-1525684935)
Concept ACK

💬 RandyMcMillan commented on pull request "Relay own transactions only via short-lived Tor or I2P connections":
(https://github.com/bitcoin/bitcoin/pull/27509#issuecomment-1525701626)
Disagree with:

opened regardless of max connections limits

The connection should be established after another tor/i2p connection is dropped - this way the connection appears to be just another connection - nothing special about it.

💬 RandyMcMillan commented on pull request "Relay own transactions only via short-lived Tor or I2P connections":
(https://github.com/bitcoin/bitcoin/pull/27509#issuecomment-1525715201)
It may also be useful to randomize the duration of the connection?

Additionally - padding the connection with dummy txs during its lifecycle may help obfuscate the real payload?

💬 pinheadmz commented on issue "Add a footgun warning to any privkey operation. ":
(https://github.com/bitcoin/bitcoin/issues/4176#issuecomment-1525717868)
This issue is unlikely to be fixed in Bitcoin Core. We'll close for now, but feel free to open another issue or pull request with a fix.

✅ pinheadmz closed an issue: "Add a footgun warning to any privkey operation. "
(https://github.com/bitcoin/bitcoin/issues/4176)

💬 pinheadmz commented on issue "MAX_BLOCK_SERIALIZED_SIZE is not a consensus-enforced constant":
(https://github.com/bitcoin/bitcoin/issues/10289#issuecomment-1525718536)
This issue is unlikely to be fixed in Bitcoin Core. We'll close for now, but feel free to open another issue or pull request with a fix.

✅ pinheadmz closed an issue: "MAX_BLOCK_SERIALIZED_SIZE is not a consensus-enforced constant"
(https://github.com/bitcoin/bitcoin/issues/10289)

💬 pinheadmz commented on issue "Collect node's metrics in Prometheus format":
(https://github.com/bitcoin/bitcoin/issues/10887#issuecomment-1525719090)
This issue is unlikely to be fixed in Bitcoin Core. We'll close for now, but feel free to open another issue or pull request with a fix.