Node Modes of Operation

The Ergo node offers several modes of operation, allowing users to balance resource requirements (disk space, memory, bandwidth) with security assumptions and desired functionality. Choosing the right mode depends on your specific use case, such as running a backend for a dApp, securing personal funds, or simply verifying transactions.

Archival Full Node

Maximum security with complete blockchain history. Stores all blocks and UTXO data from genesis.

Full transaction validation
Complete wallet restore
Full API support
High storage (100s GB+)
Learn More

Pruned Full Node

Full security with reduced storage. Keeps recent blocks and prunes older history.

Full transaction validation
Fast bootstrap sync
No wallet restore
Medium storage (~1-2GB)
Learn More

Light Full Node

Digest mode with minimal storage. Keeps UTXO digest and validates via ADProofs.

Full security
Minimal storage (~1-3GB)
Limited API support
Wallet compatibility issues
Learn More

Light SPV

Ultra-light client for transaction verification. Minimal resources, relies on full nodes.

Very fast sync
Minimal storage (MBs)
No full validation
Relies on full nodes
Learn More

Mode Comparison

Feature / ModeArchival Full NodePruned Full NodeLight Full NodeLight SPV
Primary GoalMax Security, Full HistoryFull Security, Reduced StorageFull Security, Minimal StorageTx Verification, Minimal Resources
Key ConfigstateType="utxo"
blocksToKeep=-1
stateType="utxo"
blocksToKeep > 0
stateType="digest"
blocksToKeep > 0
N/A (Client Software)
BootstrappingFull Sync from GenesisFull Sync / UTXO Snapshot / NiPoPoWFull Sync / NiPoPoW / UTXO SnapshotNiPoPoW Sync
Storage (Initial)Very High (100s GB+)Medium (~1-2GB + Recent Blocks)Low (~1-3GB + Recent Blocks)Very Low (MBs)
Storage (Ongoing)High (Grows with chain)Medium (Grows slowly)Low (Grows slowly)Very Low
Resource NeedsHigh (CPU/RAM/Disk IO)ModerateModerate-LowVery Low
Sync TimeVery LongFast (with bootstrap)Fast (with bootstrap)Very Fast
Full Tx Validation Yes Yes (for kept blocks) Yes (via ADProofs) No
API SupportFullFull (for available data)LimitedN/A
Wallet CompatibilityFull (incl. restore)New Wallets OK; No RestoreNew Wallets OK; No RestoreVerification only
Use CasesMining, Archiving, Max Trust BackenddApp Backend, Personal Wallet BackendMobile Node Backend, dApp BackendLight Wallets, Quick Verification

Detailed Explanations & Notes

1. Bootstrapping (utxoBootstrap, nipopowBootstrap)

  • These settings significantly speed up initial sync for Pruned and Digest nodes by downloading compressed UTXO snapshots or using NiPoPoW proofs.
  • Using utxoBootstrap=true is common for Pruned nodes.
  • Using nipopowBootstrap=true is common for Digest nodes.
  • Enable both for fastest sync, especially on resource-constrained devices.
  • Progress Indication: Monitor network activity or data directory size during large snapshot downloads.

2. Digest Mode (stateType="digest") Limitations

  • Keeps only authenticated digest (root hash) of UTXO set, verifying state transitions using ADProofs.
  • Wallet Compatibility: Users report issues with P2P transaction submission. Verification recommended.
  • API Limitations: Some endpoints requiring full UTXO set access may be unavailable.
  • Peer Relaying: Cannot relay transactions as they don't validate against full UTXO set.

3. Wallet Restoration (Pruned & Digest Modes)

  • Nodes with blocksToKeep > 0 cannot restore wallets from seed phrases if wallets were used before oldest kept block.
  • Use Archival Full Node (blocksToKeep = -1) or trusted explorer service for restoring older wallets.
  • For new wallets created while pruned/digest node is running, restoration might work, but archival node is safest.

4. Resource Usage

  • Storage estimates depend on blocksToKeep setting and chain activity.
  • Typical light/mobile setup using digest mode with bootstrapping: ~3GB initially.
  • Memory requirements vary: archival node (8GB+), pruned/digest nodes (2-4GB), more needed during intense activity.