#dusk $DUSK @Dusk I used to think a node caught up to the latest block was basically “fully synced.”
Then Dusk’s operator docs made me separate current state from historical coverage.
The current “Run a provisioner node” guide lists 50 GB of storage. “Run an archive node” starts at 500 GB and adds finalized historical indexes to normal chain state.
The more interesting part is fast sync.
Dusk’s “Fast sync a node” guide says download state restores a published state snapshot so a node can catch up toward the network tip. But it also warns that snapshots do not backfill archive indexes for blocks before the snapshot.
For an archive expected to answer complete history Dusk says to sync from genesis or restore a trusted backup that includes the archive databases.
That changed what “synced” means to me.
Synced to the tip ≠ complete historical coverage.
To be fair provisioners and archives are different node roles with different jobs. Current consensus participation does not require full archive history.
Dusk’s exchange integration docs specifically recommend an Archive Rusk node for finalized Moonlight history and deterministic backfills.
So for production archive infrastructure, should “ready” mean current block height alone or current height plus the earliest finalized block it can actually query?
@Dusk #dusk $DUSK
Then Dusk’s operator docs made me separate current state from historical coverage.
The current “Run a provisioner node” guide lists 50 GB of storage. “Run an archive node” starts at 500 GB and adds finalized historical indexes to normal chain state.
The more interesting part is fast sync.
Dusk’s “Fast sync a node” guide says download state restores a published state snapshot so a node can catch up toward the network tip. But it also warns that snapshots do not backfill archive indexes for blocks before the snapshot.
For an archive expected to answer complete history Dusk says to sync from genesis or restore a trusted backup that includes the archive databases.
That changed what “synced” means to me.
Synced to the tip ≠ complete historical coverage.
To be fair provisioners and archives are different node roles with different jobs. Current consensus participation does not require full archive history.
Dusk’s exchange integration docs specifically recommend an Archive Rusk node for finalized Moonlight history and deterministic backfills.
So for production archive infrastructure, should “ready” mean current block height alone or current height plus the earliest finalized block it can actually query?
@Dusk #dusk $DUSK
