MPC threshold-release · live on Sepolia

Watch a release assemble, and see what it will do before it opens.

A threshold-release scheme splits a payload into k-of-m shares, encrypts each to a committee node, and names a release condition. Nodes evaluate the condition off-chain and publish shares; the k-th share makes the payload publicly reconstructable, and it settles a block or so later. Conclave is the surface for that lifecycle — it tracks the quorum, marks the instant of reconstruction, and previews the settlement before it runs. The one network it currently supports is Nillion Blacklight L1, where a release is called a covenant; the model generalises to any threshold-release scheme.

1

Track the quorum

Every release on the network, its condition decoded, and its committee assembling toward k‑of‑m — including how many slots one operator holds.

sealed → collecting
2

Observe reconstruction

The k‑th share makes the payload reconstructable. Conclave marks that instant — the moment the secret goes public — and measures the gap before it executes.

reconstructable
3

Preview the settlement

Inside that gap, reconstruct locally and dry-run the reveal: whether it settles or reverts, whether the hook acknowledges, what moves, and how long it has already been exposed.

before it opens
Secrecy below k is cryptographic; release at the k‑th share is economic and operational, and the plaintext is public at least a block before it settles. Conclave treats that disclosure window as a measured quantity rather than a footnote — an instrument for the properties a threshold-release actually has to be judged on: feed correctness, the k-of-m collusion surface, liveness, and the share-to-settlement gap.
Deployment reading C0…
Releases
live · updating…