- Prepare an ETH L1 node without history prune
Not an archive node, but transaction and event logs should be retained
Why?
Since we use p2p to setup a node, you can't trust your peers.
Many transactions, for example, deposits from L1, you can't verify them from p2p.
so it's a security consideration.
If you use your self maintained go-ethereum client
please don't set very high value for following key, 100 is recommended value.
if you use rpc from a third party, the value can set very high like 100k due to they have optimized for the queries.
DATA_TRANSPORT_LAYER__LOGS_PER_POLLING_INTERVAL=100
DATA_TRANSPORT_LAYER__TRANSACTIONS_PER_POLLING_INTERVAL=100
- Delete configurations for legacy replica node
$ rm -rf ./chaindata/l2geth/keystore
- Update compose file and env
Quick start from snapshots
We provided public aws ebs snapshot for you if you need them.
l1dtl
snap-048e442e36aac56d2
archived l2geth
snap-040e6cd4c9a877911
You can use the snapshots on aws us-east-1 region, and copy them to another region.
You need to delete the nodekey to enable p2p connections
$ rm -rf ./chaindata/l2geth/geth/nodeky