An archive node used to be all or nothing. In Nethermind 2.0 it's a question: how much history do you need? All of it. Everything since a block you pick. A rolling window. Or the window plus named addresses from genesis. An L2 that settles on @ethereum only needs state back to the end of its challenge window. Keep a month, let the rest age out. Sync it from genesis, or stream our snapshot straight into the DB and have an archive serving in under a day. Either way the node checks what it holds against the block headers. Needs the flat DB layout, the default in 2.0. Existing archives keep working as they are. Also live on @gnosischain. Snapshots for both chains below. RC2 is out: https://github.com/NethermindEth/nethermind/releases/tag/2.0.0-rc2 We post about historical proofs next.