09 · Maintainers

Check the doors before you check the app.

A maintainer’s job on this portal is to notice when Galileo, mainnet, the faucet, or an explorer stops telling the truth. The app in front of them is usually fine. The RPC underneath is not.

Run this at the start of a shift

The commands follow the OS you pick. Ticks stay in this browser so the next person on the same machine can see what already passed. They are not a shared status page.

0/5 passed on this browser

01Galileo chain id16602 from the public testnet RPC.
02Mainnet chain id16661 from https://evmrpc.0g.ai. A Galileo id here means the URL was not swapped.
03Galileo height movedSecond reading is higher. One stuck minute is worth a second sample before you escalate.
04Faucet still claimsA fresh address receives testnet 0G, or the faucet shows a clear rate-limit rather than a 500.
05Explorers load the same height neighborhoodChain scan and your cast block-number are close. Storage scan loads for Galileo.

Write down four things when something fails

The OS and the shell. PowerShell and Git Bash on the same Windows machine are different results.
The exact RPC URL and the chain id it returned, even when the id is wrong. Especially then.
The block number, the time, and whether a second sample moved.
The address or root hash a builder says is missing, plus the explorer link.

Builder-facing changes belong on https://build.0g.ai/updates. Do not announce a contract address in a chat if the Galileo overview has not published it yet.

Addresses are allowed to move on testnet

Flow, mine, reward, and the DA entrance are published on https://docs.0g.ai/developer-hub/testnet/testnet-overview. When a builder pastes an address from an old README, compare it to that page before you debug their Solidity. The native token name is 0G. A script still saying A0GI is the script that is out of date.