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
-[Euclid Upgrade (#5): Note for Partners](https://www.notion.so/scrollzkp/Euclid-Upgrade-5-Note-for-Partners-1ad7792d22af808cad5ac643a5ecdaf0)
31
-
32
27
## Staying Up-to-Date
33
28
34
29
Keep an eye on https://github.com/scroll-tech/go-ethereum/releases for new node releases.
@@ -42,10 +37,6 @@ We recommend using the latest release at https://github.com/scroll-tech/go-ether
42
37
43
38
The preferred network name is `Scroll` or `scroll`. If you operate a user-facing service (e.g. public RPC endpoint), please consider using this name.
44
39
45
-
## Guidance for RPC Providers
46
-
47
-
For more information about Scroll RPCs and namespace configuration, please refer to this [page](https://bit.ly/scroll-l2geth-rpc)
48
-
49
40
### Hardware Requirements
50
41
51
42
**Recommended**
@@ -66,24 +57,6 @@ This section assumes you are familiar with [Docker](https://www.docker.com/) and
66
57
You will need access to a fully-synced **Ethereum Mainnet** RPC endpoint before running `l2geth`. You can maintain your own node or choose to use a 3rd-party provider that supports the standard Ethereum RPC APIs. The remainder of the article assumes that you have access to an L1 node’s HTTP RPC API at `L2GETH_L1_ENDPOINT`.
When you run l2geth using the --scroll flag, it will automatically connect to 5 default bootnodes. Additionally, we maintain 2 dedicated bootnodes for selected partners. You can connect to these through the l2geth console:
0 commit comments