Solana (Experimental)

Configure the Solana toolchain

Open Settings | Solana to review the command-line tools used by the plugin.

The settings page groups tools into two categories:

• Solana Toolchain — Solana CLI, Anchor Version Manager (AVM), Anchor CLI, and Surfpool.

• Additional Tools — Node.js and Yarn.

For each tool, the plugin displays the configured executable path and its detected version. Use the folder button next to a field to select a different executable. Click Refresh after installing a tool or changing a path to detect the tools and versions again.

If required tools are not installed, the plugin displays an Install missing tools link. Follow this link to install the missing dependencies, then return to the settings page and click Refresh to verify that they are available.

You can also open the plugin configuration from the Solana tool window while required tools are missing. In this setup state, the tool window provides an action that opens the relevant settings instead of displaying the normal project and Explorer content.

Configure Explorer networks

Open Settings | Solana | Explorer to manage the networks available in the Explorer.

The plugin provides the following networks by default:

• Mainnet Beta.

• Testnet.

• Devnet.

• Localnet.

Use the toolbar above the network list to add, remove, or edit network configurations.

To change an existing configuration, select it and click Edit. To delete a custom configuration, select it and click Remove. Configured networks become available in the Explorer tab's network selector.

Edit Anchor.toml

The plugin provides Anchor-aware editing assistance for Anchor.toml, including:

• Syntax highlighting for sections, properties, and values.

• Validation and editor inspections for the Anchor configuration.

• Context-aware completion for section properties.

• Completion for supported property values, with descriptions where available.

For example, inside the [hooks] section, completion suggests supported hook names such as pre-build, post-build, pre-deploy, post-deploy, pre-test, and post-test.

For cluster properties, completion provides the standard Solana cluster values and explains their purpose:

• devnet — the public Solana development cluster.

• localnet — a local Solana test validator.

• mainnet — the Solana mainnet-beta production cluster.

• testnet — the validator-facing Solana test cluster.

Synchronize Anchor program IDs

The editor displays the Sync Anchor Keys notification action when it detects that an Anchor program's ID declarations are out of sync with the program's generated keypair.

This commonly occurs after:

• Cloning a project without its generated deployment keypairs.

• Running an initial build that generates a new keypair.

• Replacing or regenerating a program keypair.

• Manually changing a program ID in the source code or Anchor.toml.

Click Sync Anchor Keys to run the equivalent of anchor keys sync. The generated keypair in target/deploy/<program>-keypair.json is treated as the source of truth. The action updates:

• The public key in the program's declare_id! macro.

• The corresponding program ID declaration in Anchor.toml.

After synchronization, the program source and Anchor configuration use the public key of the actual deployment keypair. Because the action edits project files, review the resulting changes before committing them.

Build and test Anchor projects

The plugin provides preconfigured run configurations for common Anchor development tasks:

• Anchor Build — builds the programs in the Anchor project.

• Anchor Test — runs the Anchor project's test suite.

Select either configuration from RustRover's run-configuration selector and run it using the standard IDE controls. Command output and errors appear in the Run tool window, allowing you to build and test the project without invoking the corresponding Anchor commands manually in a terminal.

Run a local network with Surfpool

The plugin provides a Surfpool: Start run configuration. Run it from RustRover's run-configuration selector to execute:

Surfpool output appears in the Run tool window and can include:

• Current slot and epoch information.

• Network and deployment logs.

• A transaction counter.

• A link to the Surfpool Studio interface.

After Surfpool starts, programs can be deployed to the local network from the Project tab.

Manage the wallet

The Wallet selector shows the wallet connected to the Anchor project. The adjacent toolbar provides the following actions, from left to right:

The selected wallet is used by operations that require a signer, such as deploying a program.

Manage programs

Programs declared for the selected cluster appear in the project tree.

Open a program's context menu to access the following actions:

Explore transactions

While the explorer is running, matching transactions appear in a live table with the following information:

• Slot — the slot in which the transaction was processed.

• Program — the selected program associated with the transaction.

• Status — the transaction result, such as OK for a successful transaction.

• Signature — the transaction signature.

Select a transaction to inspect its Instructions and Logs.

For every instruction, the Instructions section can show:

• The instruction index and program name.

• The decoded instruction name and argument values when the program's Anchor IDL is available.

• The instruction's stack height.

• The ordered list of account addresses supplied to the instruction.

• The raw instruction data in both Base58 and hexadecimal formats.

The Logs section shows runtime messages emitted during transaction execution, including:

• Program invocation and invocation depth.

• The executed instruction name.

• Messages emitted by the program.

• Compute units consumed and the compute-unit limit.

• Program success or failure.

Click Stop Explorer when transaction streaming is no longer needed.

Explore accounts

The Accounts view loads accounts owned by the selected programs.

The account table includes:

• Program — the selected program associated with the account.

• Account — the account's public key.

• Lamports — the account balance in lamports.

• Owner — the public key of the program that owns the account.

• Data size — the size of the account data in bytes.

• Executable — whether the account contains an executable program.

Use the Accounts toolbar to load program accounts, filter the results, or refresh the current data.

Select an account to open its details. The Details section shows:

• The account public key.

• The associated program name.

• The owner program's public key.

• The lamport balance.

• The executable status.

• The rent epoch.

The Raw data section shows:

• The account data size in bytes.

• The account data encoded as Base64.

• The account data encoded as hexadecimal.

When the program's Anchor IDL is available, the plugin adds a Decoded account section. It identifies the Anchor account type and presents its data as named, typed fields. For example, a decoded counter account can expose:

This makes it possible to inspect and verify application state directly in the IDE without manually decoding the account's binary data.

Localnet RPC is unavailable

Program deployment requires a reachable RPC service for the selected cluster. If the Localnet endpoint cannot be reached, the plugin reports an error similar to:

No transactions appear

Check that:

• The explorer is running; the button should read Stop Explorer.

• The correct cluster is selected.

• At least one program is selected in the program filter.

• The application is submitting transactions to the same network monitored by the explorer.

No accounts appear

Select the relevant program and click Get Program Accounts to load the Accounts view. If the table remains empty, confirm that the program has created accounts on the selected cluster.