Mandate
Accountable liquidity management · live on Solana devnet

Your liquidity agreements. Verified.

Monitor your operator, agree clear terms, and settle service payments with your inventory restricted to the agreed market.

Run liquidity for token teams? What operators get →
KITE/USDCOperator: your current market maker
Operational
Last 48 hourly periods46 of 47 checked periods met
Committed bids2,640 USDCat least 500 within 2%
Committed asks3,105 USDCat least 500 within 2%
Spread10 bpsat most 100
Next: the term ends in 3 days. The renewal report is ready.
Example data
How it works

Observe, agree, then manage and renew.

1 · Observe
Collecting evidence9 of 12 periods

Point Mandate at the pool your operator already manages. With no wallet and no deposit, you get a period-by-period record of what they actually delivered.

2 · Agree
Version 2, proposed by the operatorOperator bond: 250 → 200Failed periods before breach: 3 → 4TeamOperatorterms 7a68…

Draft terms from that record, see what each side commits, and negotiate by link. Both sides sign the exact same terms before anything is funded.

3 · Manage and renew
Paid to the operator712 USDC
Unused budget, returned8 USDC
Penaltiesnone
Proposed: ask for the depth that was delivered

Payment follows the checks. At the end of the term, a report shows what the service was worth and proposes the next terms.

For token teams

Keep your operator, lose the blind trust.

  • Inventory can only be quoted on your pool, and comes back
  • Pay per verified period instead of settling an invoice by hand
  • A report you can take to a renewal or a remediation conversation
For operators

Explicit terms, funded fees, a record that travels.

  • Every fee is escrowed before you accept; payment is automatic
  • Negotiate bond, tolerance and term before signing, version by version
  • A work queue with what changed and a simulated next action
What is enforced

Committed liquidity, measured the same way by everyone.

The program measures the operator's liquidity near a manipulation-resistant reference price, bin by bin, so trades against the book can't fake a pass or force a fail. What a trader can execute is shown next to it, not enforced.

Committed depth, measured bin by bin

A check values the maker's liquidity at each price bin's own price. Buying out the book right before a check moves value between the two tokens, not out of the book, so it can't fake a pass or force a fail.

Checks nobody can schedule around

Anyone can run a check at any moment, as often as they like. The maker can't know when the next one lands, so the only strategy is to stay in the market.

A reference price you can't push

Quotes are judged against a reference that follows the pair's time-weighted price at a capped speed. A price moved for one block doesn't move it.

Escrow with one exit

The issuer's inventory can only be quoted on the pair and returns at the end of the term. Fees stream out per compliant period; the bond is slashed on breach.

Read the security model
It holds up under attackSimulated participants run these against the test network. The ordinary, paid-and-renewed agreement is the everyday case; these are the edges.
Sandwiched checkCheck passed

Attempt. Mallory buys out the maker's asks and forces a check in the same transaction, hoping the lopsided book flatters or fails the maker.

Why. Liquidity is valued bin by bin at each bin's price, so the trade changes which token sits in a bin, not how much is committed.

Maker walks awayBond slashed

Attempt. Lazy Capital accepts KITE's SLA, quotes for a few minutes, then pulls every bin back into the vault.

Why. Checks fail, three missed periods slash half its bond, the inventory goes back to the issuer, and KITE re-tenders to a new maker.

Reference nudgeNo effect

Attempt. Push the pair's price for a block so the maker's quotes look off-side, or drag the reference toward a price that suits you.

Why. The reference tracks the pair's TWAP at no more than 2% a minute and distrusts oracle time after an emptied bin.

Quote for the check, pull afterBlocked

Attempt. Add liquidity just before a check lands and withdraw it straight after, so the book is only deep when someone looks.

Why. Deposits are locked for 20 seconds and checks arrive at random, so liquidity has to stay to count.

Questions

What it does, and what it doesn't.

Does Mandate hold our tokens?

No company holds them. Inventory sits in vaults owned by the agreement's program account. The operator can only place it as quotes on the agreed Meteora pool and withdraw it back to those vaults; at the end it returns to the team.

What is private and what is public?

Drafts, negotiation and observation reports stay with you: in this version, in your browser and in links you choose to share. Anything that happens on chain, such as a funded agreement, its checks, payments and penalties, is public, like every Solana transaction.

Does passing the checks mean traders get good prices?

Not necessarily. The agreement enforces committed liquidity near a reference price. What a trader can actually execute moves with every trade, so Mandate shows it next to the enforced measure and in every report, without making it the obligation.

Is monitoring a guarantee?

No. Observation tells you what the operator delivered when it was checked. Periods nobody checks are neither paid nor failed, and reports say how much of the time was covered.

What happens if the operator stops?

Checks fail, and after the agreed number of failed periods part of its bond goes to the team, the inventory is unwound and returned, and the closing report records the gap until the next operator starts.

Can we use it with real funds today?

Not yet. The program runs on Solana devnet with simulated participants. Monitoring works on mainnet pools now; escrowed agreements on mainnet wait for an independent audit.

Start with the arrangement you already have.

Monitoring needs no wallet and no deposit. See what your operator delivers, then decide what to agree.