Why $TRUST and not just $DOVU
A plain-language explanation of the dual-token design: what each token does, why one token isn’t enough, and how the two strengthen each other.
If DOVU already has $DOVU, why introduce a second token?
It’s a fair question and it deserves a direct answer, not just a whitepaper.
The short answer
$DOVU and $TRUST do fundamentally different jobs. Collapsing them into one token would mean either crippling the execution layer or compromising the authority layer.
The dual-token design is not a choice made for tokenomics optics. It is the correct technical and economic architecture for what DOVU is building.
$DOVU: Powers what happens
Powers DOVU OS, the workflow execution layer. Used for blueprint creation, audit logging, coordination events, and every action that moves a workflow forward. A transaction token whose value tracks the volume and frequency of workflows running through DOVU OS.
$TRUST: Proves who was allowed
Powers Authority Trail, a distinct protocol layer that records and verifies who had the right to act, in what role, at what point in time. This is authority-state management: identities, role banks, permissions, expiry windows, and an immutable, queryable record of role validity over time.
A different function, audience, and economic model
Authority Trail is not workflow execution. It serves a different function, a different audience, and a different economic model to DOVU OS, and it needs its own token for four concrete reasons.
Why one token is not enough
1. Different economic behaviour
$DOVU is consumed in proportion to workflow activity; $TRUST in proportion to authority-state changes: roles created, renewed, delegated, or revoked. These demand curves are independent. An enterprise managing thousands of auditor credentials should not face price volatility driven by carbon trading volume on DOVU OS, and vice versa.
2. Different supply requirements
Authority Trail supports high-frequency, granular writes at low cost (registrations, renewals, delegations, revocations) that must stay economically viable at scale, including for machine-to-machine systems and AI agents. $TRUST launches with 100 billion tokens and 4 decimal places precisely to meter these writes at a granularity $DOVU was never designed for.
3. Different stakeholder groups
Auditing bodies, credentialing authorities, enterprise compliance teams, AI infrastructure providers, and regulatory submitters may need Authority Trail without ever running workflows on DOVU OS. A separate token lets Authority Trail be adopted independently, expanding the addressable market without requiring every $TRUST user to also be a $DOVU workflow user.
4. $TRUST strengthens $DOVU rather than replacing it
At launch, the only protocol-endorsed route to acquire $TRUST is through the $DOVU/$TRUST liquidity pair, with no direct fiat, HBAR, or alternative market route. $DOVU becomes the primary protocol gateway into the Authority Trail economy. Its utility is not diluted by the second token; it is extended by it.
Fuel and licence
$DOVU: the fuel
The fuel that runs the engine: it powers every workflow, every process, every audit event on DOVU OS.
$TRUST: the licence
The licence that proves the driver was authorised to operate the vehicle at that moment, independent of how much fuel was used.
You need both. And you need them priced separately, because the cost of running an engine and the cost of maintaining a licence serve entirely different economic purposes.
What $TRUST is not
- Not token proliferation for its own sake.
- Not a mechanism to inflate total token supply across the ecosystem.
- Not primarily a governance token, a yield token, or a speculative instrument.
$TRUST has one job: to meter consequential writes to public authority-state on Hedera. It does that job in a way that $DOVU cannot, should not, and was never designed to.
$DOVU powers what happens. $TRUST proves who was allowed to make it happen.
These are different questions. They require different economic layers. And the design that links them, with $DOVU as the mandatory gateway to $TRUST, means the two tokens strengthen each other rather than compete.
About DOVU
DOVU builds infrastructure for verifiable trust on Hedera. DOVU OS enables organisations to model, execute, and audit trusted workflows across ecological assets, supply chains, issued assets, and authority-sensitive processes. Authority Trail extends this infrastructure by recording who had the right to act, in what role, and at what point in time.
Learn more about Authority Trail at authority.dovu.ai