Zero CELO gas balance is reported as a contract revert: "gas required exceeds allowance (0)"
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 50/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- cli
Research direction
Start with the celocli multisig:approve command and reproduce the failure using an authorized sender with zero CELO, then inspect how the gas-estimation error is wrapped before reaching the CLI. Done means the CLI identifies insufficient gas funds instead of reporting a contract revert, while preserving the nested error for debugging where possible.
Written by the indexing model from the issue text.
Description
Package
@celo/celocli9.0.1viem2.55.11 (dependency bundled by celocli)
Environment
- Celo Mainnet via
https://forno.celo.org - macOS on Apple Silicon
- Ledger signer (the issue appears to be independent of the signer type)
Command
celocli multisig:approve \
--for <multisig> \
--tx <transaction-id> \
--from <owner-with-zero-CELO-balance> \
--useLedger \
--node https://forno.celo.org
Describe the bug
When the sending account has a zero native CELO balance and therefore cannot pay gas, celocli reports the gas-estimation failure as a contract execution revert:
Sending Transaction: multisig: approving transaction ... failed:
Execution reverted with reason: gas required exceeds allowance (0).
ContractFunctionExecutionError: Execution reverted with reason:
gas required exceeds allowance (0).
This is misleading because the contract call itself does not revert. The account simply has no CELO with which to pay transaction fees.
In the observed case:
- the sender's native CELO balance was exactly
0; - all celocli multisig checks passed;
confirmations(transactionId, sender)remainedfalse, confirming that nothing was submitted;- a read-only trace of the same
confirmTransactioncall succeeded; - the trace estimated approximately 211,260 gas;
- funding the sender is the required remedy.
The message led us to investigate the multisig transaction and contract logic, even though neither was the source of the failure.
Expected behavior
celocli should identify this as an insufficient gas-funds error and provide an actionable message, for example:
The sender does not have enough CELO to pay transaction fees.
Sender balance: 0 CELO.
Fund the sender or select a supported --gasCurrency with sufficient balance.
It should not describe this condition as an execution revert.
Actual behavior
The underlying RPC text:
gas required exceeds allowance (0)
is wrapped as EstimateGasExecutionError, ExecutionRevertedError, TransactionExecutionError, and finally ContractFunctionExecutionError, resulting in the incorrect user-facing statement that contract execution reverted.
Suggested fix
Before sending or estimating a transaction, celocli could:
- retrieve the sender's native balance (or selected gas-currency balance);
- compare it with the estimated/upfront fee requirement where possible; and
- fail with a dedicated insufficient-gas-funds message.
Alternatively, the transaction error handler could recognize node errors matching gas required exceeds allowance (<amount>) during gas estimation and translate them into an insufficient-funds error rather than an execution revert.
The exact string may originate from the RPC client and the incorrect classification may occur in viem, but celocli should still present an actionable CLI error. Preserving the original nested error for debugging would be useful.
Reproduction outline
- Use an account that is authorized to perform a transaction but has
0CELO. - Run a celocli write command using that account as
--from. - Observe
Execution reverted with reason: gas required exceeds allowance (0)during gas estimation. - Simulate/trace the contract call independently and observe that it succeeds.
- Fund the sender with enough CELO for gas and retry.
- Dominant language
- TypeScript
- Stars
- 43
- Forks
- 36
- Avg merge
- 1h 35m
- Merged PRs (30d)
- 3
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from celo-org/developer-tooling
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
celo-org/developer-tooling#793 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
celo-org/developer-tooling#786 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
celo-org/developer-tooling#800 · 1 comment ·
-
Bridge commands duplicate signer construction and miss new signer typesPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 4/5 3-5 days Newbie friendliness 68/100
celo-org/developer-tooling#794 ·
-
--ledgerLiveMode iterates the BIP-44 change index instead of the hardened account indexPossibly taken @Steve0x2a claimed this 69 days ago. Openbug celocli
Difficulty 3/5 1-2 days Newbie friendliness 78/100
celo-org/developer-tooling#789 ·
All issues in celo-org/developer-tooling
Similar issues
-
ready-for-ai
Difficulty 1/5 Under an hour Newbie friendliness 88/100
umbraco/Umbraco-CMS-MCP-Dev#647 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
HelloAOLab/seed-bible#2173 ·
Maintainers usually reply within 1 day
-
enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
hocinehacherouf/liberarr#77 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
LibreChat-AI/LibreChat#18225 ·
Maintainers usually reply within 1 day
-
b-ber/build/epub b-ber/themes
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
triplecanopy/b-ber#790 ·
Maintainers usually reply within 1 day