diff --git a/.gitignore b/.gitignore index e2f7da094..17adee01b 100644 --- a/.gitignore +++ b/.gitignore @@ -4,4 +4,5 @@ node_modules yarn.lock .obsidian docs/.obsidian -build \ No newline at end of file +build +/static/llms.txt \ No newline at end of file diff --git a/docs/developers/quickstart.md b/docs/developers/quickstart.md index a13488f89..16bbf518e 100644 --- a/docs/developers/quickstart.md +++ b/docs/developers/quickstart.md @@ -1,4 +1,4 @@ ---- +--- sidebar_position: 2 description: Learn how to deploy your first contract on Gnosis Chain keywords: [gnosis chain, quickstart] @@ -37,7 +37,7 @@ Lastly, top up the wallet with xDAI that you'll use for contract deployments on Testnets on any EVM-compatible chains don't require real funds to pay for transactions. Instead, they use faucets that represent free tokens. You can use the following faucets to get xDAI on the Chiado testnet: - [Chiado faucet](https://faucet.chiadochain.net/) -- [Gnosis Chain Faucet](https://gnosisfaucet.com/) +- [Gnosis Chain Faucet](https://faucet.gnosischain.com/) ![faucet](/img/developers/quickstart/faucet.png) diff --git a/docs/node/README.md b/docs/node/README.md index 99e7ac47f..be4935b4b 100644 --- a/docs/node/README.md +++ b/docs/node/README.md @@ -122,7 +122,7 @@ Requirements vary client to client, for more detail see the associated system re | Lodestar | [Lodestar: Specifications](https://chainsafe.github.io/lodestar/#specifications) | | Nimbus | [Nimbus: Hardware](https://nimbus.guide/hardware.html) | | Teku | TBD | -| Prysm | [Prysm: Prerequisites](https://docs.prylabs.network/docs/install/install-with-script/#step-1-review-prerequisites-and-best-practices) | +| Prysm | [Prysm: Prerequisites](https://prysm.offchainlabs.com/docs/install-prysm/install-with-script/#step-1-review-prerequisites-and-best-practices) | **Gnosis Chain doesn't support Prysm at the moment.** diff --git a/docs/node/management/migrating-validator.md b/docs/node/management/migrating-validator.md index 82af69da3..2f69b049b 100644 --- a/docs/node/management/migrating-validator.md +++ b/docs/node/management/migrating-validator.md @@ -105,7 +105,7 @@ You can import it as follows using any installation method for your Prysm valida prysm.sh validator slashing-protection-history import --datadir=/path/to/your/validator/db --slashing-protection-json-file=/path/to/desiredimportfile ``` -- For more info, see the Prysm [Import & export slashing protection history](https://docs.prylabs.network/docs/wallet/slashing-protection) doc. +- For more info, see the Prysm [Import & export slashing protection history](https://prysm.offchainlabs.com/docs/backup-and-migration/slashing-protection/) doc. ## Teku diff --git a/docs/node/management/monitoring-node.md b/docs/node/management/monitoring-node.md index faf48fae2..19e9348ce 100644 --- a/docs/node/management/monitoring-node.md +++ b/docs/node/management/monitoring-node.md @@ -96,7 +96,7 @@ https://nimbus.guide/metrics-pretty-pictures.html#simple-metrics -https://docs.prylabs.network/docs/prysm-usage/monitoring/grafana-dashboard/ +https://prysm.offchainlabs.com/docs/monitoring-alerts-metrics/grafana-dashboard/ diff --git a/docs/node/management/monitoring-validators.md b/docs/node/management/monitoring-validators.md index 33f4684cc..9edbaf029 100644 --- a/docs/node/management/monitoring-validators.md +++ b/docs/node/management/monitoring-validators.md @@ -1,30 +1,29 @@ ---- -title: Monitoring Validators ---- +# Monitoring Validators -After setting up your validators, ensuring they are running and, most importantly, performing correctly is essential. +After setting up your validators, it’s essential to ensure they are running properly and performing as expected. ## Tool -The [bootnode.dev](https://www.bootnode.dev/) team has created a [Telegram bot](https://t.me/gbc_validators_bot) to assist you. Anyone running validators can set it up by just providing withdrawal address(es). The Bot will retrieve all the validators for you. Once registered, the bot will update you on your validators' performance and alert you if any issue occurs. +[node-sentinel.xyz](https://www.node-sentinel.xyz/) provides a [monitoring tool](https://t.me/gbc_validators_bot) to help you keep track of your validators. +It runs entirely through a Telegram bot and is free for everyone. You can register your validators by messaging the bot and providing your withdrawal address(es). The bot will automatically load all your validators and start delivering real-time stats and alerts. -### Continuously updated information on +![Node Sentinel Dashboard](/img/node/management/node-sentinel-dashboard.png) -- The number of validators you're running and their statuses (active, inactive, slashed, exited). -- The total effective balance of all your validators, combined. -- Validator’s overall performance(daily, weekly, and monthly) based on the last 100 attestations. -- Rewards earned in GNO (daily, weekly, and monthly). -- The total amount of rewards you can claim. -- Additionally, the Bot provides subsidized rewards claims, sponsored by [bootnode.dev](https://www.bootnode.dev/). +### The dashboard keeps you updated in real time with: -### Immediate alert when +- The number of validators you operate and their statuses (active, inactive, slashed, exited). +- The total effective balance of all your validators combined. +- Validator performance (daily, weekly, monthly) based on the last 100 attestations. +- Rewards earned in GNO (daily, weekly, monthly). +- The total amount of rewards available to claim. +- Subsidized reward claims, sponsored by [node-sentinel.xyz](https://www.node-sentinel.xyz/). +- A web dashboard with additional stats. -You'll receive notifications in the following situations: +### You’ll receive alerts when: -- If a validator misses more than 5 attestations consecutively. -- If the overall performance falls below 90%. -- If a validator's status changes from active to inactive, or vice versa. +- A validator changes status (e.g., from active to inactive). +- Overall performance drops. :::note -This Bot is compatible with all consensus and execution clients. +This bot is compatible with all consensus and execution clients. ::: diff --git a/docs/node/management/voluntary-exit.md b/docs/node/management/voluntary-exit.md index 9f6065be9..07d72af8b 100644 --- a/docs/node/management/voluntary-exit.md +++ b/docs/node/management/voluntary-exit.md @@ -52,13 +52,13 @@ build/nimbus_beacon_node deposits exit --data-dir=build/data/shared_gnosis_0 --v ### Prysm -Use [prysmctl tool](https://docs.prylabs.network/docs/prysm-usage/prysmctl) to voluntarily exit your validator. +Use [prysmctl tool](https://prysm.offchainlabs.com/docs/configure-prysm/prysmctl/) to voluntarily exit your validator. ```bash prysmctl validator exit --wallet-dir= --beacon-rpc-provider=<127.0.0.1:4000> ``` -- For more info, see the Prysm [Exit your validator](https://docs.prylabs.network/docs/wallet/exiting-a-validator/) doc. +- For more info, see the Prysm [Exit your validator](https://prysm.offchainlabs.com/docs/manage-validator/exiting-a-validator/) doc. ### Teku diff --git a/docs/tools/RPC Providers/README.md b/docs/tools/RPC Providers/README.md index 6b39ed82a..31d8ed8ec 100644 --- a/docs/tools/RPC Providers/README.md +++ b/docs/tools/RPC Providers/README.md @@ -114,6 +114,15 @@ high throughput for your production grade projects. Free API keys after signing up. +## dRPC + +dRPC NodeCloud offers an AI-powered load-balancer, 180+ network endpoints, flat-rate pricing +(20 CUs/method), usage analytics, and team features. PAYG from $10 — full speed, no limits. + +- [Gnosis endpoints](https://drpc.org/chainlist/gnosis-mainnet-rpc) +- [Docs](https://drpc.org/docs) +- [Chainlist](https://drpc.org/chainlist) + ## Quicknode - [Quicknode's Docs for Gnosis RPCs](https://www.quicknode.com/docs/gnosis) diff --git a/static/img/node/management/node-sentinel-dashboard.png b/static/img/node/management/node-sentinel-dashboard.png new file mode 100644 index 000000000..1cb6e7515 Binary files /dev/null and b/static/img/node/management/node-sentinel-dashboard.png differ diff --git a/static/llms.txt b/static/llms.txt index b28aa1391..aabf5bad9 100644 --- a/static/llms.txt +++ b/static/llms.txt @@ -7710,7 +7710,7 @@ Requirements vary client to client, for more detail see the associated system re | Lodestar | [Lodestar: Specifications](https://chainsafe.github.io/lodestar/#specifications) | | Nimbus | [Nimbus: Hardware](https://nimbus.guide/hardware.html) | | Teku | TBD | -| Prysm | [Prysm: Prerequisites](https://docs.prylabs.network/docs/install/install-with-script/#step-1-review-prerequisites-and-best-practices) | +| Prysm | [Prysm: Prerequisites](https://prysm.offchainlabs.com/docs/install-prysm/install-with-script/#step-1-review-prerequisites-and-best-practices) | **Gnosis Chain doesn't support Prysm at the moment.** @@ -8134,7 +8134,7 @@ You can import it as follows using any installation method for your Prysm valida prysm.sh validator slashing-protection-history import --datadir=/path/to/your/validator/db --slashing-protection-json-file=/path/to/desiredimportfile ``` -- For more info, see the Prysm [Import & export slashing protection history](https://docs.prylabs.network/docs/wallet/slashing-protection) doc. +- For more info, see the Prysm [Import & export slashing protection history](https://prysm.offchainlabs.com/docs/backup-and-migration/slashing-protection/) doc. ## Teku @@ -8258,7 +8258,7 @@ https://nimbus.guide/metrics-pretty-pictures.html#simple-metrics -https://docs.prylabs.network/docs/prysm-usage/monitoring/grafana-dashboard/ +https://prysm.offchainlabs.com/docs/monitoring-alerts-metrics/grafana-dashboard/ @@ -8419,13 +8419,13 @@ build/nimbus_beacon_node deposits exit --data-dir=build/data/shared_gnosis_0 --v ### Prysm -Use [prysmctl tool](https://docs.prylabs.network/docs/prysm-usage/prysmctl) to voluntarily exit your validator. +Use [prysmctl tool](https://prysm.offchainlabs.com/docs/configure-prysm/prysmctl/) to voluntarily exit your validator. ```bash prysmctl validator exit --wallet-dir= --beacon-rpc-provider=<127.0.0.1:4000> ``` -- For more info, see the Prysm [Exit your validator](https://docs.prylabs.network/docs/wallet/exiting-a-validator/) doc. +- For more info, see the Prysm [Exit your validator](https://prysm.offchainlabs.com/docs/manage-validator/exiting-a-validator/) doc. ### Teku