Archive-capable nodes must retain historical application state and indexes. A node bootstrapped from a state-sync snapshot does not have pre-snapshot historical state, so a full archive node must replay from genesis if it is expected to serve complete historical queries.

​
Archive configuration

Set application pruning for full historical state: 
pruning = "nothing"
pruning-keep-recent = "0"
pruning-keep-every = "0"
pruning-interval = "0"
min-retain-blocks = 0
Retain historical ABCI responses and transaction indexes: 
[storage]
discard_abci_responses = false

[tx_index]
indexer = "kv"
Enable EVM historical indexing on archive RPC profiles: 
[json-rpc]
enable-indexer = true
The full archive example disables CometBFT state sync: 
[statesync]
enable = false
The [state-sync] snapshot settings in app.toml are for serving snapshots to other nodes. They do not preserve local pre-snapshot history.

​
RPC and debug policy

The default public EVM namespace allowlist is: 
api = "eth,net,web3"
Archive sentry examples may include txpool. The full archive example includes debug, txpool, and personal, with EVM tracing configured through: 
[evm]
tracer = "json"
Do not claim uniform txpool or debug tracing support unless the deployed node’s app.toml includes those namespaces.

​
Archive sizing and backups

Size archive hosts with at least 1 TB initial archive disk, expected archive growth of about 10 GB/month, and 2 TB recommended headroom. Run archive backups monthly and keep enough spare capacity for compaction, upgrades, logs, and backup staging.

​
Application alternatives

Most applications do not need an archive node. Use: