Actions11
Overview
This node interacts with the Solana blockchain network to perform various operations such as retrieving account information, sending SOL or tokens, creating wallets, signing/verifying messages, staking SOL, and more. Specifically, the Get Account Info operation fetches detailed information about a given Solana account address.
Common scenarios where this node is beneficial include:
- Monitoring Solana account details for wallet management or auditing.
- Integrating Solana blockchain data into workflows for decentralized finance (DeFi) applications.
- Automating token transfers or balance checks within business processes.
- Managing staking activities programmatically.
For example, using the Get Account Info operation, you can retrieve metadata and status of a Solana account to verify its existence and properties before performing transactions.
Properties
| Name | Meaning |
|---|---|
| Account Address | The Solana account address to retrieve detailed information from. |
Output
The output JSON object for the Get Account Info operation contains:
success: Boolean indicating if the operation was successful.accountInfo: An object containing detailed account information retrieved from the Solana blockchain. This includes data such as lamports balance, owner, executable flag, rent epoch, and raw account data.operation: The name of the executed operation (getAccountInfo).
Example output structure:
{
"success": true,
"accountInfo": {
"lamports": 123456789,
"owner": "SomePublicKey",
"executable": false,
"rentEpoch": 123,
"data": "...base64 or buffer data..."
},
"operation": "getAccountInfo"
}
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential to connect to a Solana RPC endpoint.
- Uses the official Solana Web3.js library to interact with the blockchain.
- Requires network access to the specified Solana RPC URL.
- No additional environment variables are needed beyond the configured API credentials.
Troubleshooting
- Missing Account Address: If the account address parameter is empty or invalid, the node will throw an error stating that the account address is required.
- Account Not Found: If no account information is found for the provided address, an error will be thrown indicating no account info was found.
- Invalid Credentials: If the Solana API credentials are missing or incorrect, the node will fail to connect to the RPC endpoint.
- Network Issues: Connectivity problems with the Solana RPC server may cause timeouts or failures in fetching account info.
To resolve these issues:
- Ensure the account address is correctly formatted and valid.
- Verify that the API key credential is properly set up and has access to the Solana RPC endpoint.
- Check network connectivity and RPC endpoint availability.