Practical overview
When it fits
Use it as a parsing layer in a Rust service when you already have, or are arranging, an appropriate Solana input source and need DEX events for downstream processing.
Who it is for
- Rust developers building Solana DEX indexers or stream processors.
- Teams adding parsed DEX events to monitoring, trading or copy-trading data pipelines.
- Developers who need to filter or choose ordering behavior for parsed event output.
Documented uses
- Decode supported DEX activity from transaction, account or streaming inputs into typed events.
- Filter subscriptions by protocol and event type before downstream processing.
- Choose between Borsh and zero-copy parsing backends.
- Select an event-ordering mode to suit a pipeline's latency and ordering needs.
Requirements & limits
The repository is public and MIT-licensed. The README documents both a crates.io dependency and a local repository path dependency.
- The SDK is a parser core; applications remain responsible for downstream storage, APIs or actions.
- The README lists Yellowstone gRPC, Jito ShredStream, RPC transactions and account data as input paths.
- The repository names support for PumpFun, PumpSwap, Raydium, Meteora and Orca protocols.
- The default Borsh backend is described as maintainability-oriented, while zero-copy is available for latency-sensitive paths.
- Unordered, MicroBatch, StreamingOrdered and Ordered modes offer different latency and ordering behavior.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Add Sol Parser SDK to a Rust project
Set up the documented crate dependency and choose the Borsh or zero-copy parser backend.
Before you start
- A Rust project that uses Cargo.
- For local-path installation, a project directory and a cloned SDK repository.
Steps
Add sol-parser-sdk = "0.7.12" to the project's Cargo.toml for the crates.io dependency.
Alternatively, clone the repository and add a path dependency in Cargo.toml.
Keep the default configuration for the Borsh parser, or disable default features and enable parse-zero-copy for the zero-copy parser.
Expected outcome
The Rust project has a dependency declaration for the selected parser backend.
Guide limitations
- This setup guide does not cover building or running an application that consumes parsed events.
- The documented backend options do not specify detailed configuration or event-coverage differences.
Subscribe to filtered Yellowstone DEX events
Configure the README's Rust example to subscribe to selected protocol and event types and consume the resulting events.
Before you start
- A Rust project with Sol Parser SDK and its documented async runtime usage.
- A Yellowstone gRPC endpoint accessible to the application.
Steps
Create a YellowstoneGrpc client with the endpoint and default or custom ClientConfig.
Select protocols and construct transaction and account filters for them.
Create an EventTypeFilter containing the event types the application needs.
Call subscribe_dex_events with the filters, then consume events from the returned queue.
Expected outcome
The example provides a filtered event queue for application-side processing.
Guide limitations
- The example's public endpoint is illustrative; the guide does not establish availability or suitability of any endpoint.
- Ordering modes provide different latency and ordering behavior, and ordered output cannot guarantee upstream completeness.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 13 October 2026
- Original website title
- 0xfnzero/sol-parser-sdk · Official homepage title · retained in its source language