EmpoorioChain Anchoring

Aephoron talks to EmpoorioChain (chain ID 2026) through real, native SCALE-encoded extrinsics — not a REST middleman. 8 of 9 pallets are wired today: balances, identity-ssi (DID registration), .empoorio domains, ai-serving, skoopos-pov (ad settlement), phishing-registry, and web-reputation. The EVM/Frontier compatibility bridge is the one exception — it currently returns static stub data.

What Goes On-Chain

• .empoorio domain registrations (real, primary resolution path — not a fallback)
• Ad settlement commitments (skoopos-pov)
• Phishing registry and web-reputation entries
• DID/credential commitments — real for the pallet itself, though full end-to-end did:emp registration and VC verification from the browser is still in-progress work (see Web3 & Wallet)

What Must Stay Off-Chain

• Names, addresses, and documents
• Raw device identifiers
• Private keys and recovery phrases
• Full credential payloads unless explicitly intended for public disclosure

Verification

Apps resolve the public commitment, check status, and show a clear result to the user — on-chain reads and VC checks fail closed: invalid proofs or revoked credentials are rejected, not silently ignored. Explorer links point to EmpooScan for indexed on-chain events.