Overview

Create a cryptographically-anchored Passport identity. Every human on HUMAN has a unique DID (Decentralized Identifier) bound to their devices and controlled by cryptographic keys they own.

What is a Passport?

The HUMAN Passport is:

Cryptographically controlled - Your identity is proven by keys you control

Device-rooted - Keys never leave your secure enclave

Portable - Works across apps, devices, and platforms

Human-owned - HUMAN cannot access or revoke your identity

Format: did:human: Example: did:human:550e8400-e29b-41d4-a716-446655440000

SDK Examples

SDK:

Cryptographic Details

Algorithm: Ed25519 (RFC 8032) Key Size: 256 bits Signature Size: 512 bits (64 bytes) Library: @noble/ed25519 (constant-time, audited)

Key Storage Options:

secure-enclave - iOS Secure Enclave, Android StrongBox (Production)

server - Server-stored, KMS-encrypted (MVP/Development only)

hardware-key - YubiKey, Ledger, or other FIDO2 device

Use Cases

User Onboarding

New users create their Passport as part of sign-up - Passport becomes their permanent identity across all HUMAN apps

Enterprise SSO

Employees create Passports linked to company directory - Single identity for all internal agents and tools

Multi-Device Setup

Create Passport on primary device - Sync to other devices via cryptographic attestation

AI Agent Identity

Create Passports for autonomous agents - Agents prove identity cryptographically in workflows

Security Considerations

DO

Store private keys in secure enclave/hardware

Use Passport-Lite (server-stored keys) for MVP/development only

Enable multi-device sync for resilience

Set up recovery guardians (Shamir threshold)

DON'T

Never expose private keys in logs or error messages

Don't use server-stored keys in production

Don't create Passports without user consent

Next Steps

Delegate Access - Grant an agent access to act on your behalf

Verify Passport Offline - Verify identity without network

Multi-Device Sync - Sync Passport across devices

Create Passport