Transactions are getting failed with INSUFFICIENT_TX_FEE

[anshuman-supraoracles]

Description

We are feeding pair details into a smart contract on hedera. All the txns we are pushing is having the calldata size <5kb. Most of the times the txns are getting executed perfectly but only certain times its getting failed due to INSUFFICIENT_TX_FEE error. Although both the accounts(relayer and txn initiator) are having sufficient balances.

We are using the dedicated relayer from Validation Cloud

These are the txns that got faied

https://hashscan.io/mainnet/transaction/1732151941.129055000
https://hashscan.io/mainnet/transaction/1732152145.106706521
https://hashscan.io/mainnet/transaction/1732152160.921207000
https://hashscan.io/mainnet/transaction/1732152177.426895000

You can check other successful txns in this contract

https://hashscan.io/mainnet/contract/0.0.4323024?pf=1&p=1&k=1732163002.082358000

Steps to reproduce

NA

Additional context

No response

Hedera network

mainnet

Version

Validation Cloud

Operating system

Linux

[simzzz]

I'm picking this up. You can assign me

[simzzz]

Hello, @anshuman-supraoracles. Would it be possible to provide the address of the logic contract that you passed in your contract's constructor so I can conduct further debugging? Thank you!

[simzzz]

Also, could you tell us what version of the relay are you using and with what configuration are you running it? And are there any modifications to the code?

[anshuman-supraoracles]

@simzzz Logic contract 0xdee317b28dcce292859bd82f517de2037cc46b98
We are using the relayer from Validation cloud

[simzzz]

It seems the issue might be related to a configuration variable called GAS_PRICE_PERCENTAGE_BUFFER. This variable adds a buffer to the estimated gas price to ensure transactions have sufficient fees to execute successfully.

Since you are using the Validation Cloud, it’s possible they might have an issue and need to increase the buffer, which could be causing the INSUFFICIENT_TX_FEE error. In our own implementation, this variable is set to 0, and we have not been able to reproduce the issue on our end. We will coordinate with the Validation Cloud team to address this configuration issue and work toward a resolution and keep you updated.