The ERC-4337 wallet provider built for speed
Native smart accounts, EIP-7702, paymasters for gasless transactions, and session keys — sub-100ms wallet creation, benchmarked and open-source.
No credit card required • Free testnet accounts
ERC-4337 and EIP-7702 in one SDK
Openfort treats smart accounts as first-class citizens with native support for ERC-4337 and EIP-7702. Deploy new smart accounts or upgrade existing EOAs without changing addresses. Sub-100ms creation, 100–150ms signing — benchmarks public at openfort.io/benchmarks.
Gasless transactions built in
Openfort runs its own bundler and paymasters, served from one endpoint at api.openfort.io/rpc/{chainId}, with paymaster addresses published per chain for EntryPoint v0.6, v0.8 and v0.9. Sponsor gas from your project balance or let users pay in an ERC-20 — both gated by the policy engine. Register an external paymaster instead if you need your own sponsorship logic.
Programmable permissions per action
Session keys scoped by contract address, function selector, spend cap, and expiry. Ship game inventories, agent payments, and recurring user actions without re-prompting the user for every signature.
“Openfort has been an instrumental piece of technology for our platform. They helped us from integration to auditing the implementation.”
Christian Gascon
CTO @GFAL
Higher is better (normalized to 100%)
*Updated September 2025
The rest of the wallet stack
Smart accounts are one layer. Openfort delivers the full stack — embedded wallets, agent wallets, and stablecoin orchestration — under one SDK.
Embedded wallets
Non-custodial embedded wallets powered by OpenSigner, with full key export and self-hosting options. Read more
Agent wallets
Embedded wallets purpose-built for AI agents: session keys, x402 payments, policy-based spending limits. Read more
Wallet automations
TEE backend wallets for server-side key storage with permissions and automatic transaction execution. Read more
Frequently Asked Questions
Can't find your answer?
Openfort, Alchemy, Biconomy, Pimlico, ZeroDev and Thirdweb each run their own ERC-4337 bundler and paymaster. Privy defaults to Pimlico’s public bundler and asks you to register a bundler and paymaster URL per network. Safe ships contracts and a provider-agnostic SDK and runs neither. Openfort gives you smart accounts, the bundler and the paymaster from one vendor, without integrating a separate AA provider.
Yes, as a first-class account type called a delegated account. You upgrade an existing EOA without changing its address, and it gains gas sponsorship, transaction batching and session keys. Delegated accounts require a chain running EntryPoint v0.8 or v0.9: Arbitrum One, Base, BNB, Ethereum, Optimism and Polygon POS. Key rotation is not supported under 7702, unlike a fully programmable smart account. The 7702 Contract Delegator was audited by Quantstamp in September 2025.
Openfort smart accounts create in under 100ms and sign with low-latency infrastructure benchmarked against Privy, Turnkey, and Dynamic. Public benchmarks and reproducible code at openfort.io/benchmarks.
No. Openfort runs both. The 4337 bundler is at api.openfort.io/rpc/{chainId} with a publishable key in the Authorization header, and the same endpoint serves the paymaster — one URL for a viem createBundlerClient and createPaymasterClient pair. Paymaster addresses are published per chain for EntryPoint v0.6, v0.8 and v0.9. If you need custom sponsorship logic you can register an external paymaster and link it to a policy.
Yes. Programmable session keys are first-class in the Openfort SDK: scope by contract address, function selector, spend cap, and expiry. Ideal for game inventories, agent payments, and recurring user actions.
Smart accounts, the 4337 bundler and gas sponsorship run on Arbitrum Nova, Arbitrum One, Avalanche, Base, Beam, BNB, Ethereum, KL1 Blanche, Optimism and Polygon POS. Solana is supported through the same SDK, with wallets as EOAs and fees sponsored by a Kora fee-payer relayer rather than a paymaster. Openfort SDKs cover React, React Native, Unity, Unreal, Swift, and raw JavaScript/TypeScript.
Yes, five times by independent firms, each dated: CertiK in December 2023, Cure53 in September 2024, Omniscia in December 2024, Quantstamp on the 7702 Contract Delegator in September 2025, and Quantstamp on key management in October 2025. The signer (OpenSigner, opensigner.dev) is open-source so you can audit it yourself.