tornadocontrib/go-ethereum
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix broken links (#30143)

Browse Source
This commit is contained in:
omahs 2024-07-11 17:23:46 +02:00 committed by GitHub
parent c3e057603f
commit 65d4c718e3
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
3 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/fundamentals/peer-to-peer.md
View File

@ -3,7 +3,7 @@ title: Connecting To The Network
description: Guide to connecting Geth to a peer-to-peer network description: Guide to connecting Geth to a peer-to-peer network
--- ---
The default behaviour for Geth is to connect to Ethereum Mainnet. However, Geth can also connect to public testnets, [private networks](/docs/fundamentals/private-network) and [local testnets](/docs/developers/geth-developer/dev-mode). For convenience, the two public testnets with long term support, Goerli and Sepolia, have their own command line flag. Geth can connect to these testnets simply by passing: The default behaviour for Geth is to connect to Ethereum Mainnet. However, Geth can also connect to public testnets, [private networks](/docs/fundamentals/private-network) and [local testnets](/docs/developers/dapp-developer/dev-mode). For convenience, the two public testnets with long term support, Goerli and Sepolia, have their own command line flag. Geth can connect to these testnets simply by passing:
- `--goerli`, Goerli proof-of-authority test network - `--goerli`, Goerli proof-of-authority test network
- `--sepolia` Sepolia proof-of-work test network - `--sepolia` Sepolia proof-of-work test network

2
docs/interacting-with-geth/rpc/index.md
View File

@ -117,7 +117,7 @@ As a general rule IPC is most secure because it is limited to interactions on th
The Engine-API is a set of RPC methods that enable communication between Geth and the [consensus client](/docs/getting-started/consensus-clients). These are not designed to be exposed to the user - instead they are called automatically by the clients when they need to exchange information. The Engine API is enabled by default - the user is not required to pass any instruction to Geth to enable these methods. The Engine-API is a set of RPC methods that enable communication between Geth and the [consensus client](/docs/getting-started/consensus-clients). These are not designed to be exposed to the user - instead they are called automatically by the clients when they need to exchange information. The Engine API is enabled by default - the user is not required to pass any instruction to Geth to enable these methods.
Read more in the [Engine API spec](https://github.com/ethereum/execution-apis/blob/main/src/engine/specification.md). Read more in the [Engine API spec](https://github.com/ethereum/execution-apis/blob/main/src/engine).
## Summary {#summary} ## Summary {#summary}

2
docs/monitoring/understanding-dashboards.md
View File

@ -3,7 +3,7 @@ title: Understanding Geth's dashboard
description: How to use a dashboard to understand a Geth node's performance description: How to use a dashboard to understand a Geth node's performance
--- ---
Our [dashboards page](/docs/monitoring/dashboards.md) explains how to set up a Grafana dashboard for monitoring your Geth node. This page explores the dashboard itself, explaining what the various metrics are and what they mean for the health of a node. Note that the raw data informing the dashboard can be viewed in JSON format in the browser by navigating to the ip address and port passed to `--metrics.addr` and `--metrics.port` (`127.0.0.1:6060` by default). Our [dashboards page](/docs/monitoring/dashboards) explains how to set up a Grafana dashboard for monitoring your Geth node. This page explores the dashboard itself, explaining what the various metrics are and what they mean for the health of a node. Note that the raw data informing the dashboard can be viewed in JSON format in the browser by navigating to the ip address and port passed to `--metrics.addr` and `--metrics.port` (`127.0.0.1:6060` by default).
## What does the dashboard look like? ## What does the dashboard look like?