Investigate workaround for INSUFFICIENT_PAYER_BALANCE errors in modularized workflow

[IvanKavaldzhiev]

Mono code workflow inside web3 did have broader validations and sender's balance wasn't taken into account when transactions were simulated. Inside the modularized workflow, which utilizes hedera-app library, the same validations are conducted as in consensus nodes. This means sender's balance is taken into account.

Try to find a way to mitigate this issue inside modularized workflow, so that it doesn't throw this error.

[quiet-node]

Hey, I’m also encountering this issue with Mirror Node version 0.131.0 thought I would share it here for some extra context.

The problem occurs with eth_estimateGas, and only when using local-node (@2.37.1), MN@0.131.0, CN@0.63.0. However, it seems to work as expected on testnet (CN@62.6, MN@0.131.0)

When I run the following eth_estimateGas request with the following params:

{
    "data": "0x60806040526001600055600180556002805560405161001d9061005f565b604051809103906000f080158015610039573d6000803e3d6000fd5b50600380546001600160a01b0319166001600160a01b039290921691909117905561006b565b60a58061034f83390190565b6102d58061007a6000396000f3fe...",
    "from": "0x5e8C44D12d1828abFdc2c3C1858CE743D51Ed5fc"
}

It returns the gas estimate correctly on testnet. However, on local-node, it fails with INSUFFICIENT_PAYER_BALANCE, even though I can assure that the from address has a balance of 10 HBAR.

[bilyana-gospodinova]

@quiet-node, the issue that you are describing sounds different from the one that this ticket is about. It seems that the mirror node version is the same on testnet and on your local node, so this can't be a bug in the mirror node. Most probably there is a difference in the fee schedules configuration. Anyway, the contract deploy price has recently changed in the latest versions of hedera-app and respectively the CN, so I will suggest you to try the test with an account with a higher balance.

[quiet-node]

Hi @bilyana-gospodinova, thanks for the response.

Yes I’ve tried increasing the balance and it only seems to work when the balance exceeds 12 HBAR. However, the issue isn’t about bumping the balance or using accounts with more funds. The concern is that even when the balance is sufficient and the deployment fee is just a fraction of an HBAR, the requests are still rejected. That’s why it sounds like a bug to me.

Your explanation makes sense, and it might be more appropriate to open a ticket in the local-node repository.

[bilyana-gospodinova]

Hi @quiet-node, the deployment fees have recently changed like I mentioned. A contract deploy operation now starts at about 1$ (please refer to: https://docs.hedera.com/hedera/networks/mainnet/fees), so the deployment cost cannot be a fraction of an HBAR anymore. If needed, please ask our smart contracts team for more information about the updated fees.