What to know

  • PR36277 was merged onOctober6.
  • Initial private-broadcast connections are completed even after the transaction returns.
  • The change addresses a specific timing concern, not universal Bitcoin anonymity.

What the merged change addresses

Bitcoin Core pull request 36277 was merged on 6 October 2026. It changes the experimental private-broadcast flow so that all three initial private connections complete even when the transaction has already returned through the network. The author links the work to theoretical timing attacks discussed during review. The event is a development-branch merge. Readers should not infer that every released wallet has this behavior or that transaction-origin privacy is now solved for all Bitcoin users.

A privacy signal can be an absence

Privacy analysis often focuses on the information a system sends. This change highlights another possibility: an observer may learn from a connection that ends or behaves differently after an event elsewhere. Our interpretation is that a network feature must consider the relationship between several connections, not simply whether one connection uses an encrypted or privacy-preserving route. The complete sequence can reveal a relationship that is invisible when each individual message is reviewed in isolation.

Why completing work can preserve consistency

Continuing an initial sequence after a result is already known may appear wasteful from a simple performance perspective. From a privacy perspective, consistent behavior can reduce an observer’s ability to distinguish different internal states. That trade-off should be measured rather than hidden. A design review can ask how much additional network activity is required, what signal it is intended to suppress and what other signals remain. None of those questions implies that extra traffic always produces a worthwhile privacy improvement.

A useful threat-model exercise

For developers building transaction-relay tools, draw the parties that can observe each connection and the information they could combine. Then ask whether a peer can trigger a state change through a different path and observe the response. This is a defensive design exercise, not a procedure for probing someone else’s node. Testing should use systems the operator controls, bounded traffic and explicit expected outcomes. BijliCoin has not executed the timing scenario or independently established the complete privacy properties of this change.

The right takeaway for wallet users

A network-level privacy improvement does not erase public transaction history, information supplied to an exchange or metadata shared with a wallet service. Readers should assess the entire workflow rather than treating one opt-in feature as an anonymity switch. The development here is specific and useful: the code is being adjusted to remove one described behavioral clue. Final-release inclusion, compatibility and the remaining threat model still matter. A careful privacy claim says exactly what observation becomes harder and avoids promising protection against every possible observer.

Sources and reading

Editorial note: AI-assisted original BijliCoin synthesis. Original BijliCoin synthesis of the linked public primary source. Analysis and suggested checks are editorial interpretation; reported claims are attributed. Illustration is conceptual, not a photograph of the event.

Sources & context

  1. Bitcoin Core PR36277, merged October 6 ↗

See our editorial policy or report a correction.