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.

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

Update remote-signing.mdx #411

Merged
merged 1 commit into from
Dec 2, 2024
Merged
Changes from all commits
Commits
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
8 changes: 8 additions & 0 deletions packages/docs/pages/operators/remote-signing.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,14 @@ This guide is intended for Namada Validator operators. It outlines the use of Ho

--- Please note that you can use IP addresses instead of DNS A records. However, I’m using DNS A records here for simplicity and flexibility in managing domain names and potential future changes. Using a domain name allows easier maintenance if the server’s IP address changes.Using IP addresses directly might provide more security since it can help obscure your setup, making it less easily discoverable via DNS lookups. However, keep in mind that this is not a complete security measure, as IP addresses can still be traced through network scans.

## Namada Validator Node Config Requirements :

- `tendermint_mode` should be set to `"Validator"`
- For an advanced setup (e.g., adding sentry nodes to enhance protection against DDoS attacks), the usual configuration involves 3 signers, 3 sentry nodes, and 3 validators. In this case:
On the sentry nodes, set `tendermint_mode = "Full"`.
On the validators, set `tendermint_mode = "Validator"`.
- If not using sentry nodes, simply set `tendermint_mode = "Validator"`.

## Run These Steps on All Signer Servers:

1. Create a directory to organize your Horcrux files:
Expand Down
Loading