You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: README.md
+17-17
Original file line number
Diff line number
Diff line change
@@ -39,7 +39,7 @@ directory.
39
39
|**`geth`**| Our main Ethereum CLI client. It is the entry point into the Ethereum network (main-, test- or private net), capable of running as a full node (default), archive node (retaining all historical state) or a light node (retrieving data live). It can be used by other processes as a gateway into the Ethereum network via JSON RPC endpoints exposed on top of HTTP, WebSocket and/or IPC transports. `geth --help` and the [CLI page](https://geth.ethereum.org/docs/interface/command-line-options) for command line options. |
40
40
|`clef`| Stand-alone signing tool, which can be used as a backend signer for `geth`. |
41
41
|`devp2p`| Utilities to interact with nodes on the networking layer, without running a full blockchain. |
42
-
|`abigen`| Source code generator to convert Ethereum contract definitions into easy to use, compile-time type-safe Go packages. It operates on plain [Ethereum contract ABIs](https://docs.soliditylang.org/en/develop/abi-spec.html) with expanded functionality if the contract bytecode is also available. However, it also accepts Solidity source files, making development much more streamlined. Please see our [Native DApps](https://geth.ethereum.org/docs/dapp/native-bindings) page for details. |
42
+
|`abigen`| Source code generator to convert Ethereum contract definitions into easy-to-use, compile-time type-safe Go packages. It operates on plain [Ethereum contract ABIs](https://docs.soliditylang.org/en/develop/abi-spec.html) with expanded functionality if the contract bytecode is also available. However, it also accepts Solidity source files, making development much more streamlined. Please see our [Native DApps](https://geth.ethereum.org/docs/dapp/native-bindings) page for details. |
43
43
|`bootnode`| Stripped down version of our Ethereum client implementation that only takes part in the network node discovery protocol, but does not run any of the higher level application protocols. It can be used as a lightweight bootstrap node to aid in finding peers in private networks. |
44
44
|`evm`| Developer utility version of the EVM (Ethereum Virtual Machine) that is capable of running bytecode snippets within a configurable environment and execution mode. Its purpose is to allow isolated, fine-grained debugging of EVM opcodes (e.g. `evm --code 60ff60ff --debug run`). |
45
45
|`rlpdump`| Developer utility tool to convert binary RLP ([Recursive Length Prefix](https://ethereum.org/en/developers/docs/data-structures-and-encoding/rlp)) dumps (data encoding used by the Ethereum protocol both network as well as consensus wise) to user-friendlier hierarchical representation (e.g. `rlpdump --hex CE0183FFFFFFC4C304050583616263`). |
@@ -65,14 +65,14 @@ Recommended:
65
65
66
66
* Fast CPU with 4+ cores
67
67
* 16GB+ RAM
68
-
* High Performance SSD with at least 1TB free space
68
+
* High-performance SSD with at least 1TB of free space
69
69
* 25+ MBit/sec download Internet service
70
70
71
71
### Full node on the main Ethereum network
72
72
73
73
By far the most common scenario is people wanting to simply interact with the Ethereum
74
74
network: create accounts; transfer funds; deploy and interact with contracts. For this
75
-
particular use-case the user doesn't care about years-old historical data, so we can
75
+
particular usecase, the user doesn't care about years-old historical data, so we can
76
76
sync quickly to the current state of the network. To do so:
77
77
78
78
```shell
@@ -83,11 +83,11 @@ This command will:
83
83
* Start `geth` in snap sync mode (default, can be changed with the `--syncmode` flag),
84
84
causing it to download more data in exchange for avoiding processing the entire history
85
85
of the Ethereum network, which is very CPU intensive.
86
-
* Start up `geth`'s built-in interactive [JavaScript console](https://geth.ethereum.org/docs/interface/javascript-console),
86
+
* Start the built-in interactive [JavaScript console](https://geth.ethereum.org/docs/interface/javascript-console),
87
87
(via the trailing `console` subcommand) through which you can interact using [`web3` methods](https://github.com/ChainSafe/web3.js/blob/0.20.7/DOCUMENTATION.md)
88
88
(note: the `web3` version bundled within `geth` is very old, and not up to date with official docs),
89
89
as well as `geth`'s own [management APIs](https://geth.ethereum.org/docs/rpc/server).
90
-
This tool is optional and if you leave it out you can always attach to an already running
90
+
This tool is optional and if you leave it out you can always attach it to an already running
91
91
`geth` instance with `geth attach`.
92
92
93
93
### A Full node on the Görli test network
@@ -102,12 +102,12 @@ the main network, but with play-Ether only.
102
102
$ geth --goerli console
103
103
```
104
104
105
-
The `console` subcommand has the exact same meaning as above and they are equally
106
-
useful on the testnet too. Please, see above for their explanations if you've skipped here.
105
+
The `console` subcommand has the same meaning as above and is equally
106
+
useful on the testnet too.
107
107
108
108
Specifying the `--goerli` flag, however, will reconfigure your `geth` instance a bit:
109
109
110
-
* Instead of connecting the main Ethereum network, the client will connect to the Görli
110
+
* Instead of connecting to the main Ethereum network, the client will connect to the Görli
111
111
test network, which uses different P2P bootnodes, different network IDs and genesis
112
112
states.
113
113
* Instead of using the default data directory (`~/.ethereum` on Linux for example), `geth`
@@ -118,9 +118,9 @@ Specifying the `--goerli` flag, however, will reconfigure your `geth` instance a
118
118
`geth attach <datadir>/goerli/geth.ipc`. Windows users are not affected by
119
119
this.
120
120
121
-
*Note: Although there are some internal protective measures to prevent transactions from
122
-
crossing over between the main network and test network, you should make sure to always
123
-
use separate accounts for play-money and real-money. Unless you manually move
121
+
*Note: Although some internal protective measures prevent transactions from
122
+
crossing over between the main network and test network, you should always
123
+
use separate accounts for play and realmoney. Unless you manually move
124
124
accounts, `geth` will by default correctly separate the two networks and will not make any
125
125
accounts available between them.*
126
126
@@ -155,7 +155,7 @@ configuration file via:
155
155
$ geth --config /path/to/your_config.toml
156
156
```
157
157
158
-
To get an idea how the file should look like you can use the `dumpconfig` subcommand to
158
+
To get an idea of how the file should look like you can use the `dumpconfig` subcommand to
0 commit comments