Test the integration

A later check is meaningless if an earlier one failed. Node before the CLI. Chain id before balance. Balance before a contract deploy or a storage upload. The interactive list with tick marks is the test bench. The commands live here so you can run them in a terminal that is not this browser.

• node -v prints v20 or higher. v22 is a good default.
• git, cast, and 0g-compute-cli each print a version or a path. command not found means the toolchain guide, not a 0G outage.
• On Linux, which node should be the nvm binary if that is how you installed it.

• The chain id is exactly 16602.
• The second block number is greater than the first. If it is not, wait out a full minute once before you blame the node. A stuck number after that means you are not talking to a live Galileo RPC.
• Repeat against evmrpc.0g.ai only when you mean mainnet. That chain id is 16661. Do not mix the two in one shell session without noticing.

Claim at faucet.0g.ai while the wallet is on Galileo, then run the balance command from the tokens guide. Pass when the ether-denominated balance is greater than zero and the address page on chainscan-galileo.0g.ai shows the faucet transfer.

Then spend a little gas, with a self-transfer of zero value, and confirm the balance dropped by the fee only. That proves the key can sign. Skip this if you are not ready to unlock a keystore.

• 0g-compute-cli --help exits 0 and mentions setup-network. That is the install test. A real inference test needs a key from pc.0g.ai and the curl in the compute guide. Pass when the JSON contains choices, or when the dashboard shows the request.
• Storage passes when upload.mjs prints a root hash, hello.txt appears, and Storage Scan on Galileo finds the hash. An indexer timeout is a retry, then a check that you used the turbo indexer.
• Write down the OS, the node version, the chain id you observed, and the root hash or transaction hash. A maintainer cannot reproduce “it failed” without those four.