# need gasless onboarding

> Privy handles user onboarding, Biconomy and ZeroDev are separate credible account-abstraction providers for sponsored smart-account transactions, and a low-cost EVM chain keeps both sponsored and fallback execution affordable.

## Recommended stack

- **Privy** (wallet_and_identity) — readiness 82/100, difficulty low — Use Privy for familiar auth and embedded wallet onboarding before the smart-account transaction layer.
- **Biconomy** (transactions_and_paymasters) — readiness 79/100, difficulty medium — Use Biconomy as one account-abstraction provider for paymasters, sponsored transactions, and gasless onboarding.
- **ZeroDev** (transactions_and_paymasters) — readiness 100/100, difficulty medium — Use ZeroDev as a separate account-abstraction provider for Kernel smart accounts, bundlers, paymasters, gas sponsorship, and session-key permissions.
- **Arbitrum One** (settlement_or_execution) — readiness 80/100, difficulty low — Use a low-cost EVM chain so sponsored and fallback transactions remain affordable.

## Risks

- Do not mix provider-specific bundler, paymaster, and SDK assumptions without testing the exact chain and account implementation.
- Gas sponsorship requires policies, limits, billing, and fallback behavior; otherwise UserOps can fail when sponsorship is exhausted or unavailable.

## Next steps

- Choose one primary account-abstraction provider for the first implementation path.
- Configure paymaster policies and fallback-to-native-token behavior before production.
- Test the full onboarding flow on the exact target chain, including first transaction, policy failure, and recovery paths.

## What the agent receives

```json
{
  "intent": "I need gasless onboarding",
  "matched_intent": "gasless-onboarding",
  "recommended_stack": [
    {
      "slug": "privy",
      "name": "Privy",
      "role": "wallet_and_identity",
      "readiness_score": 82,
      "integration_difficulty": "low",
      "reason": "Use Privy for familiar auth and embedded wallet onboarding before the smart-account transaction layer."
    },
    {
      "slug": "biconomy",
      "name": "Biconomy",
      "role": "transactions_and_paymasters",
      "readiness_score": 79,
      "integration_difficulty": "medium",
      "reason": "Use Biconomy as one account-abstraction provider for paymasters, sponsored transactions, and gasless onboarding."
    },
    {
      "slug": "zerodev",
      "name": "ZeroDev",
      "role": "transactions_and_paymasters",
      "readiness_score": 100,
      "integration_difficulty": "medium",
      "reason": "Use ZeroDev as a separate account-abstraction provider for Kernel smart accounts, bundlers, paymasters, gas sponsorship, and session-key permissions."
    },
    {
      "slug": "arbitrum-one",
      "name": "Arbitrum One",
      "role": "settlement_or_execution",
      "readiness_score": 80,
      "integration_difficulty": "low",
      "reason": "Use a low-cost EVM chain so sponsored and fallback transactions remain affordable."
    }
  ],
  "excluded_candidates": [],
  "risks": [
    "Do not mix provider-specific bundler, paymaster, and SDK assumptions without testing the exact chain and account implementation.",
    "Gas sponsorship requires policies, limits, billing, and fallback behavior; otherwise UserOps can fail when sponsorship is exhausted or unavailable."
  ],
  "next_steps": [
    "Choose one primary account-abstraction provider for the first implementation path.",
    "Configure paymaster policies and fallback-to-native-token behavior before production.",
    "Test the full onboarding flow on the exact target chain, including first transaction, policy failure, and recovery paths."
  ],
  "generated_with": "composewith.eth",
  "registry_version": "2026.06.10-8752c9d"
}
```

---
Canonical: https://composewith.eth/intents/gasless-onboarding