Skip to main content

Connection Issues

HashPilot not appearing in editor

Symptoms: MCP tools not available, server not listed Solutions:
  1. Verify your config file is in the correct location
  2. Check JSON syntax is valid (no trailing commas)
  3. Restart your editor completely
  4. Check if npx hashpilot runs successfully in terminal

”Server disconnected” or timeout errors

Solutions:
  1. Check your internet connection
  2. Verify Hedera network is operational at status.hedera.com
  3. Try switching to a different network (testnet → mainnet)

Authentication Errors

INVALID_ACCOUNT_ID

Cause: Account ID format is incorrect Solution: Use format 0.0.12345 (realm.shard.num)

INVALID_SIGNATURE or KEY_PREFIX_MISMATCH

Cause: The key does not belong to the account, or a raw hex key was read as the wrong curve. HashPilot accepts both formats:
  • DER-encoded hex (starts with 302e... or 3030...): the curve is encoded in the key, nothing else to configure.
  • Raw 64-character hex (with or without 0x): the bytes do not say which curve they belong to. HashPilot assumes ECDSA, which is what the Hedera Portal issues by default. For an ED25519 account, set HEDERA_OPERATOR_KEY_TYPE=ed25519.
On startup HashPilot fetches the operator account from the Mirror Node and compares the derived public key. If they differ it tries the other curve, and if that also fails it refuses to start with a message naming both keys, so a mismatch shows up immediately instead of as INVALID_SIGNATURE later.

INSUFFICIENT_PAYER_BALANCE

Cause: Account doesn’t have enough HBAR for transaction fees Solutions:
  1. Check balance: "Check balance of 0.0.12345"
  2. Fund from Hedera Portal (testnet)
  3. Transfer HBAR from another account

RAG / Documentation Errors

”openaiApiKey is required”

Cause: OpenAI API key not configured Solution: Add OPENAI_API_KEY to your MCP config:

Empty search results

Cause: Query too specific or ChromaDB not accessible Solutions:
  1. Try broader search terms
  2. Ask for health_check with verbose: true; the services.chromadb entry shows the index URL and whether its heartbeat succeeded
  3. Verify OpenAI API key is valid
  4. If you set CHROMA_URL, check that your own server is running and indexed (see Self-hosting)

Token Operations

TOKEN_NOT_ASSOCIATED_TO_ACCOUNT

Cause: Account must associate with token before receiving it Solution: Associate first, then transfer:

TOKEN_HAS_NO_SUPPLY_KEY

Cause: Trying to mint/burn tokens without supply key Solution: When creating token, include supply key:

Smart Contract Issues

CONTRACT_REVERT_EXECUTED

Cause: Contract execution failed (reverted) Solutions:
  1. Check function parameters match expected types
  2. Verify account has sufficient balance
  3. Review contract require() conditions
  4. Use error_explain tool for details

Gas estimation failed

Solutions:
  1. Increase gas limit manually
  2. Check if function exists in ABI
  3. Verify contract is deployed on target network

Verification fails or previewnet cannot be verified

Cause: HashScan reads verification from Sourcify, which supports mainnet (chain 295) and testnet (chain 296) only. Verification also fails when the source or compiler settings differ from what produced the deployed bytecode. Solutions:
  1. Verify on testnet or mainnet; previewnet contracts cannot be verified
  2. Pass the exact source file and contract name to verify_contract
  3. For Hardhat projects ask for hardhat_contract verify; it locates the build-info file and lists the npx hardhat verify and verify.sourcify.dev alternatives
  4. For Foundry run forge verify-contract --verifier sourcify --chain 296 <address> src/Contract.sol:Contract

”forge: command not found” or Hardhat errors on init

Cause: The Foundry tools shell out to forge, cast and anvil; the Hardhat tools run npm install in the project. Solutions:
  1. Install Foundry with foundryup (HashPilot also looks in ~/.foundry/bin)
  2. Check that npm is on the PATH of the process that launched your editor
  3. Pass an absolute directory for every project operation

Network Issues

Network not reachable

Solutions:
  1. Check status.hedera.com for outages
  2. Try a different network
  3. Verify your firewall allows HTTPS connections

Wrong network

Cause: Operating on wrong network (e.g., mainnet instead of testnet) Solution: Switch network:
Or update config:

Common Error Codes


Getting Help

If you’re still stuck:
  1. Read the Best Practices for keys, networks, providers and costs
  2. Use error_explain tool:
  3. Check GitHub Issues: github.com/justmert/hashpilot/issues
  4. Hedera Discord: hedera.com/discord
  5. Hedera Documentation: docs.hedera.com