Turnkey icon

Turnkey

Use Turnkey
Join our community

Actions7

Overview

This node integrates with the Turnkey service to sign blockchain transactions securely. It supports signing Ethereum, Solana, and Tron transactions by taking an unsigned transaction in various encodings and returning a signed transaction. This is useful for workflows that require programmatic transaction signing without exposing private keys directly, such as automated payment processing, decentralized app interactions, or multi-signature wallet operations.

For example, you can provide an unsigned Ethereum transaction in hex format along with a wallet account or private key identifier, and the node will return the signed transaction ready for broadcasting to the network.

Properties

Name Meaning
Authentication Method of authentication; currently supports "API Key".
Organization ID The unique identifier of your Turnkey organization. Required to scope API calls.
Type The blockchain type of the transaction to sign. Options: Ethereum, Solana, Tron.
Encoding Encoding format of the unsigned transaction input. Options: Base64, Base58, Hex.
Sign With Wallet account address, private key address, or private key identifier used to sign the transaction.
Unsigned Transaction The raw unsigned transaction string to be signed. For Ethereum and Tron use hex format; for Solana use base64.

Output

The node outputs a JSON object containing the full response from the Turnkey API's sign transaction operation. The key part of this output is:

  • signedTransaction: The signed transaction string encoded in the same format as the input (Base64, Base58, or Hex), ready to be broadcast to the respective blockchain network.

If the input encoding was Base64 or Base58, the node converts the unsigned transaction to hex before signing and then converts the signed transaction back to the original encoding for output.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the Turnkey service.
  • Uses the Turnkey client SDK (@turnkey/http) and optionally:
    • @turnkey/api-key-stamper for API key stamping.
    • bs58 package for Base58 encoding/decoding.
  • Node configuration must include valid Turnkey API credentials and organization ID.

Troubleshooting

  • Common issues:

    • Incorrect or missing organization ID will cause authorization failures.
    • Providing unsigned transactions in an incorrect encoding or format may result in errors or invalid signatures.
    • Using an unsupported operation or missing required parameters will throw errors.

  • Error messages:

    • "Failed to execute operation: ..." indicates an error during API call or parameter handling. Check the message for details.
    • "Operation ... not supported" means the requested operation is not implemented by the node.
    • Authentication errors usually mean invalid or missing API credentials.

  • Resolutions:

    • Verify all required parameters are provided and correctly formatted.
    • Ensure the API key credential is valid and has access to the specified organization.
    • Confirm the unsigned transaction matches the expected encoding and blockchain type.

Links and References

This summary focuses on the "Sign Transaction" operation of the Turnkey node, describing its inputs, outputs, dependencies, and common troubleshooting tips based on static code analysis.

Discussion