Validator Multicast Connection

By connecting to DoubleZero I agree to the DoubleZero Terms of Service

Trading firms and businesses

If you operate a trading firm or business looking to subscribe to the feed, more details will be shared soon. Please register interest to get more information here.

If you are not already connected to DoubleZero please complete Setup, and Mainnet-Beta validator connection documentation.

If you are a validator who is already connected to DoubleZero you may continue this guide.

1. Client Configuration

Jito-Agave (v3.1.9+) and Harmonic (3.1.11+)

1. In your validator start script, add: --shred-receiver-address 233.84.178.1:7733

   You are able to send to Jito and the edge-solana-shreds group at the same time.

   example:

   #!/bin/bash
   export PATH="/home/sol/.local/share/solana/install/releases/v3.1.9-jito/bin:$PATH"
   BLOCK_ENGINE_URL=https://ny.mainnet.block-engine.jito.wtf
   RELAYER_URL=http://ny.mainnet.relayer.jito.wtf:8100
   SHRED_RECEIVER_ADDR=<JitoBlockEngineAddress>
   <...The rest of your config...>
   --shred-receiver-address 233.84.178.1:7733
   

2. Restart your validator.

3. Connect to the DoubleZero multicast group edge-solana-shreds as a publisher: doublezero connect ibrl && doublezero connect multicast --publish edge-solana-shreds

Frankendancer

1. In config.toml, add:

   [tiles.shred]
   additional_shred_destinations_leader = [ "233.84.178.1:7733", ]
   

2. Restart your validator.

3. Connect to the DoubleZero multicast group edge-solana-shreds as a publisher: doublezero connect ibrl && doublezero connect multicast --publish edge-solana-shreds

2. Confirm you're publishing leader shreds

Once you are connected you may check this dashboard to confirm you are publishing shreds. You will not see confirmation until after you have published leader shreds for at least one slot.

3. Validator Rewards

For each epoch where validators publish leader shreds, they will be proportionately rewarded for their contribution based on subscriptions. The specifics of this system will be announced, and detailed at a later date.

Troubleshooting

Not Publishing Leader Shreds:

The most common culprit in not transmitting shreds is client version:

You must be running Jito-Agave 3.1.9+, JitoBam 3.1.9+, Frankendancer, or Harmonic 3.1.11+. Other client versions will not work.

Retransmitting:

1. A common cause of shred retransmission is a simple config. You may have the flag enabled to send retransmit shreds in your startup script; you will need to disable it.

   The flag to remove in Jito-Agave is: --shred-retransmit-receiver-address.

2. Check the publisher dashboard and see if you have any retransmitted shreds. In the table, look at the No Retransmit Shreds column—a red X means you are retransmitting.

   epoch view

   Note that there are different time windows to view the publisher dashboard. If you see retransmit in the 2 epoch view, but have made a recent change, try switching to the recent slot view.

   

3. Find your client IP and look up your user in DoubleZero Data.

   

4. Click on Multicast to open your multicast view.

   The screenshot below shows: Retransmitting (undesirable) steady outbound traffic with no leader-slot pattern.

   

   The screenshot below shows: Healthy (publishing only leader shreds) outbound traffic in spikes, known as a sawtooth pattern, which line up with your leader slots.

   

The chart shows whether you are sending only leader shreds. Traffic spikes should line up with when you have a leader slot. When you have no leader slot there should be no traffic. If you are retransmitting, you will see a steady flow of traffic instead of slot-aligned spikes.