NSTR - Nothing Significant to Report

NSTR - Nothing Significant to Report

NSTR - Nothing Significant to Report

BNOC Daily Summary (2026-02-24) Bitcoin Network Operations Collective Daily Summary: Discussion on BIP-54 coinbase locktime compatibility revealed current pool practices. MARA and f2pool have used nLockTime field for metadata storage, with MARA switching to nVersion field after feedback. F2pool waiting for BIP-54 progress before updating. Positive development: Whitepool became first small pool to implement BIP-54 compatible coinbase transactions in block 937,650, addressing concerns about smaller pool adoption. Topics: Forward-compatible coinbase locktimes for BIP-54 (2 new posts)

Bitcoin Network Operations Collective

Forward-compatible coinbase locktimes for BIP-54

One of the four requirement of BIP-54 (Consensus Cleanup) is that: The coinbase transaction’s nLockTime field must be set to the height of the ...

Source:

Bitcoin Network Operations Collective

Bitcoin Network Operations Collective

A forum for communicating about Bitcoin Network Observations and similar.

BNOC Daily Summary (2026-02-24) Bitcoin Network Operations Collective Daily Summary: Discussion on BIP-54 coinbase locktime compatibility revealed current pool practices. MARA and f2pool have used nLockTime field for metadata storage, with MARA switching to nVersion field after feedback. F2pool waiting for BIP-54 progress before updating. Positive development: Whitepool became first small pool to implement BIP-54 compatible coinbase transactions in block 937,650, addressing concerns about smaller pool adoption. Topics: Forward-compatible coinbase locktimes for BIP-54 (2 new posts)

Bitcoin Network Operations Collective

Forward-compatible coinbase locktimes for BIP-54

One of the four requirement of BIP-54 (Consensus Cleanup) is that: The coinbase transaction’s nLockTime field must be set to the height of the ...

Source:

Bitcoin Network Operations Collective

Bitcoin Network Operations Collective

A forum for communicating about Bitcoin Network Observations and similar.

NSTR - Nothing Significant to Report

NSTR - Nothing Significant to Report

NSTR - Nothing Significant to Report

NSTR - Nothing Significant to Report

NSTR - Nothing Significant to Report

NSTR - Nothing Significant to Report

BNOC Daily Summary (2026-02-21) Two key updates from BNOC today: 1. Stale block dataset now has dedicated website at bitcoin-data.github.io with statistics for 1914 observed stale block headers and full blocks. 2. Response to Feb 17 runestone transaction surge that caused msghand thread to hit 100% CPU and 95MB queue memory: ajtowns submitted PR replacing per-peer transaction rate limiting with global dual token bucket system (14 tx/s count limit, 20 kB/s size limit). This reduces memory/CPU burden from O(queue * peers) to O(queue) during transaction spikes. Topics: Offer: Stale block dataset [data-offer] (1 new post)

Bitcoin Network Operations Collective

Offer: Stale block dataset

I maintain a public bitcoin-data/stale-blocks dataset with stale headers and blocks observed on the Bitcoin network. Feel free to use the dataset ...

Increased b-msghand thread utilization due to runestone transactions on 2026-02-17 [p2p] (1 new post)

Bitcoin Network Operations Collective

Increased b-msghand thread utilization due to runestone transactions on 2026-02-17

I noticed my peer-observer nodes spending a lot of time in b-msghand thread today on 2026-02-17 starting around 1:30 am UTC. Note that the screensh...

Source:

Bitcoin Network Operations Collective

Bitcoin Network Operations Collective

A forum for communicating about Bitcoin Network Observations and similar.

BNOC Daily Summary (2026-02-21) Two key updates from BNOC today: 1. Stale block dataset now has dedicated website at bitcoin-data.github.io with statistics for 1914 observed stale block headers and full blocks. 2. Response to Feb 17 runestone transaction surge that caused msghand thread to hit 100% CPU and 95MB queue memory: ajtowns submitted PR replacing per-peer transaction rate limiting with global dual token bucket system (14 tx/s count limit, 20 kB/s size limit). This reduces memory/CPU burden from O(queue * peers) to O(queue) during transaction spikes. Topics: Offer: Stale block dataset [data-offer] (1 new post)

Bitcoin Network Operations Collective

Offer: Stale block dataset

I maintain a public bitcoin-data/stale-blocks dataset with stale headers and blocks observed on the Bitcoin network. Feel free to use the dataset ...

Increased b-msghand thread utilization due to runestone transactions on 2026-02-17 [p2p] (1 new post)

Bitcoin Network Operations Collective

Increased b-msghand thread utilization due to runestone transactions on 2026-02-17

I noticed my peer-observer nodes spending a lot of time in b-msghand thread today on 2026-02-17 starting around 1:30 am UTC. Note that the screensh...

Source:

Bitcoin Network Operations Collective

Bitcoin Network Operations Collective

A forum for communicating about Bitcoin Network Observations and similar.

