Sends a user operation with a signature.
The payload to sign must be the userOpHash field of the user operation. This hash should be signed directly (not using personal_sign or EIP-191 message hashing).
The signature must be 65 bytes in length, consisting of: - 32 bytes for the r value - 32 bytes for the s value - 1 byte for the v value (must be 27 or 28)
If using the CDP Paymaster, the user operation must be signed and sent within 2 minutes of being prepared.
A JWT signed using your CDP API Key Secret, encoded in base64. Refer to the Generate Bearer Token section of our Authentication docs for information on how to generate your Bearer Token.
The address of the Smart Account to send the user operation from.
The hash of the user operation to send.
The hex-encoded signature of the user operation. This should be a 65-byte signature consisting of the r, s, and v values of the ECDSA signature. Note that the v value should conform to the personal_sign standard, which means it should be 27 or 28.
"0x1b0c9cf8cd4554c6c6d9e7311e88f1be075d7f25b418a044f4bf2c0a42a93e212ad0a8b54de9e0b5f7e3812de3f2c6cc79aa8c3e1c02e7ad14b4a8f42012c2c01b"
The sent user operation.
The network the user operation is for.
base-sepolia, base, arbitrum, optimism, zora, polygon, bnb, avalanche, ethereum, ethereum-sepolia "base"
The hash of the user operation. This is not the transaction hash, as a transaction consists of multiple user operations. The user operation hash is the hash of this particular user operation which gets signed by the owner of the Smart Account.
"0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef"
The list of calls in the user operation.
[
{
"to": "0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48",
"value": "0",
"data": "0xa9059cbb000000000000000000000000fc807d1be4997e5c7b33e4d8d57e60c5b0f02b1a0000000000000000000000000000000000000000000000000000000000000064"
},
{
"to": "0xdac17f958d2ee523a2206206994597c13d831ec7",
"value": "1000000000000000",
"data": "0x"
}
]The status of the user operation.
pending, signed, broadcast, complete, dropped, failed "pending"
The hash of the transaction that included this particular user operation. This gets set after the user operation is broadcasted and the transaction is included in a block.
"0x0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef"
The list of receipts associated with the user operation.
The receipt that contains information about the execution of user operation.
{
"revert": {
"data": "0x123",
"message": "reason for failure"
},
"blockHash": "0x386544b58930c0ec9e8f3ed09fb4cdb76b9ae0a1a37ddcacebe3925b57978e65",
"blockNumber": 29338819,
"gasUsed": "100000"
}[
{
"revert": {
"data": "0x123",
"message": "reason for failure"
},
"blockHash": "0x386544b58930c0ec9e8f3ed09fb4cdb76b9ae0a1a37ddcacebe3925b57978e65",
"blockNumber": 29338819,
"gasUsed": "100000"
}
]