Quant has no chain and no consensus of its own. Overledger takes one request, turns it into a native transaction on each network it touches, and waits for every one of them to settle.
Click a step on the right, or use the arrow keys, to jump to it. Move your mouse to shift the view.
QNT is an ERC-20 token, so Ethereum is where Quant's own token lives. Each column is one real block, newest on the right. Use the left and right arrow keys to read each block's count.
| Block | Transactions | Sealed |
|---|
Use the arrow keys to read each network's block interval and time to finality. The axis is logarithmic.
| Network | Time between blocks | Basis | Time to finality |
|---|
Overledger is Quant's platform for applications that span more than one blockchain. It is an API: one set of credentials, one data model for reads and writes, and a gateway that translates between that model and each connected network's native format. It is not a blockchain. It doesn't hold your assets, mine, validate or produce blocks. Every transaction it helps you make lands on somebody else's ledger and is settled by that ledger's own rules.
Consensus is how a network of strangers agrees on one history. Overledger doesn't need that agreement because it doesn't keep a history of its own: the record of what happened is whatever Ethereum, the XRP Ledger, Bitcoin or Hedera say happened. That's the point of the design, and also its limit. Overledger can only be as fast, as final and as reliable as the slowest network in a given request, and it inherits every network's fees and failure modes.
Most Overledger operations run in two API calls. In prepare, the app describes what it wants in Overledger's standard format and gets back a request ID and the network-specific transaction to sign. The app signs that locally, with its own key for that network. In execute, it sends the signature back and Overledger submits the transaction to the network, then lets the app read its status. Because signing happens on the app's side, Overledger never holds private keys.
A request that touches four networks is really four separate transactions, each confirmed by a different set of validators or miners with no knowledge of the others. Overledger can sequence them, wait on them and report on them as a unit, but no network can be told to undo its part because another leg failed. Anything stronger, like a swap that either completes on both sides or on neither, has to be built on top with escrows, hash locks or a settlement layer. Quant's newer Fusion product, which Quant describes as a rollup anchored to several base chains at once, is its answer to that problem; it's out of scope for this page.
QNT is an ordinary ERC-20 token on Ethereum, contract 0x4a22…4675. Its contract reports 45,467,000 tokens minted, of which about 9.55 million sit in the contract's own address, unspendable, after Quant burned the unsold tokens from its 2018 sale; most market data quotes a supply of about 14.6 million. QNT isn't gas for anything on this page. Access to Overledger is licensed, licences are paid in QNT, and Quant's treasury converts fiat payments into QNT and locks it for the licence term, which Quant has described as twelve months. Fees on the networks themselves are paid in each network's own asset. Quant has said QNT also has roles on Fusion, but that isn't something a public node can verify.
In 2023 Quant was on the vendor team for Project Rosalind, an experiment by the BIS Innovation Hub London Centre and the Bank of England into an API layer for a retail central bank digital currency. In 2023 and 2024 it was one of the technology partners in UK Finance's Regulated Liability Network experimentation phase, alongside R3 and others, providing orchestration and API tooling. In June 2026 Quant announced that Fusion had gone live on mainnet. Those are the facts this page is confident of; anything about future adoption is a forecast, not a fact.
There is no public Overledger feed, so live mode leaves the gateway dark and connects straight to the four public networks it bridges. Ethereum comes over a public JSON-RPC WebSocket (new block headers, each block's transaction count, and every QNT transfer in it). The XRP Ledger comes from a public cluster's ledger stream. Bitcoin comes from mempool.space's block feed. Hedera is polled from the public mirror node every few seconds. Every block number, transaction count, timestamp and QNT transfer is real, and the arc around each network fills with the real time since its last block. What isn't real is any connection between them: nothing on the stage is an Overledger request.
The four miniature networks are sketches, not models: a dozen dots stand in for hundreds of thousands of Ethereum validators, and the way each one "closes" a block only hints at its real mechanism, which has its own page on this site. Step-by-step mode skips ahead to Bitcoin's next block instead of waiting ten minutes, and finality times are the usual rules of thumb rather than guarantees. The API flow follows Quant's published Overledger developer documentation; read that for the real request and response formats.