Skip to content

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 (testnet chain ID 9911)
  • Transaction signing through the in-app egui popup (protected against DOM clickjacking)
  • DMS (Dracma) balance and gas estimation
  • Contract read calls without external wallet extensions

This replaces the typical window.ethereum injection pattern with a browser-controlled, audited bridge.

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:emp decentralized identifiers
  • Verifiable credential presentation
  • SIWE (Sign-In with Ethereum) and revoke flows
  • window.aephoron SSO bridge for dApps

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
  • Ecosystem payments without third-party stablecoin dependency

Security model

LayerProtection
Key storageOS enclave — Keychain / Credential Guard
JS isolationKeys never exposed to SpiderMonkey heap
TLSRustls with ML-KEM + ML-DSA (post-quantum ready)
Signing UINative egui overlay — not DOM-rendered
ShieldsTracker blocking, fingerprint resistance, HTTPS upgrade

Testnet RPC

https://rpc.testnet.empooriochain.org

Explorer: empooscan.com

Fail-closed verification

On-chain reads and VC checks fail closed — invalid proofs or revoked credentials are rejected, not silently ignored.