akash-network / akash-network/console

Missing SDL Validation - Non-uact denoms (uUSDC/uAKT) are incorrectly allowed in Wallet-Based Accounts

Open
#3,029 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
264
Forks
94
Avg merge
18h 49m
Merged PRs (30d)
297

Description

The Akash Console currently allows uusdc and uakt denoms in SDL for wallet-based accounts, even though only uact should be supported. This indicates a missing validation rule.

Expected Behavior

SDL validation should restrict denom to uact only

Any SDL using:
uusdc, uakt - should fail validation
Behavior should be consistent across all account types - managed wallet account (credit card verified account) and accounts created through keplr wallets

  placement:
    dcloud:
      pricing:
        hermes-bot:
          denom: uakt
          amount: 1000
      signedBy:
        anyOf:
          - akash1365yvmc4s7awdyj3n2sav7xfx76adc6dnmlx63


  placement:
    dcloud:
      pricing:
        hermes-bot:
          denom: ibc/170C677610AC31DF0904FFE09CD3B5C657492170E7E52372E48756B71E56F2F1
          amount: 1000
      signedBy:
        anyOf:
          - akash1365yvmc4s7awdyj3n2sav7xfx76adc6dnmlx63
        allOf: []

Image Image

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Locate the SDL validation entry point for pricing denoms and reproduce the issue with the provided uakt, uusdc, and ibc examples. Check validation for both managed wallet and Keplr-created accounts; done means non-uact denoms fail validation while uact remains accepted consistently.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.