jito-foundation / jito-relayer Goto Github PK

Hello, add the --log flag to be able to write to the specified file, if possible, thx.

Documentation: https://docs.solana.com/proposals/transactions-v2

Issue:

• Transactions can now reference on-chain lookup tables which they load addresses from.
• The relayer doesn't currently know how to load these addresses, which means it may miss forwarding transactions.

Solution:

• The relayer should be able to load addresses from on-chain lookup tables and update them on-the-fly.
• The relayer should use these cached on-chain lookup tables to determine if TxV2 packets should be forwarded.

Add a signal handler to handle Sigint (ctrl + c) for clean exit.

Many operators are reporting RPC timeout on lookup table. Either remove this call (unused) or make the RPC client timeout longer

The relayer should not be able to dos the validator or the block engine. A maximum throughput parameter should be added in the grpc interface and implemented in the relayer for all grpc connections.

Currently, the leader schedule cache attempts to update every 10 seconds. This needs to be changed to update once per epoch, with appropriate error handling and retry.

• How to setup your relayer?
• What RPC configuration needs to happen?
• What is the best location in relation to a block engine?
• What's the best port configuration for your relayer? When public vs. localhost?
• When whitelisted vs. not?
• Why does the performance of the RPC matter? Need to keep track of time.

A whitelist of trusted validators should be added to the relayer to only accept specified connections.

• ifconfig.me can sometimes return a relayers IP address as IPv6
• The validator uses solana_net_utils::get_public_ip_addr to find the validator's IP address. This runs a TCP connection to an entrypoint on the network and returns a response with the validator's IP.
• This can be leveraged in the relayer instead of using ifconfig.me or other options.

When a validator is running their own relayer, keeping track of what the current slot is isn't as important. This means that the validator can forward all packets to their own validator, independent of network time.

The connection to the block engine is incomplete. There is a draft PR from branch jl/block_engine, which contains a refactor of relayer.

After the refactor, Relayer contains instances of a router struct and a block_engine struct. The router forwards packets (with potential delay) to connected validators based on the leader schedule, and is code complete. The block_engine will forward any transactions that touch accounts in it's aoi hashset to the block engine through the grpc client.

The block_engine struct contains a blocking grpc client , which has been started, but it is incomplete. The start_bi_directional_packet_stream function has not been successfully implemented . This function needs to be implemented in the client, as well as the subscribe_aoi function to correctly update the hashset containing accounts of interest.

The block_engine also needs to implement the stream_batch_list function to filter packet batches by aoi and send to the block engine using the client.

Once a connection is established, the block_engine should update it's delta field to delay the forwarding of packets to the validator. Likewise, if the block engine is disconnected, the delta value should be returned to zero. The set value needs to come from a command line input.

Currently, if a validator attempts to subscribe to bundles from the relayer, it will panic. It would be better to just open the connection and not use it.

See neodyme report

Changes to the Solana SDK after 1.10.25 break the interface in the relayer. Specifically access to packet data is now through a method.

The relayer should be updated to accommodate these changes.

Also, the mutex on the load balancer can be removed at the same time, since it touches a lot of the same code.

Is there a way to run local relayer without specifying a block-engine?
If I don't specify the relay exit with a panic (when getting a packet)

thread 'forwarder_thread_0' panicked at transaction-relayer/src/forwarder.rs:92:45:
error sending packet batch to block engine handler

Att: @buffalu

Open source projects usually have a LICENSE file to state the license under which it is released. Please add the LICENSE file so that we know which license it is. Since it contains code from Solana Labs, I assumed it's intended to be the Apache 2 license, same as Solana?

Building with:
cargo b --release

Error output: https://gist.githubusercontent.com/bartenbach/16b44c09980a369433163e651fd901cb/raw/8c5880c87e13dfd9aad4bcd080aa45aed333b9ed/error.log