Rakurai Validator Operators
Running Rakurai turns one revenue stream into four. Alongside block rewards, a Rakurai validator earns tips from traders competing to land, prepaid subscriptions from services consuming its post-pack stream, and a share of the backrun profit those services make — each metered in its own on-chain account.
Rakurai is a fork of jito-solana running the Rakurai scheduler library, so it replaces your client rather than adding a sidecar. Rakurai currently charges no fee for running it, and you choose how much of the block reward to share with stakers through a Merkle-root-based distribution you can hand to Rakurai at 0% distribution fee.
Operationally: build the client, create an on-chain activation account, and keep the scheduler binary in step with each release. Those, plus Geyser compatibility, are what the guides below cover.
Audience: Solana validator operators who want to run the Rakurai client and maximize block rewards.
1. Where to start
| If you are… | Go to |
|---|---|
| Setting up Rakurai for the first time | Setup and build |
| Already running Rakurai and moving to a new release | Node upgrade |
| Deciding whether to share block rewards with stakers | Block reward distribution |
| Running a Geyser plugin alongside Rakurai | Geyser |
| Verifying a downloaded scheduler binary | Binary attestation |
- Running a Geyser plugin that was not rebuilt against the Rakurai crates — Geyser.
- Running a scheduler binary from a different release than the client — Node upgrade.
- Losing
LD_LIBRARY_PATHor XDP capabilities after a rebuild — Setup and build.
2. Guides
| Guide | Description |
|---|---|
| Setup and build | Prerequisites, activation account, scheduler binary, build, and CLI args |
| Node Upgrade | Fast upgrade path for existing Rakurai operators |
| Block Reward Distribution | Share block rewards with stakers via the RCA, and customize allocations |
| Geyser | Build and run Geyser plugins compatible with Rakurai |
| Binary attestation | Verify scheduler binary with GitHub artifact attestations |
| Spark geyser | Prebuilt sample Geyser plugin (ZeroMQ forwarding) |
3. What a Rakurai validator earns
Four separate revenue streams reach a Rakurai validator, each with its own on-chain account. The full model is in Reward Distribution.
| Stream | Account | Where it comes from |
|---|---|---|
| Block rewards | RCA | Leader slots; the staker share is distributed after the epoch |
| Tips | TCA | Traders and landing services tipping to get prioritized |
| Post-pack access | PSA | Prepaid subscriptions from post-pack consumers, priced from your stake |
| Backrun share | MCA | A share of profit searchers make from your post-pack stream |
Commission on block rewards is set per validator in the Rakurai Activation Account with rakurai-activation.
4. Related integrator docs
You do not need these to run a node, but they explain the traffic your validator receives:
- TIN - MEV Services — hub for bundles, tips, and post-pack
- Setup guide — block engine discovery, gRPC roles, onboarding
- Tips — how tips and virtual priority work on Rakurai nodes
- Post-pack confirmations — Admin RPC for endpoints; PSA then MCA
- P2C Subscription CLI — top up the PSA prepaid subscription (
rakurai-p2c) - Partner Tip and MevShare Revenue Settlement CLI — partner TCA / MCA inspect and settle (
rakurai-revshare)