Welcome

Syntarie is a Rust permissioned consortium settlement chain. Bounded by design. Staging-ready, not production-ready, and we will keep telling you which is which.

This is a docs site for engineers and operators. If you want the marketing pitch, the home page is for you. If you want to actually use the testnet, you're in the right place.

In plain English (for visitors without a blockchain background)

Imagine a shared accounting book between several companies who don't fully trust each other. No single party can edit it secretly, every change has to be approved by most of the group. The book lives on a small set of agreed computers, not on the public internet.

That's Syntarie. A tamper-proof shared record between known parties, with its own unit of value, a token called SCC, used to settle who-owes-who across the group.

It is not a public blockchain anyone can join to run a validator (like Bitcoin or Ethereum), only the agreed consortium members produce blocks. It is not a live mainnet today: we're on a public testnet, the SCC you claim from the faucet is free and worth zero real money, mainnet is planned but gated on operational drills + capital. It is not a memecoin or speculation token, SCC is the unit of account for the settlement work, not a price-swing play.

If that explanation is enough, jump to the testnet quickstart. The rest of this page (and most of the docs) is the technical version for engineers and operators.

What "fully tradable" means in v2

v1 ships the trading rails: wSCC on Base, a Uniswap v3 pool, seeded liquidity. That's genuinely tradable but intentionally narrow. v2 is when "fully tradable" lands:

  • CEX listings, Coinbase / Binance / Kraken track deferred to post-v1
  • Deep liquidity, beyond the v1 seeded pool (~$20–50k → growth via market signal + capital)
  • Compliance adapters, IVMS 101 / Travel Rule / MiCA, unlocks regulated EU enterprises
  • Broader trading pairs, wSCC/ETH, wSCC/wBTC alongside USDC
  • Market-maker incentives, if organic depth doesn't grow

v2 is gated on v1 actually shipping (current target ~1 focused week from "go") + post-launch market signal + capital decisions. We'll publish a docs/decisions/v2-scope-todo.md once v1 amends its §Amendments table declaring v1 shipped.

Where to start

What's currently true (2026-04-26)

  • Verified test floor: 7,341 passed + 1 ignored / 0 failed at commit 51bc3f1f (changelog)
  • Public testnet: 3 Hetzner validators in Nuremberg + Helsinki + Falkenstein, chain advancing at ~2 blocks/sec, see the live height + peer count on the home page (it self-updates every 3 seconds)
  • Latest audit verdict: BLOCKED for v1 mainnet ship, gap is operational + capital, not engineering
  • Bridge code: launch-ready (Python prover signs with real keys, rotation digest aligned to Solidity)

What's intentional, not coming-soon

Syntarie does NOT ship:

  • A general-purpose VM. Bounded native contract classes are a settled design decision, not a backlog item.
  • A generalized intent router.
  • A public mainnet, public token, airdrop, or public validator sign-up.

If your protocol needs deploy-anything VMs, Syntarie is the wrong tool. If your protocol needs a governed ledger with known operators and a predictable contract surface, it might be the right one.

How this docs site is organized

The sidebar groups pages into four buckets:

  1. Get started, install, send a transaction, run a node
  2. Architecture, what Syntarie is at the protocol level
  3. Status & audits, current state, ship readiness, audit reports
  4. Testnet + Operator, practical usage for both kinds of users

Every page on this site cites its sources. Where a claim is [VERIFIED] we link to the file:line in the repo. Where a claim is [INFERRED] we say so.