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.
Where to start
- You want to send a transaction in 30 seconds → Testnet quickstart
- You want to know what's actually shipped → v1 readiness audit
- You want to know what Syntarie is and isn't → Scope boundaries
- You want to run a node → Operator quickstart
What's currently true (2026-04-26)
- Verified test floor: 7,299 passed + 1 ignored / 0 failed at commit
80e5a51 - Public testnet: 3 Hetzner validators in Nuremberg + Helsinki, chain advancing at ~2 blocks/sec, height 154,000+
- 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:
- Get started — install, send a transaction, run a node
- Architecture — what Syntarie is at the protocol level
- Status & audits — current state, ship readiness, audit reports
- 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.