Tokenomics

What you’ll get here

a clear map of how value moves through Smart Engines — how usage turns into fees, how fees turn into burns, node-runner rewards and treasury, and why every payment is real HSUITE on one ledger.

Smart Engines works with several chains but keeps a deliberately single-ledger economy. Usage is metered, settled and distributed as real HSUITE on the XRP Ledger (XRPL), not as internal credits or IOUs. That one design choice is what makes the whole economy auditable from one place.

This section explains the token, the value loop, and each mechanism that keeps it honest.

🧠 For Normies

“Tokenomics” just means the rules of the money. Who pays, who earns, what gets created, what gets destroyed, and how you can verify all of it. Smart Engines’ answer: everything settles to one token (HSUITE) on one chain (XRPL), so the books are easy to check.

Page index

HSUITE tokenThe token itself: issuer, role, utility, and the Hedera → XRPL canonical pivot.

Value flowsThe end-to-end money path: usage → metering → fees → token → node runners.

Staking & node-runnersNode-runner deposits, the funding model, and how runner rewards are split.

DAO governanceHow rule and parameter changes are proposed, voted, and enforced via HCS.

Universal Token BridgeCross-chain token movement: the HSUITE bridge, lock-wallet bridges, what is built and what is not enabled yet.

Settlement & migrationWhat you can pay with, how a subscription payment is settled 40/40/20, and the one-time HSUITE migration.

---

The HSUITE value loop

Everything below is a different view of one loop: people use the platform, that usage is priced and settled into real HSUITE, and the HSUITE is split between a burn, the node runners who did the work, and the protocol treasury.

flowchart TD
    Use["Usage<br/>(API calls, signatures, chain ops)"] --> Meter["Metering<br/>(per-request usage count)"]
    Meter --> Pay["Payment<br/>(HSUITE on XRPL; other assets built, not yet enabled)"]
    Pay --> Settle["Subscription settle-in<br/>deposit account on XRPL"]
    Settle --> Split{"Fee distribution<br/>40 / 40 / 20"}
    Split -- "40%" --> Burn["Burn<br/>(removed from supply)"]
    Split -- "40%" --> Runners["Runner pool<br/>validators / hosts / gateways"]
    Split -- "20%" --> Treasury["Protocol treasury<br/>(validator multisig account on XRPL)"]
    Burn --> Deflation["Deflation<br/>supply shrinks"]
    Runners --> Stake["Node runners stake & run nodes"]
    Stake --> Use
    Gov["Published rule<br/>(amended through DAO governance on HCS)"] -.-> Split

Read the loop as a sentence: usage is metered, paid in real HSUITE on XRPL (other payment assets are built but not yet enabled), then split 40% burned / 40% to the node-runner pool / 20% to the treasury. The split is a field of the deposit account’s published rule, so it changes only when that rule is amended.

---

Why one ledger

Smart Engines works with several chains: today Hedera and XRPL are live, and more chains come next. The value layer stays on a single chain. That gives three properties that multi-chain token models cannot easily offer:

Auditable supply

Supply is the issuer’s outstanding obligations: the sum of every holder’s trust-line balance, which XRPL reports for the one issuer account.

Atomic, cheap burns

A burn is an XRPL payment back to the issuer, which removes the tokens from supply. It is one atomic transaction, paid for with a small XRP network fee. No cross-chain coordination.

Real settlement

A subscription payment is real HSUITE on XRPL, settled out of an on-chain deposit account — not credited internally. Paying in other assets is built but not yet enabled.

🧠 For Normies

Imagine a company that operates in ten countries but keeps one bank account in one currency. You only ever have to check one statement to know exactly how much money exists. That’s the single-ledger model.

The reasoning behind picking XRPL is its cheap atomic burns and open validator set.

---

Risk disclosures

Note

These disclosures are informational. They do not constitute a prospectus, an offer, or investment advice.

Nature of the token

HSUITE is a utility token whose function is to access and pay for services on the Smart Engines network — metering, subscriptions, deployments, and on-chain operations. It is not a security, a financial instrument, or a deposit.

Rights and obligations

Holding HSUITE confers only the right to consume Smart Engines network services and, where applicable, to participate in on-chain governance. It confers no claim to profit, dividend, revenue share, interest, equity, ownership, or repayment, and no claim against any issuer or third party. HSUITE is freely transferable on the XRP Ledger subject to network rules; certain related entitlements (e.g. subscription NFTs) are non-transferable by design.

Risk warnings

Caution

• You may lose the entire value of your holding. Crypto-asset values can be highly volatile and may fall to zero.
• Crypto-assets may not be liquid. There is no guarantee of a market, or of the ability to sell at any given time or price.
• Largely unregulated; no safety net. Crypto-assets are, in many respects, not covered by investor-compensation or deposit-insurance schemes.
• No approval. This material has not been reviewed or approved by any regulator.
• Not advice. Nothing here is investment, legal, or tax advice. Past performance is not indicative of future results.
• Technology risk. Cryptography, validators, smart contracts, and bridges carry operational, security, and protocol risks.

Sustainability

Smart Engines uses energy-efficient consensus — the XRP Ledger (no proof-of-work mining; validator-agreement consensus) for value, and Hedera Hashgraph (aBFT) for governance/consensus messaging. There is no mining.

---

Next steps

What is Smart EnginesNew to the platform? Start here.

HSUITE tokenWant the token first? Read this.

Subscriptions & MembershipsBuilding on it? See this.

GlossaryTerm unfamiliar? The glossary has permanent plain-English definitions.