Skip to content
portal

10 · Storage providers

You are the reason a root hash still resolves.

Builders upload through an indexer. You store the sectors and serve them back. This desk is the operator path: hardware, the OS you should build on, and the signals that the node is actually in the network.

Open the node guide
01

Bring this machine, or do not start the compile

Memory
32 GB
CPU
8 cores
Disk
500 GB to 1 TB SSD for a storage node
Bandwidth
100 Mbps down and up

A key-value node keeps the same CPU and memory budget. Its disk grows with the streams you choose to hold, not with a fixed terabyte. The figures come from the storage-node requirements on docs.0g.ai. Read https://docs.0g.ai/run-a-node/storage-node before you order hardware from this card alone.

02

Linux and macOS compile. Windows hosts Ubuntu.

The node is Rust. On macOS, install llvm, cmake, and protobuf with Homebrew, then rustup, then cargo build --release. On Debian, Ubuntu, Fedora, or Arch, the toolchain guide already installs the compilers. On Windows, install Ubuntu with wsl --install -d Ubuntu and do the Linux build inside it. Native PowerShell is the wrong place for this binary.

Check out a release tag

Clone https://github.com/0gfoundation/0g-storage-node.git and check out the tag you intend to operate. The docs say “latest tag” because the testnet binary moves. Write the tag into your shift notes.
03

The node is healthy when

  • It is using the Galileo RPC https://evmrpc-testnet.0g.ai and log_sync_start_block_number is 1 for a fresh testnet sync.
  • Flow, mine, and reward addresses match the Galileo overview the day you started, not a screenshot from last month.
  • The log height keeps walking toward the chain head you see from cast block-number.
  • The miner key is in the process environment or a gitignored config, never in the repository you cloned.
  • A builder’s turbo upload can be fetched. If your node is on standard and they uploaded to turbo, you will not have the bytes. Those are different networks.
04

The operator wallet still needs gas

Mining and log confirmation spend native 0G. On Galileo that is faucet gas, claimed to the operator address, then checked with cast balance. On mainnet it is real 0G. The faucet will not fill a mainnet operator, and it will not fill compute credit either.

Fund the testnet operator wallet