Our proprietary Paymaster allows developers to recharge and spend across different chains.
Particle Network’s Paymaster is a specialized tool designed to make gas payments easier and friendlier for end users across chains, leveraging Particle Network’s Omnichain Account Abstraction design. This service, which has helped us sponsor over 500k UserOperations across different networks in the previous month, is already fully integrated with Particle’s Modular Smart WaaS (Wallet-as-a-Service).
Particle’s Paymaster offers several compelling advantages, making it a powerful component of the Omnichain AA ecosystem:
Configuring webhooks allows developers to accurately control which UserOP can be accepted by the Paymaster. We use two types of webhooks:
before_paymaster_sign
.after_paymaster_sign
.Every time a Webhook request is made, a signature for the body is generated, which developers can verify to determine whether the request was sent by Particle Network. A unique public and private key (RSA-2048) is generated for each project. This key can be downloaded from the users’ Particle dashboard page for verification.
Webhooks in the Particle Network dashboard.
before_paymaster_sign
This hook will be triggered before the Paymaster signs. The Paymaster will determine whether to sign the UserOP based on the status code returned by the Hook. It includes:
chainId
UserOp
- UserOperation struct.entryPoint
- The entryPoint address.parsed
- Transaction struct. The Paymaster will attempt to parse the calldata of the UserOP. If it cannot be parsed, this field may not exist.after_paymaster_sign
This hook will trigger after the Paymaster signs. It includes:
chainId
UserOp
- UserOperation struct.entryPoint
- The entryPoint address.parsed
- Transaction struct. The Paymaster will attempt to parse the calldata of the UserOP
. If it cannot be parsed, this field may not exist.Developers can configure a whitelist of contract methods they want to sponsor in the backend. This means that after configuration, our server will only provide the Paymaster’s signature for the specified contract methods.
Whitelist Smart Contracts for Paymaster on Dashboard
The simplest way is to configure a whitelist of contract methods to sponsor. However, using Webhooks provides more flexibility, allowing for unlimited sponsorship strategies through any programmatic logic.
Developers can use Webhooks to implement any sponsorship logic they wish in conjunction with the Paymaster.
For the before_paymaster_sign
webhook, we return all the data necessary:
UserOp
UserOp
to decide which user address(sender) you want to sponsor.UserOp
to calculate the gas fee and decide whether to sponsor or not.This allows, for example, for the following business scenarios:
In many cases, programmatic sponsorship policies can be used and adapted to create a friendly experience and simplify experiences where it matters most.
To learn more about Particle’s Account Abstraction Stack, head over to the relevant SDK reference pages.
Our proprietary Paymaster allows developers to recharge and spend across different chains.
Particle Network’s Paymaster is a specialized tool designed to make gas payments easier and friendlier for end users across chains, leveraging Particle Network’s Omnichain Account Abstraction design. This service, which has helped us sponsor over 500k UserOperations across different networks in the previous month, is already fully integrated with Particle’s Modular Smart WaaS (Wallet-as-a-Service).
Particle’s Paymaster offers several compelling advantages, making it a powerful component of the Omnichain AA ecosystem:
Configuring webhooks allows developers to accurately control which UserOP can be accepted by the Paymaster. We use two types of webhooks:
before_paymaster_sign
.after_paymaster_sign
.Every time a Webhook request is made, a signature for the body is generated, which developers can verify to determine whether the request was sent by Particle Network. A unique public and private key (RSA-2048) is generated for each project. This key can be downloaded from the users’ Particle dashboard page for verification.
Webhooks in the Particle Network dashboard.
before_paymaster_sign
This hook will be triggered before the Paymaster signs. The Paymaster will determine whether to sign the UserOP based on the status code returned by the Hook. It includes:
chainId
UserOp
- UserOperation struct.entryPoint
- The entryPoint address.parsed
- Transaction struct. The Paymaster will attempt to parse the calldata of the UserOP. If it cannot be parsed, this field may not exist.after_paymaster_sign
This hook will trigger after the Paymaster signs. It includes:
chainId
UserOp
- UserOperation struct.entryPoint
- The entryPoint address.parsed
- Transaction struct. The Paymaster will attempt to parse the calldata of the UserOP
. If it cannot be parsed, this field may not exist.Developers can configure a whitelist of contract methods they want to sponsor in the backend. This means that after configuration, our server will only provide the Paymaster’s signature for the specified contract methods.
Whitelist Smart Contracts for Paymaster on Dashboard
The simplest way is to configure a whitelist of contract methods to sponsor. However, using Webhooks provides more flexibility, allowing for unlimited sponsorship strategies through any programmatic logic.
Developers can use Webhooks to implement any sponsorship logic they wish in conjunction with the Paymaster.
For the before_paymaster_sign
webhook, we return all the data necessary:
UserOp
UserOp
to decide which user address(sender) you want to sponsor.UserOp
to calculate the gas fee and decide whether to sponsor or not.This allows, for example, for the following business scenarios:
In many cases, programmatic sponsorship policies can be used and adapted to create a friendly experience and simplify experiences where it matters most.
To learn more about Particle’s Account Abstraction Stack, head over to the relevant SDK reference pages.