What It Does
Cryptographically signed proof-of-presence receipts. A mobile client proves a real device was genuinely active for a specific duration. KMS-backed signing (AWS/GCP), hash-chained JSONL transparency log, Merkle-rooted and signed M-of-N, published to GitHub, S3, and DNS TXT. Offline-verifiable via Node.js and Python SDKs.
- 📱Proof-of-Presence Receipts Mobile client submits a signed proof session. Server validates, issues a KMS-signed receipt with device ID, session duration, timestamp, and verification metadata. Receipt is self-contained and verifiable without contacting HRN servers.
- 🔗Hash-Chained Transparency Log Every admin action appended to a JSONL log, Merkle-rooted, and signed M-of-N by root keys. Published to GitHub, S3, and DNS TXT. Independent monitor nodes alert on any divergence.
- 🔑KMS-Backed Root Keys Pluggable custody: local file for dev, AWS KMS or GCP KMS for production. M-of-N signing means no single key holder can forge the transparency log.
- 🌐Multi-Anchor Publishing Transparency log roots published to GitHub, S3, and DNS TXT simultaneously. Verification requires no special software — any DNS lookup or GitHub diff confirms integrity.
- 📊React Admin Console Surfaces the live transparency head, key registry, full audit log, witness network status, and billing dashboard in a single interface.
- 📦Verifier SDKs (Node + Python) DPT verifier SDKs for Node.js and Python. Third parties verify receipts and log entries offline with no HRN account or API access required.
How a Proof Session Works
1. Device Registers Wallet
Mobile app generates a device keypair on first launch. Public key registered with HRN. Private key never leaves the device — establishes a cryptographically bound device identity.
2. Proof Session Signed
At session end, the device signs a payload: device ID, start/end timestamps, activity evidence, and a server-issued nonce. Signature is unforgeable without the device private key.
3. Server Validates & Signs
HRN validates the device signature, checks nonce freshness, verifies session constraints, then issues a KMS-signed receipt binding all session facts.
4. Third Party Verifies Offline
Any third party with the HRN public key and the Node.js or Python verifier SDK can verify the receipt offline — no API call, no HRN account, no DNG2000 dependency.
Architecture Overview
API Server
Fastify (Node 20) — wallet registration, proof session validation, receipt signing, billing. High-throughput async request handling.
Key Custody Layer
Pluggable backends: local PKCS#8 for dev, AWS KMS or GCP KMS for production. HSM-backed key material that never leaves the KMS boundary.
Transparency Log
Hash-chained JSONL append-only log. Each entry includes the hash of the previous entry. Merkle-rooted and signed M-of-N by active root keys.
External Anchors
Transparency roots published to GitHub commits, S3 objects, and DNS TXT records simultaneously. Three independent anchors — no single point of control.
Monitor Network
Independent monitor nodes poll the transparency feed and verify Merkle consistency. Alert on divergence, log tampering, or missed publishing windows.
Verifier SDKs
Node.js and Python DPT verifier SDKs. All verification logic is open and auditable. Third parties verify receipts with no HRN dependency.
Need verifiable proof-of-presence infrastructure?
HRN is available for enterprise licensing and custom deployment — attendance verification, field service confirmation, or compliance auditing.