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
## Proposed Changes
Update the merge migration docs to encourage updating mainnet configs _now_!
The docs are also updated to recommend _against_ `--suggested-fee-recipient` on the beacon node (#3432).
Additionally the `--help` for the CLI is updated to match with a few small semantic changes:
- `--execution-jwt` is no longer allowed without `--execution-endpoint`. We've ended up without a default for `--execution-endpoint`, so I think that's fine.
- The flags related to the JWT are only allowed if `--execution-jwt` is provided.
Yes. The `--staking` flag is just an alias for `--http --eth1`. The `--eth1` flag is now superfluous
163
+
so `--staking` is equivalent to `--http`. You need either `--staking` or `--http` for the validator
164
+
client to be able to connect to the beacon node.
165
+
141
166
### Can I use `http://localhost:8545` for the execution endpoint?
142
167
143
168
Most execution nodes use port `8545` for the Ethereum JSON-RPC API. Unless custom configuration is
144
169
used, an execution node _will not_ provide the necessary engine API on port `8545`. You should
145
170
not attempt to use `http://localhost:8545` as your engine URL and should instead use
146
171
`http://localhost:8551`.
147
172
148
-
### What about multiple execution endpoints?
173
+
### Can I share an execution node between multiple beacon nodes (many:1)?
174
+
175
+
It is **not** possible to connect more than one beacon node to the same execution engine. There must be a 1:1 relationship between beacon nodes and execution nodes.
176
+
177
+
The beacon node controls the execution node via the engine API, telling it which block is the
178
+
current head of the chain. If multiple beacon nodes were to connect to a single execution node they
179
+
could set conflicting head blocks, leading to frequent re-orgs on the execution node.
180
+
181
+
We imagine that in future there will be HTTP proxies available which allow users to nominate a
182
+
single controlling beacon node, while allowing consistent updates from other beacon nodes.
183
+
184
+
### What about multiple execution endpoints (1:many)?
185
+
186
+
It is **not** possible to connect one beacon node to more than one execution engine. There must be a 1:1 relationship between beacon nodes and execution nodes.
149
187
150
-
Since an execution engine can only have one connected BN, the value of having multiple execution
188
+
Since an execution engine can only have one controlling BN, the value of having multiple execution
151
189
engines connected to the same BN is very low. An execution engine cannot be shared between BNs to
0 commit comments