What Quant sells, and where QNT actually sits

Quant is selling an interoperability stack that looks and behaves like enterprise middleware first, crypto network second. The center of gravity is Overledger, a set of APIs and gateways that let customers connect blockchains and legacy systems without committing to one chain. Quant has been explicit that it monetizes this as a business: transaction fees, SaaS-style products, enterprise products, and IP licensing.

QNT is the access token layered onto that commercial product. In Quant’s own token sale documentation, QNT is framed as a utility token that “gives access” to the Overledger framework and connects the user to the Quant network, while explicitly not being a share and not granting participation rights in company meetings, per the token-sale paper.

The clearest operational linkage between Overledger usage and QNT, in currently accessible materials, is licensing. Quant’s Overledger 2.1.5 release notes state that accessing the live production platform requires an annual license fee of £100 payable in QNT per the 2.1.5 release notes.

Earlier network-economic documents (not presently available from the project’s original domains via standard retrieval, but available as third-party hosted PDFs) describe a broader model. In that model, QNT is used to validate Overledger transactions, pay consumption fees priced in fiat terms, and fund payment channels. It also describes QNT being locked for license periods and used as a priority mechanism for gateway operators in the community economic paper.

Supply and issuance constraints

QNT is tracked as an ERC-20 token on Ethereum, and Quant’s own documentation warned that Ethereum protocol behavior can impact QNT’s operation.

On current market data, trackers report Total Supply: 14,612,493 QNT and Max Supply: 14,612,493 QNT. They also report Circulating Supply: 14,544,176 QNT (with “Available Supply” shown as 14,612,493) in the market supply data.

The token sale-era business paper is clear on the intended issuance rule. QNT tokens would be created during the crowd sale period, supply would be limited to the number created during that period, and there would be no token creation, minting, or mining after the crowd sale. It also states that “token creation will be closed permanently” at the end of the token generation event.

One nuance matters for analysts. The same document describes a much higher maximum funding cap and token availability during the sale process than today’s tracked supply. It references a hard cap of 45.467 million QNT, with 31,000,000 tokens on sale and 14,467,000 tokens not for sale.

It also states two supply-reduction levers: QNT transfers were planned to be restricted for 2 months after the end of the crowd sale, and “all unredeemed tokens will be burned.”

Allocations (as documented at the TGE stage)

Two structural caveats. First, the business paper says allocation is proportional to QNT generated if the maximum cap is not reached.

Second, today’s tracked supply and circulation (around 14.6m total, 14.54m circulating on major trackers) is far below the token sale-era maximum cap framing. That gap is consistent with the same document’s “unredeemed tokens will be burned” rule, but the accessible primary document does not, on its own, provide a single reconciled post-sale supply table.

How fees move: fiat pricing, QNT locking, and the treasury circuit

Quant’s economic design is built to hide crypto volatility from customers while still forcing QNT into the settlement path. The community-network economic paper states that developer licenses are purchased in QNT “equivalent to a fixed FIAT amount,” and that the license expires annually and must be renewed using only QNT.

It then makes the key token-velocity claim: QNT are locked for the entire duration of the license and are out of circulation. If the license is renewed, tokens remain locked. If not renewed, the QNT is put back into circulation “through the Treasury at market prices for other client use.”

For production access, Quant’s release notes show the licensing fee is implemented in product, not just in concept. Overledger 2.1.5 sets an annual production license fee of £100 payable in QNT, and states that customers must pay for an Overledger license before generating a Client ID in the production environment.

There is also a dated transition policy. Quant’s license-fee announcement states that existing customers who signed up before December 15, 2021 received an additional three months of free use after that date, meaning their license fee was not due until March 15, 2022 per the licence-fee notice.

Beyond licensing, the community-network document describes ongoing consumption fees. Payments for read and write calls are described as payable in QNT based on a fiat value, with the equivalent paid to the Quant Treasury in QNT.

It also introduces a second layer that matters for power and rent extraction: platform fees. For enterprise, it describes a “platform fee calculated as a percentage of the license fee in QNT,” with QNT obtained and managed through the Treasury by Quant Network “on behalf of the client at a given day’s rate.” It claims the “Treasury - Enterprise has been live with clients since April 2019.”

