Two-factor authentication
Google Authenticator–compatible TOTP via Web Crypto (RFC 6238). Backup codes generated at setup. Withdrawals, swaps, and sends can require a valid code.
The demo implements real client-side TOTP, session persistence, and role-gated portals. Production deployments should add server-side auth, encryption, and compliance review.
Google Authenticator–compatible TOTP via Web Crypto (RFC 6238). Backup codes generated at setup. Withdrawals, swaps, and sends can require a valid code.
Multi-step identity flow with document upload, selfie capture, and admin review queue. Approved tier updates user session and badges across the app.
Trades move through in-progress, awaiting release, completed, and disputed states. Vendors release crypto only after payment proof; admins can resolve disputes.
Admins can freeze accounts and adjust limits frozen users are blocked from starting new P2P trades in the demo.
Auth state stored in empire_user with token key for API integration. Logout clears session across portals.
Use HTTPS, secure cookies, server-side validation, rate limiting, and never store secrets in front-end code. Replace mock API with audited backend services.