Skip to content

Reproduce and fix wallet bank-send out-of-gas reports before v31 testnet #31

Description

@juno-ai-dev

Context

Multiple users report ordinary wallet transactions failing after the v30 upgrade. One concrete report is a Trust Wallet → Keplr JUNO bank send displaying an out of gas error. No transaction hash or gas wanted/used values are available yet, so this is not proven to share the already-fixed v30 feegrant wiring regression.

v31 currently proves a post-upgrade bank send succeeds in the interchaintest, but it does not reproduce common wallet-generated gas limits or exercise Trust Wallet/Keplr transaction construction.

Scope

  • Collect at least one failing tx hash (or raw signed tx / complete screenshot with gas wanted, gas used, code, and log).
  • Decode the failed transaction and identify wallet-provided gas limit, fee, fee payer/granter, message type, memo, and failure phase.
  • Reproduce the same transaction shape against v30 and the exact v31 candidate.
  • Test ordinary MsgSend with representative fixed wallet gas limits and simulation-derived limits.
  • Verify current Juno chain metadata/gas-price integration in Trust Wallet and Keplr; distinguish insufficient fee from actual gas exhaustion.
  • If chain-side, add a mutation-sensitive regression and minimal fix. If wallet-side, document the exact metadata/config change and safe temporary gas guidance.

Acceptance criteria

  • At least one real report is tied to authoritative tx evidence, or the issue explicitly records that only CheckTx/UI evidence exists.
  • Root cause is classified as chain execution, RPC simulation, wallet gas estimation, wallet fee pricing, or another specific layer.
  • Exact v31 candidate passes a signed ordinary bank send using the affected wallet transaction shape.
  • Trust Wallet and Keplr send flows are manually smoke-tested on the target testnet after upgrade.
  • Validator/operator guidance states whether any app.toml or minimum-gas-price change is required.
  • Release notes include any necessary wallet/relayer integration guidance.

Non-goals

  • Do not treat the v31 oversized-uint64 gas-limit guard as a fix for ordinary out-of-gas reports without reproduction.
  • Do not change consensus fee parameters or validator settings without evidence.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:anteAnte handler and transaction fee processingbugSomething isn't workingpriority:P0Release-blocking priorityv31Juno v31 release scope

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions