Actions11
Overview
This node enables interaction with the Solana blockchain network, supporting a variety of operations such as sending SOL tokens, sending SPL tokens, staking SOL to validators, withdrawing staked SOL, creating wallets, signing/verifying messages, and retrieving account or transaction information. It is useful for automating Solana blockchain tasks within workflows, such as transferring funds, managing stakes, or verifying signatures.
A practical example includes delegating SOL tokens to a validator to earn staking rewards, or sending SPL tokens to another user programmatically.
Properties
| Name | Meaning |
|---|---|
| Amount | The amount of SOL or tokens to send or stake (numeric). |
| Validator Vote Account | The public key of the validator's vote account to which SOL will be delegated for staking. |
These properties are specifically relevant when performing the "Stake SOL" operation.
Output
The output JSON object for the "Stake SOL" operation contains:
success: Boolean indicating if the operation succeeded.stakeAccount: The public key of the newly created stake account (string).txSignature: The transaction signature string confirming the staking transaction on the Solana network.operation: The name of the operation performed ("stakeSol").
No binary data output is produced by this operation.
Dependencies
- Requires an API credential containing a private key and RPC URL to connect to the Solana network.
- Uses the official Solana Web3.js library and SPL Token library for blockchain interactions.
- Requires network access to the specified Solana RPC endpoint.
Troubleshooting
- Missing Credentials: If no credentials are provided, the node throws an error. Ensure that a valid API key credential with private key and RPC URL is configured.
- Invalid Validator Public Key: Providing an incorrect or malformed validator vote account public key will cause transaction failure.
- Insufficient Funds: Staking requires enough SOL balance to cover the stake amount plus rent exemption fees; otherwise, the transaction will fail.
- Network Issues: RPC endpoint unavailability or network errors can cause timeouts or failures.
- Error Messages:
"No credentials returned!"— Check that credentials are properly set.- Errors related to transaction submission usually indicate insufficient funds or invalid parameters.
To resolve issues, verify credentials, ensure correct input values, and confirm network connectivity.