Testnet quickstart

The shortest honest path: install the wallet, launch it, claim test SCC, send a transfer. Four steps, ~30 seconds.

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 and scc-node into ~/.local/bin, verifies their checksums against the release manifest, and detects whether you already have a previous install (it asks before overwriting and saves a .previous backup).

If ~/.local/bin isn't on your PATH, the installer's final output gives you the exact line to add for your shell (bash, zsh, or fish). Follow that, it's tailored to what you have.

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 ~/.local/bin/scc-tui
# Compare to SHA256SUMS-<platform>.txt on the release page.

2. Launch the TUI (auto-creates your wallet)

scc-tui --testnet ~/my.key

On first launch the TUI auto-creates ~/my.key (your wallet, 32 bytes of Ed25519 private key) and prints your address in the header. The header lights up yellow [TESTNET]. The Wallet tab is the first thing you'll see.

Keep ~/my.key private, anyone with that file can spend tokens at your address. On testnet that means losing test funds; on mainnet it would mean losing real ones.

3. 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.

4. Send a transfer

The shortest path is the TUI: hit [t] for the transfer workspace, paste the recipient address, enter the amount, review, and confirm. The TUI plans, signs locally, runs the safety review, and submits, the testnet bearer token is bundled into the --testnet preset.

For scripting, the protocol CLI (scc-node) plans + signs + submits over HTTP RPC. It's installed alongside scc-tui by default:

scc-node transfer-intent \
  --rpc-url http://91.99.102.167:19100 \
  --to <recipient-address-hex> \
  --amount 50

The signing key is read from the path you passed to scc-node at start (--key-path), not as a per-call flag.

About the testnet bearer token

The token UIBsO3tav34ABrYq0sSbUcNXlAGMy5DEuRvZskzFLGkMOoyK is HTTP-level auth, not a CLI flag. The public RPC nodes require it on write paths (/submit_tx, /faucet). The TUI's --testnet preset bundles it. If you craft a raw HTTP request, supply it as a Bearer header:

curl -X POST http://91.99.102.167:19100/submit_tx \
  -H "Authorization: Bearer UIBsO3tav34ABrYq0sSbUcNXlAGMy5DEuRvZskzFLGkMOoyK" \
  -H "Content-Type: application/octet-stream" \
  --data-binary @signed-tx.bin

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.