validatorsdao/slv/slv-rpc

SLV RPC Skill

Ansible playbooks and Jinja2 templates for deploying and managing Solana RPC nodes (mainnet, testnet, devnet).

Supported RPC Types

Directory Structure

ansible/
  mainnet-rpc/   — Mainnet RPC playbooks
  testnet-rpc/   — Testnet RPC playbooks
  devnet-rpc/    — Devnet RPC playbooks
  cmn/           — Shared common playbooks
jinja/
  mainnet-rpc/   — Mainnet Jinja2 templates
  testnet-rpc/   — Testnet Jinja2 templates
  devnet-rpc/    — Devnet Jinja2 templates
  cmn/           — Shared templates

Benchmarking Notes

Planned CLI shape

A natural future command shape is:

slv check geyserbench <options>

This would mirror the existing slv check grpc / slv check shreds style by passing arguments through to the installed benchmark binary.

geyserbench config generation

For shredstream and grpc benchmark flows, the agent should be able to generate config.toml from:

• benchmark type
• two endpoint URLs
• ERPC API key from ~/.slv/api.yml

If ~/.slv/api.yml does not contain the required ERPC API key, instruct the user to get a free key and configure it first.

Example config:

[config]
region = "frankfurt"
erpc_url = "https://edge.erpc.global"
erpc_api_key = "api-key"
transactions = 10000
account = "pAMMBay6oceH9fJKBRHGP5D4bD4sWpmSwMn52FMfXEA"
commitment = "processed"
 
[[endpoint]]
name = "http://shreds-fra6-1.erpc.global"
url = "http://shreds-fra6-1.erpc.global"
kind = "shredstream"
 
[[endpoint]]
name = "http://shreds-turbo-fra-1.erpc.global"
url = "http://shreds-turbo-fra-1.erpc.global"
kind = "shredstream"

For gRPC benchmarks, use the same structure but set the endpoint kind to the appropriate gRPC-compatible type.

CLI Command ↔ Playbook Mapping

The slv r CLI commands map directly to these playbooks. {net} = mainnet-rpc, testnet-rpc, or devnet-rpc.

All Playbooks

Mainnet RPC (mainnet-rpc/)

Testnet RPC (testnet-rpc/)

Devnet RPC (devnet-rpc/)

Shared Common (cmn/)

Key Variables (extra_vars)

Geyser Plugin Sources

Both plugins are built from source (no binary downloads):

• Yellowstone gRPC: https://github.com/rpcpool/yellowstone-grpc
• Richat: https://github.com/lamports-dev/richat

Yellowstone is the default plugin of init.yml. Richat is chosen with geyser_plugin: richat in the inventory, but richat has no release for agave 4.3 or later yet: init.yml stops, before it changes anything, on a node set to run such an agave. The Richat playbooks stay for when a release exists. A node that ran Richat gets richat.service stopped and disabled when it is initialised with Yellowstone, so the two never share port 10000.

Usage

ansible-playbook -i inventory mainnet-rpc/init.yml \
  -e '{"rpc_type":"Index RPC","agave_version":"4.3.2","snapshot_url":"https://..."}'

No versions.yml required — all variables can be passed via extra_vars.

Interactive Deployment Flow

See AGENT.md for the full step-by-step flow and examples/inventory.yml for output format.

Required Variables