I don't know anything and I can prove it!
-Zero Knowledge Corporation
United StatesJoined March 2026
About
ZeroPoint: Sovereign Provenance & Truth Resolver
1. MintMark (Ⓜ)
- A MintMark is a cryptographic seal over a claim.
- Each MintMark binds:
- claim_hash: SHA-256 of the canonical claim object
- topic_id: the sovereign topic/namespace this claim belongs to
- claim_id: deterministic identifier within that topic
- issuer_key: the public key of the sealing authority
- issued_at: ISO8601 timestamp
- The MintMark is verifiable offline: anyone can:
- recompute claim_hash from the claim
- verify the signature against issuer_key
- confirm topic_id + claim_id consistency
2. HHTPS (Resolver of Sealed Truth)
- HHTPS is not a website, chain, or redirect.
- It is a universal resolver for MintMarks.
- Input: a MintMark (Ⓜ) or its encoded payload.
- Output: the canonical, verified claim in the correct topic.
- Resolution flow:
- Parse MintMark → extract topic_id + claim_id + claim_hash
- Look up topic(topic_id)
- Resolve claim(claim_id) within that topic
- Verify:
- claim_hash matches the stored claim
- MintMark signature is valid
- topic policy accepts this issuer_key
- Return: verified claim + verification status
3. Topics (Sovereign Namespaces of Truth)
- A topic is a sovereign stream of claims under a shared context.
- Examples:
- topic:verified_coins
- topic:verified_identities
- topic:verified_engagements
- topic:verified_ads
- Each topic defines:
- schema: what a claim must contain
- policy: who can issue MintMarks here (issuer keys, rules)
- continuity: how claims evolve (supersede, revoke, append)
- Topics are independent but share the same MintMark + HHTPS substrate.
4. Claims
- A claim is a structured, canonical JSON object.
- Examples:
- In verified_coins:
- { incident_id, seed_anchor, trail_merkle_root, zip_hash, ownership_proof_hash }
- In verified_identities:
- { subject_id, proof_of_control, attestations, revocation_state }
- Claims are:
- deterministic (canonical JSON)
- hashable (claim_hash)
- sealed (MintMark)
- resolvable (HHTPS)
5. Bitcoin Provenance & Ownership (Your Current Live Topic)
- Topic: verified_coins
- Claim structure (simplified):
- incident_id
- seed_anchor (e.g., bc1…)
- trail_merkle_root
- artifact_hashes (json/csv/pdf/zip)
- ownership_proof_hash (sign-message/PSBT proof)
- chain_of_custody_reference
- The provenance_proof.json + exhibits (A–F) are the claim body.
- The MintMark (Ⓜ) seals that claim.
- HHTPS resolves the MintMark to:
- the full provenance packet
- verification status
- all integrity anchors (hashes, Merkle, mint mark, ownership proof)
6. Sovereign Memory & Continuity
- The Knowledge Graph is your out-of-band, sovereign memory substrate.
- It tracks:
- topics
- claims
- relationships
- supersessions
- HHTPS + MintMark operate on the live, canonical layer.
- The Knowledge Graph preserves context across tools, threads, and time.