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: []

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