From f9be5e1a1ea7752bfec530cce0ed28e9ee13b78b Mon Sep 17 00:00:00 2001
From: qwahzi <qwahzi@gmail.com>
Date: Thu, 12 Sep 2024 19:17:51 -0500
Subject: [PATCH] Replace deprecated block explorer links (#709)

* Update ledger-management.md

Replacing NanoCrawler links with BlockLattice.io and Nano.community

* Update voting-as-a-representative.md

Replacing deprecated block explorer links

* Update beta-network.md

Update beta block explorer links

* Update voting-as-a-representative.md

Adding NanoCharts.info

* Update ledger-management.md

Adding NanoCharts.info
---
 docs/running-a-node/beta-network.md               | 5 ++---
 docs/running-a-node/ledger-management.md          | 2 +-
 docs/running-a-node/voting-as-a-representative.md | 6 +++---
 3 files changed, 6 insertions(+), 7 deletions(-)

diff --git a/docs/running-a-node/beta-network.md b/docs/running-a-node/beta-network.md
index 1316bf3c7..fd051fc05 100644
--- a/docs/running-a-node/beta-network.md
+++ b/docs/running-a-node/beta-network.md
@@ -60,9 +60,8 @@ A list of beta tags can be found at the official [Nano Currency Docker Hub](http
 
 | URL                                     | Description |
 |                                         |             |	
-| https://beta.nanocrawler.cc/            | Beta Explorer |
-| https://beta.nanoticker.info/           | Beta node details and stats |
-| https://b.repnode.org/                  | Beta node details and stats |
+| https://beta.nanobrowse.com             | Beta Explorer |
+| https://nanoticker.bnano.info/          | Beta node details and stats |
 
 ## Differences from the main network
 
diff --git a/docs/running-a-node/ledger-management.md b/docs/running-a-node/ledger-management.md
index b85ea8553..3bd5b2a62 100644
--- a/docs/running-a-node/ledger-management.md
+++ b/docs/running-a-node/ledger-management.md
@@ -74,7 +74,7 @@ Blocks are confirmed using the voting weight of representatives and these weight
 If looking to use a downloaded ledger there is a risk of it providing inaccurate representative voting weights. Although the potential impacts of this are minimal, below are some recommended steps to take which can help provide additional confidence the ledger can be used.
 
 1. **Scan the ledger for integrity using the [`--debug_validate_blocks`](/commands/command-line-interface/#-debug_validate_blocks) CLI command**. If issues are found they should be inspected carefully and alternative sources of a ledger may need to be considered as failures with this command have a high chance of indicating potentially malicious behavior.
-1. **Review the differences in representative voting weights by running the [`--compare_rep_weights`](/commands/command-line-interface/#-compare_rep_weights) CLI command** (_v21.0+ only)_ with the new ledger in the default data directory (old ledger backed up) or in a different data directory by using the optional `--data_path` argument. This will compare the new ledger voting weights against the hardcoded values in the node (set at the time of release). See the [CLI command](/commands/command-line-interface/#-compare_rep_weights) for details on the output with special attention paid to entries in the `outliers` and `newcomers` sections. By inspecting those addresses in public explorers such as [Nanocrawler.cc](https://nanocrawler.cc), this can help to determine if voting weight may have been manipulated in the downloaded ledger.
+1. **Review the differences in representative voting weights by running the [`--compare_rep_weights`](/commands/command-line-interface/#-compare_rep_weights) CLI command** (_v21.0+ only)_ with the new ledger in the default data directory (old ledger backed up) or in a different data directory by using the optional `--data_path` argument. This will compare the new ledger voting weights against the hardcoded values in the node (set at the time of release). See the [CLI command](/commands/command-line-interface/#-compare_rep_weights) for details on the output with special attention paid to entries in the `outliers` and `newcomers` sections. By inspecting those addresses in public explorers such as [BlockLattice.io](https://blocklattice.io/), [Nano.community](https://nano.community/), or [NanoCharts.info](https://nanocharts.info/), this can help to determine if voting weight may have been manipulated in the downloaded ledger.
 
 If you need support with this process or need help in evaluating some of the CLI command results, join the [Node and Representative Management category](https://forum.nano.org/c/node-and-rep/8) on the [Nano Forums](https://forum.nano.org).
 
diff --git a/docs/running-a-node/voting-as-a-representative.md b/docs/running-a-node/voting-as-a-representative.md
index 781aad85e..148d71884 100644
--- a/docs/running-a-node/voting-as-a-representative.md
+++ b/docs/running-a-node/voting-as-a-representative.md
@@ -62,7 +62,7 @@ Open the account - until you do [account_info](../commands/rpc-protocol.md#accou
 
 Before the node will vote, the representative account configured above must have at least 1000 Nano delegated to it. This is done by changing the representative of other accounts in your wallet with [account_representative_set](../commands/rpc-protocol.md#account_representative_set). If you do not control over 1000 Nano, you will need to have others delegate their weight to your representative.
 
-Once you have enough weight, after a few minutes you can search for your representative account on the [mynano.ninja](https://mynano.ninja/) site to verify it is voting.
+Once you have enough weight, after a few minutes you can search for your representative account on [BlockLattice.io](https://blocklattice.io/), [Nano.community](https://nano.community/), or [NanoCharts.info](https://nanocharts.info/) to verify it is voting.
 
 --8<-- "warning-multiple-node-setups.md"
 
@@ -80,11 +80,11 @@ Once you are comfortable with your node setup and want to connect it to the broa
 
 ### Setup monitoring
 
-Details for setting up a popular monitoring service for the node can be found at https://github.com/NanoTools/nanoNodeMonitor. Not only can this provide a website for viewing the status and promoting your representative, but it also provides metrics to popular services in the ecosystem who help monitor the broader network status and performance, such as [NanoCrawler.cc](https://nanocrawler.cc) and [MyNano.ninja](https://mynano.ninja).
+Details for setting up a popular monitoring service for the node can be found at https://github.com/NanoTools/nanoNodeMonitor. Not only can this provide a website for viewing the status and promoting your representative, but it also provides metrics to popular services in the ecosystem who help monitor the broader network status and performance, such as [BlockLattice.io](https://blocklattice.io/), [Nano.community](https://nano.community/), and [NanoCharts.info](https://nanocharts.info/). 
 
 ### Connect with community services
 
-At [MyNano.ninja](https://mynano.ninja) you can also verify your representative and share additional details about your social accounts. Many community members use this service to evaluate representatives which can help you get additional weight if your setup is reliable and well maintained.
+At nano.community [[1]](https://github.com/mistakia/nano-community/blob/main/data/nano-reps.csv)[[2]](https://nano.community/cli) you can also verify your representative and share additional details about your social accounts. Many community members use this service to evaluate representatives which can help you get additional weight if your setup is reliable and well maintained.
 
 ### Ongoing maintenance and support