For Validators

The BAM Validator extends the Jito-Solana client to interface with external BAM schedulers via gRPC, receiving pre-sequenced transaction bundles and executing them in FIFO order with respect to account locks. This design maintains network security while enabling sophisticated transaction ordering strategies.

Running a validator

The validator can be deployed with all configuration options the same as the Jito-Solana client; with two mandatory additions:

--bam-url:Needed to connect to the BAM Node. Described below.
--enable-rpc-transaction-history:Needed to confirm fee payment amounts for rooted blocks

The bam_url can also be updated via the Admin RPC during runtime with the following command:

echo ' {"jsonrpc":"2.0","id":1,"method":"setBamUrl","params":["{JSS_GRPC_URL}"]}' | socat - UNIX-CONNECT:admin.rpc

Note: the first parameter can either be a valid url string or null; if one wishes to disable BAM on the validator.

The validator code is currently in audit by Ottersec and Anza, with audits slated to finish mid-July. If you are interested in running the validator in testnet or mainnet, please fill out the form here.

Fill out the form

Supported Regions

Please connect to a region / cluster that your validator is closest to.

TESTNET


ny.testnet.bam.jito.wtf
slc.testnet.bam.jito.wtf

MAINNET


ny.mainnet.bam.jito.wtf
amsterdam.mainnet.bam.jito.wtf
frankfurt.mainnet.bam.jito.wtf
slc.mainnet.bam.jito.wtf