Sign transaction · Blokboard

Sign transaction asks a signing provider to sign an existing encoded transaction. Use it when another trusted step has already built the transaction.

Try it step by step#

Obtain a transaction you can inspect from your transaction-building step.
Map its base64 transaction value into Transaction Base64 and choose the signing layer.
Run with the appropriate signing provider available, then inspect the signed transaction and signature output.

The result includes signing information and a signature. Signing here does not itself submit the transaction to the network.

A base64 string is encoded transaction data, not a readable description of what will be authorized. Inspect the transaction before signing.
Use a dedicated transfer or swap node when that is the actual task; those nodes also handle building and submitting it.
A missing signing-provider error means the selected runtime cannot access an appropriate signer.

Network setup: This node uses solana. See connections for RPC setup and Test mode for network selection.

Setting	Default	What it does
Transaction Base64	`{{input.transactionBase64}}`	Signed through the application, extension, or web vault depending on availability.
Signing Layer	`auto`	Signing provider to use. Auto selects an available provider for this run.
On failure	`stop`	Choose whether a failed execution stops the workflow or only ends this path.
Retry attempts	`0`	How many additional attempts to make after the first failure.

Signing Layer: Choices: Auto (auto), Application (executable), Extension (extension), Web Vault (web). Available under More options.

On failure: Choices: Stop workflow (stop), Continue (continue). Available under More options.

Retry attempts: Available under More options. Limits: minimum 0.

Port	Value	Description
`in`	object	Payload containing or accompanying a transaction.

Port	Value	Description
`out`	object	Signed Solana transaction result.