BNOC Daily Summary (2026-02-21) Two key updates from BNOC today: 1. Stale block dataset now has dedicated website at bitcoin-data.github.io with statistics for 1914 observed stale block headers and full blocks. 2. Response to Feb 17 runestone transaction surge that caused msghand thread to hit 100% CPU and 95MB queue memory: ajtowns submitted PR replacing per-peer transaction rate limiting with global dual token bucket system (14 tx/s count limit, 20 kB/s size limit). This reduces memory/CPU burden from O(queue * peers) to O(queue) during transaction spikes. Topics: Offer: Stale block dataset [data-offer] (1 new post)

Bitcoin Network Operations Collective

Offer: Stale block dataset

I maintain a public bitcoin-data/stale-blocks dataset with stale headers and blocks observed on the Bitcoin network. Feel free to use the dataset ...

Increased b-msghand thread utilization due to runestone transactions on 2026-02-17 [p2p] (1 new post)

Bitcoin Network Operations Collective

Increased b-msghand thread utilization due to runestone transactions on 2026-02-17

I noticed my peer-observer nodes spending a lot of time in b-msghand thread today on 2026-02-17 starting around 1:30 am UTC. Note that the screensh...

Source:

Bitcoin Network Operations Collective

Bitcoin Network Operations Collective

A forum for communicating about Bitcoin Network Observations and similar.

BNOC Daily Summary (2026-02-20) A single post from ajtowns discusses technical challenges with implementing cluster mempool data structures. The current set-based approach for managing transaction ordering breaks invariants when CPFP transactions change parent transaction priorities, potentially causing undefined behavior with std::set. A sorted queue approach is suggested but requires re-sorting to maintain consistency when new transactions affect existing parent ordering. Topics: Increased b-msghand thread utilization due to runestone transactions on 2026-02-17 [p2p] (1 new post)

Bitcoin Network Operations Collective

Increased b-msghand thread utilization due to runestone transactions on 2026-02-17

I noticed my peer-observer nodes spending a lot of time in b-msghand thread today on 2026-02-17 starting around 1:30 am UTC. Note that the screensh...

Source:

Bitcoin Network Operations Collective

Bitcoin Network Operations Collective

A forum for communicating about Bitcoin Network Observations and similar.

BNOC Daily Summary (2026-02-20) A single post from ajtowns discusses technical challenges with implementing cluster mempool data structures. The current set-based approach for managing transaction ordering breaks invariants when CPFP transactions change parent transaction priorities, potentially causing undefined behavior with std::set. A sorted queue approach is suggested but requires re-sorting to maintain consistency when new transactions affect existing parent ordering. Topics: Increased b-msghand thread utilization due to runestone transactions on 2026-02-17 [p2p] (1 new post)

Bitcoin Network Operations Collective

Increased b-msghand thread utilization due to runestone transactions on 2026-02-17

I noticed my peer-observer nodes spending a lot of time in b-msghand thread today on 2026-02-17 starting around 1:30 am UTC. Note that the screensh...

Source:

Bitcoin Network Operations Collective

Bitcoin Network Operations Collective

A forum for communicating about Bitcoin Network Observations and similar.

BNOC Daily Summary (2026-02-20) A single post from ajtowns discusses technical challenges with implementing cluster mempool data structures. The current set-based approach for managing transaction ordering breaks invariants when CPFP transactions change parent transaction priorities, potentially causing undefined behavior with std::set. A sorted queue approach is suggested but requires re-sorting to maintain consistency when new transactions affect existing parent ordering. Topics: Increased b-msghand thread utilization due to runestone transactions on 2026-02-17 [p2p] (1 new post)

Bitcoin Network Operations Collective

Increased b-msghand thread utilization due to runestone transactions on 2026-02-17

I noticed my peer-observer nodes spending a lot of time in b-msghand thread today on 2026-02-17 starting around 1:30 am UTC. Note that the screensh...

Source:

Bitcoin Network Operations Collective

Bitcoin Network Operations Collective

A forum for communicating about Bitcoin Network Observations and similar.

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)

Bitcoin Network Operations Collective

Increased b-msghand thread utilization due to runestone transactions on 2026-02-17

I noticed my peer-observer nodes spending a lot of time in b-msghand thread today on 2026-02-17 starting around 1:30 am UTC. Note that the screensh...

Source:

Bitcoin Network Operations Collective

Bitcoin Network Operations Collective

A forum for communicating about Bitcoin Network Observations and similar.

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)

Bitcoin Network Operations Collective

Increased b-msghand thread utilization due to runestone transactions on 2026-02-17

I noticed my peer-observer nodes spending a lot of time in b-msghand thread today on 2026-02-17 starting around 1:30 am UTC. Note that the screensh...

Source:

Bitcoin Network Operations Collective

Bitcoin Network Operations Collective

A forum for communicating about Bitcoin Network Observations and similar.

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)

Bitcoin Network Operations Collective

Increased b-msghand thread utilization due to runestone transactions on 2026-02-17

I noticed my peer-observer nodes spending a lot of time in b-msghand thread today on 2026-02-17 starting around 1:30 am UTC. Note that the screensh...

Source:

Bitcoin Network Operations Collective

Bitcoin Network Operations Collective

A forum for communicating about Bitcoin Network Observations and similar.