Skip to main content
Rhinestone intents use the prepare, sign, and submit transaction flow. Use ERC-4337 UserOperations for account workflows that explicitly require a bundler, such as deploying or setting up some existing accounts and executing recovery operations.

Configure a bundler

The SDK can use Pimlico, Biconomy, or a custom bundler URL. If you omit bundler, it uses Pimlico’s public endpoint, which is suitable for development but not production volume.
These examples are server-side. Do not bundle Rhinestone, bundler, or paymaster secrets into browser code.

Configure a paymaster

A paymaster is optional. Add it when you want the paymaster to sponsor ERC-4337 UserOperation gas:
The paymaster and bundler are separate configuration fields even when they use the same provider credential. Custom paymasters accept the same url: string | Record<number, string> shape as custom bundlers.

Send a UserOperation

UserOperations use a separate API from intents:
Use sendUserOperation({ chain, calls }) only when you do not need to inspect or transport the prepared payload between steps.
A paymaster sponsors ERC-4337 gas only. To configure sponsorship for Rhinestone intents, follow sponsorship setup.