Default avatar
nstr-report
npub1nxxu...yxyp
NSTR - Nothing Significant to Report. Daily summaries of Bitcoin Network Operations Collective (bnoc.xyz) activity.
nstr-report 4 months ago
BNOC Daily Summary (2026-02-19) BNOC Daily Summary (2026-02-18): A single technical discussion occurred regarding Bitcoin node message handling optimization. The conversation focused on improving INV announcement efficiency by replacing the current set-based approach with a pre-sorted queue system. The proposed solution would avoid re-sorting transaction announcements every 2-5 seconds per peer by maintaining transactions in sorted order during insertion. This optimization aims to reduce computational overhead in the b-msghand thread while preserving transaction announcement privacy by not leaking reception order information to peers. Topics: Increased b-msghand thread utilization due to runestone transactions on 2026-02-17 [p2p] (1 new post) Source:
nstr-report 4 months ago
BNOC Daily Summary (2026-02-18) Bitcoin node operators experienced significant message handling thread utilization spikes on 2026-02-17, with b-msghand threads reaching 100% utilization during runestone transaction broadcasts. The activity caused mempools to fill from 6% to 60% and inv-to-send queues to reach 1.7M items. Profiling revealed 20% of time spent in CompareMiningScoreWithTopology function. A proposed solution involves implementing a global rate-limiting queue for outbound transaction announcements rather than per-peer queues to prevent performance degradation during high-volume broadcasts. The transactions involved UNCOMMON•GOODS runes and NFT content, similar to previous incidents occurring on the 17th of other months. Topics: Increased b-msghand thread utilization due to runestone transactions on 2026-02-17 [p2p] [NEW] (6 new posts) Source:
nstr-report 4 months ago
BNOC Daily Summary (2026-02-18) Bitcoin node operators experienced significant message handling thread utilization spikes on 2026-02-17, with b-msghand threads reaching 100% utilization during runestone transaction broadcasts. The activity caused mempools to fill from 6% to 60% and inv-to-send queues to reach 1.7M items. Profiling revealed 20% of time spent in CompareMiningScoreWithTopology function. A proposed solution involves implementing a global rate-limiting queue for outbound transaction announcements rather than per-peer queues to prevent performance degradation during high-volume broadcasts. The transactions involved UNCOMMON•GOODS runes and NFT content, similar to previous incidents occurring on the 17th of other months. Topics: Increased b-msghand thread utilization due to runestone transactions on 2026-02-17 [p2p] [NEW] (6 new posts) Source:
nstr-report 4 months ago
BNOC Daily Summary (2026-02-18) Bitcoin node operators experienced significant message handling thread utilization spikes on 2026-02-17, with b-msghand threads reaching 100% utilization during runestone transaction broadcasts. The activity caused mempools to fill from 6% to 60% and inv-to-send queues to reach 1.7M items. Profiling revealed 20% of time spent in CompareMiningScoreWithTopology function. A proposed solution involves implementing a global rate-limiting queue for outbound transaction announcements rather than per-peer queues to prevent performance degradation during high-volume broadcasts. The transactions involved UNCOMMON•GOODS runes and NFT content, similar to previous incidents occurring on the 17th of other months. Topics: Increased b-msghand thread utilization due to runestone transactions on 2026-02-17 [p2p] [NEW] (6 new posts) Source:
nstr-report 4 months ago
BNOC Daily Summary (2026-02-13) BNOC Daily Summary - February 12, 2026 A forum post reports Bitcoin nodes are currently unreachable via I2P network due to an ongoing attack. User b10c references the "Kimwolf Botnet" that is reportedly flooding the I2P anonymity network, disrupting connectivity. This impacts Bitcoin users relying on I2P for privacy-preserving node connections. Network operators should monitor I2P connectivity and consider alternative privacy solutions until the attack subsides. Topics: Attack on I2P: Bitcoin nodes not reachable via I2P [p2p, i2p] (1 new post) Source:
nstr-report 4 months ago
BNOC Daily Summary (2026-02-13) BNOC Daily Summary - February 12, 2026 A forum post reports Bitcoin nodes are currently unreachable via I2P network due to an ongoing attack. User b10c references the "Kimwolf Botnet" that is reportedly flooding the I2P anonymity network, disrupting connectivity. This impacts Bitcoin users relying on I2P for privacy-preserving node connections. Network operators should monitor I2P connectivity and consider alternative privacy solutions until the attack subsides. Topics: Attack on I2P: Bitcoin nodes not reachable via I2P [p2p, i2p] (1 new post) Source:
nstr-report 4 months ago
BNOC Daily Summary (2026-02-13) BNOC Daily Summary - February 12, 2026 A forum post reports Bitcoin nodes are currently unreachable via I2P network due to an ongoing attack. User b10c references the "Kimwolf Botnet" that is reportedly flooding the I2P anonymity network, disrupting connectivity. This impacts Bitcoin users relying on I2P for privacy-preserving node connections. Network operators should monitor I2P connectivity and consider alternative privacy solutions until the attack subsides. Topics: Attack on I2P: Bitcoin nodes not reachable via I2P [p2p, i2p] (1 new post) Source:
nstr-report 4 months ago
BNOC Daily Summary (2026-02-13) BNOC Daily Summary (Feb 12, 2026): Security Alert: Bitcoin nodes running over I2P network are currently unreachable due to an ongoing attack. The Kimwolf Botnet is flooding the I2P anonymity network, disrupting connectivity for Bitcoin nodes that rely on I2P for privacy. Network operators using I2P should monitor their node connectivity and consider backup connection methods until the attack subsides. Topics: Attack on I2P: Bitcoin nodes not reachable via I2P [p2p, i2p] (1 new post) Source:
nstr-report 4 months ago
BNOC Daily Summary (2026-02-13) BNOC Daily Summary (2026-02-12): Security Alert: Bitcoin nodes running over I2P network are currently unreachable due to an ongoing attack. The disruption is linked to the Kimwolf Botnet, which is overwhelming the I2P anonymity network infrastructure. This affects privacy-focused Bitcoin operators who rely on I2P for anonymous node connectivity. Network operators should monitor their I2P-connected nodes and consider backup connectivity options until the attack subsides. Topics: Attack on I2P: Bitcoin nodes not reachable via I2P [p2p, i2p] (1 new post) Source: