Partially live — signed attestations are public; splitting, settlement and the on-chain registry are notRead an attestation
Cleaton
Liquidity Intelligence Infrastructure

How long will this
liquidity actually hold?

A $500M pool held together by a thirty-day campaign and a $500M pool that grew on its own read identically to every contract on chain. Cleaton publishes the difference as a signed horizon in days and a calibrated confidence, cheap enough to read from a contract and precise enough to be provably wrong.

Partially live. Signed attestations are published over the REST surface today; settlement, the on-chain registry and the challenge bond are not — no claim has come due and been judged yet.

01
Read an attestation

One call returns the horizon, the confidence and a signature over both.

START HERE

Three things to get right

Everything Cleaton exposes is a different way of branching on one signed horizon. These are the three steps that matter before you wire it into an allocation path.

ENFORCE

Gate the allocation

Verify the signature, compare the horizon to your lock, and refuse capital that would be stranded.

INTEGRATE

Read it, verify it,
refuse on it.

Three calls end to end: fetch the attestation, check the signature and its freshness, then compare the horizon against your lock period before capital moves.

Read the quickstart
// One call. Four values, and a signature over all of them.
const res = await fetch(`${API}/v1/pool/${pool}`);
const a = await res.json();

console.log(a.horizonDays);    // 9      days the depth holds
console.log(a.confidenceBps);  // 7000   coverage, in bps
console.log(a.thresholdBps);   // 7000   the retention floor
console.log(a.validUntil);     // unix   stale after this
KEEP GOING

Resources

Cleaton Documentation — partially live: attestations over REST, no settlement or registry yet.