Transaction inclusion latency (delay)

General
1

Hello Monad community.

I am running a Monad full node on a high-performance Hetzner server and performing tests on transaction submission latency.

The Setup and Observation

My application listens to new blocks via a WebSocket (WS) connection to my local node. Upon receiving a new block notification, it immediately submits a transaction.

  • Consistent Delay: A transaction submitted immediately after block N is consistently included in block N+3.

  • Minimal Software Latency: The internal latency from the time I receive the new block number until the transaction is submitted to my node is very low, approximately 20ms.

The Goal

I am looking for methods or configurations that could significantly increase the probability of transaction inclusion in the next block (N+1).

Actions Already Tested (Did Not Improve Inclusion Time)

  1. Fixed Gas Cost: Used a fixed gas cost to bypass the transaction simulation step on my node.

  2. High Fees: Set fixed, but very high, values for both max_fee_per_gas and max_priority_fee_per_gas.

Request for Guidance

Given the minimal internal latency, is this delay likely related to mempool prioritization logic or perhaps a specific node configuration parameter that could be optimized for submission speed?

Any guidance from experienced node operators or the core team is greatly appreciated.

Thank you :folded_hands: .

2 Likes