ACTUALDynamic Fee ON
SUCCESS
- Token Transfer-event net base units
- Outer Swap fee pips
- Subject gas
The original block replayed. State root, receipts root and block hash matched the canonical record.
RECORDED RESULT · NO LIVE EXECUTION
Hookr / Dynamic Fee
Both succeed.
The economics change.
What if Dynamic Fee had been off for a real historical purchase, while LP Rewards and arb recapture stayed on?
Robinhood Chain 4663 · Block 93251803
A signed 0.01 ETH purchase inside the original seven-arrival block.
Checking the recorded display data…
Recorded data unavailable.
The display summary is missing, altered or inconsistent. No comparison is shown.
BRANCHDynamic Fee OFF
SUCCESS
- Token Transfer-event net base units
- Outer Swap fee pips
- Subject gas
A separate BRANCH world from the original parent state, executed using the same Go/Nitro backend with the declared initial intervention.
Same purchase. Different consequences.
token Transfer-event net
subject gas
outer fee, pips
These are observations of this purchase, not a profit forecast or an independently proven final token balance.
The whole block stays in the experiment.
All seven original arrivals keep their order. The selected purchase is arrival 3. Both histories finish every arrival successfully.
The six other arrivals retain their individual gas and event payloads. State commitments and cumulative gas can still differ after the purchase.
Inspect all seven recorded arrivals
| Arrival | Transaction hash | ACTUAL | BRANCH | Gas ON → OFF |
|---|
Change the rule. Keep the signed inputs.
The intervention happens before arrival 0, at parent checkpoint 93251802. It has whole-block scope, including the arrivals before the selected purchase.
- Rules maxFeePips
- 11500 → 3000
- Rules dynamicFeeSens
- 2 → 0
- Root mode
- 3 → 2
Held fixed
LP Rewards 100. Arb recapture enabled. Original signed transactions, historical router, arrival order and execution environment.
Two initial storage-word writes across Rules and Root. No synthetic funding, transaction re-signing or onchain broadcast.
Inspect exact results and state commitments
Base units are exact integers. A synthetic BRANCH block hash does not identify a block on the live chain.
What supports this result?
The accepted run and the checks in this browser answer different questions.
Recorded native executionCompleted
ACTUAL replay completed, followed by a separate BRANCH world executed using the same Go/Nitro backend. Opening this page does not execute either world.
Original-state inputsAuthenticated in run
Original-parent state proofs and code identities were authenticated in the accepted run. The private witness is not included here; this page does not repeat its MPT checks.
Canonical ACTUALTriple match
ACTUAL stateRoot, receiptsRoot and blockHash matched the historical record before BRANCH execution began.
Recorded evidence integrityPassed in run
The installed verify/compare checked the accepted evidence. This browser checks only the display summary's pinned SHA-256 and structural consistency, not EVM correctness or the original archive.
Independent heterogeneous executionNot established
This case has one Go/Nitro execution backend. No independent Rust result or cryptographic proof of the full state transition is included.
Full Lawful relationUnresolved
The typed admission extension remains experimental. Its full L1–L9 obligations remain unresolved. Qualified Claims for this case: 0. This summary is not a BranchClaim 0.2 or EvidenceEnvelope 0.2.
One case, with a defined boundary.
The retained witness covers this executed plan. The result does not establish arbitrary-pool support, other Hook Block interventions, consensus or finality. Economic assurance remains unresolved.