Two units, because one unit cannot do both jobs.

Kanvo is a mobile application. $KNVO is a fixed-supply utility token associated with the ecosystem around it. The central decision in this design is that these two things are kept apart on purpose — the application needs a unit that does not move, and an ecosystem asset needs one that is transferable and independently priced.

The two-layer economy

Each layer has one job, each has its own unit, and they meet at a single controlled boundary. A mainstream user can complete the entire application loop without acquiring, seeing, or knowing about $KNVO.

Kanvo Credits

Credits are the application's internal unit of account. They exist for one reason: so that a person can look at a screen and know what something costs. The granularity matters — Kanvo's costs are dominated by metered inference, storage and compute, which price in fractions of a cent, and a unit fine enough to express…

Fixed supply, and where it goes

A fixed maximum supply does not create scarcity in any economically meaningful sense, does not support a price, and is not a reason to expect one to rise. Scarcity is a relationship between supply and demand, and a cap constrains only one side of it. What determines the monetary conditions a participant faces is how m…

The unlock schedule

A fixed maximum supply published without an unlock schedule is close to meaningless. A participant assessing $KNVO needs to know not what the ceiling is, but what is arriving, and when. Releases happen on eight dates rather than monthly, so the curve below is a staircase and each step is a date on which a whole tranch…

Circulation instead of destruction

$KNVO received for services is not burned. It enters a treasury and re-enters the economy. A token that disappears on use has borrowed the vocabulary of currency while removing the property that makes currency work — the relevant question is not how quickly supply can be destroyed, but how much genuine activity a give…

What is published, and how often

Transparency is a set of specific artifacts on a schedule, not a value statement. Each artifact below should be checkable by a third party without Kanvo's cooperation — a circulating-supply figure that cannot be reconciled against published addresses is an assertion, not a disclosure.

Product metrics before token metrics

A $KNVO economy attached to an application nobody uses is not a healthy token economy with a product problem; it is a failure with an active order book. The reporting set is ordered accordingly.

What is deferred, and in what order

Governance is deferred rather than promised: introduced before there is anything substantive to govern, it produces theatre, and theatre creates expectations. The stages below are gated on one another, and the gates are real.

What Kanvo undertakes

Each of these is cheap to state; the exclusions above are what they cost. Published together because publishing only the half that flatters would be the first deviation.