Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deafult denom doesn't guarantee the fee token to be whitelisted #645

Open
MrLutik opened this issue Mar 21, 2024 · 1 comment
Open

Deafult denom doesn't guarantee the fee token to be whitelisted #645

MrLutik opened this issue Mar 21, 2024 · 1 comment

Comments

@MrLutik
Copy link
Collaborator

MrLutik commented Mar 21, 2024

After network initialization with a default denom token I was expecting to be able to pay fees with it.

IN:

sekaid query tokens token-black-whites --output=json --home=/sekai | jq

OUT:

{
  "data": {
    "whitelisted": [
      "ukex"
    ],
    "blacklisted": [
      "frozen"
    ]
  }
}

So to whitelist the token I need UKEX.

The network was initialized with following commands:

sekaid init VALNODE --bech32-prefix test --chain-id testnet-1 --default-denom utest --home /sekai
sekaid keys add genesis --home /sekai --keyring-backend test
sekaid add-genesis-account genesis 300000000000000utest --home /sekai --keyring-backend test
sekaid gentx-claim --address genesis --moniker GENESIS --home /sekai --keyring-backend test

PROBLEM: If you initialized the network with a default token and never added any ukex you won't be able to perform any operations/txs.

@kiragpg
Copy link
Contributor

kiragpg commented Apr 18, 2024

This issue was resolved on latest release as well, can you check and close the ticket after confirmation @MrLutik

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants