Overview
Exodua is built around three priorities: security, simplicity, and composability. Whether you need to sign a contract, view an NFT, or swap tokens across chains, Exodua puts a single, auditable seed and clear UX at the center of your experience. This document describes the product, how it works, and how to get started.
Key features
Security model
Exodua separates signing authority from network interaction. Keys are generated locally using BIP-39/BIP-44 standards and protected by an optional Secure Element or OS-level keystore. Transaction signing is explicit — the user reviews human-readable transaction fields before any approval, and advanced users can inspect raw RLP/serialized payloads. Recovery uses a mnemonic phrase and a guided, clear backup flow; we encourage hardware backups for high-value accounts.
How Exodua handles privacy
No personal data is required to use Exodua. The wallet avoids centralized analytics by default — opt-in telemetry is available for those who want to help improve the product. IP-level privacy is the responsibility of the network; Exodua supports configurable RPC endpoints and private relay integrations for advanced users.
Design & UX
The interface favors clarity: balances are shown with fiat conversions, pending transactions show countdowns and nonce details, and action flows minimize surprise by showing gas estimates, fee breakdowns, and optional nonce locks for manual chain management. Onboarding includes a short interactive tutorial explaining seed backup, secure passphrase options, and how to connect to a dApp safely.
Integration & developer notes
Exodua exposes a secure provider shim compatible with the EIP-1193 spec and supports WalletConnect v2 for mobile bridging. Developers can request metadata (chainId, accounts, supportedMethods) and will receive clear user prompts for every signature or permission request. A lightweight JSON-RPC proxy allows per-origin rate limits and optional transaction previews for enhanced UX.