Economic Primitive
Block  — MKV Issued  — Regime  — Confidence  — ZK BN128 BTC Anchored
Protocol Primitive

Two functions.
One atomic protocol.

One ZK-proven output per block. Merkle-rooted. Bitcoin-anchored. Two things you can do with it.

COMMIT

Lock something
to the chain.

For
  • Research publishers who need a timestamped, unforgeable record
  • Signal producers proving a call was made before the outcome
  • Institutions anchoring data to an auditable on-chain reference
  • Anyone who needs: I said this. Here is the proof.
Go to COMMIT →
RESOLVE

Test something
against the chain.

For
  • Prediction markets that need trustless settlement without an oracle
  • DeFi contracts that trigger on real-world regime state
  • Analysts registering a falsifiable claim and letting math decide
  • Anyone who needs: the chain said so. Here is the proof.
Go to RESOLVE →
Live Example
COMMIT + RESOLVE used together. One atomic event. Two views.
See the demo →
Atomic Protocol

One output. Two functions.
The output does not change.

The protocol produces one atomic output per block. ZK-proven, Merkle-rooted, Bitcoin-anchored. Two functions compose on it. COMMIT locks any data output to the chain record, unforgeable and publicly verifiable. RESOLVE registers a falsifiable claim against a future block, then the chain decides. TRIGGER is the claim. SETTLE is the automatic verdict. One user action. One return value.

Atomic Output — Markovian Protocol
matrixM ∈ ℜ³×³  Markov transition matrix, calibrated to block history
pathViterbi(M, observations)  most probable state sequence
proofSchnorr σ(BN128)  zero-knowledge validity proof
rootSHA-256 Merkle  commitment to the full observation set
anchorBitcoin OP_RETURN  immutable on-chain timestamp
COMMIT
TRIGGER
SETTLE
Protocol specification
# COMMIT stamp(data_output, zk_proof, merkle_root, btc_anchor) # TRIGGER register(condition="regime == DISTRIBUTION for 3 blocks") fires(when=chain_state matches condition) # SETTLE create(question, target_block) resolves(at=target_block, outcome=chain_state)
Backtest

Atomic output. 26-year verification.

The primitive's value rests on one question: does the regime output carry predictive information? 26 years of daily data across four asset classes. Null hypothesis rejected in every series. No leverage. No lookahead.

QQQ · 26yr
+1,303%
vs +696% buy & hold
USO · 20yr
+473%
vs −76% buy & hold
Sharpe · QQQ
0.915
vs 0.432 passive
Max Drawdown
−17.5%
vs −83% buy & hold
Confidence threshold ≥0.60. Backtest spans 1999–2025. Full methodology, permutation tests, and asset-class breakdown: whitepaper §5 →
Two Functions

COMMIT and RESOLVE.
The technical layers underneath.

Two functions. COMMIT locks data to the chain. RESOLVE registers a claim and returns a verdict. COMMIT, TRIGGER, and SETTLE are the technical layer names, but the user experience is two verbs.

COMMIT
COMMIT — alphasynth.net

Lock something to the chain.

Any data output, ZK-committed to the regime state, Merkle-rooted, Bitcoin-anchored. The record is unforgeable and publicly verifiable. No custodian. Permanent.

stamp.markovianprotocol.com →
RESOLVE
TRIGGER + SETTLE — sigmasynth.net / quantsynth.net

Test something against the chain.

Register a falsifiable claim against a future block. Name the condition. Name the block. The chain returns MATCH or MISS. No oracle. No trusted party. TRIGGER is the input. SETTLE is the automatic verdict.

trigger.markovianprotocol.com →