alchemy_requestPaymasterAndData
Requests coverage for a UserOperation. Returns paymasterAndData if approved, errors if not.
Path parameters
Request
Additional data you wish to include in the request, such as proof of humanity.
The policy ID or list of policy IDs.
The entrypoint address the request should be sent through. This MUST be one of the entry points returned by the supportedEntryPoints RPC call and match the version of the user operation in the entryPoint field.
Dummy signature for the operation. This is useful for estimating gas costs.
Partial UserOperation object, missing paymasterAndData and signature fields. This can be either a v0.6 or v0.7 user operation, but MUST match the version of the entry point at the address in the entryPoint field.
Optional fields to override default gas and fee behavior – these can be multiplier overrides or absolute overrides.
Allows changes to the state of a contract before executing the call. For example, you can modify variable values (like balances or approvals) for that call without changing the contract itself on the blockchain. In more technical terms, the state override set is an optional parameter that allows executing the call against a modified chain state. It is an address-to-state mapping, where each entry specifies some state to be overridden prior to executing the call. Each address maps to an object containing:
Response
The response object may be one of two types: - For entrypoint v0.6: an object with property paymasterAndData. - For entrypoint v0.7: an object with properties paymasterData, paymasterVerificationGasLimit, and paymasterPostOpGasLimit.