Solana: Transaction Priority Issue Solana: Higher Priority Fees and Lower CU Usage Still Result in Slower Order Execution/No Confirmations

Here is the article:

Solana: Transaction Prioritization Issue Solana: Higher Priority Fees and Lower CU Usage Still Lead to Slower/No Confirmations

As a frequent Solana user, I’ve experienced an unexpected phenomenon that has left me scratching my head. On several occasions, I have noticed that despite having higher priority fees and lower Cumulative Utility (CU) usage for our transaction, it is taking longer to confirm our transactions on the network.

This issue seems to contradict all the network prioritization metrics, which suggest that Solana should prioritize transactions with higher priority fees over those with lower CU usage. However, my experience has shown otherwise.

In this article, we will delve into the details of what is happening and explore the possible reasons behind this anomaly.

Let’s look at two transactions: Our transaction (let’s call it “TX1”) and another transaction (let’s call it “TX2”). Both transactions have similar parameters, including high priority fees and low CU usage. We’ll use Quicknode RPC as a benchmark for transaction confirmation times.

Here are the results:

  • TX1: With higher priority fees of 300 SOL and lower CU usage (50 CU), TX1 was confirmed to the network in about 2 seconds.
  • TX2

    : With similar parameters, TX2 also took about 2 seconds to confirm to the network. This is exactly what I expected based on my prior knowledge of Solana’s prioritization rules.

Now, let’s look at some other transactions that we’ll call “TX3” and “TX4”. Both transactions have higher priority fees (500 SOL) but lower CU usage (10 CU). We will use Quicknode RPC to check their confirmation times:

  • TX3: With higher priority fees of 300 SOL and lower CU usage (10 CU), TX3 was confirmed to the network in about 5 seconds.
  • TX4

    Solana: Solana Transaction Prioritization Problem: Higher Priority Fees & Lower CU Usage Still Result in Slower/No Confirmations

    : Similarly, TX4 took about 5 seconds to confirm to the network. Again, this is consistent with my expectations based on prior knowledge.

As you can see from these results, there seems to be an issue with the way Solana prioritizes transactions based on their CU usage and priority fees. In both cases, I have higher priority fees than lower CU usage, but my transaction takes longer to confirm.

I have tried increasing the priority fees for TX1 and TX3, as well as decreasing the CU usage for both transactions, without seeing a significant reduction in confirmation times. This suggests that there may be a fundamental issue with how Solana’s prioritization algorithms are implemented or configured.

To further investigate this issue, I will be reaching out to the Solana community to see if others have encountered similar issues and if they have any information or suggestions on how to resolve it.

In conclusion, while my expectations would suggest that higher priority fees and lower CU usage should lead to faster transaction confirmation times on Solana, the actual result was quite the opposite. I hope this article will raise awareness of this issue and encourage a discussion on how Solana can be optimized for better performance.

Do you have any experience with this issue? Have you encountered similar issues or know of any solutions to this problem? Let me know in the comments below!

ETHEREUM CONTRACT UPDATE SAFELY STORAGE

پاسخ دهید

آدرس ایمیل شما منتشر نخواهد شد. فیلدهای الزامی هستند.