Skip to content

Modify the config name #110

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 9, 2025
Merged

Modify the config name #110

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion zq2/docs/nodes/node.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -115,7 +115,7 @@ There are two options you can choose from:
settings to start the node from a checkpoint. Detailed instructions for this configuration
are available in [syncing-from-checkpoints](../nodes/checkpoints/index.md#syncing-a-node-from-a-checkpointsyncing-a-node-from-a-checkpoint).

- Synchronization from the genesis(passive syncing).
- Synchronization from the genesis.

This method initializes the node from the genesis block, ensuring that the node processes
the entire blockchain history. However, this process is time-consuming, as the node must
Expand Down
6 changes: 3 additions & 3 deletions zq2/docs/nodes/passive-pruning.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ Zilliqa nodes support two **mutually exclusive** configuration parameters:
- **Use case:** Ideal for **validator nodes** that only need recent block data for performance.
- **Note:** Pruning only starts **after** more than `N` blocks are present. No backward sync is performed to reach count `N`.

### `node.sync.sync_base_height`
### `node.sync.base_height`

- **Purpose:** Ensures the lowest block retained is at height `N`.
- **Effect:** Deletes blocks **below** height `N` and **passively syncs** blocks from `TIP` backwards to `N`.
Expand Down Expand Up @@ -59,7 +59,7 @@ node.sync.prune_interval = 10000
Set the following in the config:

```toml
node.sync.sync_base_height = 0
node.sync.base_height = 0
```

* Node begins **passive syncing backwards** toward block `0`.
Expand Down Expand Up @@ -88,7 +88,7 @@ node.sync.sync_base_height = 0
| Config | Purpose | Passive Sync | Prune Old Blocks | Use Case |
| ---------------------------- | ------------------------ | ------------ | ---------------- | -------------- |
| `node.sync.prune_interval` | Retain latest `N` blocks | ❌ | ✅ | Validator Node |
| `node.sync.sync_base_height` | Retain from `N` to TIP | ✅ | ✅ | Archive Node |
| `node.sync.base_height` | Retain from `N` to TIP | ✅ | ✅ | Archive Node |

---

Expand Down