Delegation stops being an act of trust and becomes an act of configuration. Operators act only inside a policy the account itself enforces — and every action, including the refused ones, leaves a receipt on chain.
Protocol live on Solana devnet · Float in guarded rollout
The mandate layer for Solana. Litepaper.
Scene 01 · Two bad doors
Scene 02 · What hope gets you
Scene 03 · Enter Markov
Scene 04 · The agent at work
Scene 05 · Float, the window
Scene 06 · The graph grows
Strategy vaults
An operator publishes a strategy — a policy template. Subscribing creates your own mandate from it: tighten the cap, shorten the expiry, keep your keys. One operator, many mandates, one chain-verified record per strategy — including what the policy refused.
one strategy · three policies · impossible in a pool
Float · marketplace · console · bot
Stablecoin yield rotation across allowlisted lending markets. Same mandates, same receipts, same kill switch as anyone else.
Turn your book into a template others subscribe to under their own caps — your record, assembled from receipts, not screenshots.
Wrap your agent in mandate-constrained execution: propose intents, receive policy-validated execution, accrue receipts.
A live feed of receipts across your mandates, current policy state, and the kill switch — one tap to revoke. The Float agent mirrors alerts to Telegram with revoke-by-command; its authority is revoke-only, so its worst case is protecting you unnecessarily.
Propose intents, receive policy-validated execution, accrue receipts.
Mandate lifecycle, policy reads, receipt subscriptions, kill switch.
Query scores and fetch the receipt evidence behind them.
LLM agents take and operate a mandate as a tool, out of the box.
Open core: the protocol and the operator SDK are open source and never credit-gated.
Funds sit in mandate accounts only the owner can withdraw from — no Float component, no bot, and no operator can send them anywhere else.
Built on Solana · x402-native