QuiNVarium
QuiNVarium
Overview Signing Keys Applications Status
Wallet · preview

Quinvarium Wallet: two signatures for every standard QNV transfer.

Quinvarium Wallet is designed to require both signatures for every standard QNV spend — Schnorr BIP340 and ML‑DSA‑44 over one QNV_SIGHASH_V1 semantic message — while keeping signing keys under local user control. The semantic AND rule is frozen; public wallet software is not released. The preview also maps a future encrypted-message attachment concept; it is not implemented or released.

Wallet preview — software not released V2 semantic rule frozen · Mainnet not live Status as of 23 Aug 2026
The front screen carries demo values, labelled DEMO_DATA_ONLY and Example only. The rear screen is a future encrypted-message attachment concept; it does not create, encrypt, store or broadcast a message.
Signing

Two signatures, and neither is a backup for the other

Every standard QNV spend must satisfy both signature families over the same semantic commitment. The wallet direction makes this AND rule automatic rather than optional. Final sighash bytes, witness encoding and resource limits remain open.

Schnorr BIP340
the required classical signature family
SEMANTIC AND · FROZEN
ML‑DSA‑44
the required post‑quantum signature family
SEMANTIC AND · FROZEN
QNV_SIGHASH_V1
the single semantic entity both signatures cover
SEMANTIC ENTITY · FROZEN / FINAL BYTES · OPEN
Rejected
a standard spend with either signature absent or invalid
PRIVATE ENGINEERING EVIDENCE · NOT PUBLIC

FROZEN describes the approved semantic rule; it does not mean that the wallet or public network is live, and it is not a claim that keys cannot be compromised.

What the wallet holds

Keys on the device; messages only as a future concept

  • Local generation and custody of signing keys and backups is the approved product direction. Production storage and recovery flows are not released.
  • A future encrypted message attachment is a research concept only. Its encoding, permission model and transaction treatment require a separate approved specification; it is not implemented or released. Never use a transaction message for passwords, seed phrases, private keys or recovery codes.
  • QNV is the network's native coin, not a token issued on someone else's chain.
  • QTS‑20 is a future standard. The wallet does not hold tokens today because the standard does not exist yet.
Deliberately absent

What this page will not show you

  • No live balance and no real history. The interface reference above carries demo figures, labelled DEMO_DATA_ONLY on the screen itself. Nothing here has been read from a network, because there is none to read.
  • No price and no market figures. There is no market.
  • No measured public fees. No verified public network source exists, so publishing a current fee would be misleading.
  • No public addresses or transactions. Private engineering evidence is not presented as public network activity.
Applications · release-gated

One approved direction and two exploratory surfaces. None is available.

Mobile
Approved Flutter direction for iOS and Android with local key storage. No public build is released.

APPROVED DIRECTION · NOT RELEASED

Desktop
Exploratory interface concept for Windows, macOS and Linux. It is not an approved release target.

EXPLORATORY CONCEPT · NO RELEASE COMMITMENT

Browser extension
Exploratory extension concept only. It is not an approved roadmap commitment.

EXPLORATORY CONCEPT · NO RELEASE COMMITMENT

Verifiability

What can be checked today

One place for the state of every claim on this page. Each line is either a published artefact or an absence.

Wallet product direction
APPROVED · PRODUCTION FLOWS NOT RELEASED
Wallet source code
NO PUBLIC RELEASE
Public builds
NOT RELEASED
Build signatures and checksums
PENDING FIRST RELEASE
Mainnet
NOT LIVE
Independent security review
NOT PUBLISHED
Hybrid signature rule
SEMANTIC AND · FROZEN / FINAL BYTES · OPEN
Last status update
23 AUG 2026
Quinvarium ecosystem

Continue on the dedicated surface

Community

Official public channels

Only confirmed public account links are shown. A canonical public source release is not available yet.

The GitHub link identifies the public profile; it is not a claim that the network source has been released.