The earlier infrastructure notebook paired Besu IBFT 2.0 with Terraform-managed cloud hosts, Ethstats, and Ethernal/Blockscout explorers. Its useful structure is the progression from chain identity to observable application behavior.
Establish the same network
Generate the genesis configuration and validator keys, distribute the intended genesis file, configure discovery/bootstrap peers, and start the nodes. Agreement on genesis and validator membership matters separately from peer connectivity.
| Component | Observation to establish |
|---|---|
| Validator client | Expected chain identity, peers, and consensus participation |
| RPC | Actual responses for the intended chain and block progression |
| Wallet | Correct network selection and a confirmed example interaction |
| Explorer | Indexing the same chain, with visible indexing lag |
| Monitoring | Fresh host/client metrics and meaningful alert delivery |
A dashboard, RPC response, and explorer page each prove only their own part of that path.
Keep experiment parameters with the experiment
The source recorded a 30-million gas limit, a one-second block target, and a minimum gas-price setting of 1,000 wei. Those are recorded choices, not universal Besu defaults or demonstrated capacity. Its Ubuntu 20.04 and t3.medium-era hardware suggestions also require workload-specific validation.
Estimate disk from retained data
The old calculation assumed one roughly 1 KB block per second for ten 365-day years. That arithmetic gives 315,360,000 blocks, or about 315.36 decimal GB at exactly 1,000 bytes each. It is a hypothetical block-data total, not a minimum database size or a storage plan.
The source’s fixed 109-byte transaction breakdown was inconsistent and did not model the actual transaction encoding. State, receipts, indexes, client database overhead, pruning/history policy, snapshots, and backups change retained disk use. Measure growth for the selected client configuration and workload.
Sources: earlier infrastructure repository and Besu IBFT tutorial. No cloud host, key, chain, transaction, or Terraform deployment was created.