Skip to content

Quantum-protected flows

In DogeSoft (especially Pill and the indexer), “quantum” is a product label for verifiable, multi-step flows: attestation, commit–reveal timelines, and UI that makes you see what you are signing. It is not a claim that consumer hardware runs physical quantum processors—it is a formal security story on Doge L1 and in indexer data where the product ships it.

What you get

  • Commit–reveal patterns where the protocol separates intent and final reveal, so the chain and the indexer can agree on ordering and inclusion for those flows.
  • Opt-in protection funnels (where built) for inscriptions or UTXOs you want to treat with stricter ceremony than a plain send.
  • Visible health in the Explorer (e.g. PQC- or attestation-related KPIs) when the deployment has those ingest paths enabled—a product and infrastructure choice, not a vibe check.

What is not in public docs

  • No private keys, HSM playbooks, or production API tokens.
  • No one-line SQL to “fix” attestation—operators use internal runbooks.

Normative bytes for inscriptions: Inscription standard v1. This page is the framing for the Q-word in our stack.