Hardware root of trust
The device that makes possession part of access.
Phantom Key is the physical access anchor for the Phantom ecosystem.
It binds vault access to a trusted USB device, creating a real-world boundary around sensitive data. Without the trusted device present, protected vaults stay sealed.
Access model
Possession becomes part of the unlock path
Keyfile
+
Trusted USB key
+
Vault policy
=
Access
Physical possession becomes part of the security boundary instead of being left outside the model.
Why it exists
Software credentials alone are not enough.
- Many products rely on accounts, remote systems, and always-on infrastructure, expanding the trust surface.
- Phantom Key narrows that boundary by introducing a possession requirement.
- Part of the access model lives in hardware the user physically controls.
Core role
Built as the suite-wide trust anchor.
- Hardware-bound vault unlocking
- Presence-aware session control
- Shared use across Obscura, Attestor, Recovery, and future Phantom applications
Placeholder
Hardware workflow preview coming soon
This section is reserved for Phantom Key device setup, lifecycle management, rotation, and revocation flows.
Phantom Key preview placeholder
Future updates will show trusted-device enrollment, replacement flows, and how hardware presence is enforced across Phantom products.
Join the waitlist for Phantom Key
Follow the development of hardware-bound security across the Phantom ecosystem and hear when Phantom Key is ready for early access.