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
Hildr is an OP Stack rollup client written in Java 21. And follow the [spec](https://github.com/ethereum-optimism/optimism/blob/develop/specs/rollup-node.md):
8
+
Hildr is an OP Stack Rollup Node written in Java 21. You can check out the [architecture](https://docs.optimism.io/builders/node-operators/architecture) of OP Stack, hildr is the equivalent of op-node.
Running a sequencer node is currently not possible and there is no option to vote on blocks as part of the consensus mechanism or fork-choice like on Ethereum.
Copy file name to clipboardExpand all lines: docs/op-besu-docs/index.md
+3-2
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,4 @@
1
-
# Op-Besu
1
+
# Op-besu
2
+
3
+
[Op-besu](https://github.com/optimism-java/op-besu) is a fork of [Besu](https://github.com/hyperledger/besu) that implement the [execution engine](https://github.com/ethereum-optimism/specs/blob/main/specs/fjord/exec-engine.md) of [OP stack](https://stack.optimism.io/). You can check out the [architecture](https://docs.optimism.io/builders/node-operators/architecture) of OP Stack, op-besu is the equivalent of op-geth.
2
4
3
-
[Op-Besu](https://github.com/optimism-java/op-besu) is a fork of [Besu](https://github.com/hyperledger/besu) that supports the [execution engine](https://github.com/ethereum-optimism/specs/blob/main/specs/fjord/exec-engine.md) of [OP stack](https://stack.optimism.io/).
@@ -38,16 +73,17 @@ Unpack the downloaded files and change into the `op-besu-<release>` directory.
38
73
</TabItem>
39
74
40
75
<TabItemvalue="devnet or other"label="devnet or other">
76
+
You can check how to generate a devnet genesis file [here](https://docs.optimism.io/builders/chain-operators/deploy/genesis).
77
+
Also you could use the [optimism devnet tool](https://github.com/ethpandaops/optimism-package).
41
78
42
79
```shell
43
-
cd op-besu-<release> && \
44
80
./bin/besu \
45
81
--genesis-file=<devnet genesis file> \
46
82
--p2p-enabled=false \
47
83
--discovery-enabled=false \
48
-
--data-path=<your data dir> \
84
+
--data-path=datadir \
49
85
--engine-rpc-enabled \
50
-
--engine-jwt-secret=<jwt secret file> \
86
+
--engine-jwt-secret=./jwt.txt \
51
87
--rpc-http-enabled \
52
88
--host-allowlist=* \
53
89
--engine-host-allowlist=* \
@@ -58,3 +94,13 @@ Unpack the downloaded files and change into the `op-besu-<release>` directory.
58
94
</TabItem>
59
95
60
96
</Tabs>
97
+
98
+
:::danger Warning
99
+
100
+
The following settings are a security risk in production environments:
101
+
102
+
- Enabling the HTTP JSON-RPC service (`--rpc-http-enabled`) and setting `--rpc-http-host` to 0.0.0.0 exposes the RPC connection on your node to any remote connection.
103
+
- Setting `--host-allowlist` to `"*"` allows JSON-RPC API access from any host.
104
+
- Setting `--rpc-http-cors-origins` to `"all"` or `"*"` allows cross-origin resource sharing (CORS) access from any domain.
import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem';
2
2
3
-
# Use docker
4
-
5
-
You can use Docker to run [Op-Besu](https://github.com/optimism-java/op-besu) or [Op-Geth](https://github.com/ethereum-optimism/op-geth) as a Optimism EL node on the testnets.
6
-
7
3
## Prerequisites
8
4
9
-
Download and install [Docker](https://www.docker.com/products/docker-desktop).
5
+
Download and install [Docker](https://docs.docker.com/get-started/get-docker/).
docker run -it -p 8545:8545 -p 8551:8551 -v ./jwt.txt:/jwt/jwtsecret \
56
+
-v ./datadir:/data/ \
57
+
ghcr.io/optimism-java/op-besu:latest \
58
+
--genesis-file=<devnet genesis file> \
59
+
--p2p-enabled=false \
60
+
--discovery-enabled=false \
61
+
--data-path="/data/" \
62
+
--engine-rpc-enabled \
63
+
--engine-jwt-secret="/jwt/jwtsecret" \
64
+
--rpc-http-enabled \
65
+
--host-allowlist="*" \
66
+
--engine-host-allowlist="*" \
67
+
--logging=INFO \
68
+
--version-compatibility-protection=false
69
+
```
28
70
29
71
</TabItem>
30
72
</Tabs>
73
+
74
+
:::danger Warning
75
+
76
+
The following settings are a security risk in production environments:
77
+
78
+
- Enabling the HTTP JSON-RPC service (`--rpc-http-enabled`) and setting `--rpc-http-host` to 0.0.0.0 exposes the RPC connection on your node to any remote connection.
79
+
- Setting `--host-allowlist` to `"*"` allows JSON-RPC API access from any host.
80
+
- Setting `--rpc-http-cors-origins` to `"all"` or `"*"` allows cross-origin resource sharing (CORS) access from any domain.
0 commit comments