# Biconomy

> Account abstraction tooling for smart accounts, paymasters, bundlers, and gasless onboarding.

- Readiness score: **79/100** (score.v2)
- Integration difficulty: medium
- Chains: arbitrum-one, arbitrum-sepolia, bsc
- Categories: accounts, paymasters, gasless
- Last verified: 2026-05-29 by composewith.eth seed research (confidence: medium)

## Resources

- docs: https://docs.biconomy.io/
- sdk: https://github.com/bcnmy/biconomy-client-sdk
- template: https://docs.biconomy.io/
- support: https://discord.gg/biconomy
- grant: https://www.biconomy.io/

## Good for

- gasless onboarding
- session keys
- sponsored transactions
- consumer apps

## Avoid for

- fully self-hosted ERC-4337 infra without provider dependency

## Capabilities

### Gasless transactions (production-ready)
Best for: onboarding, abstracted gas, sponsored actions
- Paymaster rules, quotas, and pricing need upfront validation.

## Composes with

- **privy** (wallet_and_identity; supports) — Privy can provide embedded wallet and social-login onboarding before Biconomy handles sponsored smart-account transactions.
- **safe** (operational_controls; supports) — Safe-style smart account patterns can pair with Biconomy paymasters and account abstraction workflows.
- **zerodev** (transactions_and_paymasters; alternative) — ZeroDev is a separate account-abstraction provider for smart accounts, paymasters, bundlers, session keys, and chain abstraction; choose one primary provider per app path.
- **gelato** (automation; supports) — Gelato can automate follow-up transactions or recurring tasks after sponsored user actions.

## Per-chain support

### bsc (production-ready)
- Docs: https://docs.biconomy.io/
- Configure the bundler and paymaster for BNB Smart Chain (chain id 56) to sponsor first-transaction onboarding.
- Limitations: Paymaster sponsorship rules, quotas, and pricing must be validated for BSC before relying on gasless flows in production.
- Verified 2026-06-10 (source: https://docs.biconomy.io/)

## Advisories

- **Paymaster signature replay fixed in SDK 3.4.2** (security_fix, required_security) — A signature replay in the paymaster verification path allowed sponsored transactions to be reused across sessions. Fixed in @biconomy/sdk 3.4.2. Upgrade and invalidate any paymaster signatures cached before the upgrade.

---
Canonical: https://composewith.eth/protocols/biconomy · JSON: https://composewith.eth/protocols/biconomy.json