add reviewer suggestion and new validator keys

Author: oeggert

blog/2025/devnet-reset.md

@@ -2,7 +2,6 @@
 category: 2025
 date: 2025-01-24
 seo:
-    title: Upcoming Devnet Reset Notification
     description: Devnet is scheduled to reset on Monday, February 3, 2025 due to Clio databases nearing capacity. Learn more.
 labels:
     - Advisories
@@ -30,13 +29,13 @@ This reset affects Devnet only. Other networks will continue to operate as usual
 
 The reset will delete all ledger data in Devnet, including all accounts, transactions, balances, settings, offers, AMMs, escrows, and other data. This means all balances will be reset to zero and the block number will start at one again. No changes are anticipated to services such as Devnet APIs, faucets, Explorers, access rights, and wallet integrations; these services usually manage resets without issues.
 
-Devnet will have its amendment statuses restored to match XRPL Mainnet. Any existing accounts or other data will need new test XRP from the faucet and will need to be re-created. 
+Any existing accounts or other data will need new test XRP from the faucet and will need to be re-created.
 
 If code relies on specific addresses, a request to the faucet can fund the same address again. However, any AMMs that are re-created after the reset will generally have different account addresses. As a reminder, it's best not to use the same addresses or key pairs on Mainnet and any developer networks.
 
-The important URLs, Network ID, and validator settings for Devnet will remain the same.
+As part of the reset, we'll also be updating the validator list with a new publisher key. The important URLs and Network ID will remain the same.
 
-## Action Recommended
+## Actions Required
 
 If you run a `rippled` server that is connected to Devnet, after the reset you should delete your database data and restart the server. Database files and folders are defined in the config file in the `[database_path]` and `[node_db]` stanzas. If you use the default config, you can run the following commands:
 
@@ -46,6 +45,16 @@ rm -r /var/lib/rippled/db/*
 systemctl restart rippled.service
 ```
 
+You will also have to update the `[validator_list_keys]` keys stanza in your `validators.txt` file:
+
+```
+[validator_list_sites]
+https://vl.devnet.rippletest.net
+
+[validator_list_keys]
+EDBB54B0D9AEE071BB37784AF5A9E7CC49AC7A0EFCE868C54532BCB966B9CFC13B
+```
+
 ## Learn, Ask Questions, and Discuss
 
 We’re exploring long-term solutions to enhance network resilience and ensure you’re well-prepared, including: