Etherspot

Plug the SDK into your app and ship Web3 flows your users understand. Start by initializing a client, generating a smart account address for each new user, and letting them act before the account is deployed on-chain. Because the address is precomputed, you can show a wallet-ready identity at signup, link it to an email or social login of your choice, and sponsor the first actions so no one needs to preload gas. From there, trigger an activation only when the user performs something meaningful—claiming a reward, minting, or making a purchase—so the first impression is fast and low-friction.

For checkout and subscriptions, build a single flow that bundles multiple contract calls and submits them as one operation. Add items to a cart, approve tokens, run the payment, and record metadata—then send the whole batch with one confirmation. Let users pay fees in a token you choose or cover them entirely; the relay network handles broadcasting, retries, and fee management across supported chains. Your UI can stay network-agnostic: set a target chain in code, preview costs, simulate the call set, and dispatch. If anything fails, the SDK returns clear statuses you can surface in the receipt screen.

Games and interactive apps can push actions in the background without forcing players to switch networks or learn new flows. Keep assets in user-owned smart accounts; trigger upgrades, trades, or claims as players progress; and sponsor lightweight moves to keep momentum. Use scoped permissions inside your app so common actions proceed with a single confirmation, while valuable events still request an explicit sign. Queue actions if the user goes offline, and submit when they return or when network conditions improve—your logic stays the same; the relayer takes care of timing and gas.

Wallet builders can manage balances, NFTs, and history across multiple networks through one interface. Show a unified portfolio, batch sends, and bridge or swap under the hood while keeping control client-side. In development, switch to testnets, simulate transactions before sending, and inspect relay outcomes with verbose logs. In production, set spending limits, define which contracts your app can call, and fall back to user-paid gas if sponsorship is exhausted. Roll out updates without migrating keys—the smart account remains the user’s and works consistently across chains.