Self‑ID & Consent Receipts Pack
Identity and access you can prove—without storing sensitive data on-chain.
Timeverse Identity focuses on signed receipts and time‑bounded consent: who granted what access, within which verified window, under which policy.
What Self-ID means here
Self‑ID is not “social media identity.”
It is a cryptographic identity (keys + signatures) used to produce verifiable receipts for actions and permissions.
What you get (business outcomes)
- Consent that is verifiable
Turn “we allowed access” into a signed, time-bound receipt you can audit later.
- Reduced data exposure
Store proofs and hashes—avoid storing the underlying sensitive content inside the coordination layer.
- Stronger compliance posture
Receipts can be exported and reviewed as evidence, not just logs.
Key capabilities
1) Self‑ID (key-bound identity)
- identity keys (Ed25519)
- signature verification
- replay resistance (nonce horizon)
2) Consent receipts (TSAE)
A consent or access event can generate a TSAE receipt binding:
- time window (ticks)
- scope / purpose
- issuer and audience IDs
- coarse spatial context (SWT/Tile)
3) Optional anchoring
Anchor hash(TSAE) to Clockchain for durable proof.
Use cases
- Time‑bounded access to an API or resource
- Commercial agreements and approvals
- Device enrollment and key rotation evidence
- “Who approved what, when, and under which constraints?”
Health Access Proofs (Pilot / Enterprise only)
Health scope (careful by design)
Timeverse does not store medical records.
In health pilots, we focus on proofs of access/consent (receipts + hashes) and integrations with existing compliant storage.
This is offered as Pilot + Enterprise, with strict scope and compliance review.
Packaging
- Included in Team
- Enterprise adds retention, exports, SIEM integration, and private deployments