# Namada Dry Run Testnet - validator/full node instructions ### Summary: As one of the final steps before mainnet, there will be a coordinated short term public testnet using the finalized genesis files and software release. The primary goals of the dry-run are for validators to test out their keys and configurations and for everyone to test the process of advancing through the phases of mainnet via governance. - Namada version: **[v0.45.1](https://github.com/anoma/namada/releases/tag/v0.45.1)** - CometBFT version **[v0.37.11](https://github.com/cometbft/cometbft/releases/tag/v0.37.11)** - Chain-id: **namada-dryrun.abaaeaf7b78cb3ac** - Starts: **Tuesday, November 12 @ 15:00 UTC** - Duration: **10 days (estimated)** Relevant forum post: https://forum.namada.net/t/namada-dry-run-overview/1029/10 ### Instructions for genesis validators: 1. Install Namada **[v0.45.1](https://github.com/anoma/namada/releases/tag/v0.45.1)** by your preferred method (from source, precompiled binaries). Refer to the docs for [installation instructions](https://docs.namada.net/introduction/install). 2. (Optional) By default, Namada will store its data in `$HOME/.local/share/namada` on Ubuntu systems. This is called the 'base directory'. For instructions on setting a different base directory, see [here](https://docs.namada.net/operators/ledger/base-directory). To check the default base directory on your OS, use `namadac utils default-base-dir`. 3. Set the following environment variables ``` export NAMADA_NETWORK_CONFIGS_SERVER="https://testnet.namada-dryrun.tududes.com/configs" export VALIDATOR_ALIAS=your-validator-alias export CHAIN_ID=namada-dryrun.abaaeaf7b78cb3ac ``` 4. Copy your pre-genesis `validator-wallet.toml` into the following location, creating the directory if necessary: ```$BASE_DIR/pre-genesis/$VALIDATOR_ALIAS/validator-wallet.toml``` **Note:** on Ubuntu, this corresponds to ```~/.local/share/namada/pre-genesis/$VALIDATOR_ALIAS/validator-wallet.toml``` 5. Initialize your node: ``` namadac utils join-network --chain-id $CHAIN_ID --genesis-validator $VALIDATOR_ALIAS ``` 6. Add some persistent peers to your `config.toml` file. First, select from the published list of peers at the bottom of this page. Then, open your node's configuration located at `$BASE_DIR/$CHAIN_ID/config.toml` and find the field `persistent_peers` (which should be empty). Add peers in the format `tcp://<node id>@<IP address>:<port>` separated by commas. Aim to add about 10 persistent peers to your config. **Example on Ubuntu:** In the file `~/.local/share/namada/$CHAIN_ID/config.toml` Add peers following this format (more peers can be found at the bottom of this page): ``` persistent_peers = "tcp://05309c2cce2d163027a47c662066907e89cd6b99@74.50.93.254:26656,tcp://2bf5cdd25975c239e8feb68153d69c5eec004fdb@64.118.250.82:46656" ``` 7. Start *before genesis time* and leave it running -- at genesis time, it will become active. Start your node using the command ```namadan ledger run``` **Note: for instructions on running your node as a `systemd service`, see [here](https://docs.namada.net/operators/ledger/running-a-full-node#running-the-namada-ledger-as-a-systemd-service)** After the initial startup, you should see in the logs: ```Waiting for ledger genesis time: DateTimeUtc(2024-11-12T15:00:00Z)``` If your node is correctly configured as a genesis validator, you should also see: ```This node is a validator.``` 8. At genesis time, once enough voting power is online, you should begin to see new blocks in your node's logs. ### Instructions for full nodes: 1. Same as above 2. Same as above 3. `export NAMADA_NETWORK_CONFIGS_SERVER` and `export CHAIN_ID` only 4. Skip this step 5. Omit the `--genesis-validator` argument: ```namadac utils join-network --chain-id $CHAIN_ID``` 6. Same as above 7. Same as above, except you should see ```This node is not a validator.``` ### Persistent Peers If you want to have your peer listed here for others to use, you can find your node-id with the following command (must be run *after* starting your node): ``` NODE_ID=$(cometbft show-node-id --home $HOME/.local/share/namada/$CHAIN_ID/cometbft/ | awk '{last_line = $0} END {print last_line}') echo $NODE_ID ``` **Persistent Peers List:** ``` tcp://05309c2cce2d163027a47c662066907e89cd6b99@74.50.93.254:26656 tcp://2bf5cdd25975c239e8feb68153d69c5eec004fdb@64.118.250.82:46656 tcp://75825cae136729aaf519ad62684b9b796c5593fd@138.197.133.118:26656 tcp://abcf5f7802dffff5f146edb574f070ab684576a7@176.9.24.46:26656 tcp://08771d75bf7f4421ce6e22c8742101c337e34eec@135.181.5.27:34200 tcp://bdc23b0df729a0f9346d916df09488b1d571cd9e@193.35.50.208:26656 tcp://fe7967decf7aedafc2c1278fea5ae3f6a7395117@75.119.159.247:26656 tcp://c8f1e8090686493e947c84e26ee124c6b1d855b0@148.113.9.92:26655 tcp://bab35c72f4134a03a53cae96bb2992cd155ac1d7@185.16.39.116:26656 tcp://a7afea109743747962849bb81fcb20ecdd7bda38@62.3.101.91:26656 tcp://d4a187ad131d384e802ef1d61ebac2c2cc5f0b05@185.198.49.133:46656 tcp://d882a10dec0da40b045aeb13175a6d4f97194888@62.3.101.89:26656 tcp://d066462f86cf4b7ea7c83140ed2debf6c74966d6@109.123.242.26:26656 tcp://e5182b9bfa6f66c9483e726c2f659f4bce352a8a@213.133.103.17:26656 tcp://6a7918b86ddc7da4d3eba52dc496bb84a56997a5@148.251.84.4:46656 tcp://386e7ed798f41ddc4c406d59f467c8e648391266@namada-p2p.blackblocks.io:26601 tcp://5ae5584f8e8cad6087d8672a2e898c0a88cbb140@namada-p2p.blackblocks.io:26602 tcp://12901e4cbb03c205251abb50492ecef289fed711@namada-p2p.blackblocks.io:26603 ``` ### Additional docs resources: - [Node configuration reference](https://docs.namada.net/operators/ledger/env-vars) - [`systemd` service file example](https://docs.namada.net/operators/ledger/running-a-full-node#running-the-namada-ledger-as-a-systemd-service) - [Operator reference](https://docs.namada.net/operators)