mirror
/
go-ethereum
mirror of https://github.com/ethereum/go-ethereum
2
0
Fork 1
Code Issues Releases Wiki Activity

Merge branch 'master' of github.com:ethereum/geth-website

Browse Source
pull/26459/head^2
Nicolás Quiroz 2 years ago
parent 8940cabc38 572a5cfa9f
commit 24f8b3d6fa
13 changed files with 61 additions and 31 deletions
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Show Stats Download Patch File Download Diff File
  1. 4
      src/pages/docs/developers/geth-developer/disclosures.md
  2. 1
      src/pages/docs/developers/geth-developer/private-network.md
  3. 24
      src/pages/docs/faq.md
  4. 5
      src/pages/docs/fundamentals/sync-modes.md
  5. 0
      src/pages/docs/getting-started/consensus-clients.md
  6. 0
      src/pages/docs/getting-started/getting-started-with-clef.md
  7. 0
      src/pages/docs/getting-started/getting-started.md
  8. 0
      src/pages/docs/getting-started/installing-geth.md
  9. 0
      src/pages/docs/resources.md
  10. 0
      src/pages/docs/tools/abigen.md
  11. 0
      src/pages/docs/tools/devp2p.md
  12. 0
      src/pages/docs/tools/puppeth.md
  13. 58
      url-list.csv

4
src/pages/docs/developers/geth-developer/disclosures.md
Unescape View File

