SLV Adds Local Mode - Manage Solana Validator and RPC Nodes Directly on SSH Login Nodes with AI Agents. Also Ideal as a Migration Destination for solv Users
ELSOUL LABO B.V. has released the latest version of its Solana development tool, SLV, adding a Local Mode. This enables users to directly manage and operate nodes via an AI agent utilizing natural language. It also offers a smooth migration path for users of its predecessor tool, solv.
📋 Article Processing Timeline
- 📰 Published: April 4, 2026 at 09:18
- 🔍 Collected: April 4, 2026 at 05:30
- 🤖 AI Analyzed: April 18, 2026 at 04:08 (334h 37m after Collected)
ELSOUL LABO B.V. (Headquarters: Amsterdam, Netherlands; CEO: Fumitake Kawasaki) and Validators DAO, developers and operators of the open-source Solana development tool SLV, have released the latest version (slv 2026.4.3.1005) adding Local Mode.
Previously, SLV was designed to operate as a management node controlling remote nodes. With this release, it is now possible to run SLV directly on the node logged into via ssh, enabling Local Mode to manage the node itself. Setup is completed simply by selecting Local Mode in the `slv onboard` wizard.
SLV Official Website: https://slv.dev/ja
Getting Started: https://slv.dev/ja/doc/general/getting-started/
Why Local Mode? — Eliminating a Hop of Complexity
Remote management is powerful when centrally operating multiple nodes. However, managing Solana validators and Solana RPC nodes involves a high cognitive load in itself. Adding a remote management configuration meant further increasing that cognitive load.
Local Mode eliminates this extra hop of complexity. You log into a node via ssh and run SLV directly on that node. Because the management target and the execution environment are the same, the configuration becomes simple and operations become intuitive.
In many cases, Solana node operation starts with a single unit. It is rare to suddenly start with remote management of multiple nodes, so starting with Local Mode is a more natural onboarding path.
From Local to Remote — Phased Migration Inheriting Settings
SLV's Local Mode also includes migration upon scaling in its design.
Environments built in Local Mode can be migrated to a remote management configuration as the project grows. A guided path is provided to smoothly scale up from direct management of a single node to batch management of multiple nodes utilizing Ansible, while inheriting your settings.
There is no need to design a large-scale configuration from the start. Begin with the single node in front of you and migrate to remote management when necessary. This phased growth path is SLV's design philosophy.
As a Migration Destination for solv Users — Inheriting the Predecessor's Design Philosophy
SLV's predecessor is solv, developed by Epics DAO. solv enjoyed deep-rooted popularity for its style of installing directly on a node for easy single-node operation, and is still in use today despite updates having ended.
SLV's Local Mode inherits this solv design philosophy — the intuitiveness of managing the logged-in node as is. While maintaining the familiar local execution style of solv, users can utilize all SLV features, such as natural language operation by AI agents, MCP-compatible toolsets, and tracking of the latest Solana clients.
Since updates to solv have ended, migration is necessary to continue keeping up with Solana network version upgrades. Proceeding alongside the SLV AI agent allows you to complete the migration process smoothly. We recommend migrating early to ensure you can continue riding on future updates.
AI Console — Natural Language Operation Management Even in Local Mode
The AI Console launched with `slv c` operates just as well in Local Mode. Since the AI agent does not run on the local computer but is executed by connecting to an external high-performance model (ChatGPT / Claude), it does not affect the node's specifications.
Deploying validators, upgrading, downgrading, switching identities, building Solana RPC nodes, and setting up Solana Geyser gRPC — all these can be executed simply by talking to the AI agent on the logged-in node. Upon startup, it automatically checks for the latest versions of agave, jito-solana, firedancer, yellowstone-grpc, etc., and displays update candidates.
The configuration where the AI agent resides on the node can be utilized not only for operation management but also for developing Solana apps. Everything from code generation to deployment can be completed on the node through conversation with the AI, and SLV AI will also handle it if environment migration becomes necessary.
Setup Completed in Minutes
There are two ways to start using Local Mode.
The easiest method is to select Local Mode in the `slv onboard` wizard. The wizard will guide you through connecting the AI provider, selecting the model, and configuring the skills to use, all at once. It is also possible to configure it by specifying `localhost` from the CLI, which is a convenient option for users accustomed to operating SLV.
With either method, the time required from installation to starting operations in natural language is just a few minutes.
YouTube Video "Deploy a Solana Validator with ZERO Coding — SLV AI Does It All": https://www.youtube.com/watch?v=RUvWiSE1pYQ
Supported Clients and Future Roadmap
Currently, SLV supports Agave, Jito Agave, Firedancer, and Jito Firedancer.
Future updates plan to support DoubleZero configurations and the AllNodes Client (a validator client with optimizations provided by AllNodes, operating on the AllNodes environment). Both are environments highly requested by many users, and we will proceed with supporting them sequentially, targeting this month through next month.
Combination with the ERPC Platform
By deploying an environment built with SLV onto the ERPC platform, you gain access right from the start to high-speed snapshot downloads within the platform, zero-distance communication with Solana validators, and configurations specifically tuned for Solana. Solana RPC, Solana Geyser gRPC, Solana Shredstream (Epic Shreds), bare-metal servers, VPS, and Global Storage are all integrated within the same platform.
ERPC Official Website: https://erpc.global/ja
Provided as Open Source
SLV continues to be provided as open source. Anyone involved in Solana operations — validator operation, Solana RPC building, app development — can use SLV's AI agent environment for free.
Thank you for always using SLV. We will continue development to provide an environment where everyone can leverage AI agents for their node operations.
SLV GitHub: https://github.com/validatorsDAO/slv
Inquiries
For inquiries regarding SLV and ERPC, please create a support ticket on the Validators DAO Official Discord.
Validators DAO Official Discord: https://discord.gg/C7ZQSrCkYR
Link List
SLV Official Website: https://slv.dev/ja
SLV Getting Started: https://slv.dev/ja/doc/general/getting-started/
SLV GitHub: https://github.com/validatorsDAO/slv
ERPC Official Website: https://erpc.global/ja
Epics DAO Official Website: https://epics.dev/ja
Validators DAO Official Discord: https://discord.gg/C7ZQSrCkYR
Previously, SLV was designed to operate as a management node controlling remote nodes. With this release, it is now possible to run SLV directly on the node logged into via ssh, enabling Local Mode to manage the node itself. Setup is completed simply by selecting Local Mode in the `slv onboard` wizard.
SLV Official Website: https://slv.dev/ja
Getting Started: https://slv.dev/ja/doc/general/getting-started/
Why Local Mode? — Eliminating a Hop of Complexity
Remote management is powerful when centrally operating multiple nodes. However, managing Solana validators and Solana RPC nodes involves a high cognitive load in itself. Adding a remote management configuration meant further increasing that cognitive load.
Local Mode eliminates this extra hop of complexity. You log into a node via ssh and run SLV directly on that node. Because the management target and the execution environment are the same, the configuration becomes simple and operations become intuitive.
In many cases, Solana node operation starts with a single unit. It is rare to suddenly start with remote management of multiple nodes, so starting with Local Mode is a more natural onboarding path.
From Local to Remote — Phased Migration Inheriting Settings
SLV's Local Mode also includes migration upon scaling in its design.
Environments built in Local Mode can be migrated to a remote management configuration as the project grows. A guided path is provided to smoothly scale up from direct management of a single node to batch management of multiple nodes utilizing Ansible, while inheriting your settings.
There is no need to design a large-scale configuration from the start. Begin with the single node in front of you and migrate to remote management when necessary. This phased growth path is SLV's design philosophy.
As a Migration Destination for solv Users — Inheriting the Predecessor's Design Philosophy
SLV's predecessor is solv, developed by Epics DAO. solv enjoyed deep-rooted popularity for its style of installing directly on a node for easy single-node operation, and is still in use today despite updates having ended.
SLV's Local Mode inherits this solv design philosophy — the intuitiveness of managing the logged-in node as is. While maintaining the familiar local execution style of solv, users can utilize all SLV features, such as natural language operation by AI agents, MCP-compatible toolsets, and tracking of the latest Solana clients.
Since updates to solv have ended, migration is necessary to continue keeping up with Solana network version upgrades. Proceeding alongside the SLV AI agent allows you to complete the migration process smoothly. We recommend migrating early to ensure you can continue riding on future updates.
AI Console — Natural Language Operation Management Even in Local Mode
The AI Console launched with `slv c` operates just as well in Local Mode. Since the AI agent does not run on the local computer but is executed by connecting to an external high-performance model (ChatGPT / Claude), it does not affect the node's specifications.
Deploying validators, upgrading, downgrading, switching identities, building Solana RPC nodes, and setting up Solana Geyser gRPC — all these can be executed simply by talking to the AI agent on the logged-in node. Upon startup, it automatically checks for the latest versions of agave, jito-solana, firedancer, yellowstone-grpc, etc., and displays update candidates.
The configuration where the AI agent resides on the node can be utilized not only for operation management but also for developing Solana apps. Everything from code generation to deployment can be completed on the node through conversation with the AI, and SLV AI will also handle it if environment migration becomes necessary.
Setup Completed in Minutes
There are two ways to start using Local Mode.
The easiest method is to select Local Mode in the `slv onboard` wizard. The wizard will guide you through connecting the AI provider, selecting the model, and configuring the skills to use, all at once. It is also possible to configure it by specifying `localhost` from the CLI, which is a convenient option for users accustomed to operating SLV.
With either method, the time required from installation to starting operations in natural language is just a few minutes.
YouTube Video "Deploy a Solana Validator with ZERO Coding — SLV AI Does It All": https://www.youtube.com/watch?v=RUvWiSE1pYQ
Supported Clients and Future Roadmap
Currently, SLV supports Agave, Jito Agave, Firedancer, and Jito Firedancer.
Future updates plan to support DoubleZero configurations and the AllNodes Client (a validator client with optimizations provided by AllNodes, operating on the AllNodes environment). Both are environments highly requested by many users, and we will proceed with supporting them sequentially, targeting this month through next month.
Combination with the ERPC Platform
By deploying an environment built with SLV onto the ERPC platform, you gain access right from the start to high-speed snapshot downloads within the platform, zero-distance communication with Solana validators, and configurations specifically tuned for Solana. Solana RPC, Solana Geyser gRPC, Solana Shredstream (Epic Shreds), bare-metal servers, VPS, and Global Storage are all integrated within the same platform.
ERPC Official Website: https://erpc.global/ja
Provided as Open Source
SLV continues to be provided as open source. Anyone involved in Solana operations — validator operation, Solana RPC building, app development — can use SLV's AI agent environment for free.
Thank you for always using SLV. We will continue development to provide an environment where everyone can leverage AI agents for their node operations.
SLV GitHub: https://github.com/validatorsDAO/slv
Inquiries
For inquiries regarding SLV and ERPC, please create a support ticket on the Validators DAO Official Discord.
Validators DAO Official Discord: https://discord.gg/C7ZQSrCkYR
Link List
SLV Official Website: https://slv.dev/ja
SLV Getting Started: https://slv.dev/ja/doc/general/getting-started/
SLV GitHub: https://github.com/validatorsDAO/slv
ERPC Official Website: https://erpc.global/ja
Epics DAO Official Website: https://epics.dev/ja
Validators DAO Official Discord: https://discord.gg/C7ZQSrCkYR
FAQ
What is SLV's Local Mode?
It is a feature that allows you to run SLV directly on the logged-in node and use an AI agent to manage and operate that node itself.
Why is it necessary to migrate from solv?
Since solv has ended its updates, migrating to SLV, which has equivalent features and AI management, is recommended to keep up with Solana updates.
Does using the AI Console affect the node's performance?
No, the AI agent relies on external models (ChatGPT/Claude) for processing, so there is no impact on the node's own resources.