One more signal shows up in modern developer documentation. Overledger API examples include a gatewayFee object denominated in QNT units, even in sandbox workflows. That is not a full economic spec, but it is consistent with QNT being treated as the network fee unit inside the platform interface.

Governance and parameter control: the power map

QNT does not function like a governance token in any meaningful on-chain sense. Quant’s token sale documentation states that QNT “does not give any right to participate in the general meetings of the Company,” and more bluntly that acquiring QNT “shall not grant any right or influence over Quant Network’s organisation and governance.”

That single clause collapses a lot of decentralization narratives. If you hold QNT, you do not control pricing, onboarding, product roadmap, treasury policy, or fee routing by virtue of the token. You are structurally in the position of a customer or speculator around a company-run platform, not a voter in a protocol republic. For a governance-token comparison, see our review of Maker tokenomics.

The business paper also reserves broad discretion for Quant to change terms. It states Quant Network “may change this T&C at any time at its sole discretion,” and that continued use of the platform or continued holding of QNT means the user accepts modified terms. That is not blockchain governance. That is corporate governance imposed onto token holders.

Now connect that to the product reality. The Overledger 2.1.5 release notes show Quant implemented an annual license fee in the UI flow and required it for production access. That is a parameter flip with direct token-demand consequences, executed as a normal software release, not as a token-holder vote. For an on-chain governance contrast, see our review of Tezos tokenomics.

The community-network economic paper is even more explicit about centralized coordination in the “Treasury” role. It describes a treasury that handles QNT payments flowing from multi-chain apps and users to Overledger gateways, and describes Quant managing QNT through the Treasury “on behalf of the client” for some fee types. This is operationally convenient. It is also a concentration point. Whoever controls treasury policy controls the throttle on QNT’s functional sink and source.

Even in the gateway layer, the incentives are mediated by rules that Quant sets. The same document describes gateway operators earning fees for function requests processed before a timeout, and introduces a “lock up (stake) an increasing amount of QNT” mechanism that affects priority. Under normal conditions, the locked amount is returned at the end of the lockup period, and only deviation from protocol risks forfeiture. That sounds like crypto-native governance until you read the last line: it states that forfeiture “will not occur” if the operator runs the gateway software provided by Quant. That is a software and policy choke point, not credibly neutral protocol enforcement.

Demand drivers, and what you still cannot model cleanly

The bull case for QNT token demand is straightforward in mechanism terms. License fees and usage fees are described as fiat-denominated, converted into QNT, and locked in ways that reduce circulating availability. Gateway operators also have an incentive to lock more QNT to gain priority and earn more fees.

The problem is observability and enforceability. The documents that describe the lock-and-treasury model in detail are not currently retrievable from the project’s original domains via standard access methods, and the current official materials that are easily accessible (release notes and modern developer documentation) do not provide a public ledger-style dashboard of licenses sold, QNT locked by term, or treasury inflows and outflows. That weakens modelability and lowers confidence in parameter stability.

Market supply data hints at a near-fully circulating asset from a market-float perspective. It reports 14,544,176 circulating out of 14,612,493 total. That leaves limited room for a “future unlock overhang” narrative. It also means that any meaningful lockup effect, if it exists, has to show up as time-bound escrow behavior or operational wallets, not as a large scheduled emissions or cliff unlock schedule.

If you are trying to value QNT as an institutional adoption derivative, you are left with indirect indicators: product release cadence, the existence and pricing of the license fee in production, and whatever on-chain movements can be convincingly attributed to treasury and escrow contracts. The public docs, as accessible today, do not give you a clean, auditable bridge between Overledger customer growth and on-chain QNT sinks.

Risk analysis (ranked) + dominant risk

Quant’s token design is clean on one axis. No emissions after the sale. No staking yield promised at the base layer. Supply is capped on major trackers at 14,612,493.

It is weak on the axis that matters most to a governance power analyst. Control over the economic parameters that drive demand is concentrated in a company that explicitly denies token holders governance rights, and that can revise terms at its discretion.

Dominant risk: governance centralization creates parameter instability

The core risk is not “centralization” as a vibe. It is the specific and documented power asymmetry.

