Qlyphs How it works
The chain records, the indexer interprets, witnesses attest and your wallet decides. Four roles, kept apart on purpose.
Who does what in Qlyphs, and why are those jobs kept apart?
Qlyphs turns signed Quantus transactions into an asset system: fungible tokens, unique Quarks and markets priced in QTC. Its core is QLYP, a deterministic protocol. Its operations are recorded on Quantus, and anyone running the same rules over the same history gets the same balances.
The idea fits in one sentence: ownership should be reconstructible from chain history, and a purchase should never depend on a server deciding to deliver after it has your money.
Four roles, one transaction
- 01 / 05
You sign an exact call
Your wallet builds the Quantus transaction itself, shows you the asset, amount, destination and cost, and signs it on your device. An application can propose a transaction; it cannot change what the wallet authorizes.
- 02 / 05
Quantus orders it
The chain authenticates the signature, puts the transaction in a block and executes its native QTC transfers. It records the QLYP message, but it does not decide whether that message is a valid token operation.
- 03 / 05
The indexer gives it meaning
An indexer reads finalized blocks in order and applies the published QLYP rules. Balances, ownership and reservations are the result. It never holds your recovery phrase or a key that can spend your QTC.
- 04 / 05
Two witnesses agree
Two independent replay engines, one in TypeScript and one in Python, compute the same finalized state from the chain and each sign it with ML-DSA-87. Their agreement is evidence, not a mathematical proof that both are honest.
- 05 / 05
Your wallet checks before paying
For a protected purchase, the wallet verifies both signatures against keys compiled into it, checks the offer it is about to pay for, and only then signs. Missing evidence disables the purchase instead of falling back to trust.
What each role is allowed to claim
Quantus: order and execute
The chain authenticates your signature, orders transactions and runs native QTC transfers. A successful Quantus transaction does not, on its own, prove a QLYP operation was valid.
The rules: accept or reject
QLYP checks the message format, your sequence, your authorization, the amounts and the prior state. A token effect exists only when the whole rule set accepts the operation.
The indexer: replay and serve
It replays finalized blocks and serves the resulting views. It holds neither your recovery phrase nor any key that can spend your QTC.
The witnesses: attest
Two independent replay engines sign the state they computed. Their signatures matter only because your wallet checks them against keys it was built with.
The server is not the settlement authority
A valid purchase delivers tokens through the protocol's own transition rules. A server callback, a database row or a manually approved balance is never the source of ownership.