Skip to main content

Summary

DA Builder supports two EIP-7702 integration paths: TrustedProposer for fast setup and TrustlessProposer for account-owner authorization on every delegated call.

Choose An Integration Path

Start with TrustedProposer unless your application already requires account-owner authorization for every delegated call.

Network Configuration

TrustedProposer Workflow

TrustedProposer is the fastest way to use DA Builder. The transaction sender can keep submitting normal signed transactions after setup.
  1. Create or choose a dedicated EOA.
  2. Deposit ETH into the Spire GasTank for that EOA.
  3. Submit an EIP-7702 authorization that delegates the EOA to Spire’s TrustedProposer.
  4. Send transaction submissions to the DA Builder RPC endpoint.
  5. Store the returned transaction hash.
  6. Poll eth_getTransactionReceipt or dab_transactionStatus.
  7. Use direct RPC fallback for outages, unsupported methods, or non-aggregated operational paths.

TrustedProposer Delegation With Foundry

TrustlessProposer Workflow

TrustlessProposer is for applications that need DA Builder aggregation without trusting Spire to choose arbitrary delegated execution.
  1. Delegate the EOA to TrustlessProposer.
  2. Fund the Spire GasTank.
  3. Update the application to sign proposer call payloads.
  4. Submit the signed proposer call through DA Builder.
  5. Poll status and implement direct RPC fallback.

IProposer Interface

TrustlessProposer Security Requirements

For a complete implementation, see TrustlessProposer.sol↗.

TrustlessProposer Delegation With Foundry

TrustlessProposer Example Call

This example builds the exact calldata shape used by TrustlessProposer.onCall(...) and uses ethers v6.

Next Steps