@ -41,9 +41,9 @@ In keeping with this policy, we have taken inspiration from [Solidity bug disclo
## Disclosed vulnerabilities ## Disclosed vulnerabilities
There is a JSON-formatted list ([`vulnerabilities.json`](/docs/vulnerabilities/vulnerabilities.json)) of some of the known security-relevant vulnerabilities concerning Geth. There is a JSON-formatted list ([`vulnerabilities.json`](/vulnerabilities.json)) of some of the known security-relevant vulnerabilities concerning Geth.
As of version `1.9.25`, Geth has a built-in command to check whether it is affected by any publically disclosed vulnerability, using the command `geth version-check`. This command will fetch the latest json file (and the accompanying [signature-file](/docs/vulnerabilities/vulnerabilities.json.minisig), and cross-check the data against it's own version number. As of version `1.9.25`, Geth has a built-in command to check whether it is affected by any publically disclosed vulnerability, using the command `geth version-check`. This command will fetch the latest json file (and the accompanying [signature-file](vulnerabilities.json.minisig), and cross-check the data against it's own version number.
The list of vulnerabilities was started in November 2020, and covers mainly `v1.9.7` and forward. The list of vulnerabilities was started in November 2020, and covers mainly `v1.9.7` and forward.

1
src/pages/docs/developers/geth-developer/private-network.md
Unescape View File

@ -38,6 +38,7 @@ Clique consensus is a PoA system where new blocks can be created by authorized '
Every blockchain starts with a genesis block. When Geth is run with default settings for the first time, it commits the Mainnet genesis to the database. For a private network, it is generally preferable to use a different genesis block. The genesis block is configured using a _genesis.json_ file whose path must be provided to Geth on start-up. When creating a genesis block, a few initial parameters for the private blockchain must be defined: Every blockchain starts with a genesis block. When Geth is run with default settings for the first time, it commits the Mainnet genesis to the database. For a private network, it is generally preferable to use a different genesis block. The genesis block is configured using a _genesis.json_ file whose path must be provided to Geth on start-up. When creating a genesis block, a few initial parameters for the private blockchain must be defined:
- Ethereum platform features enabled at launch (`config`). Enabling and disabling features once the blockchain is running requires scheduling a [hard fork](https://ethereum.org/en/glossary/#hard-fork). - Ethereum platform features enabled at launch (`config`). Enabling and disabling features once the blockchain is running requires scheduling a [hard fork](https://ethereum.org/en/glossary/#hard-fork).
- Initial block gas limit (`gasLimit`). This impacts how much EVM computation can happen within a single block. Mirroring the main Ethereum network is generally a [good choice](https://etherscan.io/chart/gaslimit). The block gas limit can be adjusted after launch using the `--miner.gastarget` command-line flag. - Initial block gas limit (`gasLimit`). This impacts how much EVM computation can happen within a single block. Mirroring the main Ethereum network is generally a [good choice](https://etherscan.io/chart/gaslimit). The block gas limit can be adjusted after launch using the `--miner.gastarget` command-line flag.
- Initial allocation of ether (`alloc`). This determines how much ether is available to the addresses listed in the genesis block. Additional ether can be created through mining as the chain progresses. - Initial allocation of ether (`alloc`). This determines how much ether is available to the addresses listed in the genesis block. Additional ether can be created through mining as the chain progresses.

24
src/pages/docs/faq.md
Unescape View File

@ -18,12 +18,7 @@ RPC stands for Remote Procedure Call. RPC is a mode of communication between pro
The `jwtsecret` file is required to create an authenticated connection between Geth and a consensus client. JWT stands for JSON Web Token - it is signed using a secret key, proving each party's identity. Read about how to create `jwt-secret` in Geth on our [Connecting to consensus clients](/content/docs/getting_started/consensus-clients.md) page. The `jwtsecret` file is required to create an authenticated connection between Geth and a consensus client. JWT stands for JSON Web Token - it is signed using a secret key, proving each party's identity. Read about how to create `jwt-secret` in Geth on our [Connecting to consensus clients](/content/docs/getting_started/consensus-clients.md) page.
<<<<<<< HEAD:content/docs/faq.md
#### I noticed my peercount slowly decreasing, and now it is at 0. Restarting doesn't get any peers.
=======
## I noticed my peercount slowly decreasing, and now it is at 0. Restarting doesn't get any peers. ## I noticed my peercount slowly decreasing, and now it is at 0. Restarting doesn't get any peers.
>>>>>>> geth-next:src/pages/docs/faq.md
This may be because your clock has fallen out of sync with other nodes. You can [force a clock update using ntp](https://askubuntu.com/questions/254826/how-to-force-a-clock-update-using-ntp) like so: This may be because your clock has fallen out of sync with other nodes. You can [force a clock update using ntp](https://askubuntu.com/questions/254826/how-to-force-a-clock-update-using-ntp) like so:
@ -50,11 +45,6 @@ Additional details and/or any updates on more robust handling are at <https://gi
The current default syncing mode used by Geth is called [snap sync](https://github.com/ethereum/devp2p/blob/master/caps/snap.md). Instead of starting from the genesis block and processing all the transactions that ever occurred (which could take weeks), snap sync downloads the blocks, and only verifies the associated proof-of-works, assuming state transitions to be correct. Downloading all the blocks is a straightforward and fast procedure and will relatively quickly reassemble the entire chain. The current default syncing mode used by Geth is called [snap sync](https://github.com/ethereum/devp2p/blob/master/caps/snap.md). Instead of starting from the genesis block and processing all the transactions that ever occurred (which could take weeks), snap sync downloads the blocks, and only verifies the associated proof-of-works, assuming state transitions to be correct. Downloading all the blocks is a straightforward and fast procedure and will relatively quickly reassemble the entire chain.
Many people assume that because they have the blocks, they are in sync. Unfortunately this is not the case. Since no transaction was executed, so we do not have any account state available (ie. balances, nonces, smart contract code and data). These need to be downloaded separately and cross-checked with the latest blocks. This phase is called the state trie download phase. Snap sync tries to hasten this process by downloading contiguous chunks of useful state data, instead of doing so one-by-one, as in previous synchronization methods. Geth downloads the leaves of the trie without the intermediate nodes that connect the leaves to the root. The full trie is regenerated locally. However, while this is happening, the blockchain is progressing, meaning some of the regenerated state trie becomes invalid. Therefor, there is also a healing phase that corrects any errors in the state trie. The state sync has to progress faster than the chain growth otherwise it will never finish. Many people assume that because they have the blocks, they are in sync. Unfortunately this is not the case. Since no transaction was executed, so we do not have any account state available (ie. balances, nonces, smart contract code and data). These need to be downloaded separately and cross-checked with the latest blocks. This phase is called the state trie download phase. Snap sync tries to hasten this process by downloading contiguous chunks of useful state data, instead of doing so one-by-one, as in previous synchronization methods. Geth downloads the leaves of the trie without the intermediate nodes that connect the leaves to the root. The full trie is regenerated locally. However, while this is happening, the blockchain is progressing, meaning some of the regenerated state trie becomes invalid. Therefor, there is also a healing phase that corrects any errors in the state trie. The state sync has to progress faster than the chain growth otherwise it will never finish.
<<<<<<< HEAD:content/docs/faq.md
Geth can also be sync'd with `--syncmode full`. In this case, Geth downloads and independently verifies every block since genesis in sequence, including re-executing transactions to verify state transitions. Although Geth verifies every block since genesis, only 128 blocks are stored in memory.
=======
>>>>>>> geth-next:src/pages/docs/faq.md
Geth can also be sync'd with `--syncmode full`. In this case, Geth downloads and independently verifies every block since genesis in sequence, including re-executing transactions to verify state transitions. Although Geth verifies every block since genesis, only 128 blocks are stored in memory. Geth can also be sync'd with `--syncmode full`. In this case, Geth downloads and independently verifies every block since genesis in sequence, including re-executing transactions to verify state transitions. Although Geth verifies every block since genesis, only 128 blocks are stored in memory.
@ -66,11 +56,7 @@ This cryptographic linking is done by creating a tree-like data structure, where
Read more about Merkle Tries in general and the Ethereum state trie specifically on [ethereum.org](https://ethereum.org/en/developers/docs/data-structures-and-encoding/patricia-merkle-trie) Read more about Merkle Tries in general and the Ethereum state trie specifically on [ethereum.org](https://ethereum.org/en/developers/docs/data-structures-and-encoding/patricia-merkle-trie)
<<<<<<< HEAD:content/docs/faq.md
#### Why does the state trie download phase require a special syncing mode?
=======
## Why does the state trie download phase require a special syncing mode? ## Why does the state trie download phase require a special syncing mode?
>>>>>>> geth-next:src/pages/docs/faq.md
The trie data structure is an intricate interlink of hundreds of millions of tiny cryptographic proofs (trie nodes). To truly have a synchronized node, you need to download all the account data, as well as all the tiny cryptographic proofs to verify that no one in the network is trying to cheat you. This itself is already a crazy number of data items. The trie data structure is an intricate interlink of hundreds of millions of tiny cryptographic proofs (trie nodes). To truly have a synchronized node, you need to download all the account data, as well as all the tiny cryptographic proofs to verify that no one in the network is trying to cheat you. This itself is already a crazy number of data items.
@ -82,15 +68,6 @@ Snap syncing was introduced by version [1.10.0](https://blog.ethereum.org/2021/0
You can read more in the article posted above why snap sync replaced fast sync in Geth. You can read more in the article posted above why snap sync replaced fast sync in Geth.
<<<<<<< HEAD:content/docs/faq.md
#### What is wrong with my light client?
Light sync relies on full nodes that serve data to light clients. Historically, this has been hampered by the fact that serving light clients was turned off by default in geth full nodes and few nodes chose to turn it on. Therefore, light nodes often struggled to find peers. Since Ethereum switched to proof-of-stake, Geth light clients have stopped working altogether. Light clients for proof-of-stake Ethereum are expected to be implemented soon!
#### Why do I need another client in addition to Geth?
Historically, running Geth was enough to turn a computer into an Ethereum node. However, when Ethereum transitioned to proof-of-stake, responsibility for consensus logic and block gossip was handed over to a separate consensus layer client. However, Geth still handles transactions and state management. When the consensus client is required to create a new block, it requests Geth to gather transactions from the transaction pool, execute them to compute a state transition and pass this information back to the consensus client. When the consensus client receives a new block from a peer, it passes the transactions to Geth to re-execute to verify the proposed state-transition. There is a clear separationm of concerns between the two clients, meaning that both are required for a computer function as an Ethereum node.
=======
## What is wrong with my light client? ## What is wrong with my light client?
Light sync relies on full nodes that serve data to light clients. Historically, this has been hampered by the fact that serving light clients was turned off by default in geth full nodes and few nodes chose to turn it on. Therefore, light nodes often struggled to find peers. Since Ethereum switched to proof-of-stake, Geth light clients have stopped working altogether. Light clients for proof-of-stake Ethereum are expected to be implemented soon! Light sync relies on full nodes that serve data to light clients. Historically, this has been hampered by the fact that serving light clients was turned off by default in geth full nodes and few nodes chose to turn it on. Therefore, light nodes often struggled to find peers. Since Ethereum switched to proof-of-stake, Geth light clients have stopped working altogether. Light clients for proof-of-stake Ethereum are expected to be implemented soon!
@ -98,4 +75,3 @@ Light sync relies on full nodes that serve data to light clients. Historically,
## Why do I need another client in addition to Geth? ## Why do I need another client in addition to Geth?
Historically, running Geth was enough to turn a computer into an Ethereum node. However, when Ethereum transitioned to proof-of-stake, responsibility for consensus logic and block gossip was handed over to a separate consensus layer client. However, Geth still handles transactions and state management. When the consensus client is required to create a new block, it requests Geth to gather transactions from the transaction pool, execute them to compute a state transition and pass this information back to the consensus client. When the consensus client receives a new block from a peer, it passes the transactions to Geth to re-execute to verify the proposed state-transition. There is a clear separationm of concerns between the two clients, meaning that both are required for a computer function as an Ethereum node. Historically, running Geth was enough to turn a computer into an Ethereum node. However, when Ethereum transitioned to proof-of-stake, responsibility for consensus logic and block gossip was handed over to a separate consensus layer client. However, Geth still handles transactions and state management. When the consensus client is required to create a new block, it requests Geth to gather transactions from the transaction pool, execute them to compute a state transition and pass this information back to the consensus client. When the consensus client receives a new block from a peer, it passes the transactions to Geth to re-execute to verify the proposed state-transition. There is a clear separationm of concerns between the two clients, meaning that both are required for a computer function as an Ethereum node.
>>>>>>> geth-next:src/pages/docs/faq.md

5
src/pages/docs/fundamentals/sync-modes.md
Unescape View File

@ -1,8 +1,3 @@
---
title: Sync modes
description: Introduction to the three ways to sync Geth
---
Syncing is the process by which Geth catches up to the latest Ethereum block and current global state. There are several ways to sync a Geth node that differ in their speed, storage requirements and trust assumptions. This page outlines three sync configurations for full nodes and one for light nodes. Syncing is the process by which Geth catches up to the latest Ethereum block and current global state. There are several ways to sync a Geth node that differ in their speed, storage requirements and trust assumptions. This page outlines three sync configurations for full nodes and one for light nodes.
## Full nodes ## Full nodes

0
src/pages/docs/getting_started/consensus-clients.md → src/pages/docs/getting-started/consensus-clients.md
Unescape View File

0
src/pages/docs/getting_started/getting-started-with-clef.md → src/pages/docs/getting-started/getting-started-with-clef.md
Unescape View File

0
src/pages/docs/getting_started/getting-started.md → src/pages/docs/getting-started/getting-started.md
Unescape View File

0
src/pages/docs/getting_started/installing-geth.md → src/pages/docs/getting-started/installing-geth.md
Unescape View File

0
src/pages/resources.md → src/pages/docs/resources.md
Unescape View File

0
src/pages/docs/tools/abigen/index.md → src/pages/docs/tools/abigen.md
Unescape View File

0
src/pages/docs/tools/devp2p/index.md → src/pages/docs/tools/devp2p.md
Unescape View File

0
src/pages/docs/tools/puppeth/index.md → src/pages/docs/tools/puppeth.md
Unescape View File

58
url-list.csv
Unescape View File

@ -0,0 +1,58 @@
OLD Geth website URLS,Equivalent NEW website URLs,Relative path to markdown file,Notes
https://geth.ethereum.org/,https://geth.ethereum.org,src/pages/homepage,will be react page
https://geth.ethereum.org/downloads/,https://geth.ethereum.org/downloads,src/pages/downloads,will be react page
https://geth.ethereum.org/docs/,https://geth.ethereum.org/docs,src/pages/docs,n/a
https://geth.ethereum.org/docs/getting-started,https://geth.ethereum.org/docs/getting_started,src/pages/docs/getting_started/getting_started.md,n/a
https://geth.ethereum.org/docs/getting-started/geth-and-clef,https://geth.ethereum.org/docs/getting_started_with_clef.md,src/pages/docs/getting_started/getting-started-with-clef.md,n/a
https://geth.ethereum.org/docs/getting-started/dev-mode,https://geth.ethereum.org/docs/developers/geth-developers/dev-mode,src/pages/docs/developers/geth-developer/dev-mode.md,n/a
https://geth.ethereum.org/docs/install-and-build/installing-geth,https://geth.ethereum.org/docs/getting_started/install-geth,src/pages/docs/getting_started/backup-restore.md,n/a
https://geth.ethereum.org/docs/install-and-build/backup-restore,https://geth.ethereum.org/docs/getting_started/backup-restore,src/pages/docs/getting_started/installing-geth.md,n/a
https://geth.ethereum.org/docs/install-and-build/cross-compile,page removed,page removed,n/a
https://geth.ethereum.org/docs/interface/command-line-options,https://geth.ethereum.org/fundamentals/command-line-options,src/pages/docs/fundamentals/command-line-options.md,n/a
https://geth.ethereum.org/docs/interface/pruning,https://geth.ethereum.org/docs/fundamentals/pruning,src/pages/docs/fundamentals/pruning.md,n/a
https://geth.ethereum.org/docs/interface/merge,page removed,page removed,n/a
https://geth.ethereum.org/docs/interface/consensus-clients,https://geth.ethereum.org/docs/getting_started/consensus-client,src/pages/docs/getting_started/consensus-clients.md,n/a
https://geth.ethereum.org/docs/interface/peer-to-peer,https://geth.ethereum.org/docs/fundamentals/peer-to-peer,src/pages/docs/fundamentals/peer-to-peer.md,n/a
https://geth.ethereum.org/docs/interface/les,https://geth.ethereum.org/docs/fundamentals/les,src/pages/docs/fundamentals/les.md,n/a
https://geth.ethereum.org/docs/interface/managing-your-accounts,https://geth.ethereum.org/docs/fundamentals/account-management,src/pages/docs/fundamentals/account-management.md,n/a
https://geth.ethereum.org/docs/faq,https://geth.ethereum.org/docs/faq,src/pages/docs/faq.md,n/a
https://geth.ethereum.org/docs/interface/javascript-console,https://geth.ethereum.org/docs/interacting-with-geth/javascript-console,src/pages/docs/interacting-with-geth/javascript-console.md,n/a
https://geth.ethereum.org/docs/interface/private-network,https://geth.ethereum.org/docs/developers/geth-developer/private-network,src/pages/docs/developers/geth-developer/private-network.md,n/a
https://geth.ethereum.org/docs/interface/mining,page removed,page removed,n/a
https://geth.ethereum.org/docs/interface/metrics,https://geth.ethereum.org/docs/monitoring/metrics,src/pages/docs/monitoring/metrics.md,n/a
https://geth.ethereum.org/docs/dapp/native,https://geth.ethereum.org/docs/developers/dapp-developer/native,src/pages/docs/developers/dapp-developer/native.md,n/a
https://geth.ethereum.org/docs/dapp/tracing,https://geth.ethereum.org/docs/developers/dapp-developer/tracing,src/pages/docs/developers/dapp-developer/tracing.md,n/a
https://geth.ethereum.org/docs/dapp/custom-tracer,https://geth.ethereum.org/docs/developers/dapp-developer/custom-tracer,src/pages/docs/developers/dapp-developer/custom-tracer.md,n/a
https://geth.ethereum.org/docs/dapp/builtin-tracers,https://geth.ethereum.org/docs/developers/dapp-developer/built-in-tracer,src/pages/docs/developers/dapp-developer/built-in-tracers.md,n/a
https://geth.ethereum.org/docs/dapp/native-accounts,https://geth.ethereum.org/docs/developers/dapp-developer/native-accounts,src/pages/docs/developers/dapp-developer/native-accounts.md,n/a
https://geth.ethereum.org/docs/dapp/native-bindings,https://geth.ethereum.org/docs/developers/dapp-developer/native-bindings,src/pages/docs/developers/dapp-developer/native-bindings.md,n/a
https://geth.ethereum.org/docs/dapp/mobile,https://geth.ethereum.org/docs/developers/dapp-developer/mobile,src/pages/docs/developers/dapp-developer/mobile.md,n/a
https://geth.ethereum.org/docs/dapp/mobile-accounts,page removed,page removed,n/a
https://geth.ethereum.org/docs/rpc/server,https://geth.ethereum.org/docs/interacting-with-geth/rpc/server,src/pages/docs/interacting-with-geth/rpc/server.md,n/a
https://geth.ethereum.org/docs/rpc/pubsub,https://geth.ethereum.org/docs/interacting-with-geth/rpc/pubsub,src/pages/docs/interacting-with-geth/rpc/pubsub.md,n/a
https://geth.ethereum.org/docs/rpc/batch,https://geth.ethereum.org/docs//interacting-with-geth/rpc/batch,src/pages/docs/interacting-with-geth/rpc/batch.md,n/a
https://geth.ethereum.org/docs/rpc/graphql,https://geth.ethereum.org/docs/interacting_with_geth/rpc/graphql,src/pages/docs/interacting-with-geth/rpc/graphql.md,n/a
https://geth.ethereum.org/docs/rpc/ns-admin,https://geth.ethereum.org/docs/interacting_with_geth/rpc/ns-admin,src/pages/docs/interacting-with-geth/rpc/ns-admin.md,n/a
https://geth.ethereum.org/docs/rpc/ns-clique,https://geth.ethereum.org/docs/interacting_with_geth/rpc/ns-clique,src/pages/docs/interacting-with-geth/rpc/ns-clique.md,n/a
https://geth.ethereum.org/docs/rpc/ns-debug,https://geth.ethereum.org/docs/interacting_with_geth/rpc/ns-debug,src/pages/docs/interacting-with-geth/rpc/ns-debug.md,n/a
https://geth.ethereum.org/docs/rpc/ns-eth,https://geth.ethereum.org/docs/interacting_with_geth/rpc/ns-eth,src/pages/docs/interacting-with-geth/rpc/ns-eth.md,n/a
https://geth.ethereum.org/docs/rpc/ns-les,https://geth.ethereum.org/docs/interacting_with_geth/rpc/ns-les,src/pages/docs/interacting-with-geth/rpc/ns-les.md,n/a
https://geth.ethereum.org/docs/rpc/ns-miner,https://geth.ethereum.org/docs/interacting_with_geth/rpc/ns-miner,src/pages/docs/interacting-with-geth/rpc/ns-miner.md,n/a
https://geth.ethereum.org/docs/rpc/ns-net,https://geth.ethereum.org/docs/interacting_with_geth/rpc/ns-net,src/pages/docs/interacting-with-geth/rpc/ns-net.md,n/a
https://geth.ethereum.org/docs/rpc/ns-personal,https://geth.ethereum.org/docs/interacting_with_geth/rpc/ns-personal,src/pages/docs/interacting-with-geth/rpc/ns-personalmd,n/a
https://geth.ethereum.org/docs/rpc/ns-txpool,https://geth.ethereum.org/docs/interacting_with_geth/rpc/ns-txpool,src/pages/docs/interacting-with-geth/rpc/ns-txpool.md,n/a
https://geth.ethereum.org/docs/rpc/objects,https://geth.ethereum.org/docs/interacting_with_geth/rpc/objects,src/pages/docs/interacting-with-geth/rpc/objects.md,n/a
https://geth.ethereum.org/docs/developers/dev-guide,https://geth.ethereum.org/docs/developers/geth-developer/dev-guide,src/pages/docs/developers/geth-developer/devguide.md,n/a
https://geth.ethereum.org/docs/developers/code-review-guidelines,https://geth.ethereum.org/docs/developers/geth-developer/code-review-guidelines,src/pages/docs/developers/geth-developer/code-review-guidelines.md,n/a
https://geth.ethereum.org/docs/developers/issue-handling-workflow,https://geth.ethereum.org/docs/developers/geth-developer/code-review-guidelines,src/pages/docs/developers/geth-developer/issue-handling-workflow.md,n/a
https://geth.ethereum.org/docs/developers/dns-discovery-setup,https://geth.ethereum.org/doce/developers/geth-developer/dns-discovery-setup,src/pages/docs/developers/geth-developer/dns-discovery-workflow.md,n/a
https://geth.ethereum.org/docs/clef/introduction,https://geth.ethereum.org/docs/tools/clef/introduction,src/pages/docs/tools/clef/introduction.md,n/a
https://geth.ethereum.org/docs/clef/tutorial,https://geth.ethereum.org/docs/tools/clef/tutorial,src/pages/docs/tools/clef/tutorial.md,n/a
https://geth.ethereum.org/docs/clef/cliquesigning,https://geth.ethereum.org/docs/tools/clef/clique-signing,src/pages/docs/tools/clef/clique-signing.md,n/a
https://geth.ethereum.org/docs/clef/rules,https://geth.ethereum.org/docs/tools/clef/rules,src/pages/docs/tools/clef/rules.md,n/a
https://geth.ethereum.org/docs/clef/setup,https://geth.ethereum.org/docs/tools/clef/setup,src/pages/docs/tools/clef/setup.md,n/a
https://geth.ethereum.org/docs/clef/apis,https://geth.ethereum.org/docs/tools/clef/apis,src/pages/docs/tools/clef/apis.md,n/a
https://geth.ethereum.org/docs/clef/datatypes,https://geth.ethereum.org/docs/tools/clef/datatypes,src/pages/docs/tools/clef/datatypes.md,n/a
https://github.com/ethereum/go-ethereum/tree/gh-pages/docs/_vulnerabilities/vulnerabilities.json,https://github.com/ethereum/go-ethereum/tree/gh-pages/docs/_vulnerabilities/vulnerabilities.json,src/pages/docs/vulnerabilities/vulnerabilities.json,must be served at original URL
https://github.com/ethereum/go-ethereum/tree/gh-pages/docs/_vulnerabilities/vulnerabilities.json.minisig,https://github.com/ethereum/go-ethereum/tree/gh-pages/docs/_vulnerabilities/vulnerabilities.json.minisig,src/pages/docs/vulnerabilities/vulnerabilities.json.minisig,must be served at original URL
https://github.com/ethereum/go-ethereum/tree/gh-pages/docs/_vulnerabilities/vulnerabilities.md,https://geth.ethereum.org/docs/developers/geth-developers/discloures,src/pages/docs/developers/geth-developers/disclosures,moved to /docs and renamed
1 OLD Geth website URLS Equivalent NEW website URLs Relative path to markdown file Notes
2 https://geth.ethereum.org/ https://geth.ethereum.org src/pages/homepage will be react page
3 https://geth.ethereum.org/downloads/ https://geth.ethereum.org/downloads src/pages/downloads will be react page
4 https://geth.ethereum.org/docs/ https://geth.ethereum.org/docs src/pages/docs n/a
5 https://geth.ethereum.org/docs/getting-started https://geth.ethereum.org/docs/getting_started src/pages/docs/getting_started/getting_started.md n/a
6 https://geth.ethereum.org/docs/getting-started/geth-and-clef https://geth.ethereum.org/docs/getting_started_with_clef.md src/pages/docs/getting_started/getting-started-with-clef.md n/a
7 https://geth.ethereum.org/docs/getting-started/dev-mode https://geth.ethereum.org/docs/developers/geth-developers/dev-mode src/pages/docs/developers/geth-developer/dev-mode.md n/a
8 https://geth.ethereum.org/docs/install-and-build/installing-geth https://geth.ethereum.org/docs/getting_started/install-geth src/pages/docs/getting_started/backup-restore.md n/a
9 https://geth.ethereum.org/docs/install-and-build/backup-restore https://geth.ethereum.org/docs/getting_started/backup-restore src/pages/docs/getting_started/installing-geth.md n/a
10 https://geth.ethereum.org/docs/install-and-build/cross-compile page removed page removed n/a
11 https://geth.ethereum.org/docs/interface/command-line-options https://geth.ethereum.org/fundamentals/command-line-options src/pages/docs/fundamentals/command-line-options.md n/a
12 https://geth.ethereum.org/docs/interface/pruning https://geth.ethereum.org/docs/fundamentals/pruning src/pages/docs/fundamentals/pruning.md n/a
13 https://geth.ethereum.org/docs/interface/merge page removed page removed n/a
14 https://geth.ethereum.org/docs/interface/consensus-clients https://geth.ethereum.org/docs/getting_started/consensus-client src/pages/docs/getting_started/consensus-clients.md n/a
15 https://geth.ethereum.org/docs/interface/peer-to-peer https://geth.ethereum.org/docs/fundamentals/peer-to-peer src/pages/docs/fundamentals/peer-to-peer.md n/a
16 https://geth.ethereum.org/docs/interface/les https://geth.ethereum.org/docs/fundamentals/les src/pages/docs/fundamentals/les.md n/a
17 https://geth.ethereum.org/docs/interface/managing-your-accounts https://geth.ethereum.org/docs/fundamentals/account-management src/pages/docs/fundamentals/account-management.md n/a
18 https://geth.ethereum.org/docs/faq https://geth.ethereum.org/docs/faq src/pages/docs/faq.md n/a
19 https://geth.ethereum.org/docs/interface/javascript-console https://geth.ethereum.org/docs/interacting-with-geth/javascript-console src/pages/docs/interacting-with-geth/javascript-console.md n/a
20 https://geth.ethereum.org/docs/interface/private-network https://geth.ethereum.org/docs/developers/geth-developer/private-network src/pages/docs/developers/geth-developer/private-network.md n/a
21 https://geth.ethereum.org/docs/interface/mining page removed page removed n/a
22 https://geth.ethereum.org/docs/interface/metrics https://geth.ethereum.org/docs/monitoring/metrics src/pages/docs/monitoring/metrics.md n/a
23 https://geth.ethereum.org/docs/dapp/native https://geth.ethereum.org/docs/developers/dapp-developer/native src/pages/docs/developers/dapp-developer/native.md n/a
24 https://geth.ethereum.org/docs/dapp/tracing https://geth.ethereum.org/docs/developers/dapp-developer/tracing src/pages/docs/developers/dapp-developer/tracing.md n/a
25 https://geth.ethereum.org/docs/dapp/custom-tracer https://geth.ethereum.org/docs/developers/dapp-developer/custom-tracer src/pages/docs/developers/dapp-developer/custom-tracer.md n/a
26 https://geth.ethereum.org/docs/dapp/builtin-tracers https://geth.ethereum.org/docs/developers/dapp-developer/built-in-tracer src/pages/docs/developers/dapp-developer/built-in-tracers.md n/a
27 https://geth.ethereum.org/docs/dapp/native-accounts https://geth.ethereum.org/docs/developers/dapp-developer/native-accounts src/pages/docs/developers/dapp-developer/native-accounts.md n/a
28 https://geth.ethereum.org/docs/dapp/native-bindings https://geth.ethereum.org/docs/developers/dapp-developer/native-bindings src/pages/docs/developers/dapp-developer/native-bindings.md n/a
29 https://geth.ethereum.org/docs/dapp/mobile https://geth.ethereum.org/docs/developers/dapp-developer/mobile src/pages/docs/developers/dapp-developer/mobile.md n/a
30 https://geth.ethereum.org/docs/dapp/mobile-accounts page removed page removed n/a
31 https://geth.ethereum.org/docs/rpc/server https://geth.ethereum.org/docs/interacting-with-geth/rpc/server src/pages/docs/interacting-with-geth/rpc/server.md n/a
32 https://geth.ethereum.org/docs/rpc/pubsub https://geth.ethereum.org/docs/interacting-with-geth/rpc/pubsub src/pages/docs/interacting-with-geth/rpc/pubsub.md n/a
33 https://geth.ethereum.org/docs/rpc/batch https://geth.ethereum.org/docs//interacting-with-geth/rpc/batch src/pages/docs/interacting-with-geth/rpc/batch.md n/a
34 https://geth.ethereum.org/docs/rpc/graphql https://geth.ethereum.org/docs/interacting_with_geth/rpc/graphql src/pages/docs/interacting-with-geth/rpc/graphql.md n/a
35 https://geth.ethereum.org/docs/rpc/ns-admin https://geth.ethereum.org/docs/interacting_with_geth/rpc/ns-admin src/pages/docs/interacting-with-geth/rpc/ns-admin.md n/a
36 https://geth.ethereum.org/docs/rpc/ns-clique https://geth.ethereum.org/docs/interacting_with_geth/rpc/ns-clique src/pages/docs/interacting-with-geth/rpc/ns-clique.md n/a
37 https://geth.ethereum.org/docs/rpc/ns-debug https://geth.ethereum.org/docs/interacting_with_geth/rpc/ns-debug src/pages/docs/interacting-with-geth/rpc/ns-debug.md n/a
38 https://geth.ethereum.org/docs/rpc/ns-eth https://geth.ethereum.org/docs/interacting_with_geth/rpc/ns-eth src/pages/docs/interacting-with-geth/rpc/ns-eth.md n/a
39 https://geth.ethereum.org/docs/rpc/ns-les https://geth.ethereum.org/docs/interacting_with_geth/rpc/ns-les src/pages/docs/interacting-with-geth/rpc/ns-les.md n/a
40 https://geth.ethereum.org/docs/rpc/ns-miner https://geth.ethereum.org/docs/interacting_with_geth/rpc/ns-miner src/pages/docs/interacting-with-geth/rpc/ns-miner.md n/a
41 https://geth.ethereum.org/docs/rpc/ns-net https://geth.ethereum.org/docs/interacting_with_geth/rpc/ns-net src/pages/docs/interacting-with-geth/rpc/ns-net.md n/a
42 https://geth.ethereum.org/docs/rpc/ns-personal https://geth.ethereum.org/docs/interacting_with_geth/rpc/ns-personal src/pages/docs/interacting-with-geth/rpc/ns-personalmd n/a
43 https://geth.ethereum.org/docs/rpc/ns-txpool https://geth.ethereum.org/docs/interacting_with_geth/rpc/ns-txpool src/pages/docs/interacting-with-geth/rpc/ns-txpool.md n/a
44 https://geth.ethereum.org/docs/rpc/objects https://geth.ethereum.org/docs/interacting_with_geth/rpc/objects src/pages/docs/interacting-with-geth/rpc/objects.md n/a
45 https://geth.ethereum.org/docs/developers/dev-guide https://geth.ethereum.org/docs/developers/geth-developer/dev-guide src/pages/docs/developers/geth-developer/devguide.md n/a
46 https://geth.ethereum.org/docs/developers/code-review-guidelines https://geth.ethereum.org/docs/developers/geth-developer/code-review-guidelines src/pages/docs/developers/geth-developer/code-review-guidelines.md n/a
47 https://geth.ethereum.org/docs/developers/issue-handling-workflow https://geth.ethereum.org/docs/developers/geth-developer/code-review-guidelines src/pages/docs/developers/geth-developer/issue-handling-workflow.md n/a
48 https://geth.ethereum.org/docs/developers/dns-discovery-setup https://geth.ethereum.org/doce/developers/geth-developer/dns-discovery-setup src/pages/docs/developers/geth-developer/dns-discovery-workflow.md n/a
49 https://geth.ethereum.org/docs/clef/introduction https://geth.ethereum.org/docs/tools/clef/introduction src/pages/docs/tools/clef/introduction.md n/a
50 https://geth.ethereum.org/docs/clef/tutorial https://geth.ethereum.org/docs/tools/clef/tutorial src/pages/docs/tools/clef/tutorial.md n/a
51 https://geth.ethereum.org/docs/clef/cliquesigning https://geth.ethereum.org/docs/tools/clef/clique-signing src/pages/docs/tools/clef/clique-signing.md n/a
52 https://geth.ethereum.org/docs/clef/rules https://geth.ethereum.org/docs/tools/clef/rules src/pages/docs/tools/clef/rules.md n/a
53 https://geth.ethereum.org/docs/clef/setup https://geth.ethereum.org/docs/tools/clef/setup src/pages/docs/tools/clef/setup.md n/a
54 https://geth.ethereum.org/docs/clef/apis https://geth.ethereum.org/docs/tools/clef/apis src/pages/docs/tools/clef/apis.md n/a
55 https://geth.ethereum.org/docs/clef/datatypes https://geth.ethereum.org/docs/tools/clef/datatypes src/pages/docs/tools/clef/datatypes.md n/a
56 https://github.com/ethereum/go-ethereum/tree/gh-pages/docs/_vulnerabilities/vulnerabilities.json https://github.com/ethereum/go-ethereum/tree/gh-pages/docs/_vulnerabilities/vulnerabilities.json src/pages/docs/vulnerabilities/vulnerabilities.json must be served at original URL
57 https://github.com/ethereum/go-ethereum/tree/gh-pages/docs/_vulnerabilities/vulnerabilities.json.minisig https://github.com/ethereum/go-ethereum/tree/gh-pages/docs/_vulnerabilities/vulnerabilities.json.minisig src/pages/docs/vulnerabilities/vulnerabilities.json.minisig must be served at original URL
58 https://github.com/ethereum/go-ethereum/tree/gh-pages/docs/_vulnerabilities/vulnerabilities.md https://geth.ethereum.org/docs/developers/geth-developers/discloures src/pages/docs/developers/geth-developers/disclosures moved to /docs and renamed
Write Preview
Loading…
Cancel
Save