Identity Creation
This page describes how GetTrusted creates identities.
Create a hardware-backed master identity that anchors all trust relationships in GetTrusted.
Overview
The identity-creation process establishes a unique, cryptographically verifiable identity on a user’s device. It uses hardware-backed key generation, mnemonic recovery, and one-time master key delegation and master based backup encryption key to ensure that no long-term secrets exist outside secure enclaves.
Process Flow
flowchart TD
A[1. User Input<br/>• Pass phrase user provided - 2 words 3 letters or more for 7 characters] --> B[2. BIP39 Mnemonic Generation<br/>• 24 words = 256-bit entropy<br/>• Hardware randomness]
B --> C[3. Master Key Derivation PBKDF2-SHA512<br/>• 100,000 iterations<br/>• Input: mnemonic + password]
C --> D[HKDF-SHA256 key expansion<br/>• Output: 32-byte key]
D --> E[4. Master Identity Components<br/>• Master Private Key P-256 ECDSA<br/>• Master Public Key<br/>• Fingerprint SHA-256 of pubkey<br/>• Backend ID is fingerpint of certificate]
E --> F[5. Device Key Generation in Hardware<br/>• Secure Enclave / StrongBox / TPM<br/>• Generate P-256 keypair<br/>• Private key: hardware-only<br/>• Public key: extractable]
F --> G[6. Certificate Creation<br/>• X.509 Device Certificate<br/>• Signed by Master Private Key<br/>• Subject: Device ID<br/>• Contains: Device Public Key]
G --> H[7. Master Key Destruction<br/>• CRITICAL: Master private key DESTROYED<br/>• Only device key remains<br/>• Certificate proves authority]
H --> I[8. Hardware Storage<br/>• Platform Keychain / Keystore<br/>• Store: Device key + Certificate<br/>• Type: kSecClassIdentity]
I --> R((Result:<br/>Complete hardware-backed identity<br/>with certificate delegation))Cryptographic Summary
Mnemonic
BIP39 (Entropy 256-bit)
–
User memory / optional QR
Recovery seed
Master Key
ECDSA P-256
256 bit
Temporary memory
Signs device certificates once
Device Key
ECDSA P-256
256 bit
Secure Enclave / StrongBox
Ongoing identity operations
Encryption
AES-256-GCM
256 bit
Runtime
Protect private data at rest/in transit
Security Guarantees
Master private key exists only once, then is destroyed.
Device private keys are hardware-bound and non-exportable.
Recovery is mnemonic-based, not key-based — the master key is reconstructed, never stored.
Certificates cryptographically prove device authority without exposing master secrets.
Strategic Implications
GetTrusted identities are born secure-by-design: there are no static credentials to steal. Hardware-backed key generation eliminates centralized trust, enabling verifiable, user-owned identity for every interaction.
Last updated