Skip to content

Staker file generation using openssl #1019

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
jO-Osko merged 1 commit into from
Nov 12, 2025
Merged

Staker file generation using openssl #1019

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 docs/run-node/4-register-validator.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -146,6 +146,16 @@ This poses a risk of staked funds being locked against the unrecoverable NodeID

## Run the node

Create `staker.key` and `staker.crt` files using

```bash
openssl req -x509 -newkey rsa:4096 -keyout staker.key -out staker.crt -days 36500 -nodes -subj '/CN=localhost'
```

You will also need the `signer.key` file which is auto-generated and, by default, found in '~/.avalanchego/staking/' folder.
Note that `staker.key` and `staker.crt` are also auto-generated and stored in the same folder, but you must
**not** use them for successful validator registration!

Now, start your node using command-line flags or environment variables that point to your `staker.key`, `staker.crt` and `signer.key` files.
This ensures your node always starts with the correct `Node-ID`.

Expand Down
Loading