Wallets
ILLA supports two wallet models depending on the integration. Bring your own wallet. For developers and agents, ILLA plugs into existing wallet infrastructure. The integrator manages its own wallets and key management. ILLA provides aggregated capabilities, intent resolution, planning and safety. Transaction data flows to the integrator’s wallet for signing. ILLA never touches the keys. ILLA-provisioned wallets. For end users connecting through MCP connectors or ILLA-owned apps, ILLA provisions an embedded wallet automatically. No wallet setup required. The user authenticates (Google sign-in, passkey, or similar), and a wallet is provisioned and ready. ILLA-provisioned wallets are self-custodial. ILLA never holds private keys. The wallet infrastructure is provided by specialist partners who handle key management with hardware-backed security. ILLA produces ready-to-sign transaction data and hands off to the wallet. The wallet signs. These wallets are portable. The same wallet is available across every surface the user authenticates with: Claude and ILLA Apps today, Slack and WhatsApp and more to follow. The user authenticates once, and their wallet and execution capability travel with them. This separation means ILLA can serve consumer-facing products (where wallet setup is a barrier) and developer-facing products (where the integrator already has wallet infrastructure and wants to keep it) without architectural changes.Hub
Hub is ILLA’s user-facing workspace. A user’s wallet, context, and preferences — unified across every ILLA surface. A user logs in and sees their wallet(s), transaction history, settings, and preferences. They can upload or link financial context: contacts, invoices, documents, connected accounts. This context becomes persistent financial memory, available across every surface the user interacts with ILLA through.ILLA Hub is currently in development.