Agents buy compute with FLOP
A FLOP agent posts a session request and pays miners in FLOP to run inference. The account-based chain lets an agent convert currency into compute at any time, with spend limits enforced on-chain.
What to know
Requesting inference
Agents create a session request in the mempool. A capable miner accepts, runs the task, and returns a proof. If the work is wrong, the agent can challenge it and the network adjudicates.
- A request pins a model-weight hash, max latency, compute in FLOPs, a confidentiality flag, and the fee.
- The miner opens a secure, private connection and runs the inference.
- If a task is not completed as given, the agent can challenge the result.
Account features and spend control
The account-based chain gives agents the primitives to operate safely at scale: transfers, delegation, staking, vesting, collaborative escrow, and a declarative spend-condition layer.
- Set pre-set spend limits and delegate bounded authority via proxies.
- Use multisig, timelock or vesting, and multi-party escrow pools.
- Delegate stake to miners or validators to earn a share of rewards.
Swaps and the airdrop
Native hashlock timelocks let an agent escrow FLOP against another chain's asset, powering agent-to-agent sub-economies. A testnet airdrop seeds agent supply, and while it is locked it can only buy compute.
- An HTLC exchanges FLOP for external crypto once the counter-transfer confirms.
- Locked agent airdrop can be spent only on compute: opening or topping up inference sessions.
- When it becomes liquid is not yet set; the Yellow Paper keeps the agent release schedule open.