Practical overview
When it fits
Use it when a Solana validator needs to publish selected updates to a message bus for an RPC service or downstream data-processing workflow.
Who it is for
- Teams building or operating Solana RPC infrastructure.
- Developers creating message consumers or custom indexes from validator updates.
- Solana validator operators who need to route selected account or transaction data to a message bus.
Documented uses
- Stream selected Solana validator data to a message bus.
- Feed transaction, account, block and slot updates to downstream consumers in the Plerkle Serialization format.
- Use validator-side ingestion as a component in an RPC service or bespoke indexing workflow.
- Process Solana account snapshots through the described ETL component.
Requirements & limits
The source repository is public and identifies the license as AGPL-3.0.
- Solana 1.10.41 or later is required, and calling components must support V2 GeyserPlugin types.
- The library is configured through the validator's Geyser plugin configuration; the process also needs messenger environment configuration.
- Redis appears as a documented messenger configuration example, while the design aims to support different message-bus technologies.
- Producer settings let operators choose buffering and confirmation behavior; the README notes that Processed updates can rarely be reverted, while higher confirmation levels take longer.
- Consumers must configure delivery behavior and a distinct consumer ID when scaling across instances to avoid duplicated messages.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Build the plugin library locally
Compile the Rust project into a shared library for a Linux or macOS validator setup.
Before you start
- Rust/Cargo build environment
- Linux or macOS
Steps
From the repository, run the command below for a debug build or the command below for a release build.
cargo buildcargo build --releaseOn Linux, locate
libplerkle.soin the target folder; on macOS, look forlibplerkle.dylib.Use the resulting library path in the validator's Geyser plugin configuration as the
libpathvalue.
Expected outcome
A locally built plugin library and a configuration path that identifies it to the validator.
Guide limitations
- This covers building and identifying the library, not running a validator or confirming a deployment.
- The README requires Solana 1.10.41 or later and V2 GeyserPlugin support from calling components.
- The README's configuration example is explicitly labeled as an example, not a definitive configuration.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 14 October 2026
- Original website title
- metaplex-foundation/digital-asset-validator-plugin · Official homepage title · retained in its source language

