chore: add note on XRPL node spinup (#1371)

Author: benjamin852

src/content/docs/validator/amplifier/verifier-onboarding.mdx

@@ -96,7 +96,11 @@ docker run -p 50051:50051 --env MNEMONIC_CMD=auto --env NOPASSWORD=true --env AD
 Leave this process running in the background, and perform additional commands in a new terminal window or shell.
 
 <Callout>
-Note: If you are running a validator as well, you must run different `tofnd` instances for `vald` (for your validator) and `ampd` (for your verifier). You cannot use the same `tofnd` instance for both.
+Note: If you are running a validator as well, you should use a different node for your verifier (the Axelar node that ampd connects to) on both testnet and mainnet than the one being run for your validator node to prevent loss of rewards in case the verifier fails. This node can use the `everything` pruning config to reduce resource use. 
+</Callout>
+
+<Callout>
+Note: You also must run different `tofnd` instances for `vald` (for your validator) and `ampd` (for your verifier). You cannot use the same `tofnd` instance for both.
 </Callout>
 
 ## Set up `ampd`

src/content/docs/validator/external-chains/xrpl.mdx

@@ -147,12 +147,21 @@ You can query the node with:
 curl -H 'Content-Type: application/json' -d '{"method":"server_info","params":[{}]}' http://localhost:5005
 ```
 
+## Axelar Node Configuration
 
-### Ampd Configuration
-Once your node is up and running, you need to add the `XRPL` chain to your [ampd daemon's](https://github.com/axelarnetwork/axelar-amplifier/tree/main/ampd) `config.toml`file. This can be done by adding in the following configuration:
+Due to a bug in the Cosmos SDK that appears when the database is being read from under heavy load, when `ampd` is trying to broadcast transactions, your Axelar node may run into issues when running (such as an `AppHash` error). An example of such an error may appear as follows:
+
+`ERR CONSENSUS FAILURE!!! err="precommit step; +2/3 prevoted for an invalid block: wrong Block.Header.AppHash`
 
-For testnet:
+Your node orchestration needs to be updated to perform a `rollback` when a node crashes. The rollback command must be executed **before restarting the Axelar node** to auto-recover from such errors. The rollback can be performed by running:
 
+```bash
+axelard rollback
+```
+
+
+### Ampd Configuration
+Once your node is up and running, you need to add the `XRPL` chain to your [ampd daemon's](https://github.com/axelarnetwork/axelar-amplifier/tree/main/ampd) `config.toml`file. This can be done by adding in the following configuration:
 
 <tabs>
   <tab-item title="Mainnet">