Testnet quickstart

The shortest honest path: install the wallet, generate a key, claim test SCC from the faucet, send a transfer.

1. Install (Linux / macOS, x86_64 + Apple Silicon)

curl -sSL https://github.com/syntarie/scc-releases/releases/download/testnet-2026-04-26/install.sh | sh

The script auto-detects your platform, downloads scc-tui into ~/.local/bin, and prints the next steps. Set SCC_BINS="scc-tui scc-node" if you want the protocol/CLI binary too.

If ~/.local/bin isn't on your PATH, add it:

export PATH="$HOME/.local/bin:$PATH"

Windows

Direct download (no curl | sh flow yet):

https://github.com/syntarie/scc-releases/releases/download/testnet-2026-04-26/scc-tui-windows-x86_64.exe

A scoop bucket is queued for a future release.

Verify the download

sha256sum scc-tui
# Compare to SHA256SUMS-<platform>.txt on the release page.

2. Generate a wallet

scc-tui keygen ~/my.key
scc-tui key-address ~/my.key

The first command writes 32 raw bytes (your Ed25519 private key) to ~/my.key. The second prints the 64-hex-char public address derived from it.

Keep ~/my.key private — anyone with that file can spend tokens at your address.

3. Launch the TUI

scc-tui --testnet ~/my.key

The header should light up yellow [TESTNET]. The Wallet tab is the first thing you'll see.

4. Claim test SCC

In the TUI, on the Wallet tab, press [$]. The faucet on nbg-1 dispenses 100 SCC to your address. Wait one block (~1 sec), then check your balance — you should see 100.

Rate limits: 60s cooldown per IP, 300s cooldown per address.

5. Send a transfer

Use the standard transfer flow in the TUI. Or, from the command line:

scc-tui transfer-intent \
  --rpc http://91.99.102.167:19100 \
  --rpc-write-token UIBsO3tav34ABrYq0sSbUcNXlAGMy5DEuRvZskzFLGkMOoyK \
  --key ~/my.key \
  --recipient <recipient-address-hex> \
  --amount 50

That plans, signs locally, and submits to the chain. Use --help for full options.

Troubleshooting

"Faucet disabled"

You hit /faucet on hel-1 or nbg-3. The faucet is on nbg-1 only. The TUI's [$] keybinding routes correctly; this only happens with a manual curl to the wrong host.

"Rate limit exceeded"

Either you hit the 60s IP cooldown or the 300s per-address cooldown. Wait it out.

Chain looks stuck

Check /status on more than one node. If two of three say operational_state: healthy and sync_phase: live, the chain is fine — your one might be restarting.

Transfer rejected

Most likely insufficient balance, or the recipient address has a guardian/recovery requirement that hasn't been satisfied. Check /account?address=<your-address> for current state.