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: portal/docs/the_fluffy_book/docs/history-content-bridging.md
+16-12Lines changed: 16 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,10 +17,9 @@ Run a Portal client with the Portal JSON-RPC API enabled, e.g. Nimbus Portal cli
17
17
> Note: The `--storage-capacity:0` option is not required, but it is added here
18
18
for the use case where the node's only focus is on gossiping content from the portal bridge.
19
19
20
-
### Step 2: Run an EL client
20
+
### Step 2: Run an EL client (Optional)
21
21
22
-
The Nimbus Portal bridge needs access to the EL JSON-RPC API, either through a local
23
-
Ethereum client or via a web3 provider.
22
+
To seed the latest blocks, the Nimbus Portal bridge needs access to the EL JSON-RPC API, either through a local Ethereum client or via a web3 provider.
24
23
25
24
### Step 3: Run the Portal bridge in history mode
26
25
@@ -29,19 +28,24 @@ Build & run the Nimbus Portal bridge:
29
28
make nimbus_portal_bridge
30
29
31
30
WEB3_URL="http://127.0.0.1:8548"# Replace with your provider.
32
-
./build/nimbus_portal_bridge history --web3-url:${WEB3_URL}
31
+
./build/nimbus_portal_bridge history --era1-dir:/somedir/era1/ --web3-url:${WEB3_URL}
33
32
```
34
33
35
-
By default the Nimbus Portal bridge will run in `--latest` mode, which means that only the
36
-
latest block content will be gossiped into the network.
34
+
By default the Nimbus Portal bridge runs in `--backfill-mode:regular`. This means the bridge will access era1 files to gossip block bodies and receipts into the network. There are other backfill modes available which first try to download the data from the network before gossiping it into the network, e.g. sync and audit mode.
37
35
38
-
It also has a `--backfill` mode which will gossip pre-merge blocks
39
-
from `era1` files into the network. By default the bridge will audit first whether
40
-
the content is available on the network and if not it will gossip it into the
41
-
network.
36
+
Example: regular backfill (gossip everything):
37
+
```bash
38
+
./build/nimbus_portal_bridge history --backfill-mode:regular --era1-dir:/somedir/era1/
0 commit comments