Architecture
Eoonia Wallet is a Flutter app that follows clean architecture: screens on top, business rules in the middle, encrypted storage and blockchain clients at the bottom.
The big picture
mermaid
flowchart TB
subgraph ui [What you see]
H[Home & balances]
O[Onboarding]
S[Settings & security]
D[DeFi & dApps]
end
subgraph biz [Business logic]
U[Use cases]
M[Domain models]
end
subgraph data [Data]
R[Repositories]
L[Hive encrypted storage]
end
subgraph svc [Services]
W[Web3Dart EVM]
P[Polkadart Substrate]
WC[WalletConnect]
end
ui --> biz --> data --> svcIn one sentence: you tap a button → the app runs a use case → data is read or written locally → blockchain APIs do the on-chain work.
Layers
| Layer | What it does |
|---|---|
| UI | Screens, widgets, BLoC state — Home, onboarding, staking, bridge, settings |
| Business | Use cases (create wallet, send tx), validation, wallet/token models |
| Data | Repositories, Hive local DB, remote APIs |
| Services | Web3Dart, Polkadart, WalletConnect, Ledger, biometrics |
Multi-chain
- EVM (Ethereum, Polygon): Web3Dart
- EmpoorioChain (Substrate): Polkadart / Empoorio SDK paths in the app
Network list and public endpoints: Supported networks.
Security model
- Keys generated and stored on device (encrypted Hive + secure storage)
- Biometric gate before sensitive actions
- Optional Ledger hardware signing
- Quantum-aware security research in
QuantumSecuritySystem— see Security guide
Ecosystem modules
In-app modules connect to the Empoorio stack (not separate login silos):
Forge → DMS Hub → Eoonia ID → Pulse → Market → Vault → Bridge → Creator Studio → and more.
Overview: Creator Studio.
Source layout
lib/
├── core/ # SDK helpers, models, services
├── ui/ # Screens (home, onboard, settings, DeFi)
assets/ # Images, animations
docs/ # Developer documentation in the repoDeeper detail: projects/Eoonia_Wallet/docs/architecture/overview.md.
Related
- Installation
- Flutter SDK
- EmpoorioChain — settlement layer
- KryptoOS — identity credentials