Skip to content

docs(node): add consensus listen-address and chain switching info #52

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

Closed
jenpaff wants to merge 1 commit into from
Closed

docs(node): add consensus listen-address and chain switching info #52

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
10 changes: 10 additions & 0 deletions src/pages/guide/node/rpc.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,16 @@ tempo node \
--http.api eth,net,web3,txpool,trace
```

## Switching chains

When switching between chains (e.g., from Moderato to Presto), use a fresh datadir or delete the existing database:
Copy link
Copy Markdown
Contributor

@kuyziss kuyziss Feb 1, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

shouldn't we also delete the consensus datadir?

Copy link
Copy Markdown
Contributor

@kuyziss kuyziss Feb 1, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

also, it feels kind of obvious and might suggest the wrong ideas for people to reuse the same node for different networks, and then many things can go wrong there, because if we specify this, why don't we also specify that when switching chains they should use a different snapshot arg, different args in general etc?

Copy link
Copy Markdown
Contributor Author

@jenpaff jenpaff Feb 1, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For context was in response to tempoxyz/tempo#2304. Maybe instead of documenting we should find ways to make the UX better when running a tempo node for a different chain e.g. namespaced data dirs


```bash
rm -rf <datadir>/db
```

This is required because each chain has a different genesis block.

## Manually downloading snapshots

Daily snapshots for the persistent testnet can be found at [https://snapshots.tempoxyz.dev](https://snapshots.tempoxyz.dev). You can extract them either using
Expand Down
1 change: 1 addition & 0 deletions src/pages/guide/node/validator.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,6 +47,7 @@ tempo node --datadir <datadir> \
--port 30303 \
--discovery.addr 0.0.0.0 \
--discovery.port 30303 \
--consensus.listen-address 0.0.0.0:8000 \
--consensus.signing-key <path> \
--consensus.fee-recipient <validator_wallet_address> \
```
Expand Down
Loading