Solana icon

Solana

Perform operations on Solana network: send SOL, send token, get balance, create wallet, sign/verify messages, stake, and more.

Overview

This node enables interaction with the Solana blockchain network, providing a variety of operations such as creating wallets, sending SOL or SPL tokens, checking balances, staking SOL, and signing or verifying messages. The "Sign Message" operation specifically allows users to cryptographically sign arbitrary messages using their private key, which is useful for proving ownership of an address or authorizing actions off-chain. This can be beneficial in scenarios like authenticating users, generating verifiable signatures for agreements, or integrating with decentralized applications requiring signed messages.

Properties

Name Meaning
Message The text message that you want to sign or verify.

(Note: For the "Sign Message" operation, only the "Message" property is relevant.)

Output

The output JSON object for the "Sign Message" operation contains:

  • success: A boolean indicating if the signing was successful.
  • signature: The base58-encoded cryptographic signature of the input message.
  • operation: The string "signMessage" indicating the performed operation.

Example output structure:

{
  "success": true,
  "signature": "base58EncodedSignatureString",
  "operation": "signMessage"
}

No binary data output is produced by this operation.

Dependencies

  • Requires a valid Solana API credential containing a private key and RPC URL to connect to the Solana network.
  • Uses the @solana/web3.js library for blockchain interactions.
  • Uses tweetnacl for cryptographic signing.
  • Uses bs58 for base58 encoding/decoding.
  • Requires n8n environment configured with the appropriate Solana API credentials.

Troubleshooting

  • Missing Message: If the "Message" property is empty or not provided, the node will throw an error stating that the message is required for signing.
  • Invalid Credentials: If the Solana API credentials are missing or invalid (e.g., incorrect private key), signing will fail.
  • Network Issues: Connectivity problems with the Solana RPC endpoint may cause failures.
  • Error Handling: If an error occurs during execution and "Continue On Fail" is disabled, the node will stop and report the error; otherwise, it will return the error message paired with the input item.

Links and References

Discussion