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

Fetching balances throws an error #218

Open
fadeev opened this issue Feb 10, 2025 · 2 comments
Open

Fetching balances throws an error #218

fadeev opened this issue Feb 10, 2025 · 2 comments
Labels
bug Something isn't working

Comments

@fadeev
Copy link
Member

fadeev commented Feb 10, 2025

npx hardhat balances
An unexpected error occurred:

Error: Network empty does not exist.
    at ZetaChainClient.getEndpoint (/Users/fadeev/github.com/zeta-chain/toolkit/packages/client/src/getEndpoint.ts:9:11)
    at /Users/fadeev/github.com/zeta-chain/toolkit/packages/client/src/getBalances.ts:180:32
    at Array.map (<anonymous>)
    at ZetaChainClient.getBalances (/Users/fadeev/github.com/zeta-chain/toolkit/packages/client/src/getBalances.ts:179:38)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async SimpleTaskDefinition.main [as action] (/Users/fadeev/github.com/zeta-chain/toolkit/packages/tasks/src/balances.ts:104:19)
    at async Environment._runTaskDefinition (/Users/fadeev/github.com/zeta-chain/toolkit/node_modules/hardhat/src/internal/core/runtime-environment.ts:351:14)
    at async Environment.run (/Users/fadeev/github.com/zeta-chain/toolkit/node_modules/hardhat/src/internal/core/runtime-environment.ts:184:14)
    at async main (/Users/fadeev/github.com/zeta-chain/toolkit/node_modules/hardhat/src/internal/cli/cli.ts:322:7)
@fadeev fadeev added the bug Something isn't working label Feb 10, 2025
@fadeev
Copy link
Member Author

fadeev commented Feb 10, 2025

Some supported chains have chain_name empty.

https://zetachain-athens.blockpi.network/lcd/v1/public/zeta-chain/observer/supportedChains

   {
      "chain_id": "18333",
      "chain_name": "empty",
      "network": "btc",
      "network_type": "testnet",
      "vm": "no_vm",
      "consensus": "bitcoin",
      "is_external": true,
      "cctx_gateway": "observers",
      "name": "btc_signet_testnet"
    },
    {
      "chain_id": "18334",
      "chain_name": "empty",
      "network": "btc",
      "network_type": "testnet",
      "vm": "no_vm",
      "consensus": "bitcoin",
      "is_external": true,
      "cctx_gateway": "observers",
      "name": "btc_testnet4"
    },
    {
      "chain_id": "421614",
      "chain_name": "empty",
      "network": "arbitrum",
      "network_type": "testnet",
      "vm": "evm",
      "consensus": "arbitrum_nitro",
      "is_external": true,
      "cctx_gateway": "observers",
      "name": "arbitrum_sepolia"
    },
    {
      "chain_id": "43113",
      "chain_name": "empty",
      "network": "avalanche",
      "network_type": "testnet",
      "vm": "evm",
      "consensus": "snowman",
      "is_external": true,
      "cctx_gateway": "observers",
      "name": "avalanche_testnet"
    }

@fadeev
Copy link
Member Author

fadeev commented Feb 10, 2025

@CharlieMc0 @lumtis what's the difference between name and chain_name? The toolkit was relying in chain_name, and the empty values broke some of the functionality.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant