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
Building geth requires both a Go (version 1.9 or later) and a C compiler.
21
+
Building geth requires both a Go (version 1.10 or later) and a C compiler.
22
22
You can install them using your favourite package manager.
23
23
Once the dependencies are installed, run
24
24
@@ -35,12 +35,12 @@ The go-ethereum project comes with several wrappers/executables found in the `cm
35
35
| Command | Description |
36
36
|:----------:|-------------|
37
37
|**`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 Wiki page](https://github.com/ethereum/go-ethereum/wiki/Command-Line-Options) for command line options. |
38
-
|`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://github.com/ethereum/wiki/wiki/Ethereum-Contract-ABI) 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://github.com/ethereum/go-ethereum/wiki/Native-DApps:-Go-bindings-to-Ethereum-contracts) wiki page for details. |
38
+
|`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://github.com/ethereum/wiki/wiki/Ethereum-Contract-ABI) 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://github.com/ethereum/go-ethereum/wiki/Native-DApps:-Go-bindings-to-Ethereum-contracts) wiki page for details. |
39
39
|`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. |
40
40
|`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`). |
41
41
|`gethrpctest`| Developer utility tool to support our [ethereum/rpc-test](https://github.com/ethereum/rpc-tests) test suite which validates baseline conformity to the [Ethereum JSON RPC](https://github.com/ethereum/wiki/wiki/JSON-RPC) specs. Please see the [test suite's readme](https://github.com/ethereum/rpc-tests/blob/master/README.md) for details. |
42
-
|`rlpdump`| Developer utility tool to convert binary RLP ([Recursive Length Prefix](https://github.com/ethereum/wiki/wiki/RLP)) dumps (data encoding used by the Ethereum protocol both network as well as consensus wise) to userfriendlier hierarchical representation (e.g. `rlpdump --hex CE0183FFFFFFC4C304050583616263`). |
43
-
|`swarm`| Swarm daemon and tools. This is the entrypoint for the Swarm network. `swarm --help` for command line options and subcommands. See [Swarm README](https://github.com/ethereum/go-ethereum/tree/master/swarm) for more information. |
42
+
|`rlpdump`| Developer utility tool to convert binary RLP ([Recursive Length Prefix](https://github.com/ethereum/wiki/wiki/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`). |
43
+
|`swarm`| Swarm daemon and tools. This is the entry point for the Swarm network. `swarm --help` for command line options and subcommands. See [Swarm README](https://github.com/ethereum/go-ethereum/tree/master/swarm) for more information. |
44
44
|`puppeth`| a CLI wizard that aids in creating a new Ethereum network. |
45
45
46
46
## Running geth
@@ -72,7 +72,7 @@ This command will:
72
72
This tool is optional and if you leave it out you can always attach to an already running Geth instance
73
73
with `geth attach`.
74
74
75
-
### Full node on the Ethereum test network
75
+
### A Full node on the Ethereum test network
76
76
77
77
Transitioning towards developers, if you'd like to play around with creating Ethereum contracts, you
78
78
almost certainly would like to do that without any real money involved until you get the hang of the
@@ -83,10 +83,10 @@ network with your node, which is fully equivalent to the main network, but with
83
83
$ geth --testnet console
84
84
```
85
85
86
-
The `console` subcommand have the exact same meaning as above and they are equally useful on the
87
-
testnet too. Please see above for their explanations if you've skipped to here.
86
+
The `console` subcommand has the exact same meaning as above and they are equally useful on the
87
+
testnet too. Please see above for their explanations if you've skipped here.
88
88
89
-
Specifying the `--testnet` flag however will reconfigure your Geth instance a bit:
89
+
Specifying the `--testnet` flag, however, will reconfigure your Geth instance a bit:
90
90
91
91
* Instead of using the default data directory (`~/.ethereum` on Linux for example), Geth will nest
92
92
itself one level deeper into a `testnet` subfolder (`~/.ethereum/testnet` on Linux). Note, on OSX
@@ -103,7 +103,7 @@ separate the two networks and will not make any accounts available between them.
103
103
104
104
### Full node on the Rinkeby test network
105
105
106
-
The above test network is a crossclient one based on the ethash proof-of-work consensus algorithm. As such, it has certain extra overhead and is more susceptible to reorganization attacks due to the network's low difficulty / security. Go Ethereum also supports connecting to a proof-of-authority based test network called [*Rinkeby*](https://www.rinkeby.io) (operated by members of the community). This network is lighter, more secure, but is only supported by go-ethereum.
106
+
The above test network is a cross-client one based on the ethash proof-of-work consensus algorithm. As such, it has certain extra overhead and is more susceptible to reorganization attacks due to the network's low difficulty/security. Go Ethereum also supports connecting to a proof-of-authority based test network called [*Rinkeby*](https://www.rinkeby.io) (operated by members of the community). This network is lighter, more secure, but is only supported by go-ethereum.
107
107
108
108
```
109
109
$ geth --rinkeby console
@@ -139,13 +139,13 @@ This will start geth in fast-sync mode with a DB memory allowance of 1GB just as
139
139
140
140
Do not forget `--rpcaddr 0.0.0.0`, if you want to access RPC from other containers and/or hosts. By default, `geth` binds to the local interface and RPC endpoints is not accessible from the outside.
141
141
142
-
### Programatically interfacing Geth nodes
142
+
### Programmatically interfacing Geth nodes
143
143
144
144
As a developer, sooner rather than later you'll want to start interacting with Geth and the Ethereum
145
145
network via your own programs and not manually through the console. To aid this, Geth has built-in
146
146
support for a JSON-RPC based APIs ([standard APIs](https://github.com/ethereum/wiki/wiki/JSON-RPC) and
147
147
[Geth specific APIs](https://github.com/ethereum/go-ethereum/wiki/Management-APIs)). These can be
148
-
exposed via HTTP, WebSockets and IPC (unix sockets on unix based platforms, and named pipes on Windows).
148
+
exposed via HTTP, WebSockets and IPC (UNIX sockets on UNIX based platforms, and named pipes on Windows).
149
149
150
150
The IPC interface is enabled by default and exposes all the APIs supported by Geth, whereas the HTTP
151
151
and WS interfaces need to manually be enabled and only expose a subset of APIs due to security reasons.
@@ -173,7 +173,7 @@ on all transports. You can reuse the same connection for multiple requests!
173
173
174
174
**Note: Please understand the security implications of opening up an HTTP/WS based transport before
175
175
doing so! Hackers on the internet are actively trying to subvert Ethereum nodes with exposed APIs!
176
-
Further, all browser tabs can access locally running webservers, so malicious webpages could try to
176
+
Further, all browser tabs can access locally running web servers, so malicious web pages could try to
177
177
subvert locally available APIs!**
178
178
179
179
### Operating a private network
@@ -241,7 +241,7 @@ that other nodes can use to connect to it and exchange peer information. Make su
241
241
displayed IP address information (most probably `[::]`) with your externally accessible IP to get the
242
242
actual `enode` URL.
243
243
244
-
*Note: You could also use a fullfledged Geth node as a bootnode, but it's the less recommended way.*
244
+
*Note: You could also use a full-fledged Geth node as a bootnode, but it's the less recommended way.*
245
245
246
246
#### Starting up your member nodes
247
247
@@ -264,7 +264,7 @@ an OpenCL or CUDA enabled `ethminer` instance. For information on such a setup,
264
264
[EtherMining subreddit](https://www.reddit.com/r/EtherMining/) and the [Genoil miner](https://github.com/Genoil/cpp-ethereum)
265
265
repository.
266
266
267
-
In a private network setting however, a single CPU miner instance is more than enough for practical
267
+
In a private network setting, however a single CPU miner instance is more than enough for practical
268
268
purposes as it can produce a stable stream of blocks at the correct intervals without needing heavy
269
269
resources (consider running on a single thread, no need for multiple ones either). To start a Geth
270
270
instance for mining, run it with all your usual flags, extended by:
@@ -298,7 +298,7 @@ Please make sure your contributions adhere to our coding guidelines:
298
298
* E.g. "eth, rpc: make trace configs optional"
299
299
300
300
Please see the [Developers' Guide](https://github.com/ethereum/go-ethereum/wiki/Developers'-Guide)
301
-
for more details on configuring your environment, managing project dependencies and testing procedures.
301
+
for more details on configuring your environment, managing project dependencies, and testing procedures.
0 commit comments