FAQs

How much does it cost and how does DA Builder make money?

In summary, DA Builder takes a portion of the savings provided to users. Refer to Cost Structure for details.

Will using DA Builder impact transaction inclusion or in-block transaction positioning?

DA Builder frees up funds that users can apply to priority fees if they choose. Combined with the ability to submit a bundle of transactions from multiple entities, this should improve likelihood of timely inclusion and secure favorable in-block ordering.

What happens if DA Builder has an outage?

Redundant infrastructure is in place to minimize downtime, but if an outage does occur the simplest fallback is to submit the transaction directly through any standard RPC endpoint. The transaction can be sent exactly as it would be if the EOA had no account code set via EIP-7702. This process can be automated to ensure operations remain independent of DA Builder, which functions purely as an optional cost-saving layer.

Does using DA Builder change the signature process for transactions?

DA Builder requires an EOA with EIP-7702 enabled and delegated to a Proposer contract. This setup allows signed transactions from multiple parties to be batched and submitted together.

In order to make this a trustless process (i.e. ensure only transactions signed by the transaction originator can be executed), implement a TrustlessProposer or using the default implementation deployed here. It uses a message signing technique (EIP 712) to ensure the transaction originator has approved the transaction but that allows for others to execute it on their behalf.