Skip to content

Latest commit

 

History

History
79 lines (44 loc) · 4.05 KB

faqs.md

File metadata and controls

79 lines (44 loc) · 4.05 KB
Raw

❓ FAQs

Creating and Managing FT with CLI

What if the account's non-zero balance will be removed from the whitelist?

If an account's non-zero balance is removed from the whitelist, the account will still be able to spend any tokens it has received. However, if you try to send new tokens to this account, the transaction will fail.

Creating and Managing NFT with CLI

Can a token be always burnt by an owner?

No, when a token is frozen, it cannot be burnt. Also, burning feature needs to be enabled on NFT class id level.

In order to burn a token, does burning feature always need to be enabled?

In general yes. However, an issuer of a token, can always burn it (while they own it), regardless of the feature setting.

Can all tokens within an NFT class be frozen/unfrozen at once?

No. There's no single command allowing to achieve that. It can, though, be done programmatically (for example, by utilizing the output returned by cored q nft nfts --class-id=$NFT_CLASS_ID --node=$RPC_URL --chain-id=$CHAIN_ID command).

Others

How to point cored to a specific network?

By default, cored binary points to the local node(localhost:26657).

To point it to a specific node you should use two flags - --node and --chain-id.

For example status for the specific node can be retrieved this way:

cored status --node={NODE_URL_WITH_PORT} --chain-id={CHAIN_ID}

NODE_URL_WITH_PORT and CHAIN_ID can be found at network variables page

How to fix account not found error?

If you see the next message:

Error: rpc error:
  code = NotFound desc = rpc error:
    code = NotFound desc = account testcore1q07ldrjnr8xtsy3rz82yxqcdrffu3uw3daslrw not found:
      key not found

Two reasons might cause this issue:

  1. Your account probably has zero balance, and it is not visible on the network. You should fund it before using it.
  2. RPC node you used to send the request is not fully synced, use another RPC node or wait for sync completion.

How to fix key not found error?

If you see the next message:

Error: testcore1f2dyj8dhdv62ytrkuvn832ezzjdcpg2jhrtzvy.info: key not found

Probably, your RPC_URL and/or chain-id belong to different networks. Also, this error often occurs when you have added your account into a specific keyring (i.e. --keyring-backend=test) and you forget to specify that keyring in CLI command.

Useful Links

Websites

Coreum Front Page

Github

Communication

Discord Validators channel