Attestations are live over REST — contracts are not deployed yetRead an attestation
Cleaton
DURABILITY ATTESTATION FOR AUTONOMOUS CAPITAL

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.

Read an attestationWhat the fields mean

Specification stage. No contracts are deployed — the REST surface and the signature format are what exist today.

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.

Verify a signatureDeposit Guard
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 is expected to hold
console.log(a.confidenceBps);  // 7000   calibrated coverage, in basis points
console.log(a.thresholdBps);   // 7000   retention floor the horizon is against
console.log(a.validUntil);     // unix   after this the attestation is stale
KEEP GOING

Resources

Whitepaper

The hazard model, the conformal calibration, and what is not solved.

Surface catalogue

All 36 surfaces across contract, API, agent and automation layers.

Blog

Working notes, including the limitations that get their own posts.