Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Transactions are getting failed with INSUFFICIENT_TX_FEE #3283

Open
anshuman-supraoracles opened this issue Nov 21, 2024 · 4 comments
Open
Assignees
Labels
bug Something isn't working

Comments

@anshuman-supraoracles
Copy link

anshuman-supraoracles commented Nov 21, 2024

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

@anshuman-supraoracles anshuman-supraoracles added the bug Something isn't working label Nov 21, 2024
@Nana-EC Nana-EC moved this from Backlog to Sprint Backlog in Smart Contract Sprint Board Nov 21, 2024
@simzzz
Copy link
Contributor

simzzz commented Dec 6, 2024

I'm picking this up. You can assign me

@Nana-EC Nana-EC moved this from Sprint Backlog to Tasks In Progress in Smart Contract Sprint Board Dec 6, 2024
@simzzz
Copy link
Contributor

simzzz commented Dec 10, 2024

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
Copy link
Contributor

simzzz commented Dec 11, 2024

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
Copy link
Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Tasks In Progress
Development

No branches or pull requests

2 participants