Watch the Burn 🔥

When EIP-1559 gets deployed, ETH will be burned in every block if transactions exist. This website will show you how much ETH got burned in total and per block.

If you have a local Ethereum (we use geth but you can use any ETH client) instance, you can update REACTAPPWEB3_URL in .env.production.local to your local ETH instance and run this offline! The instructions below show how to deploy it to a remote website under nginx.

Donate towards Server Costs 💰

The costs of running this experiment is pretty high since it requires a dev version of Geth to be up and running which requires lots of memory and cpu. The VM and SSD storage currently costs exactly $200/month USD. If you would like to help out with the costs, please reach out to me.

If you would like to tip, my gitcoin grant.

Setup dev environment ⚙

Setting up the environment requires a geth instance, daemon geth proxy, and react web app. Optionally, you can install the varnish cache in between.

Setup geth

• Clone geth and build docker image. Assumes /data on local system exists

git clone https://github.com/ethereum/go-ethereum.git
   cd go-ethereum
   docker build -t ethereum-node .
   mkdir /data

• To run Geth inside Docker, run one of the following:

* Mainnet

docker run --net=host --name=geth -dti -v /data:/data ethereum-node --datadir=/data/mainnet --mainnet --port=3030 --http --http.port=8545 --http.api="net,web3,eth" --http.corsdomain="localhost"  --ws --ws.port=8546 --ws.api="net,web3,eth" --ws.origins="*" --maxpeers=100

Setup the Geth Proxy Daemon

• Easiest thing is use docker.

docker build -t geth-proxy ./daemon

• Run the docker instance against your geth.

docker run -d --name=geth-proxy --restart=on-failure:3 --net=host -v /data/geth-proxy:/data geth-proxy --addr=:8080 --geth-endpoint-http=http://localhost:8545 --geth-endpoint-websocket=ws://localhost:8546 --db-path=/data/mainnet.db --development

If you include --initializedb it will start initializing the database since EIP-London, will take time. If you take it out, then it basically just starts at the current head.

Optional: Varnish cache to cache all Geth RPC calls

• Easiest thing is use docker.

docker build -t geth-varnish ./cache

• Run the docker instance against your geth.

docker run -d --name geth-cache --net host -e GETHHTTPHOST=localhost -e GETHHTTPPORT=8545 -e VARNISHPORT=8081 -e CACHESIZE=1g geth-varnish

• Run the daemon against the varnish port.

docker run -d --name=geth-proxy --restart=on-failure:3 --net=host -v /data/geth-proxy:/data geth-proxy --addr=:8080 --geth-endpoint-http=http://localhost:8081 --geth-endpoint-websocket=ws://localhost:8546 --db-path=/data/mainnet.db --development

Setup web dev environment

• Create env file:

cp .env .env.local

• Add your geth ws url to .env.local point it to your daemon port:

REACTAPPWEB3_URL=localhost:8080

• Install packages

npm install

• Run the web app:

npm start

• Launch the web app (goerli):

open http://mainnet.go.localhost:3000:

Some devops maintenance

Send transactions to testnet

Install web3 CLI client curl -LSs https://raw.githubusercontent.com/gochain/web3/master/install.sh | sh use it to create a test account, and you can use it to send transactions.

Access geth console If you ran the mainnet docker geth, you can just do, not rm is there so it cleans the container up after closing!:

docker run --rm -ti -v /data:/data ethereum-node --datadir=/data/mainnet attach