Ethras
Ask for Historical Capabilities, Not Just an Archive Node Label
Separate old blocks, receipts, state, proofs, traces, and orphan retention when choosing an Ethereum data source for an application.
Field notes for developers
Ethras Blog
RPC tutorials, product updates, and engineering notes.
An Executable RPC Retry Budget: Bound Amplification Before Backoff
Derive a cross-operation retry bound, calculate pushback-aware schedules, and test a complete outage with a deterministic executable controller.
Diagnose eth_estimateGas Before Increasing the Limit
Separate execution reverts, sender affordability, gas caps, and changing state to make estimation failures actionable.
Ethereum Stablecoin Fortnight: Tracked Dollar-Pegged Supply Fell 4.47%
Ethereum's tracked USD-pegged supply fell 4.47% across two weeks of daily snapshots. We separate the USDT and USDC contribution, changing concentration, and claims the data cannot support.
Ethereum's Quantum Migration: The Hard Part Is Retiring Old Authority
A deeper look at Ethereum's post-quantum transition: legacy account permissions, validator identity, KZG binding, proof aggregation, and the difficult cutover decisions.
RPC API Keys in Browser Apps: What Build Variables Cannot Hide
Learn why frontend environment variables cannot protect RPC credentials, where a server boundary helps, and how to prepare a practical key rotation process.
From Transaction Hash to Finality: Build an Ethereum Receipt Tracker
Track submitted Ethereum transactions through pending, replacement, execution, and finality while keeping retries from creating duplicate business actions.
Estimate Ethereum Fees with eth_feeHistory Without Promising Inclusion
Read base-fee history and tip percentiles, keep fee caps separate from gas limits, and design an estimator with explicit freshness and spending policies.
Glamsterdam ePBS: How Proposers and Builders Divide Block Production
Follow the planned ePBS hand-off from builder commitment to payload reveal, and learn which assumptions operators and applications should review.
JSON-RPC Batches: Match Responses by ID and Recover Partial Results
Build a batch reader that handles out-of-order responses, individual errors, missing results, and notifications without losing successful work.