SettleMint
ComponentsInfrastructureAccount abstraction

Bundlers

How DALP exposes an authenticated bundler JSON-RPC endpoint for ERC-4337 discovery, UserOperation submission, and ERC-7677 paymaster sponsorship.

A bundler prepares valid ERC-4337 UserOperations for an EntryPoint. DALP exposes an authenticated bundler JSON-RPC endpoint so integrations can discover the active chain and EntryPoint, submit and track UserOperations, and request paymaster sponsorship. Every operation is scoped to the calling organization's wallets and runs inside DALP's policy, signer, and tracking controls.

Requires: account abstraction enabled for the deployment.

Where the bundler fits

Bundlers sit between a smart account and the EntryPoint contract. In a standard ERC-4337 flow, a client builds a UserOperation and sends it for relay. The relay validates the operation, then submits it to the EntryPoint.

In DALP, that protocol role is wrapped by platform controls. DALP resolves the EntryPoint for the active EVM network, applies signer and policy checks, coordinates paymaster readiness when sponsorship is used, and records the final transaction outcome through platform tracking.

Rendering diagram...

The UserOperation carries the smart-account call. DALP keeps the regulated-platform controls beside that call. Those controls cover request permission, signer or multisig approval, gas sponsorship readiness, and final transaction recording.

Callable JSON-RPC surface

Use Bundler JSON-RPC when an integration needs account abstraction discovery data before it builds a flow.

Discovery questionJSON-RPC methodWhat DALP returns
Which chain is active?eth_chainIdThe active network chain ID as a hexadecimal string.
Which EntryPoint is supported?eth_supportedEntryPointsThe EntryPoint address resolved for the active network.

The endpoint also accepts authenticated, organization-scoped UserOperation submission, gas estimation, lookup, and ERC-7677 paymaster methods. Operations only act on wallets owned by the calling organization, so they run inside DALP's approval, sponsorship, and tracking model rather than bypassing it. See Bundler JSON-RPC for the full method list.

Boundary for integrations

Use the bundler-compatible endpoint for ERC-4337 discovery and UserOperation flows. Use the REST smart wallet and paymaster surfaces to manage wallet state and configure sponsorship.

NeedUse
Read active chain IDBundler JSON-RPC discovery
Read supported EntryPointBundler JSON-RPC discovery
Submit or track a UserOperationBundler JSON-RPC UserOperation methods
Manage smart wallet state or signersREST smart wallet endpoints
Configure paymaster funding or sponsorshipREST paymaster endpoints
Track final transaction stateDALP transaction tracking and event surfaces

This split lets ERC-4337-aware clients discover the network shape and submit UserOperations while DALP keeps enforcing its approval, sponsorship, and tracking model.

Failure modes to expect

EntryPoint discovery depends on network configuration and indexed Directory data. If the Directory contract is not configured, discovery returns an unavailable error. If the EntryPoint registration exists on-chain but has not been indexed yet, discovery returns a not-found error. Retry only after the deployment configuration is complete and indexing has caught up.

Unsupported methods return JSON-RPC method-not-found responses when the request includes an id. Paymaster methods also return method-not-found when gas sponsorship is not enabled for the organization. Notifications without an id return 204 No Content under JSON-RPC notification semantics.

On this page