💬 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.

✅ pinheadmz closed an issue: "Collect node's metrics in Prometheus format"
(https://github.com/bitcoin/bitcoin/issues/10887)

💬 pinheadmz commented on issue "listtransactions results order unkown":
(https://github.com/bitcoin/bitcoin/issues/17739#issuecomment-1525723265)
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: "listtransactions results order unkown"
(https://github.com/bitcoin/bitcoin/issues/17739)

💬 pinheadmz commented on issue "Adoption of BIP39/44/49/84, and classification of (extended) pub/priv keys, addresses, mnemonics, etc":
(https://github.com/bitcoin/bitcoin/issues/17748#issuecomment-1525723992)
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: "Adoption of BIP39/44/49/84, and classification of (extended) pub/priv keys, addresses, mnemonics, etc"
(https://github.com/bitcoin/bitcoin/issues/17748)

💬 pinheadmz commented on issue "Manual-pruning cursor rewind":
(https://github.com/bitcoin/bitcoin/issues/19807#issuecomment-1525725401)
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: "Manual-pruning cursor rewind"
(https://github.com/bitcoin/bitcoin/issues/19807)

💬 pinheadmz commented on issue "BIP158: block filter encoding is inefficient in case of hash collisions":
(https://github.com/bitcoin/bitcoin/issues/27003#issuecomment-1525731399)
This is not a Bitcoin Core problem and should be addressed on the mailing list to update the BIP.

✅ pinheadmz closed an issue: "BIP158: block filter encoding is inefficient in case of hash collisions"
(https://github.com/bitcoin/bitcoin/issues/27003)