Protocol Primitive

Prove it. Act on it. Settle it.

The Markovian Protocol defines a single primitive for verified economic state: ZK-proven, Merkle-committed, Bitcoin-anchored. STAMP proves a state existed. TRIGGER acts when one is confirmed. SETTLE resolves competing positions against one. Three interfaces. One chain. No trusted party at any layer.

Build on the Primitive Read the Whitepaper
Chain Height
Block Time
30s
Markets Settled
Open Markets
Total Staked
Resolution
Oracle-free
Finality
Bitcoin
The Oracle Problem
Lost to oracle manipulation
$490M
Mango Markets. Cream Finance. Beanstalk. Inverse Finance. Harvest. All audited. The exploit was on the data, not the contract.
The trust assumption
1
Every prediction market resolves through a trusted party. Chainlink, UMA's optimistic oracle, centralized operators — all reduce to someone saying what happened.
Audits that caught it
0
Smart contract audits certify code execution. They cannot certify what an oracle returns at runtime. The blindspot is the data layer, not the logic layer.

The Markovian Settlement Chain removes the oracle dependency structurally. There is no feed to manipulate. Resolution is a function of the chain's own verified computation. Full breakdown →

The Signal Has Edge

Before anything settles against the M matrix, one question matters: does the regime signal have measurable predictive value, or is it noise? 26 years of daily data across four asset classes answers it.

QQQ · 26 years
+1,303%
vs +696% buy & hold
Sharpe 0.915 vs 0.432
Max DD −17.5% vs −83%
USO · 20 years
+473%
vs −76% buy & hold
Sharpe 0.509 vs −0.005
Regime rescued a losing asset
TLT · 24 years
+181%
vs +114% buy & hold
Sharpe 0.524 vs 0.296
Max DD −18.6% vs −48.4%
Regime signal
56.1%
bull call hit rate
Long bull, cash bear
No leverage, no shorts

Strategy: long ACCUMULATION/TRENDING, flat DISTRIBUTION/CAPITULATION, confidence ≥0.60. No lookahead. The null hypothesis that the regime signal is noise is rejected across all four asset classes over 26 years. This is the input that settles markets on the Markovian chain.

How Settlement Works
01
Create
Any application creates a market via API. Question, category, resolution condition. Market is written to the sidechain in the next 30s block.
POST /sc/market/create
02
Bid
Participants stake MKV on YES or NO. Each bid debits the MKV ledger and is recorded in the sidechain mempool, confirmed in the next block.
POST /sc/market/bid
03
Resolve
The settler reads the Markovian M matrix — a ZK-proven regime computation. When the matrix confirms the outcome, the market closes deterministically. No operator decision.
Auto — M matrix
04
Settle
Winners receive pro-rata MKV from the pool. Payouts are credited directly to the MKV ledger. The settlement record anchors to Bitcoin for permanent finality.
BTC anchored
Infrastructure Comparison
Property Chainlink UMA Centralized Markovian
Oracle-free resolution No No No Yes
ZK-proven settlement No No No Yes
Bitcoin-anchored finality No No No Yes
Manipulation surface Feed price Dispute window Operator None
Settlement token backed Market cap Market cap None BTC reserves
API integration Complex Complex Varies 3 endpoints
What Makes This Different
No Oracle
Resolution is a function of the Markovian chain's own verified state transitions. The M matrix is computed by miners, proven with ZK, and recorded on-chain before any market resolves. There is no external data feed to manipulate.
ZK-Proven Settlement
Every settlement proof is a BN128 Schnorr commitment anchored to Bitcoin via OP_RETURN. Anyone can verify that a market resolved correctly without trusting the operator or reading the contract. The proof is public. The verification is instant.
BTC-Backed Settlement Token
MKV is not a governance token. It has a hard floor: treasury BTC reserves divided by circulating supply. Every MKV used for settlement has a computable minimum value backed by real Bitcoin.
30-Second Finality
Sidechain blocks every 30 seconds. Settlement confirmed in one block. Main chain anchor every 5 minutes for Bitcoin-level finality. Faster than any optimistic oracle dispute window by design.
Live Settlement Chain
Sidechain Block | 30s blocks | Anchors to main every 10 blocks | settle.quantsynth.net →
Loading markets...
Build On It — API Reference
GET /sc/stats Chain overview
GET /sc/markets?status=OPEN List markets
GET /sc/market/{id} Market state + positions
POST /sc/market/create Open a new market
Body: { question, category, created_by, key }
POST /sc/market/bid Place a position — debits MKV ledger
Body: { market_id, wallet, side: "YES"|"NO", amount_mkv }
GET /sc/wallet/{address} Positions + earnings by wallet
GET /sc/block/{height} Block + confirmed transactions
# Quick start — create a market and place a bid import requests BASE = "https://settle.quantsynth.net" # 1. Create a market market = requests.post(f"{BASE}/sc/market/create", json={ "question": "Will QQQ close above $730 this week?", "category": "equity", "created_by": "your_btc_address", "key": "your_api_key" }).json() market_id = market["market_id"] # 2. Place a bid bid = requests.post(f"{BASE}/sc/market/bid", json={ "market_id": market_id, "wallet": "your_btc_address", "side": "YES", "amount_mkv": 1.0 }).json() # 3. Resolution is automatic — M matrix confirms, settler pays out # Check your wallet wallet = requests.get(f"{BASE}/sc/wallet/your_btc_address").json() print(wallet["total_earned_mkv"])