status-im/nimbus-eth1
2
0
Fork 0
mirror of https://github.com/status-im/nimbus-eth1.git synced 2025-01-28 04:55:33 +00:00
Code Issues Projects Releases Wiki Activity

Let Fluffy default join testnet via the testnet bootstrap nodes (#1620)

Browse Source
This commit is contained in:
Kim De Mey 2023-06-28 23:53:27 +02:00 committed by GitHub
parent d4bf1ffbcf
commit 389ef89632
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 13 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
fluffy/README.md
View File

@ -55,14 +55,9 @@ make fluffy
### Run a Fluffy client on the public testnet ### Run a Fluffy client on the public testnet
There is a public [Portal testnet](https://github.com/ethereum/portal-network-specs/blob/master/testnet.md#portal-network-testnet) which contains nodes of different clients.
We run a fleet of Fluffy nodes that are part of this testnet.
Provide the `--network:testnet0` option to join this network.
```bash ```bash
# Connect to the Portal testnet and enable the JSON-RPC APIs # Connect to the Portal testnet bootstrap nodes and enable the JSON-RPC APIs
./build/fluffy --network:testnet0 --rpc --table-ip-limit:1024 --bucket-ip-limit:24 ./build/fluffy --rpc --table-ip-limit:1024 --bucket-ip-limit:24
``` ```
The `table-ip-limit` and `bucket-ip-limit` options are needed to allow more The `table-ip-limit` and `bucket-ip-limit` options are needed to allow more
@ -70,6 +65,12 @@ nodes with the same IPs in the routing tables. The default limits are there
as security measure. It is currently needed to increase the limits for the testnet as security measure. It is currently needed to increase the limits for the testnet
because the fleet of Fluffy nodes runs on only 2 machines / network interfaces. because the fleet of Fluffy nodes runs on only 2 machines / network interfaces.
There is a public [Portal testnet](https://github.com/ethereum/portal-network-specs/blob/master/testnet.md#portal-network-testnet)
which contains nodes of different clients.
Fluffy will default join the network through these bootstrap nodes.
You can also explicitly provide the `--network:testnet0` option to join this
network, or `--network:none` to not connect to any of these bootstrapn odes.
> **_Note:_** The `--network` option selects automatically a static set of > **_Note:_** The `--network` option selects automatically a static set of
specific bootstrap nodes belonging to a "testnet". Currently `testnet0` is the specific bootstrap nodes belonging to a "testnet". Currently `testnet0` is the

2
fluffy/conf.nim
View File

@ -83,7 +83,7 @@ type
desc: desc:
"Select which Portal network to join. This will set the " & "Select which Portal network to join. This will set the " &
"network specific bootstrap nodes automatically" "network specific bootstrap nodes automatically"
defaultValue: PortalNetwork.none defaultValue: PortalNetwork.testnet0
name: "network" }: PortalNetwork name: "network" }: PortalNetwork
# Note: This will add bootstrap nodes for both Discovery v5 network and each # Note: This will add bootstrap nodes for both Discovery v5 network and each

8
fluffy/docs/content_seeding.md
View File

@ -34,7 +34,7 @@ Run Fluffy and trigger the propagation of data with the
`portal_history_propagateEpochAccumulators` JSON-RPC API call: `portal_history_propagateEpochAccumulators` JSON-RPC API call:
```bash ```bash
./build/fluffy --network:testnet0 --rpc --table-ip-limit:1024 --bucket-ip-limit:24 ./build/fluffy --rpc --table-ip-limit:1024 --bucket-ip-limit:24
# From another terminal # From another terminal
curl -s -X POST -H 'Content-Type: application/json' -d '{"jsonrpc":"2.0","id":"1","method":"portal_history_propagateEpochAccumulators","params":["./user_data_dir/"]}' http://localhost:8545 | jq curl -s -X POST -H 'Content-Type: application/json' -d '{"jsonrpc":"2.0","id":"1","method":"portal_history_propagateEpochAccumulators","params":["./user_data_dir/"]}' http://localhost:8545 | jq
@ -47,7 +47,7 @@ accumulators are available on the history network:
Make sure you still have a fluffy instance running, if not run: Make sure you still have a fluffy instance running, if not run:
```bash ```bash
./build/fluffy --network:testnet0 --rpc --table-ip-limit:1024 --bucket-ip-limit:24 ./build/fluffy --rpc --table-ip-limit:1024 --bucket-ip-limit:24
``` ```
Run the `content_verifier` tool and see if all epoch accumulators are found: Run the `content_verifier` tool and see if all epoch accumulators are found:
@ -79,7 +79,7 @@ Ethereum JSON-RPC endpoint.
`portal_history_propagate` JSON-RPC API call: `portal_history_propagate` JSON-RPC API call:
```bash ```bash
./build/fluffy --network:testnet0 --table-ip-limit:1024 --bucket-ip-limit:24 --log-level:info --rpc ./build/fluffy --table-ip-limit:1024 --bucket-ip-limit:24 --log-level:info --rpc
# From another shell # From another shell
curl -s -X POST -H 'Content-Type: application/json' -d '{"jsonrpc":"2.0","id":"1","method":"portal_history_propagate","params":["./user_data_dir/eth-history-data.json"]}' http://localhost:8545 | jq curl -s -X POST -H 'Content-Type: application/json' -d '{"jsonrpc":"2.0","id":"1","method":"portal_history_propagate","params":["./user_data_dir/eth-history-data.json"]}' http://localhost:8545 | jq
@ -92,7 +92,7 @@ curl -s -X POST -H 'Content-Type: application/json' -d '{"jsonrpc":"2.0","id":"1
Run a Fluffy node with the JSON-RPC API enabled. Run a Fluffy node with the JSON-RPC API enabled.
```bash ```bash
./build/fluffy --network:testnet0 --rpc --table-ip-limit:1024 --bucket-ip-limit:24 ./build/fluffy --rpc --table-ip-limit:1024 --bucket-ip-limit:24
``` ```
Build & run the `beacon_chain_bridge`: Build & run the `beacon_chain_bridge`: