Web3 & Wallet
Aephoron ships Web3 as first-class browser infrastructure — not as injected extensions. Private keys live in OS secure enclaves (Keychain, Credential Guard), never in the JavaScript heap.
window.aephoron API
dApps interact with the native stack via window.aephoron:
- Chain connection to EmpoorioChain (chain ID
2026) - Transaction signing through the in-app egui popup (protected against DOM clickjacking)
- DMS (Dracma) balance and gas estimation via native SCALE-encoded extrinsics
- Contract read calls without external wallet extensions
This replaces the typical window.ethereum injection pattern with a browser-controlled, audited bridge.
EVM bridge status
8 of 9 EmpoorioChain pallets are wired via real SCALE-encoded extrinsics (balances, identity-ssi, .empoorio domains, ai-serving, ad settlement, phishing registry, web reputation). The EVM/Frontier compatibility bridge (eth_getBalance, eth_blockNumber, and similar calls) currently returns static stub data — full live EVM RPC support is coming soon, not yet live.
Eoonia Wallet
Eoonia is embedded in Aephoron:
- HD wallet and account management
- WalletConnect v2 — QR pairing with mobile wallets
- EmpoorioChain signing (Cosmos-style messages)
- Session persistence across browser restarts
See Eoonia Integration for cross-product flows.
Sovereign login
Login flows use embedded wallet identity without exporting keys:
did:empdecentralized identifiers — credentials can be stored and viewed locally today- Verifiable credential presentation UI is built; cryptographic VC/signature verification is an open, in-progress item
- SIWE (Sign-In with Ethereum) works today for wallet-based login
window.aephoronSSO bridge for dApps
Current DID/VC status
On-chain did:emp registration and full VC signature verification are open TODOs, not shipped yet. What works today: local credential storage/display and SIWE-based wallet login. Identity is complementary to wallet signing — credentials prove attributes; the wallet signs transactions.
DMS (Dracma)
Native token across the Empoorio stack:
- Gas on EmpoorioChain
- Loogo node incentives (roadmap)
- Empoorio Ads rewards — infrastructure built, default reward contract deployment still pending
- Ecosystem payments without third-party stablecoin dependency
Security model
| Layer | Protection |
|---|---|
| Key storage | OS enclave — Keychain / Credential Guard |
| JS isolation | Keys never exposed to SpiderMonkey heap |
| TLS | Rustls with ML-KEM + ML-DSA (post-quantum ready) |
| Signing UI | Native egui overlay — not DOM-rendered |
| Shields | Ad blocking, tracker blocking, fingerprint resistance, HTTPS upgrade |
| DNS | DNS-over-HTTPS (DoH), RFC 8484 — Empoorio, Cloudflare, Quad9, or custom provider |
Testnet RPC
https://rpc.testnet.empooriochain.orgExplorer: empooscan.com
Fail-closed verification
On-chain reads and VC checks fail closed — invalid proofs or revoked credentials are rejected, not silently ignored.