Docs

Getting Started

Onboard your validator to Flowra: registration, installation, configuration, and verification.

This guide takes a working Solana validator to a Flowra-connected validator. The switch is a client swap plus configuration, comparable to moving between Agave and Jito-Solana; budget one maintenance window.

Prerequisites

  • A running mainnet or testnet validator on Agave or Jito-Solana. The Flowra client is built on the Jito-Solana codebase, so operators of either will find the setup familiar.
  • Hardware meeting standard Agave validator recommendations. Flowra adds no additional hardware requirements.
  • Outbound connectivity from your validator to your region's Block Engine and Relayer endpoints (gRPC/TLS). See Endpoints.
  • Your validator identity pubkey, for registration.

Onboarding steps

Send your identity pubkey and preferred region to info@flowra.wtf (a self-service registration portal is TBD ). You will receive confirmation along with the current endpoint values for your region.

Download or build the client Public repo TBD :

git clone <flowra-validator-repo>
cd flowra-validator
cargo build --release --bin agave-validator

The result is a drop-in agave-validator binary with Flowra's bundle pipeline built in.

Add the Flowra flags to your validator startup (full reference: Configuration):

export FLOWRA_PBP_CONFIG=/etc/flowra/flowra-pbp.toml   # optional policy file

agave-validator \
    # ... your existing flags ...
    --block-engine-url <REGION_BLOCK_ENGINE_URL> \
    --relayer-url <REGION_RELAYER_URL> \
    --tip-payment-program-pubkey <TIP_PAYMENT_PROGRAM> \
    --tip-distribution-program-pubkey <TIP_DISTRIBUTION_PROGRAM> \
    --merkle-root-upload-authority <MERKLE_AUTHORITY> \
    --commission-bps <YOUR_MEV_COMMISSION> \
    --bundle-cu-reserve-pct 15

Endpoint and program values are listed in Endpoints & addresses. All regional values must point at the same region.

Restart on the new binary during your normal procedure (ledger-safe restart, wait for your leader window to pass). Note that the Block Engine connection is established only after ledger replay completes.

Verify in the logs:

grep -iE "block_engine|bundle" validator.log | tail -50
# Expect: auth handshake complete, packet and bundle subscriptions active,
#         PBP policy pushed (if configured), tip crank healthy

Once your next leader slots pass, confirm bundles are landing and tips are accruing to your tip distribution account. A public dashboard for per-validator auction stats is TBD .

Rollback

Rolling back is the reverse of step 3: restart on your previous binary with your previous flags. There is no on-chain state to unwind; Flowra participation is purely an infrastructure-layer choice.

Next

Full flag & PBP reference
../configuration/
Regional endpoints
../endpoints/