Portal Community
What it does: The Solana node (solana) is a Solnet-backed ExecutionNode covering 17 of a 47-operation design, spanning all 10 resources — account, block, transaction, token, nft, staking, program, wallet, nonce, utility. 11 operations are free JSON-RPC reads; 6 are signed writes that move real value or state on-chain and require a vault-backed wallet credential.

Quick Start

  1. Add a Solana node to your workflow
  2. Set resource to account and operation to balance
  3. Enter an address (e.g. 11111111111111111111111111111111, the System Program)
  4. Leave cluster unset to use the default (mainnet-beta), or set it to devnet for free testing
  5. Run the workflow — the node returns the account's lamport/SOL balance
Tip: Every operation on this node shares the same three config keys — resource, operation, cluster — plus a small set of operation-specific fields, and signing operations add one more: credentialID. Learn the pattern once on Input & Output and Signing & Credentials, and every operation below follows it.

Pages in This Guide

Configuration

appsettings.json, the default cluster, and dependency registration.

Clusters

Mainnet-beta, devnet, testnet, commitment levels, and vault-backed RPC URLs.

Account Operations

balance and getInfo — lamport/SOL balances and raw account metadata.

Block Operations

latestSlot — the current tip of the chain.

Transaction Operations

get a transaction's status and logs; sendNative for signed SOL transfers.

Token Operations

SPL token balance, Associated Token Account creation, and transfers.

NFT Operations

getAsset — current owner of a Solana NFT mint.

Staking Operations

delegate, getAccount, and getValidators for native SOL staking.

Program Operations

readAccountState — raw bytes owned by any on-chain program.

Wallet Operations

signMessage and getPublicKey against the configured credential.

Nonce Operations

get — durable nonce account state for offline/async transaction signing.

Utility Operations

convertUnits — lamports ⇄ SOL, no network call.

Signing & Credentials

The CRYPTO_WALLET vault credential, accepted key formats, and which 6 operations need it.

Input & Output

The shared config-key pattern and how errors surface.

Examples

Worked workflow patterns using this node.

Troubleshooting

Common errors and how to fix them.

Roadmap

The remaining 30 of 47 catalogued operations — what's next and why.

Core Concepts

Solnet-Backed RPC

Every operation on this node talks to a Solana JSON-RPC endpoint via the Solnet client library. Reads query whichever cluster you point the node at; writes are built and signed server-side using a wallet secret key resolved from the vault, then submitted and (for sendNative) confirmed before the node returns.

Resources

Operations are grouped by resource, matching Solana's own conceptual boundaries:

Reads vs. Signed Writes

11 of the 17 implemented operations are free reads requiring no credential. The other 6 — transaction/sendNative, token/createAta, token/transfer, staking/delegate, wallet/signMessage, wallet/getPublicKey — sign with a wallet secret key resolved from a CRYPTO_WALLET vault credential. See Signing & Credentials.

Clusters

Every operation runs against one of Solana's clusters, selected per-call via the cluster config key. See Clusters for URLs, commitment levels, and defaults.

Operation Summary

Resource Operations Signing? Guide Page
accountbalance, getInfoNoAccount Operations
blocklatestSlotNoBlock Operations
transactionget, sendNativesendNative onlyTransaction Operations
tokenbalance, createAta, transfercreateAta, transferToken Operations
nftgetAssetNoNFT Operations
stakingdelegate, getAccount, getValidatorsdelegate onlyStaking Operations
programreadAccountStateNoProgram Operations
walletsignMessage, getPublicKeyBothWallet Operations
noncegetNoNonce Operations
utilityconvertUnitsNoUtility Operations
17 of 47: This node implements 17 catalogued operations today. The remaining 30 — including account creation/transfer, token mint, NFT metadata via Metaplex, generic program instruction calls, and stake account creation — are tracked on the Roadmap page.