CHIP-2025-03 · Faster Blocks for Bitcoin Cash
Tempnet stress test
One-minute blocks under sustained load. Watch block capacity, fees and next-block inclusion as the experiment runs.
Connecting to the experiment…
Raw data ↗LIVE / OBSERVED TRANSACTIONS
Transaction stream
Waiting for a successful transaction observation.
Each tile is a real campaign transaction; larger tiles represent more serialized bytes on a logarithmic scale. New acknowledgements enter from the left, and observed confirmations move to the right. The first view places existing history without replaying it. This is a bounded sample of the 120 recent acknowledged transactions and40 recent confirmations, updated about every5seconds. Animation shows observed state changes, not measured network propagation. Quiet periods produce no artificial transactions.
01 / BLOCK PRODUCTION
Block timing
Waiting for observed blocks.
Local block receipt intervals, sampled every two seconds, against the 60-second target. Observation gaps and catch-up batches are excluded. Header timestamp intervals are a separate series; individual blocks need not arrive on target.
02 / ADAPTIVE CAPACITY
ABLA: capacity and demand
Waiting for observed blocks.
Actual block size and consensus limit, with control and elastic components normalized to the one-minute interval. Each transition is checked against the pinned BCHN ABLA reference implementation. Sizes are decimal kB.
03 / FEE MARKET
Confirmed fee rates
Waiting for observed blocks.
Confirmed-block fee rates in sat/byte: byte-weighted 10th, 50th and 90th percentiles, excluding coinbase. Coinbase-only blocks have no fee-rate point. Mined fees are not a guaranteed threshold for the next block.
04 / THE NEXT-BLOCK ASSUMPTION
Next-block inclusion by fee
Earlier varied-fee comparison
Current campaign probes pay 1 sat/byte. The historical comparison retains earlier fee bands. Included ÷ eligible probes is shown for each cohort. Eligibility requires confirmed inputs, a stable submission tip, and acknowledgement at least ten seconds before the next canonical block is observed. Boundary races, observation gaps and dependent transactions are excluded. Counts matter: early percentages can represent very small samples.
These observations inform zero-confirmation assumptions. Size, relay, template timing and other miners also affect inclusion; neither confirmation nor DSProof coverage guarantees a zero-confirmation payment.
WORKLOAD
Transaction mix
| Shape | Count | Mean bytes | Mean sat/B |
|---|
P2PKH, consolidations, fan-outs and many-input/output synthetic CashFusion/CoinJoin shapes. Synthetic shapes are not actual mixing sessions. Inventory funding is recorded separately.
CONFLICT DETECTION
Double-spend proofs
Awaiting a controlled pipeline probe.
A controlled P2PKH output is spent twice to test node generation, P2P relay, Fulcrum lookup/subscription and explorer visibility. Intentional conflicts are separate from ordinary fee cohorts. The public faucet's P2SH funding script is outside DSProof coverage.
Recorded observations
CANONICAL CHAIN
Recent observed blocks
| Height | Received · UTC | Transactions | Bytes / limit | Fill | ABLA check |
|---|
EXPERIMENT NOTES
What are we testing?
Load and fee selection
Daily randomized quiet, trickle, flood and sustained-full phases run until November 15, 2026 at 07:00 EST (12:00 UTC). Sustained phases maintain a backlog as ABLA changes the block limit. All new campaign transactions use exactly 1 sat/byte, including funding and conflict probes. Earlier varied-fee observations remain labeled as historical.
All generated spends use outputs controlled by the experiment. There is no monetary fee cap. Inventory is replenished as confirmed inputs run low. Shared-host resource limits can pause new traffic; pauses and stale observations are reported.
Implementation and evidence
Node: BCHN draft MR2184, revision 344220cf5f8a. Protocol target: 60 seconds. Read the Faster Blocks CHIP.
This is one observer's live network experiment, not a controlled estimate of every miner. The public JSON feed contains the displayed aggregates and recent series. Detailed receipts and full history are retained for analysis. Signing keys and private node credentials stay on the backend.