Identity & Privacy

T-REX (Regulated Exchanges)

Security tokens enforce compliance at transfer — only verified investors can hold, automatic checks against regulations. Design implications: show verification status prominently, guide through KYC/identity verification, display transfer eligibility before attempting. Design decisions: how to handle failed compliance checks — educational messaging, clear next steps for verification, balance regulatory requirements with user frustration.

Stages: Asset Management

Minimal Soulbound NFTs

Tokens marked as 'locked' cannot be transferred — minimal soulbound implementation for credentials, memberships, achievements. Design implications: show 'Soulbound' or 'Non-transferable' badge, hide/disable transfer buttons, explain permanence clearly. Design decisions: whether to show soulbound tokens in trading contexts at all — filter out or display with clear 'Not for Sale' status.

Stages: Approving & Permissioning, Asset Management

Consensual Soulbound Tokens

Soulbound tokens require recipient consent before minting and have predetermined burn rules (issuer-only, owner-only, both, neither). Design implications: show consent flow before accepting SBT, display burn authority clearly, add 'Request Burn' action where applicable. Design decisions: how to present burn authority — affects user understanding of permanence, recovery options if keys lost.

Stages: Approving & Permissioning, Asset Management

Stealth Addresses

Senders generate one-time stealth addresses for recipients — receive funds privately without revealing main wallet. Design implications: show 'Send Privately' option, explain stealth address concept simply, add stealth transaction scanner for recipients. Design decisions: how to onboard users to stealth — complexity vs privacy benefit, whether to default to private or make it opt-in, scanning UX for finding received funds. 77K addresses deployed via Umbra. Part of the On-Chain Activity Is Public by Default pain point (High severity, Research status). Users often don't realize their complete financial history is visible — stealth addresses are one of four leading privacy solutions.

Stages: Authentication & Identity

Stealth Meta-Address Registry

Users register stealth meta-addresses in central registry — senders look up recipient's stealth keys to send privately. Design implications: add 'Register for Private Payments' onboarding, show registration status, enable ENS-like stealth address lookup. Design decisions: registry discoverability vs privacy — registered users are known to want privacy, balance convenience with metadata exposure.

Stages: Authentication & Identity

Identity-aggregated NFT

NFTs aggregate multiple verified identities (Twitter, Discord, wallet addresses) into single on-chain profile — portable reputation. Design implications: show connected identities with verification status, add 'Link Identity' flow, display identity proofs. Design decisions: privacy controls for which identities visible — selective disclosure UI, granular sharing permissions, balance transparency with privacy.

Stages: Authentication & Identity

Soulbound Badge

Badges bound to other NFTs (not wallets) — achievements tied to your PFP, credentials attached to identity NFT. Design implications: show badge hierarchy (which NFT owns which badges), display nested ownership, indicate badge permanence. Design decisions: how deep to visualize badge chains — could be complex graphs, need to handle loops, balance completeness with comprehension.

Stages: Asset Management

Secure Messaging Protocol

End-to-end encrypted messaging between wallet addresses — private on-chain communication with session support. Design implications: show encryption status indicator, display message history by session, add public key registration flow. Design decisions: key management UX — how to handle key rotation, session organization, balance security (key expiry) with convenience (persistent conversations).

Stages: Specialized Interactions