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: public/content/developers/docs/apis/javascript/index.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ In order for a web app to interact with the Ethereum blockchain (i.e. read block
8
8
9
9
For this purpose, every Ethereum client implements the [JSON-RPC](/developers/docs/apis/json-rpc/) specification, so there are a uniform set of [methods](/developers/docs/apis/json-rpc/#json-rpc-methods) that applications can rely on.
10
10
11
-
If you want to use JavaScript to connect with an Ethereum node, it's possible to use vanilla JavaScript but several convenience libraries exist within the ecosystem that make this much easier. With these libraries, developers can write intuitive, one-line methods to initialize JSONRPC requests (under the hood) that interact with Ethereum.
11
+
If you want to use JavaScript to connect with an Ethereum node, it's possible to use vanilla JavaScript but several convenience libraries exist within the ecosystem that make this much easier. With these libraries, developers can write intuitive, one-line methods to initialize JSON-RPC requests (under the hood) that interact with Ethereum.
12
12
13
13
Please note that since [The Merge](/roadmap/merge/), two connected pieces of Ethereum software - an execution client and a consensus client - are required to run a node. Please ensure your node includes both an execution and consensus client. If your node is not on your local machine (e.g. your node is running on an AWS instance) update the IP addresses in the tutorial accordingly. For more information please see our page on [running a node](/developers/docs/nodes-and-clients/run-a-node/).
Copy file name to clipboardExpand all lines: public/content/developers/docs/nodes-and-clients/index.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -168,7 +168,7 @@ Nethermind is an Ethereum implementation created with the C# .NET tech stack, li
168
168
169
169
- an optimized virtual machine
170
170
- state access
171
-
- networking and rich features like Prometheus/Grafana dashboards, seq enterprise logging support, JSONRPC tracing, and analytics plugins.
171
+
- networking and rich features like Prometheus/Grafana dashboards, seq enterprise logging support, JSON-RPC tracing, and analytics plugins.
172
172
173
173
Nethermind also has [detailed documentation](https://docs.nethermind.io), strong dev support, an online community and 24/7 support available for premium users.
Copy file name to clipboardExpand all lines: public/content/developers/docs/nodes-and-clients/run-a-node/index.md
+5-5Lines changed: 5 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -227,7 +227,7 @@ This section will guide you through starting execution clients. It only serves a
227
227
- Defines data directory, where all the data including blockchain will be stored
228
228
- Make sure to substitute the path with a real one, e.g. pointing to your external drive
229
229
- Enables interfaces for communicating with the client
230
-
- Including JSONRPC and Engine API for communication with consensus client
230
+
- Including JSON-RPC and Engine API for communication with consensus client
231
231
- Defines path to `jwtsecret` for authenticated API
232
232
- Make sure to substitute the example path with a real one which can be accessed by clients, e.g. `/tmp/jwtsecret`
233
233
@@ -237,7 +237,7 @@ Please keep in mind that this is just a basic example, all other settings will b
237
237
238
238
##### Running Besu
239
239
240
-
This example starts Besu on mainnet, stores blockchain data in default format at `/data/ethereum`, enables JSONRPC and Engine RPC for connecting consensus client. Engine API is authenticated with token `jwtsecret` and only calls from `localhost` are allowed.
240
+
This example starts Besu on mainnet, stores blockchain data in default format at `/data/ethereum`, enables JSON-RPC and Engine RPC for connecting consensus client. Engine API is authenticated with token `jwtsecret` and only calls from `localhost` are allowed.
241
241
242
242
```
243
243
besu --network=mainnet \
@@ -259,7 +259,7 @@ besu --Xlauncher
259
259
260
260
##### Running Erigon
261
261
262
-
This example starts Erigon on mainnet, stores blockchain data at `/data/ethereum`, enables JSONRPC, defines which namespaces are allowed and enables authentication for connecting the consensus client which is defined by the `jwtsecret` path.
262
+
This example starts Erigon on mainnet, stores blockchain data at `/data/ethereum`, enables JSON-RPC, defines which namespaces are allowed and enables authentication for connecting the consensus client which is defined by the `jwtsecret` path.
263
263
264
264
```
265
265
erigon --chain mainnet \
@@ -272,7 +272,7 @@ Erigon by default performs a full sync with 8GB HDD which will result in more th
272
272
273
273
##### Running Geth
274
274
275
-
This example starts Geth on mainnet, stores blockchain data at `/data/ethereum`, enables JSONRPC and defines which namespaces are allowed. It also enables authentication for connecting consensus client which requires path to `jwtsecret` and also option defining which connections are allowed, in our example only from `localhost`.
275
+
This example starts Geth on mainnet, stores blockchain data at `/data/ethereum`, enables JSON-RPC and defines which namespaces are allowed. It also enables authentication for connecting consensus client which requires path to `jwtsecret` and also option defining which connections are allowed, in our example only from `localhost`.
276
276
277
277
```
278
278
geth --mainnet \
@@ -287,7 +287,7 @@ Check [docs for all configuration options](https://geth.ethereum.org/docs/fundam
287
287
288
288
##### Running Nethermind
289
289
290
-
Nethermind offers various [installation options](https://docs.nethermind.io/nethermind/first-steps-with-nethermind/getting-started). The package comes with various binaries, including a Launcher with a guided setup, which will help you to create the configuration interactively. Alternatively, you find Runner which is the executable itself and you can just run it with config flags. JSONRPC is enabled by default.
290
+
Nethermind offers various [installation options](https://docs.nethermind.io/nethermind/first-steps-with-nethermind/getting-started). The package comes with various binaries, including a Launcher with a guided setup, which will help you to create the configuration interactively. Alternatively, you find Runner which is the executable itself and you can just run it with config flags. JSON-RPC is enabled by default.
0 commit comments