The August 2026 Bitcoin consensus events
Independent, evidence-first monitoring of the BIP-110 activation window and the expected eCash hard fork. This site pairs a plain-language explanation of what can happen with live data read in the same terms.
feed timestamp: live at launch
The five heights are fixed consensus heights. Dates drift with hashrate and are projections, not consensus parameters, and follow the client-source-aligned projection (the technical walkthrough's independent projection lands up to four days later for the same heights). The current tip, phase, and blocks-to-next values above are read live from the event-clock feed; if it is unreachable, the pending placeholders shown here remain. The passed, next, and "you are here" markers on the rail reflect the live tip the same way.
* The eCash-fork alignment at 963,648 is an expectation from the 2026-07 eCash announcement, not a settled fact, and could still shift. See the eCash stub for the reconfirmable source.
BIP-110 is a temporary restrictive soft fork (Reduced Data Temporary Softfork, RDTS). A BIP-110-valid block is still valid to an unmodified node, but not every ordinary block is valid to a BIP-110 node. Whether that difference ever produces two chains depends on miners, not on the calendar.
The dated, height-stamped developments ledger goes live at launch. The newsroom pipeline publishes sourced entries (BIP-110, eCash, mining, infrastructure, meta), newest first, and the two or three most recent will preview here.
The full timeline of record lives on the Timeline page.
count: live at launch classified as present in Core but not Knots. Absence is a policy difference, not proof of rejection.
Red mark is the 55 percent voluntary threshold. Header bit 4 is a claim, not enforcement.
A crawl sample of advertised flags, not authenticated enforcement or hash power.
| Endpoint | Stratum state |
|---|---|
| OCEAN default | live at launch |
| OCEAN bip110 | live at launch |
| Comparison pool A | live at launch |
Per-endpoint template intent, spooled from Stratum, pending.
What RDTS is, why signalling and enforcement are different things, and what a temporary restrictive soft fork actually restricts.
Read the overview › Data carriageOutput-script size, push limits, witness and Tapscript rules, and how per-input grandfathering actually works.
See the rule set › ActivationSTARTED, mandatory signalling, LOCKED_IN, ACTIVE, EXPIRED, and the scenarios each boundary can produce.
Trace the paths › Reading the live dataWhich header, peer, tip, and mempool signals matter, and why absence never proves rejection.
Learn to read it ›