Open ytrezq opened 2 years ago
I just need my own node enpoint parity_tracecallmany for evading Tornado Cash rpc censorship so I would like to reduce database size for the consensus layer since I just need the execution layer.
A consensus node with state history is not required for an archival execution node. Lighthouse will store all historic blocks even when running in "pruned" mode, which is all that's required to fetch execution node history.
I also failed to find how to run lighthouse as a light client.
We don't have a light client.
I'll leave this issue open for someone to update the docs
@michaelsproul sorry for the wording but how to run lighthouse in pruned mode with only storing the last 10 epochs then?
@ytrezq There's no mode that just stores the last N epochs. Your options currently are:
--slots-per-restore-point
flag, this will use anywhere from 50GB-3TB more disk space. More info here: https://lighthouse-book.sigmaprime.io/advanced_database.html.It has been a while since the issue is open, at this moment, the pruning in Lighthouse is pretty much auto-prune for states, blobs and payloads, see: https://discord.com/channels/605577013327167508/746918775919738893/1262720320465539112
The database for a freshly synced beacon node is ~100-120 GB
If you want to run as archive node (which is not required unless you want access to full states information), refer: https://lighthouse-book.sigmaprime.io/checkpoint-sync.html#reconstructing-states
I couldn’t find the answer myself. I just need my own node enpoint
parity_tracecallmany
for evading Tornado Cash rpc censorship so I would like to reduce database size for the consensus layer since I just need the execution layer.I also failed to find how to run lighthouse as a light client.