One user in Discord asked: can the Generator connect to any of their Ethereum execution RPCs, or only the one tied to the validator used for registration? They run validators across several regions, some non-custodial, and wanted to place the Generator next to an existing RPC to cut latency. They couldn't pick a region until they knew the answer.
The team's answer: the validator is there to establish the Generator's identity, the execution RPC is just the data source, and the Generator doesn't need to be colocated with the validator or use its node. Host it wherever it makes operational sense.
The install page gets halfway there ("a node you run yourself, a node co-located with your validator, or a managed provider") but never comes out and says the rule, so a multi-region operator still can't answer that question from the docs alone.
One user in Discord asked: can the Generator connect to any of their Ethereum execution RPCs, or only the one tied to the validator used for registration? They run validators across several regions, some non-custodial, and wanted to place the Generator next to an existing RPC to cut latency. They couldn't pick a region until they knew the answer.
The team's answer: the validator is there to establish the Generator's identity, the execution RPC is just the data source, and the Generator doesn't need to be colocated with the validator or use its node. Host it wherever it makes operational sense.
The install page gets halfway there ("a node you run yourself, a node co-located with your validator, or a managed provider") but never comes out and says the rule, so a multi-region operator still can't answer that question from the docs alone.