The complete, public documentation of the Internet Identity Card — current release v10.0, with the superseded v9.0 and v8.4.1 editions preserved below. Every file is SHA-256 fingerprinted and timestamped on the Bitcoin and Ethereum blockchains.
The official documents below — User Guide, Technical Specification, Engineering Specification, and Threat Model — are freely available for review, audit, and reference. Their integrity is anchored on the Bitcoin and Ethereum blockchains and on OpenTimestamps. The underlying architecture is disclosed in six open defensive publications on Technical Disclosure Commons (CC BY 4.0).
The generator application and the IIC Wallet (both distributed inside the Complete Package), however, are not publicly downloadable. Due to the critical and sensitive nature of identity infrastructure, access to the generator and the Wallet is granted through a controlled onboarding process intended to support security, compliance, and operational alignment.
For demo requests or partnership inquiries, please contact us at demo@internetidentitycard.com.
v10.0 focuses on the protection of the issuer’s local vault. The vault encryption key is never written to storage: it is wrapped in two independent Argon2id envelopes — one derived from the memorable word, one from a recovery phrase issued once at setup — and exists in memory only for the duration of a session.
The hybrid signature suite and the exported card format are carried forward from v9.0; cards exported by v9.0 are unaffected. The Technical Specification and the Engineering Specification set out the complete change record for this release.
Creating, opening, sharing and signing. Rewritten for v10.0: the vault now asks for your memorable word each time it opens, and a recovery phrase is issued once at setup. Both follow from the vault key protection introduced in this release.
Architecture, cryptography and verification flows. New in v10.0: dual-envelope vault key protection with per-envelope KDF labelling, the corrected signature chain with a persistent counter and truncation anchor, and the receipt status field that distinguishes a classical receipt from a hybrid one. The hybrid ECDSA P-256 + ML-DSA-65 suite and the exported card format are unchanged from v9.0.
Provenance, implementation and standards. Includes a section on the verification method used for this release: why a correction is treated as complete only once its journey has been executed end to end from a file:// URL with the network disabled.
Assets, adversaries, STRIDE analysis and residual risks. This edition adds an asset the v9.0 model did not name — the issuer’s local vault at rest — and the adversary that reaches it. Two STRIDE dispositions are marked as corrected: they were stated more favourably than the implementation supported.
Installing, using and managing the IIC Wallet. The Wallet software is unchanged at v1.0 and is unaffected by the v10.0 corrections. Revision 5 corrects three cross-references: the companion guide version, the list of defensive publications, and the description of where the Wallet is distributed.
A single archive containing the IIC generator v10.0 (~537 KB), the four official v10.0 documents, the Wallet User Guide v1.0 r5, the change specification, the pre-release audit, the manifest tool, and a SHA256SUMS checksum file. This package does not contain the Wallet application itself, which ships in the access-controlled Complete Package. Because it includes the generator, it is provided through the controlled onboarding process described above.
🔒 Request access — demo@internetidentitycard.comSHA256SUMS, which lists every file in the package. It is not the digest of any archive: a ZIP embeds timestamps and compression choices that differ between runs, so its digest cannot be reproduced and proves nothing about the contents. Verify with shasum -c SHA256SUMS, then compare the result with the digest above. Anchored on Bitcoin at block 961351 and on Ethereum at block 25701188 on 7 August 2026. The value written in the Bitcoin OP_RETURN is the OriginStamp Merkle root of that batch; the package digest is a leaf beneath it, and the certificate supplies the path.Released 3 July 2026, superseded by v10.0. v9.0 introduced hybrid post-quantum signing — ECDSA P-256 combined with ML-DSA-65 (FIPS 204) — an embedded offline verification engine in every exported card, and a deterministic modular build. Those mechanisms are carried forward unchanged into v10.0, which refines the implementation rather than replacing the architecture. These editions remain published and fully verifiable: their blockchain timestamp proofs are permanent.
“PQC-ready” denotes FIPS 204 algorithmic conformance in code; it is not a FIPS 140 CMVP validation or an ANSSI qualification.
Step-by-step instructions to create your first card, choose between Quick and Secure modes, share your identity safely, understand SHA-256 page integrity, and answer common questions about Memorable Words, Card Passphrases, and recovery. Updated for v9.0.
Architecture, cryptography and verification flows — including the hybrid post-quantum signature suite introduced in v9.0: ECDSA P-256 combined with ML-DSA-65 (FIPS 204), crypto-agile suite registry, hybrid receipts v3.0, deterministic modular build, and the embedded offline verification engine.
Provenance, engineering innovations and standards compliance: single-file zero-dependency architecture, offline self-verification, hybrid post-quantum signing, multi-zone canonical neutralization, and the complete prior-art and registration record since 2013.
Security analysis, trust assumptions and residual risks — with the quantum adversary now explicitly addressed: harvest-now/decrypt-later and harvest-now/forge-later scenarios, STRIDE analysis of the hybrid posture, and a candid statement of what remains out of scope.
How to install and use the IIC Wallet — the optional offline PWA that collects and organizes your cards. Unchanged since v8.4.1: the v1.0 edition and its blockchain anchor of 7 June 2026 remain current.
The Complete Package is a single archive (14 files) containing the four official v9.0 documents (User Guide, Technical Specification, Engineering Specification, Threat Model), the Wallet User Guide v1.0, the IIC generator application v9.0 (~493 KB, hybrid post-quantum signing), the IIC Wallet PWA (offline card viewer, with manifest, service worker and Apache config), the README, and a SHA256SUMS checksum file. Because it includes the generator and the Wallet, this download is provided through the controlled onboarding process described above.
🔒 Request access — demo@internetidentitycard.comOnce granted, you can verify the authenticity of the archive against the published SHA-256 hash.
Superseded by v9.0 on 3 July 2026. These editions remain published and fully verifiable: their blockchain timestamp proofs are permanent.
Step-by-step instructions to create your first card, choose between Quick and Secure modes, share your identity safely, understand SHA-256 page integrity, and answer common questions about Memorable Words, Card Passphrases, and recovery.
Full cryptographic architecture and API reference. Covers AES-256-GCM, Argon2id RFC 9106 (96 MiB, t=4, p=4) for both cards and backups, ECDSA P-256, the dual-passphrase architecture, SHA-256 page integrity (Mode A), IIFE module isolation, threat model, and storage format.
System architecture, provenance timeline (2013–2026), defensive publications (TDCommons #10079, #10167 and #10394), standards compliance, and version history. Documents NIST, RFC, GDPR alignment and the registration timeline of Https Card — Internet Identity Card Ltd. Reference document for procurement, due diligence, and compliance reviews.
Realistic security analysis: trust assumptions, assets, adversary model (A1–A4), STRIDE analysis, ten concrete attack scenarios, and an honest account of residual risks and out-of-scope threats (compromised devices, generator authenticity, coercion, quantum). Companion to the Technical & Engineering Specifications.
Complete step-by-step guide to the IIC Wallet: installation (desktop and mobile, local use or PWA), first-launch consent dialog, three methods to add cards (drag-drop, file picker, auto-open .iic), opening cards, removing cards, the six-layer security model, troubleshooting common dialogs, and a full FAQ.
The Complete Package is a single archive containing the five official documents (User Guide, Wallet User Guide, Technical Specification, Engineering Specification, Threat Model), the IIC generator application (~338 KB), the IIC Wallet PWA (offline card viewer, ~31 KB, with manifest, service worker and Apache config), the README, and a SHA256SUMS checksum file. Because it includes the generator and the Wallet, this download is provided through the controlled onboarding process described above.
🔒 Request access — demo@internetidentitycard.comOnce granted, you can verify the authenticity of the archive against the published SHA-256 hash and ECDSA P-256 signature.
The IIC Wallet is an optional offline application that lets you collect and organize all your IIC cards in one place. It runs entirely in your browser, stores nothing on any server, and works without an internet connection. The Wallet never sees the unencrypted content of secured cards — each card retains its own cryptographic protections (Argon2id key derivation, AES-256-GCM encryption, SHA-256 page integrity, ECDSA P-256 signatures).
Distribution model: the Wallet is included in the IIC Complete Package — the same controlled-access archive that contains the generator. It is never hosted publicly. After receiving the package, you choose how to use it: locally on your desktop, or by hosting it on your own private server for mobile use.
.iic files.iic card opens it directly in the Wallet.Once you have received the IIC Complete Package, the Wallet is in the wallet/ folder. You can use it two ways:
wallet/iic-viewer.html in Chrome, Edge, Brave, Safari or Firefox..iic or .html cards into the Wallet, or use the file picker.wallet/ folder on any HTTPS server you control (local Apache, nginx, or a private cloud)..iic auto-open support.wallet/ folder on an HTTPS server you control..html or .iic files — this is an Apple OS-level restriction that applies to every web-based app. On iOS, the Wallet still works fully, but each card must be added manually via the file picker or drag-and-drop inside the Wallet. The other platforms (Android, macOS, Windows, Linux with Chromium browsers) support full auto-open.
The cryptographic constructions underlying the Internet Identity Card are disclosed as open prior art on Technical Disclosure Commons (operated by Elsevier), released under the Creative Commons Attribution 4.0 license with explicit patent waivers from the inventor. They are indexed by Google Scholar, Semantic Scholar, and the bepress Digital Commons Network. The v9.0 multi-zone canonical neutralization and in-file stapled freshness constructions were blockchain-anchored on 3 July 2026 and published on 5 July 2026. The sixth and most recent disclosure — the post-quantum ready, offline-verifiable credential construction — was published on 23 July 2026 and anchored on Ethereum and Bitcoin on 23–24 July 2026.
Because disclosures are filed continuously, each specification edition cites the publications that existed on its own date of issue: the v9.0 editions of 3 July 2026 therefore predate the sixth disclosure and do not reference it. This page is the authoritative index of the complete corpus.
Discloses the complete v9.0 credential construction: hybrid classical + post-quantum signing (ECDSA P-256 and ML-DSA-65, FIPS 204) verified together, an embedded verification engine enabling full verification inside the document itself with no network, a crypto-agile suite registry allowing future algorithm migration, and a deterministic build producing a reproducible self-contained single-file credential.
Discloses the canonical neutralization ordering (v2) by which one self-serialized document simultaneously embeds hybrid classical + post-quantum signatures, a self-referential SHA-256 integrity digest, and a blockchain anchor written after signing — collapsing the triple circular dependency to a single deterministic fixed point verifiable fully offline.
Discloses Zone F: successive Micali-style hash-chain freshness tokens stapled by the holder into a dedicated length-preserving zone of an immutable self-verifying document — excluded from both signature and integrity coverage — giving an offline verifier a FRESH / STALE / INVALID ruling with no re-signing, no server, and no PKI.
Discloses the TOTP-derived symmetric key system, dual-domain PBKDF2 architecture, AES-256-GCM encryption, IIFE module isolation, ECDSA P-256 signatures, and single-file HTML distribution model for offline issuer-mediated access control.
Discloses two new constructions: (i) the SHA-256 page integrity scheme (Mode A) with fail-closed lockdown, and (ii) the dual-passphrase key architecture using Argon2id RFC 9106 (96 MiB, t=4, p=4) for per-export recipient passphrases.
Discloses the ecosystem-wide defense-in-depth architecture: multi-marker structural validation, bidirectional filename-identifier verification with triple checkpoint, the non-degrading optional offline launcher pattern (PWA), and bundled access-controlled distribution with universal blockchain verifiability — combined with the prior two publications into six independent fail-closed verification layers.
Pick the one that matches your role and what you want to do.
In addition to file verification, you can verify the SHA-256 integrity of every HTML page on this site in real time — directly in your browser, using the W3C Web Crypto API. Nothing is uploaded.
The documents and records on this page are provided for informational purposes only. They do not constitute legal recognition, certification, accreditation, or endorsement by any authority, and no warranty of any kind is given in relation to them. Internet Identity Card ™ is a private software-based identity and verification platform developed by Https Card — Internet Identity Card Ltd. References to standards, electronic signatures, eIDAS, or regulatory frameworks are informational only; conformance to a cryptographic standard in code is distinct from formal evaluation and does not constitute a FIPS 140 CMVP validation or an ANSSI qualification. Use of this website and of the software is governed by the Terms & Conditions.