Quant’s own token sale documentation states that holding QNT gives you no right or influence over the organization and governance of Quant Network, no right to participate in company meetings, and no claim to dividends or interest.

That matters because QNT’s demand thesis depends on parameters that are not credibly locked by code:

License pricing is a product decision. Quant introduced an annual license fee for production Overledger access, implemented it via a UI flow, and denominated it in QNT at £100. That is a unilateral move with direct impact on QNT’s structural bid. Nothing in the accessible primary docs indicates token holders can veto increases, decreases, waivers, bundling, or migration of fees to fiat-only rails.

Treasury mediation is a control point. The community-network economic paper describes QNT conversion and management “through the Treasury,” and QNT being put back into circulation through the treasury when licenses are not renewed. That is effectively a discretionary market-operations interface. The more the economic model relies on treasury behavior, the more QNT holders are underwriting treasury execution risk and policy risk rather than purely protocol risk.

Gateway incentives are software-shaped. The same paper describes gateway priority as a function of locked QNT and states that deviations leading to forfeiture “will not occur” if operators run Quant’s gateway software. That implies rule enforcement is coupled to the vendor’s implementation choices. This is the opposite of a neutral, adversarially hardened validator set.

Who bears this risk. Mostly QNT holders, because the token price is the residual claimant on a business model they do not govern. Also enterprise customers, because fee predictability depends on a vendor’s pricing and compliance posture.

How it shows up. Not as a chain halt. As a gradual repricing of the token when the market updates its beliefs about whether QNT will remain the mandatory settlement asset for Overledger access and usage.

Measurable indicators. Release notes that change fee schedules. Changes in accepted payment methods for licenses. Shifts in documentation that move from “QNT-only” language to “QNT optional” language. Evidence of treasury behavior changing lockup duration or settlement flows.

If you want one sentence: QNT is economically coupled to Quant’s commercial policy choices, and the token explicitly grants no governance power to constrain those choices.

Top 3 risks

  1. Parameter drift risk (pricing and settlement rules): Trigger: Quant changes license pricing, fee composition, or settlement rails in a way that reduces mandatory QNT usage. Mechanism: demand for QNT is policy-driven because production access requires licenses payable in QNT today and other fees are described as treasury-mediated conversions. Who bears it: QNT holders first, then ecosystem participants building on usage assumptions. Measurable indicators: new release notes introducing, removing, or repricing QNT-denominated license fees; documentation updates to payment methods.

  2. Treasury execution and opacity risk: Trigger: treasury operations become a liquidity bottleneck or behave in ways the market interprets as discretionary supply management. Mechanism: the model describes QNT flowing into and out of circulation via the treasury when licenses renew or expire, and describes Quant managing QNT “on behalf of the client.” Who bears it: QNT holders through price impact, and customers through service continuity if treasury processes fail. Measurable indicators: observable on-chain movements linked to treasury/escrow contracts, widening spreads during demand spikes, or documentation changes to lock/unlock rules.

  3. Platform dependency risk (Ethereum and vendor stack): Trigger: material issues in Ethereum or changes in how Quant integrates signing, custody, or gateway software. Mechanism: QNT is based on Ethereum per Quant’s own documentation, and Quant’s product stack relies on vendor-operated software layers for access and transaction workflows. Who bears it: customers and QNT holders through outages, degraded trust, or migration friction. Measurable indicators: statements of chain migration plans, major changes in supported signing/custody flows, or prolonged disruptions in production access.

If you are building around QNT or underwriting it, treat it like a tokenized access right to a company-governed platform, not like an autonomous protocol asset. That framing will keep you honest about where power sits.

For teams doing token economy design work, QNT is a useful case study in how to engineer demand with licensing and lockups, and how governance centralization can dominate the risk surface. If you need tokenomics consulting on similar “enterprise-first” models, you want your docs and telemetry to be audit-friendly from day one.

If you’re building internal benchmarks, our research reports can help you pressure-test how demand sinks and governance power map to price narratives.

If you’re formalizing your framework, start with the core design components so assumptions about fees, lockups, and control points stay explicit.



This article is part of our Tokenomics Deep Dive series.