Provider Security & Performance Considerations
In this section, we address the security of block templates and performance considerations as part of your builder-boost integration.
In the builder requirements, an additional relay is introduced to your Builder Implementation. We emphasize that payloads aren't sent out of your builder environment.
The inclusion of an extra relay is solely aimed at streamlining the integration process with your builder-boost sidecar module. Here is a simplified example of a Primev-enabled builder setup:
Are there any performance costs of sending Block Templates to builder-boost?
The impact of sending templates to an additional relay specification on system performance is minimal. Incorporating additional computation into a system always carries some costs. However, to prevent sequential blocking, the builder-boost call is executed in a dedicated, short-lived go-routine. This impact is mitigated by the fact that we make only a single HTTP call, utilizing data that is already allocated on the heap for the relays' operation.
Where does Geth construct the payload being sent to builder-boost?
Geth has already allocated the payload in the heap to send it to relays. Primev builder modifications simply obtain a read-only reference to the data to ensure that it can be sent to your builder-boost instance.
What are the security considerations of enabling Primev?
To safeguard your builder-boost sidecar, we employ a share-secret authentication mechanism that can be configured in both the builder-boost and the modified geth instances. This setup ensures that malicious payloads cannot be posted to your builder-boost instance externally.
For maintaining the Confidentiality of your block data, we strongly recommend utilizing an HTTPS connection when sending data to builder-boost.