Brickken SignInstall

Summary

Sign a blockchain transaction locally using a private key.

Inputs

• transactionJson (required) — JSON string or object representing the transaction to sign, containing fields such as to, chainId, value, data, gasLimit, nonce, etc.

Output shape

An array of objects, each with a "json" field containing signedTransaction, signerAddress, and transactionHash, plus a "pairedItem" linking back to the input item.

The node processes each input item individually; if continueOnFail is enabled, errors are captured as objects with error messages instead of throwing.

Examples

Example 1: Add a signed transaction to a workflow chain.

Provide a transaction JSON with required fields and connect the node; it will output an object with signedTransaction and signerAddress.

Example 2: Batch sign multiple transactions.

Pass an array of transaction JSON objects as separate items; each item yields a signed result in the output array.

Example 3: Handle signing errors gracefully.

Enable continueOnFail; the node will output error objects for any malformed transaction JSON.