Join the testnet

ΑʹThe deployment record

The ceremony ran once, at block 2,518,440 (2026-07-07). It issued 100,000,000 OBOL into the pot and one identity-token unit into the issuer, both without a reissuance token, and seeded the stability reserve. None of it can be repeated or revoked; a new deployment would be a different set of asset ids.

The issuer anchor is also the scan floor: a wallet indexes the chain from that height, so your node has to be synced past it before any command works. The collateral asset is the testnet peg asset, which your node reports as pegged_asset.

ΒʹThe oracle set

Five keys, fixed at compile time inside the vault covenant: changing the set would change the vault CMR and therefore every address in the deployment. Three of the five sign a price tick; the protocol key verifies the quote inside the covenant, the nostr key identifies the publisher on the relay.

Per-slot freshness is visible in the explorer. The oracles have no public HTTP: they publish over the relay, and their admin ports stay on loopback.

ΓʹThe config file

Those values ship as one file, liquid-testnet.toml, which every role reads - the wallet, the app, the keeper, the explorer. Two places serve the same bytes:

• explorer.testnet.styx.network/config - what deploy/join-testnet.sh downloads.
• deploy/liquid-testnet.toml in the repository - the same file under a commit signed by the maintainer key.

Compare them if you like; they are byte-identical, and the record above is the same data in prose. Tampering is not much of a threat anyway: your wallet cross-checks the config's genesis against your own node and refuses to sign against a chain that disagrees, and every address in the deployment is derived from the asset ids and the oracle keys, so a wrong file produces addresses where nothing lives.

ΔʹJoining

One idempotent script writes ~/.styx: a node dir with generated RPC credentials, your keys, the config above, and one app.toml that both the app and the CLI read.

git clone https://github.com/standardsats/styx-cdp && cd styx-cdp
nix develop
deploy/join-testnet.sh

It ends by printing what it cannot do for you, in order: start the node, wait for the sync to pass block 2,518,440, point a Liquid-testnet faucet at your funding address, run the app. First sync takes a few hours. The long way, section by section, is in TESTNET.md.