Zero CELO gas balance is reported as a contract revert: "gas required exceeds allowance (0)"
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 50/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Tranquilo
- Stack tecnológico
- typescript
- Área
- cli
Línea de trabajo
Comienza con el comando celocli multisig:approve y reproduce el fallo usando un remitente autorizado sin CELO; después, inspecciona cómo se envuelve el error de estimación de gas antes de llegar a la CLI. Se considera terminado cuando la CLI identifica fondos de gas insuficientes en lugar de informar de un revert del contrato, conservando el error anidado para la depuración cuando sea posible.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.
- Lenguaje dominante
- TypeScript
- Estrellas
- 43
- Forks
- 36
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de celo-org/developer-tooling
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
celo-org/developer-tooling#793 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
celo-org/developer-tooling#786 ·
-
Dificultad 3/5 1-2 días Aptitud para principiantes 55/100
celo-org/developer-tooling#800 · 1 comentario ·
-
Bridge commands duplicate signer construction and miss new signer typesPosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abierto
Dificultad 4/5 3-5 días Aptitud para principiantes 68/100
celo-org/developer-tooling#794 ·
-
--ledgerLiveMode iterates the BIP-44 change index instead of the hardened account indexPosiblemente ocupada @Steve0x2a la tomó hace 45 días. Abiertobug celocli
Dificultad 3/5 1-2 días Aptitud para principiantes 78/100
celo-org/developer-tooling#789 ·
Todos los issues de celo-org/developer-tooling
Issues similares
-
[Bug]: Circular app layout navigation and help icons are shifted upward in the official demoAbiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
cloudscape-design/components#5184 ·
Los mantenedores suelen responder en 2 días
-
enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
JarX-Concepts/react-native-platform-components#130 ·
Los mantenedores suelen responder en 1 día
-
fix(api): optimize-for-web /preview outer catches miss asDecoderOutOfMemory on V8 OOM and SIGKILLAbiertoarea: backend bug priority: low
Dificultad 2/5 1-3 horas Aptitud para principiantes 83/100
snapotter-hq/SnapOtter#3773 ·
Los mantenedores suelen responder en 1 día
-
ai-driven-qa ux-audit
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
linagora/twake-contacts-frontend#386 ·
Los mantenedores suelen responder en 1 día
-
git: README should state plainly that without --repository every reachable repository is in scopeAbiertodocumentation server-git v2
Dificultad 1/5 1-3 horas Aptitud para principiantes 84/100
modelcontextprotocol/servers#5225 ·
Los mantenedores suelen responder en 1 día