SW4P Documentation
OpenAPIOpen app
Browse documentation
Smart Account Flows

Smart Account Flows

The source defines two EVM smart-account surfaces. Production payment execution is currently disabled during migration:

  • delegated EIP-7702 bridge requests
  • ERC-4337 UserOperation bridge requests

These are reference backend contracts, not currently available payment routes. They are not yet a polished universal wallet product, and they do not currently expose managed session-key APIs.

What Exists Today

  • POST /v1/bridge/delegated
  • GET /v1/account/delegation/:address
  • GET /v1/account/delegates
  • POST /v1/bridge/userop
  • POST /v1/account/paymaster
  • POST /v1/account/estimate-gas
  • GET /v1/account/entrypoints

These routes are currently surfaced through wallet-authenticated backend and frontend app flows. They are not part of the public API-key TypeScript or Rust SDK clients today.

Flow Selection

Use delegated bridge when:

  • the user is an EOA
  • you already have an EIP-7702 authorization
  • you want a one-transaction delegated batch such as approve plus bridge

Use ERC-4337 when:

  • the user is operating through a smart contract account
  • you need bundler-based submission
  • you may want optional paymaster sponsorship

Current Limits

  • EIP-7702 delegation status is currently treated as transient. The backend does not claim persistent active delegation state.
  • session keys are discussed in backend architecture comments but are not yet a dedicated managed API surface
  • paymaster sponsorship depends on per-chain backend configuration and can be unavailable without breaking the core UserOperation flow
  • these routes are EVM smart-account surfaces, not a chain-abstracted wallet contract across all SW4P rails

Recovery Notes

When a smart-account request fails:

  • keep the original authorization or UserOperation payload
  • record the returned txHash, userOpHash, or backend error body
  • re-query delegation or entrypoint availability before retrying
  • request a fresh paymaster payload before retrying a sponsored UserOperation
  • do not assume session-key revocation or delegation persistence tooling exists yet in the SW4P API

Frontend Truth

The frontend surface is a smart-account lab for these reference routes. It is suitable for builder testing and contract validation, not for claiming a fully abstracted consumer wallet experience.