Merge branch 'master' into production

packages/docs/pages/networks/testnets.en-US.mdx

@@ -5,11 +5,11 @@ For more context read:
 [Announcing Namada Public Testnets](https://blog.namada.net/announcing-namada-public-testnets/)
 
 ## Latest Testnet
-- Namada public testnet 14:
-  - From date: 5th of October 2023 17:00 UTC
-  - Namada protocol version: `v0.23.0`
+- Namada public testnet 15:
+  - From date: 14th of December 2023 17:00 UTC
+  - Namada protocol version: `v0.28.0`
   - Cometbft version: `0.37.2`
-  - CHAIN_ID: `public-testnet-14.5d79b6958580`
+  - CHAIN_ID: `tbd`
 
 The history of all testnets can be found [here](./testnets/testnet-history.mdx).
 
@@ -25,9 +25,9 @@ If you find a bug, please submit an issue with the `bug` [issue template](https:
 
 1. [Environment setup](./testnets/environment-setup.mdx)
 2. [Pre-genesis instructions](./testnets/pre-genesis.mdx)
-3. [Pre-genesis validator setup](../operators/validators/genesis-validator-setup.mdx)
+3. [Pre-genesis validator setup](../operators/validators/validator-setup.mdx)
 4. [Pre-genesis validator apply](./testnets/genesis-validator-apply.mdx)
-5. [Running your genesis validator](../operators/validators/run-your-genesis-validator.mdx)
+5. [Running your genesis validator](../operators/validators/validator-setup.mdx#start-validating)
 6. [Running a full node](../operators/ledger/running-a-full-node.mdx)
 7. [Becoming a validator post-genesis](./testnets/post-genesis-validator.mdx)
 

packages/docs/pages/networks/testnets/campfire.en-US.mdx

@@ -18,7 +18,7 @@ The most up-to-date docs on joining Campfire ⛺🔥 can be found [here](https:/
 Currently, Campfire ⛺🔥 docs only detail support for Ubuntu machines. 
 </Callout>
 
-The user will need to have installed the [Stack-Orchestrator](https://github.com/vknowable/stack-orchestrator), which is a general tool for quickly and flexibly launching and managing a software stack in a containerized environment. The docs are found in the [README](https://github.com/vknowable/stack-orchestrator/README.md) of the repo, and the tool can be installed by running the following command:
+The user will need to have installed the [Stack-Orchestrator](https://github.com/vknowable/stack-orchestrator), which is a general tool for quickly and flexibly launching and managing a software stack in a containerized environment. The docs are found in the [README](https://github.com/vknowable/stack-orchestrator/#readme) of the repo, and the tool can be installed by running the following command:
 
 ```bash copy
 git clone https://github.com/vknowable/stack-orchestrator.git

packages/docs/pages/networks/testnets/faq.en-US.mdx

@@ -2,7 +2,7 @@
 
 ### **Q: How do I join as a validator post-genesis?**
 
-**A:** Joining as a validator post genesis can be done following [these instructions](../../operators/validators/post-genesis-validator-setup.mdx).
+**A:** Joining as a validator post genesis can be done following [these instructions](../../operators/validators/validator-setup.mdx).
 
 ### **Q: How do I use the Faucet?**
 

packages/docs/pages/networks/testnets/genesis-validator-apply.en-US.mdx

@@ -6,33 +6,68 @@ Before a testnet launches, you can apply to be a genesis validator.
 
 ### Set up
 
-Follow [this guide](../../operators/validators/genesis-validator-setup.mdx#pre-genesis) on how to generate your "pre-genesis" validator files.
+Follow [this guide](../../operators/validators/validator-setup.mdx#pre-genesis) on how to generate your "pre-genesis" validator files.
 
-After this, you'll have a `validator.toml` file, the contents of which will look something like the following:
+<Callout>
+All pre-genesis validators are expected to bond `1000000` NAM tokens. At least that many tokens will be allocated to the pre-genesis validator key
+</Callout>
+
+After this, you'll have a signed `transactions.toml` file, the contents of which will look something like the following:
 
 ```toml
-[validator.1337-validator]
-consensus_public_key = "00056fff5232da385d88428ca2bb2012a4d83cdf5c697864dde34b393333a72268"
-eth_cold_key = "0103d985a8345ef505cf139c3dfbd5f5a1da73d2864c62ce9d0a98da73898a59f6f9"
-eth_hot_key = "010241bb691e44dd3c4263522474e45751e97307e92326250f96c1bcd0a06880875d"
-account_public_key = "00f1bd321be2e23b9503653dd50fcd5177ca43a0ade6da60108eaecde0d68abdc8"
-protocol_public_key = "0054c213d2f8fe2dd3fc5a41a52fd2839cb49643d960d7f75e993202692c5d8783"
-dkg_public_key = "6000000054eafa7320ddebf00c9487e5f7ea5107a8444f042b74caf9ed5679163f854577bf4d0992a8fd301ec4f3438c9934c617a2c71649178e536f7e2a8cdc1f8331139b7fd9b4d36861f0a9915d83f61d7f969219f0eba95bb6fa45595425923d4c0e"
+[[established_account]]
+vp = "vp_user"
+threshold = 1
+public_keys = ["tpknam1qrf7k5r2kvuppxnp0ruapkkd5szmyxzjxg7t64salgz5wrf6d327wmdh8xj"]
+
+[[validator_account]]
+address = "tnam1q9yprrkkhy0kfngwg59rxx9q2f8kj5ufhctn4n6u"
+vp = "vp_user"
 commission_rate = "0.01"
-max_commission_rate_change = "0.05"
-net_address = "1.2.3.4:26656"
-tendermint_node_key = "00e1a8fe1abceb700063ab4558baec680b64247e2fd9891962af552b9e49318d8d"
+max_commission_rate_change = "0.01"
+net_address = "1.2.3.4:1000"
+
+[validator_account.consensus_key]
+pk = "tpknam1qz2t8q4xt0vtm4x8kclr4lxhp0sea3956jzltdc2kqx4428a3queja2jx7p"
+authorization = "signam1qp2a25j2x2u5ggawvd6fa4z8h7m0tw3ndtulzfwzxtfe6487arazthq2s28v5lmekn6dlp9qukehxwvanzyhfcgqpu7y6cut5l928qsxr3pp7k"
+
+[validator_account.protocol_key]
+pk = "tpknam1qzwl3qsqtthmdwa2xn8pgymlsl3r8mdx53qgpm7xwwxgmn4hg0hjccnd27q"
+authorization = "signam1qzp03svcajhr7f68ayy3kq8xq4l78j7qdnxfc2v0g3s0qt69gkxhm0kx866hg77wty9hj004jfn94pavkmfqxqhyypjs0padv99vrjsqeqgg9q"
+
+[validator_account.tendermint_node_key]
+pk = "tpknam1qqwxpdvqyqlke25cfg46knx3slmzl84ap6v3kunu5r4efu3va3n7zf7nduz"
+authorization = "signam1qpwzap7pczw3dlxjjxauhls9rya4fpxu4mmtrplkx9yfur5t3cf4wmwkvexnd4jyaeme3l9tfuxt7aapzzmjjsejsz8zz5upccykafgyu3dzqm"
+
+[validator_account.eth_hot_key]
+pk = "tpknam1qypdeegcgv32w6ynrqsaml546rn9jr8ua9pv54t0dpdyuf2069eyflghxz99u"
+authorization = "signam1qx5ve2mcu2s8pajr4w6tat9z3v3p4g75zy9vug0w7epwdzapg7k8u3jxrsg5kax4xk7p3maxv49va98hsz6ntdfs2fx3whk70raepyg3qyn0nufq"
+
+[validator_account.eth_cold_key]
+pk = "tpknam1qyp0659xh8e8la0gx39f40epmamgug5l2ddgpplfe2zgpm8xlk7yzhcpnfx2e"
+authorization = "signam1q806c02930rdnac5jtxtnmdr6jwhfwteu4eqchu0xe5jgaqsv0znztam6u3tyatme6fh72les7d502wpajqa0v8l5kc8cpef4nv8py5lqyv80ct3"
+
+[validator_account.metadata]
+email = "[email protected]"
+
+[validator_account.signatures]
+tpknam1qrf7k5r2kvuppxnp0ruapkkd5szmyxzjxg7t64salgz5wrf6d327wmdh8xj = "signam1qptu8kxn9apr7e7h438d60gsaqyupvgcur9rcxva4ft3vzh67y4qv2v2rm7ugg469kpe6qx7cr206n8tk0daqw9h03k72m6ffqwf56swvg0cjs"
+
+[[bond]]
+source = "tnam1q9yprrkkhy0kfngwg59rxx9q2f8kj5ufhctn4n6u"
+validator = "tnam1q9yprrkkhy0kfngwg59rxx9q2f8kj5ufhctn4n6u"
+amount = "100"
+
+[bond.signatures]
+tpknam1qrf7k5r2kvuppxnp0ruapkkd5szmyxzjxg7t64salgz5wrf6d327wmdh8xj = "signam1qqgn525t548eg7nrwhrlke0n6r8d3zqw79tdkeyva79r6snc26ew6fq2fkvunljw7l6hq5ed6e8dqyaq9afexwd88gnprlusjds77qgq57ej0a"
 ```
 
 This file contains only public information and is safe to share publicly.
 
-<Callout>
-The field `tendermint_node_key` is named this for legacy reasons. It is actually the CometBFT consensus public key.
-</Callout>
 
 ### Submitting the config
-If you want to be a genesis validator for the testnet, please make a pull request to https://github.com/anoma/namada-testnets adding your validator.toml file to the relevant directory (e.g. `namada-public-testnet-2` for the second public testnet), renaming it to `$alias.toml`. 
-E.g. if you chose your alias to be "bertha", submit the file with the name `bertha.toml`. You can see what an example PR looks like [here](https://github.com/anoma/namada-testnets/pull/29).
+If you want to be a genesis validator for the testnet, please make a pull request to https://github.com/anoma/namada-testnets adding your signed `transactions.toml` file to the relevant directory (e.g. `namada-public-testnet-2` for the second public testnet), renaming it to `$alias.toml`. 
+E.g. if you chose your alias to be "bertha", submit the file with the name `bertha.toml`. You can see what an example PR looks like [here](https://github.com/anoma/namada-testnets/pull/2616).
 
 ### Wait for the `CHAIN_ID`
 Wait until the corresponding `CHAIN_ID` has been distributed.

packages/docs/pages/networks/testnets/joining-the-testnet.en-US.mdx

@@ -5,7 +5,7 @@ Depending on whether you are a genesis validator, you can join the latest testne
 ## Joining as a genesis validator
 Joining the testnet validator is identical to that of a mainnet validator.
 
-For this reason, please refer to [these docs](../../operators/validators/run-your-genesis-validator.mdx).
+For this reason, please refer to [these docs](../../operators/validators/validator-setup.mdx#start-validating).
 
 ## Joining as a full node
 If you are not a genesis validator, please follow the steps for [joining as a full node](../../operators/ledger/running-a-full-node.mdx). 

packages/docs/pages/networks/testnets/migrating-testnets.en-US.mdx

@@ -2,74 +2,6 @@ import { Callout, Steps } from 'nextra-theme-docs'
 
 # Steps for migrating testnets
 
-This guide will help you migrate your validator node from one testnet to another. These steps are optional, and for most testnets, these steps will not be needed.
-
-## Resetting your validator node (optional)
-
-<Callout type="info">
-With the release of `v0.19.0` we have introduced mandatory keys for validators. These keys are `eth_hot_key` and `eth_cold_key` that are used for Ethereum bridge purposes.
-</Callout>
-
-### Locate the namada base directory
-
-Depending on the testnet you are migrating from, the base directory will be located in different places.
-For this reason, we will save the base directory path to a variable.
-
-#### Before `v0.15.3`
-If you are migrating from a testnet BEFORE `v0.15.3`, then your home directory and relevant files will be located in a `.namada`. The location of this directory depends where you initially ran the command `namadac utils join-network --chain-id <CHAIN_ID> --genesis-validator <ALIAS>`. It will be located in the directory in which that command was executed.
-
-Once located, you can save the base directory path to a variable. For example, if the join-network command was ran from your home directory, you can run:
-```bash copy
-export BASE_DIR=$HOME/.namada
-```
-
-#### After `v0.15.3`
-If you are migrating from a testnet AFTER `v0.15.3`, then your base directory and relevant files will be located in `.local/share/namada` on Linux and `Library/Application Support/Namada` on MacOS. You can verify the default directory on your machine by running:
-```bash copy
-export BASE_DIR=$(namadac utils default-base-dir)
-```
-
-
-<Callout type="info" emoji="🤓">
-Technically, the correct directory will be the one assigned to `$XDG_DATA_HOME`, 
-but if you haven't set that variable, it will default to the one given above.
-</Callout>
-
-<Steps>
-### IMPORTANT! Save your `pre-genesis` folder in the ledger base directory
-
-Before we delete any folders, we want to make sure we save our `pre-genesis` folder. This folder contains your validator keys, and we want to make sure we don't lose them.
-
-```bash copy
-mkdir $HOME/backup-pregenesis && cp -r $BASE_DIR/pre-genesis $HOME/backup-pregenesis/
-```
-
-### **Ensure keys are saved**
-
-`ls backup-pregenesis` should output a saved `wallet.toml`.
-
-###  Delete the base directory
-
-```bash copy
-rm -rf $BASE_DIR/*
-```
-
-### Check that namada and cometbft binaries are correct. 
-
-`namada --version` should yield `v0.22.0` and `cometbft version` should output `0.37.2`
-
-
-
-### Create a pre-genesis directory
-
-```bash copy
-mkdir $BASE_DIR/pre-genesis
-```
-
-### Copy the backuped file back to `$BASE_DIR/pre-genesis` folder
-```bash copy
-cp -r backup-pregenesis/* $BASE_DIR/pre-genesis/
-```
-</Steps>
-
-**You should now be ready to go!**
+<Callout>
+With the introduction of `v0.28.0` there is no way to migrate keys over. Please follow the instructions from scratch.
+</Callout>

packages/docs/pages/networks/testnets/post-genesis-validator.en-US.mdx

@@ -2,7 +2,7 @@
 
 After genesis, you can still join the network as a user and become a validator through self-bonding. 
 
-After [joining the network as a full node](../../operators/ledger/running-a-full-node.mdx), you must [create a validator account](../../operators/validators/post-genesis-validator-setup.mdx).
+After [joining the network as a full node](../../operators/ledger/running-a-full-node.mdx), you must [create a validator account](../../operators/validators/validator-setup.mdx).
 
 After this has been completed, you will need to increase your validator's `bonded-stake`, which can be done by self-bonding tokens sourced from the faucet.
 

packages/docs/pages/networks/testnets/testnet-history.en-US.mdx

@@ -6,41 +6,25 @@ This page covers all installation steps required by various upgrades to testnets
 
 ## Latest Upgrade
 
-- Namada public testnet 14 (soft-upgrade hot-fix):
-  - From date: 19th of October 2023 9:00 UTC
-  - Namada protocol version: `v0.23.1`
-  - Cometbft version: `0.37.2`
-  - CHAIN_ID: `public-testnet-14.5d79b6958580`
+No upgrades are currently scheduled.
 
-How to upgrade to the latest testnet:
-The upgrade is a soft upgrade, meaning that there is no consensus breaking change to the new binaries, and they are backwards compatible. Validators are encouraged to upgrade to the latest version of the binaries, which can be found [here](https://github.com/anoma/namada/releases/tag/v0.23.1)
-
-Then, simply stop the current ledger and restart it with the new binaries. This can be done by running the following commands:
+## Latest Testnet
 
-```bash copy
-OS="Linux" # Or OS="Darwin" for Mac
-wget https://github.com/anoma/namada/releases/download/v0.23.1/namada-v0.23.1-${OS}-x86_64.tar.gz
-tar -xvf namada-v0.23.1-${OS}-x86_64.tar.gz --strip-components 1 -C /usr/local/bin/ #sudo may be required
-killall namadan
-namada --version #should output v0.23.1
-NAMADA_CMT_STDOUT=true namada node ledger run
-```
+- Namada public testnet 15:
+  - From date: 14th of December 2023 17:00 UTC
+  - Namada protocol version: `v0.28.0`
+  - Cometbft version: `0.37.2`
+  - CHAIN_ID: `tbd`
 
-<Callout type="info">
-Note that the `v0.23.1` Linux binaries require Ubuntu LTS, which means that some older versions of Ubuntu will not be compatible (only Ubuntu `22.04` or later). In this case, it is recommended to build from source in order to upgrade.
-</Callout>
 
-## Latest Testnet
+## Testnet History Timeline
 
-- Namada public testnet 14:
+- Namada public testnet 14 (offline):
   - From date: 5th of October 2023 17:00 UTC
   - Namada protocol version: `v0.23.0`
   - Cometbft version: `0.37.2`
   - CHAIN_ID: `public-testnet-14.5d79b6958580`
 
-
-## Testnet History Timeline
-
 - Namada public testnet 13 (offline):
   - From date: 12th of September 2023 17:00 UTC
   - Namada protocol version: `v0.22.0`
@@ -202,7 +186,8 @@ mkdir backup-pregenesis && cp -r .namada/pre-genesis backup-pregenesis/
 rm -r .namada/public-testnet-3.0.81edd4d6eb6
 rm .namada/public-testnet-3.0.81edd4d6eb6.toml
 ```
-WARNING: Do not delete the entire `.namada` folder, as it contains your pre-genesis keys. If this is accidentally done, you will have to copy over the backup-pregenesis file. See [these instructions](../../operators/validators/run-your-genesis-validator.mdx) for more details
+WARNING: Do not delete the entire `.namada` folder, as it contains your pre-genesis keys. If this is accidentally done, you will have to copy over the backup-pregenesis file. 
+
 3. Rejoin the network
 ```bash copy
 export CHAIN_ID="public-testnet-3.0.81edd4d6eb6"

packages/docs/pages/operators.en-US.mdx

@@ -7,4 +7,4 @@ The guide assumes that you have already installed the node and are familiar with
 
 - [Running a full node](./operators/ledger.mdx)
 - [Running a validator node](./operators/validators.mdx)
-- [Setting up a local network](./operators/local-network.mdx)
+- [Setting up a local network](./operators/networks/local-network.mdx)

packages/docs/pages/operators/_meta.json

@@ -2,7 +2,7 @@
     "hardware": "Hardware requirements",
     "ledger": "Running a full node",
     "validators": "Validators",
-    "local-network": "Setting up a local network",
+    "networks": "Starting a network",
     "ibc": "IBC Relayers",
     "troubleshooting": "Troubleshooting",
     "eth-bridge": "Eth bridge",