Sign a transaction with a wallet’s private key share via MPC.
EVM: Provide unsigned transaction fields as a JSON object and the endpoint
will RLP-encode them, sign via MPC, and return a fully serialized signed
transaction (hex-encoded with 0x prefix) ready for broadcast.
Solana: Provide a base64-encoded serialized Solana transaction (as built by
@solana/web3.js). The endpoint signs it via MPC and returns the signed
transaction as a base64 string ready for broadcast.
Your partner secret key (server-side only)
UUID for request tracing. Para returns one if omitted.
Wallet ID
"0a1b2c3d-4e5f-6789-abcd-ef0123456789"
EVM: JSON object with unsigned transaction fields. Solana: base64-encoded serialized transaction string. The API differentiates by type — objects are treated as EVM, strings as Solana.
Signed transaction
Signed transaction ready for broadcast. EVM: RLP-encoded hex string with 0x prefix. Solana: base64-encoded string.
"0x02f8..."