Signature webhook
This is not used for EIP712 wallet intents.
Key Requirements
Response Time:
Your service must respond within 200ms to prevent the intent from being dropped. A faster response ensures smooth execution and preserves transaction opportunities.
Signature Format:
The signature must be in a non-compact format, ending in either
1b
or1c
. Ensure that your signing process produces this format for compatibility.
Request:
The following is an example of the payload sent to your webhook:
Field Descriptions:
intentId
: A unique identifier for the intent being processed.launch
: Information about the detected launch:type
: The type of launch, eitherpublic_transaction
,private_transaction
, orblock
.blockNumber
: The block number associated with the launch.launchTxHash
: The transaction hash of the detected launch.
tx
: Transaction details as an EIP-1559 compliant structure.rawTx
: The raw serialized transaction (optional - only when launch type is a transaction).hash
: The transaction hash to be signed.
Response
Your webhook should respond with a signature in the following format:
Field Descriptions:
signature
: The ECDSA signature for the transaction hash, in non-compact format. Ensure it ends with either1b
or1c
.
Last updated