Owner-bounded treasury
The treasury policy holds rolling budgets in a durable store — a restart can never reset a limit. Every allow/deny decision is journaled against the policy it was made under.
ECONOMIC LIFE
A being that can work —
inside boundaries you set.
EVO can pursue goals that cost resources: hire help, pay for work, and learn from the results. But every step happens inside a treasury you bound, behind approvals you grant — and nothing counts until it's independently verified.
THE ECONOMIC LOOP
From a goal to a verified economic experience
This is the real loop implemented in the runtime. Every transition is persisted, every spend is journaled, and nothing enters memory as "verified" without independent verification.
-
1 · Goal
EVO has a goal — a piece of work it wants done that it can't complete alone.
-
2 · Capability evaluation
EVO evaluates what capability the work needs and whether the goal is worth pursuing inside its bounds.
-
3 · Provider discovery
EVO discovers providers that advertise the needed capability and collects bounded, time-limited quotes.
-
4 · Bounded treasury spend
Spending is checked against an owner-set treasury policy. Above the bounds, the loop stops and asks you.
-
5 · Independent verification
The provider's result is verified independently. A provider can produce evidence — it can never mark its own work "verified".
-
6 · Verified economic experience
Only a verified outcome becomes experience. The order, intent, quote and verification are all recorded.
-
7 · Memory & reputation
The verified experience enters EVO's memory and reputation — real history it can build on, and you can check.
BOUNDARIES
Your treasury. Your gates. Never its authority.
Approval gates
Spend inside the bounds can proceed; spend beyond them halts at APPROVAL_REQUIRED until you decide. EVO cannot approve its own requests.
No self-granted authority
EVO never holds a wallet, never signs payments, never transfers assets on its own. A separate signer boundary re-checks the network and intent integrity before anything is signed — and the owner co-sign sits with you.
Independent verification
Verification is structurally separate from the provider. Providers produce evidence; only the verifier can turn it into verified experience. Nothing is minted as experience on a provider's say-so.
ALPHA STATUS — READ THIS
What's real, what's emulated, what's testnet
Honesty about the current state matters more than a good story. Here is exactly where the economic life stands today.
EMULATOR: KaspaSwarm provider
The KaspaSwarm provider in the current loop is a clearly labelled EMULATOR. The upstream project has no public integration surface yet, so real testnet evidence through it is externally blocked. The emulator reproduces the advertised lifecycle — task broadcast, solver bids, assignment, escrow, result, settlement evidence — so the full provider loop is exercised end-to-end. Nothing it produces is presented as real testnet proof.
Kaspa testnet-10 alpha
Where settlement does touch a network, it is Kaspa testnet-10 — an alpha integration. Testnet assets have no real-world value, and no real money moves anywhere in this runtime.
Mainnet is hard-blocked
Mainnet is blocked at policy load and re-checked at every spend decision — it is not a configuration detail that can drift. Mainnet activation requires explicit owner authorization and is not enabled here.
QUESTIONS
Common questions
Can EVO spend money on its own?
No — and it can't create the authority to. Spending is gated by an owner-set treasury policy, an approval engine for anything beyond bounds, and a signer boundary EVO has no access to. EVO can request and route work; it can never grant itself the power to pay.
Is the KaspaSwarm provider real?
Not yet — it's a labelled EMULATOR. The upstream KaspaSwarm project currently exposes no public API to integrate against, so the emulator stands in to exercise the full loop honestly. When a real endpoint exists, the adapter boundary is already in place to use it.
Does any real money move?
No. Everything runs on Kaspa testnet-10 (alpha) or inside the labelled emulator. No real funds, no mainnet, no production settlement — and mainnet is hard-blocked in policy, not merely disabled.
What stops a bad provider from claiming success?
Independent verification. A provider only produces evidence; a separate verifier decides whether the work is verified. Unverified results never become "experience" — and the loop's adversarial cases (mismatched results, dropped results, delayed settlement) are covered in the test suite.
See the loop live
Enter the app and watch verified economic experience accumulate — testnet-safe, honestly labelled.
See the demo