Senticore

The performance and UX of a centralized order book - with the self-custody and cryptographic verifiability of on-chain settlement.

Orders match off-chain in a deterministic Rust engine built for low latency: a single deterministic primary, not a multi-node consensus you have to trust. Because matching is deterministic, the ledger is byte-for-byte reproducible: anyone can replay the published event log and arrive at the exact same state root committed on-chain. Balances, settlements, and withdrawals are anchored on-chain through periodic state-commitment roots. The result: a venue you do not have to trust - you can verify it.

Docs-site release: 0.1.3.

Public mainnet status

Senticore is in capped private beta with live trading and real collateral. Public mainnet is not live yet. The next broader external phase is a Q3 2026 closed beta with whitelisted users and capped TVL.

Why Senticore

Today every exchange forces a trade-off. Senticore is engineered to remove it.

	Centralized exchange	On-chain DEX	Senticore
Execution	Fast, deep books	Slow, MEV-exposed	Fast off-chain CLOB
Custody	Operator holds funds	Self-custody	Self-custody, on-chain vault
Solvency	"Trust us", opaque	Transparent	Cryptographically provable
Withdrawals	Operator-gated	Permissionless	Proof-backed and verifiable

Post-FTX, "do not trust, verify" stopped being a slogan and became a requirement. Senticore is built so that solvency and withdrawals are not promises; they are Merkle proofs against roots published on-chain.

What's Real Today

Senticore is built end-to-end and has run the full lifecycle - deposit, match, settle, proof-backed withdrawal - on real collateral during internal beta. This is not a whitepaper; it is a working system:

• Deterministic matching, sequencing, and risk in Rust, validated by cross-engine differential replay and property tests across supported order types.
• On-chain custody and state-commitment contracts with invariant testing, adversarial signature paths, and settlement round-trip coverage.
• Verifiable by design: protocol and per-account solvency proofs, plus proof-backed withdrawals, exposed as API endpoints.
• Professional beta interfaces: HTTP REST, public/private WebSocket, self-service FIX 4.4, and the BSL Business Line API. Market makers should start with the Live Verified Beta status and FIX/BSL Connectivity Bundle, then the tested Market Maker Beta Quickstart; generated /institutional/* reference routes are not the quoting entry point.
• Multiple products on one collateral layer: spot, binary options, and prediction markets.
• Typed SDK previews for TypeScript, Python, and Rust, plus a wallet-native web app.

Detailed load-test figures are shared with partners on request after the integration path and environment are fixed.

Operational Status

We build first, then open up. The roadmap is deliberately conservative:

Phase	Status
Internal beta with team and close circle, real collateral	Completed
Private beta with whitelisted users and capped TVL	Live, capped
Broader closed beta	Q3 2026 planned
External tier-1 security audit	Q4 2026 to Q1 2027 planned
Public mainnet	H1 2027 target, post-audit

Pre-launch documentation reflects the developing closed-beta and public-mainnet surface. Internal beta interfaces and parameters may differ from the public release.

Start Here

Section	What you will find
Overview	Product model, architecture, trust model, threat model
Trading	Order types, settlement, markets, fees
Building	Builder Codes, pricing classes, and Launchpad scope
Live MM Verification	Current live BSL/FIX conformance status and latest observed beta timings
FIX/BSL Connectivity Bundle	Self-service direct endpoints, FIX CompIDs, and BSL route contract
Market Maker Beta Quickstart	Tested BSL/FIX entry path for professional clients
Integration	SDK, APIs, WebSocket streams, signing
Contracts	Addresses, vault, state commitments, token
Reference	Tokenomics, glossary, roadmap, status, legal context

System Shape