QAISS is building a neutral quantum-AI coordination layer. Follow the public roadmap and verify every claim.

Ecosystem · proposal

A network that proves its results.

QAISS verification is objective: a simulator result reproduces bit-for-bit or it doesn’t, and hardware results can be compared statistically. On top of that we are building an open proof-of-reproduction network. The off-chain parts come first. Anything that touches the token waits for legal review.

Off-chain parts in developmentToken utility: proposed, not active

The flywheel

Verified work creates demand for more verified work.

Demand should come from use, not speculation. Here, it comes from people who need results checked and people who own the hardware to check them.

The token's proposed role is a security bond for reproducers, never a toll on the free tools. Full reasoning and sources: docs/TOKEN-UTILITY-STRATEGY.md.

Proposed · nothing active

Where the token may fit

Each item needs legal review, a published policy and the owner’s approval before anything moves. None pays yield or a share of revenue.

SOULBOUND CREDENTIALS

Non-transferable badges such as Verified Reproducer, GPU Operator, QPU Operator, Educator and Challenge solver. Reputation is earned, never bought.

Token: None to earn. Bonded reproducers may get higher bounty limits (proposed).

ProposedGate: Separate badge mint (Bubblegum V2 or SAS); counsel review
REPRODUCER BONDS

Reproducers lock QAISS as a security deposit. A provably false simulator passport forfeits part of it after a challenge window. The bond pays no yield.

Token: Core proposed utility: a work-token bond.

ProposedGate: Counsel review (custody, ESMA); published policy; later an audited program
GRANTS TREASURY

Public multisig that funds adapters, GPU parity runs, curricula and translations under a published grant policy.

Token: Proposed: grants in QAISS or USDC.

ProposedGate: Wallets published; Squads multisig; grant policy; counsel
TECHNICAL GOVERNANCE

Votes on passport spec versions, the benchmark protocol and certified backends. Never on company or treasury investments.

Token: Proposed: token-weighted signalling, executed by the multisig.

ProposedGate: Counsel review; limited to technical scope
PAID SERVICES (LATER)

Certified benchmark reports, priority reproduction and private registries for institutions, priced in fiat or USDC.

Token: Proposed: a published share could fund bounties and grants. No buyback without counsel.

ProposedGate: Revenue; legal entity; counsel
SHAREABLE ACTIONS (BLINKS)

“Fund this bounty” and “verify this passport” links that open in the visitor’s own wallet. This website never signs anything.

Token: Proposed: funding from the user’s own wallet.

ProposedGate: Separate API host; counsel

Not investment advice. The QAISS token is not described as equity, a share of revenue or a profit instrument. No price, return or listing is promised. No utility is active until it is listed as such on the token page.

Principles

Rules we hold ourselves to

01

Product first

The Lab, the verifier and the docs stay free and need no wallet.

02

Token only where it secures or coordinates

The token is used for bonds, reputation and technical governance. Where SOL or USDC is enough, no token is forced.

03

No yield, no revenue share, no price talk

This follows MiCA marketing rules and ESMA guidance on what makes a token a financial instrument.

04

Transparency before utility

Distribution, treasury wallets and the decision record come first.

05

The website never signs

Any transaction is signed in the visitor’s own wallet or CLI, never by this site.

Plan

Phases and gates

A phase starts only when the gate before it is met. Gates are evidence, not dates.

  1. PHASE 0

    Foundations

    • Legal entity and counsel engaged
    • Decision record (with counsel)
    • Treasury wallets and multisig published
    • Ecosystem and transparency pages

    Gate: Wallets published; counsel review under way

  2. PHASE 1

    Proof network, off-chain

    • Passport registry (anchoring CLI and page)
    • Quantum challenges with proofs
    • Bounty board with automatic verification
    • Quantum-readiness centre

    Gate: 10 external verified submissions; first GPU passport; counsel sign-off on bounty terms

  3. PHASE 2

    Light on-chain

    • Soulbound credentials on a separate mint
    • Reproducer bonds held in a multisig under a published policy
    • Blinks API
    • Technical-governance signalling

    Gate: Bond policy reviewed by counsel; 20 bonded reproducers

  4. PHASE 3

    Trustless

    • Audited Anchor program: escrow, bonds, challenge window
    • Verified build; program made immutable after audit

    Gate: Security audit passed

  5. PHASE 4

    Revenue

    • Certified reports and private registries for institutions
    • Published allocation policy

    Gate: Paying institutions; counsel

Release notes

Engineering updates,
not hype.

Research drafts, releases, and every change to a public claim. No price talk.

Subscriptions open once the project publishes its privacy policy and mailing endpoint.