ACCOUNT ABSTRACTION
Particle Account Abstraction FAQ
Find Frequently Asked Questions about Particle Account Abstraction.
How can I support new ERC-20 tokens for Gas payments?
How can I support new ERC-20 tokens for Gas payments?
Answer: Particle Network uses the Biconomy Paymaster to sponsor transactions using ERC-20 tokens for gas fees. To support new ERC-20 tokens, it is dependent on Biconomy’s integration. The availability of a token for gas payments is determined by Biconomy’s supported token list.
For a complete list of supported ERC-20 tokens, please refer to the Biconomy documentation.
On which chains can I fund the Paymaster?
On which chains can I fund the Paymaster?
Answer: You can fund the Paymaster by depositing USDT on either Ethereum or BNB Chain through the Paymaster menu on the Particle Network Dashboard.The choice of chain only affects the deposit origin, not the Paymaster’s functionality. Once deposited, USDT is converted to the native token of the target chain, enabling you to sponsor transactions on any supported EVM chain.To view the full list of supported EVM chains, head over to the Network Coverage page.
No USDT deposit is needed for testnet sponsorship.
Can I use a custom smart account?
Can I use a custom smart account?
Answer: The AA SDK currently doesn’t offer native support for custom smart accounts. We support a select range of smart accounts:
- SimpleAccount:
SIMPLE - Biconomy:
BICONOMY - CyberConnect:
CYBERCONNECT - Light:
LIGHT - Xterio:
XTERIO
For more information on supported smart accounts and how to initialize them, visit the AA SDK documentation.
Can I automate transactions and/or remove confirmation pop-ups?
Can I automate transactions and/or remove confirmation pop-ups?
Answer: Yes, with Biconomy V2, you can use session keys to grant users the ability to conditionally delegate signing authority. This allows for the automation of transactions and the elimination of confirmation pop-ups, providing a smoother user experience.
Learn more about implementing Session Keys in your application.
How do I use a custom Bundler?
How do I use a custom Bundler?
Answer: Although our SDK doesn’t natively support custom Bundlers, you can still create a
UserOperation object using the SDK. Once constructed, this object can be executed via a standard API call to your own Bundler endpoint.For detailed guidance on creating and using
UserOperation objects, check out our API reference.How do I use a custom Paymaster?
How do I use a custom Paymaster?
Answer: The AA SDK currently only supports Particle’s native Paymaster, accessible via the Particle Network Dashboard, and Biconomy’s Paymaster. If you wish to use a custom Paymaster, you’ll need to integrate it through a custom API in your application, sponsoring a
UserOperation constructed by the AA SDK/API.After that, using our SDK, you can execute the resulting UserOperation (including paymasterAndData from your Paymaster).For more details on the available endpoints, visit the AA APIs documentation.
What are the differences between the natively supported smart accounts?
What are the differences between the natively supported smart accounts?
Answer: Each natively-supported smart account differs in feature-set (such as session keys, multi-chain signatures, and so on).Below is a table detailing the core differences between account types as it relates to the features they support.
| Account Type | Session Keys | Transferable Signer | Multichain Signatures | Gasless Transactions |
|---|---|---|---|---|
| Biconomy (V2) | ✓ | ✓ | ✓ | ✓ |
| Biconomy (V1) | ✗ | ✗ | ✗ | ✓ |
| Light | ✗ | ✓ | ✗ | ✓ |
| Xterio | ✗ | ✗ | ✗ | ✓ |
| CyberConnect | ✗ | ✗ | ✗ | ✓ |
| SimpleAccount | ✗ | ✗ | ✗ | ✓ |
For more information on the chains supported by each account type, head over to the Network Coverage page.
Still need help?Open a ticket with Particle’s Developer Relations team through the dedicated Telegram support bot.