Roadmap ↗
QKITE LEDGER / ARCHITECTURE

Shared truth.
Private data.

Agree on what matters.
Keep what’s yours, yours.

The QKite Ledger design connects organizations through one shared ledger — with private data, verifiable decisions, and trust built in.

Explore the use cases ▶ See how it works
Permissioned by design. Post-quantum by default.
THE QKITE LEDGER NETWORKILLUSTRATIVE VIEW
QKite LedgerONE SHARED LEDGER
Select a participant to see their view ↗
LETTER OF CREDIT #04812 Verified
Issuing bank’s view Private details accessible
Ledger architecture
What QKite Ledger is

A shared record everyone trusts. Data only the right parties see.

Most business networks force a choice: put data on a shared ledger and expose it, or keep it private and lose a common source of truth. qkite keeps both. Every participant agrees on one ordered history, while each piece of business data stays inside the circle of organizations it belongs to.

01 / Ledger

One globally ordered ledger

Every organization sees the same sequence of events and can replay it from the first block to verify the current state independently.

02 / Privacy

Private collections

Each collection has a public, declared list of member organizations. Only their nodes receive, process and store its data.

03 / Policy

Attestation policies

Every business action states which organizations must vouch for its result, written as composable OutOf, And and Or rules.

04 / Validation

Validators verify, never peek

Validators check that the required organizations signed the same result under the exact committed policy. The validator role does not require private payloads.

05 / Crypto

Post-quantum by default

Signatures use ML-DSA and key establishment uses ML-KEM, both NIST standards, to support records designed for long-term verification.

06 / Finality

Byzantine fault tolerant

A block is final once a quorum of validators signs it. The network keeps working when some validators fail or misbehave.

How a private transaction flows

Execution stays inside the circle. Agreement is network-wide.

  1. Submit, encrypted

    An authorized organization signs a request. Its private payload is encrypted so only the member organizations of the target collection can open it.

  2. Member organizations execute

    Each member runs the same deterministic smart contract. The contract cannot read clocks, randomness, networks or files, so every honest member gets the same answer.

  3. Members attest the result

    Each member signs an attestation of the result. The contract's published policy decides whose attestations are required.

  4. Validators check the policy

    Validators confirm the attestations match and satisfy the committed policy, then order the transaction. No private payload is needed to do this.

  5. Commit

    The ledger records the verified transaction for everyone. The private state changes only at the organizations that belong to the collection.

Policies you can read

Trust rules are public, versioned and on the ledger.

Who must agree before something counts is not hidden in a vendor's database. Each smart contract declares an attestation policy for every function. The policy is committed to the ledger, and a change is a new version everyone can inspect.

  • And requires every listed party.
  • Or accepts any one of them.
  • OutOf requires a threshold, such as 3 of 5.
policy: release_payment v2
  • And
    • Issuing Bank
    • Or
      • Advising Bank
      • Confirming Bank
    • OutOf 2
      • Inspector A
      • Inspector B
      • Inspector C
Built on qkite

Five products for networks where trust is shared but data is not.

Each product is being developed as a set of smart contracts, policies and applications for one industry workflow, running on a qkite network your consortium operates.

Trade finance

TradeLedger

Letters of credit and invoice finance shared between banks, with double financing blocked across the network.

See TradeLedger → Credentials

CredVault

Degrees, licences and certificates that are checked through signed answers while personal records remain private.

See CredVault → Supply chain

ChainOfCustody

Traceability for every unit of medicine or critical goods, with commercial terms kept away from competitors.

See ChainOfCustody → Governance

ConsortiumVote

Elections and resolutions where anyone can verify the result with ballot choices private to voters and authorized auditors.

See ConsortiumVote → Procurement

BidSeal

Sealed tenders that open only when the evaluation committee agrees, with a permanent audit trail.

See BidSeal →
Engineering principles

Predictable where it matters.

Deterministic contractsWebAssembly smart contracts, with Go as the first SDK. Execution is bounded and identical on every node.
Organization identityEvery participant belongs to a named organization with explicit roles, bound to the network's genesis.
Verifiable historyAny node can rebuild its state from genesis and prove it matches what everyone else holds.
No custom cryptoOnly standardized, well-analyzed primitives. Nothing invented in-house.
ONE PROTOCOL. SHARED POSSIBILITIES.

Understand the workflow.
See the bigger picture.

Qkite is in active development with design partners.
Explore the protocol and the other applications built on it.

Explore all use cases