Fractal ID · interactive mechanism simulation

Users verify once with Fractal → an attestation is issued and reused across integrated dApps (OAuth-style KYC). But raw ID documents pile up in a central vault behind an operator account — the honeypot that a 2024 breach exposed. Edit the parameters, or trigger the failure mode.
New users verify once Fractal ID KYC doc + liveness + AML, $2 Central PII vault 0 records held Attestation issued OAuth-style credential Relying dApps (250+) 0 credential reuses Attacker operator account — inactive
Verified users
0
Credential reuses
0
Verification revenue
$0
PII records in vault
0
Records breached
0
Parameters — edit me
1.2/s
$2.0
5
14d
Controls

Illustrative simulation. Defaults mirror the researched Fractal ID mechanism (~$1–3/verification, OAuth-style reusable attestations across 250+ integrations, a centralized PII vault, and the July 2024 breach of ~55k users via a compromised operator account) — but timing, batch sizes, and exact figures are randomized for visualization, not live onchain data. Lower "PII retention window" toward idOS's dataless model to see how less-held data shrinks breach exposure. Part of The Onchain Experiment Atlas.