tip · #874,231Lk · 158Brk · 0.94epoch · 6072median · 148Bmempool · 14.2 MvBfee · 24 sat/vBDRA · stableclamp · nonenode · syncedtip · #874,231Lk · 158Brk · 0.94epoch · 6072median · 148Bmempool · 14.2 MvBfee · 24 sat/vBDRA · stableclamp · nonenode · synced
bitcoin · research proposal · 2026

Dynamic Data Rate
Adjustment/ DRA

A self-regulating OP_RETURN policy for Bitcoin. DRA replaces arbitrary data carrier limits with a deterministic, market-responsive mechanism — adapting blockspace capacity to actual on-chain demand.

block height
874,231
mainnet · simulated
DRA limit Lk
160BOP_RETURN
current epoch
6,072
window = 144 blocks
demand ratio rk
0.949
median / Lk-1
live blockflowepoch_window = 8 · simulated
adaptive limit Lkhigh data-pressure blockmoderatenominal
/ design principles
01
Deterministic
Adjustment is computed from on-chain data alone. No oracles, no governance committees, no off-protocol inputs.
02
Market-responsive
Capacity follows demand the way difficulty follows hashrate — measured per epoch, clamped to safe bounds.
03
Manipulation-resistant
Logarithmic damping plus min/max ratio clamps neutralize spam and starvation attacks.
04
Backwards-compatible
DRA replaces only the static datacarrier policy. Consensus rules remain untouched.
/ the mechanism

One equation.
Zero arbitrary constants.

Every epoch, DRA observes the median OP_RETURN payload across the last N blocks and computes a damped log adjustment. The result is clamped between L_min and L_max. The protocol — not a developer — sets the next limit.

core update rule
  Dh   = OP_RETURN bytes in block h
  Mk   = median{ Dh : h ∈ epoch k }
  rk   = clamp( Mk / Lk-1 , r_min , r_max )

  Lk  = clamp( Lk-1 · (1 + ½·log₂(rk)) ,
              L_min , L_max )
epoch · 144 blocks
L_min · 80 B
L_max · 320 B
r ∈ [0.5, 2.0]

Watch the policy evolve.

Open the protocol terminal. Inspect live blocks, run simulations, and see how DRA would have behaved across Bitcoin history.