Skip to content
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

feat: add snapshot reference for mainnet #47

Merged
merged 1 commit into from
Dec 20, 2024
Merged

feat: add snapshot reference for mainnet #47

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
9 changes: 9 additions & 0 deletions pages/node/pd/join-network.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,6 +36,15 @@ configs to a network data directory (by default, `~/.penumbra/network_data`).
If any data exists in the network data directory, this command will fail. See
the section above on resetting node state.

Finally, if the network you're joining has undergone a chain upgrade before,
you'll need to fetch historical blocks from an archive. Here's an example for
how to do that for the `penumbra-1` chain:

```shell
curl -O https://artifacts.plinfra.net/penumbra-1/penumbra-node-archive-latest.tar.gz
tar -xzf penumbra-node-archive-latest.tar.gz -C ~/.penumbra/network_data/node0/
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Draft status because I'm still waiting for this archive to finish uploading...

```

### Running `pd` and `cometbft`

Copy the systemd service configs into place from the [project git repo](https://github.com/penumbra-zone/penumbra):
Expand Down
Loading