Sign a transaction
Signs a transaction with the given EVM account. The transaction should be serialized as a hex string using RLP.
The transaction must be an EIP-1559 dynamic fee transaction. The developer is responsible for ensuring that the unsigned transaction is valid, as the API will not validate the transaction.
Headers
A JWT signed using your Wallet Secret, encoded in base64. Refer to the Generate Wallet Token section of our Authentication docs for more details on how to generate your Wallet Token.
An optional UUID v4 request header for making requests safely retryable. When included, duplicate requests with the same key will return identical responses. Refer to our Idempotency docs for more information on using idempotency keys.
36
Path Parameters
The 0x-prefixed address of the EVM account.
Body
Response
Successfully signed transaction.
The response is of type object
.