From the 4 September 2026 relaunch to runtime 211, EmpoorioChain's EVM layer rejected every Ethereum transaction — MetaMask, Hardhat and the Eoonia extension included. Root cause: a generic extrinsic type without self-contained-call support. Timeline, cause, fix, lesson.

For months EmpoorioChain's native DEX could not settle a single swap on the live chain — with pallets wired and tests green — because the account that collects swap fees had never received an existential deposit and therefore did not exist. Found and fixed in runtime 220.

EmpoorioChain's treasury is capped at 10 % of its balance per period. Until runtime 217 the period constant was twelve hours, not a year — turning the cap into permission to empty the treasury in a week. How a unit error hid in a constant, how it was found, and the rule it produced.

EmpoorioChain's decentralization report described three validators across three AWS regions that never existed. The inventory file contained Substrate's development accounts as placeholders; the audit script that should have caught it never read the chain and exited with success. Found and corrected 5 September 2026.

The model artefact Ailoos served to mobile nodes for LoRA training contained randomly initialised weights, not the trained model. Every exporter in the repository built the architecture and exported without loading a checkpoint. Phones trained on noise, loss fell anyway, artefacts were merged and rewarded. Found 8 September 2026.

An honest inventory of what a developer can actually use to build on EmpoorioChain today: the Rust SDK and CLI, the Dart SDK, Polkadot.js, MetaMask through Frontier — and what is not published yet, including the TypeScript package that returns 404 on npm.

No tour, no houses: the Empoorio ecosystem's physical footprint is two validators and two RPC nodes in one data centre in Logroño, one dedicated server for Ailoos, a team in Spain, and apps distributed in Spain. Why that matters for latency, risk and the next decentralization step.

EmpoorioChain has written incident-response playbooks for validator compromise, finality stalls, bad runtime upgrades and key exposure. They exist because the ecosystem has had incidents — a cryptominer on a server, a rootkit on another, a leaked backend key. What the playbooks say and what happened.

Account abstraction, permit approvals, token-bound accounts, blob commitments, MEV protection, royalties, flash loans and compliance — implemented as runtime pallets, with the Ethereum standard each one maps to.

From 6 August to 8 September 2026 no Ailoos mobile node succeeded in uploading a trained adapter. A security fix added an upload secret to the coordinator; the app requested it, discarded it, and received HTTP 422 on every upload. Confirmed in the production database.

A chain without deterministic finality can reorganise, and every exchange and custodian on it prices that risk. EmpoorioChain's GRANDPA finality is deterministic: finalized means final. What that guarantees, what it does not (two validators, zero fault tolerance), and where pallet-insurance fits.

Every project in the Empoorio ecosystem with its real status — production, testing, development, or paper — as measured in the September 2026 audit. The chain, the wallet, the AI network, the browser, thirteen apps, twelve websites. No conference, no keynote: a table.

EmpoorioChain's first hackathon is fully designed and not yet announced: a 48-hour virtual event with native-DeFi, AI/zkML and identity tracks, judged on innovation and native pallet use, with prizes in testnet DMS and no financial commitment. The plan, and the three things that must exist before the date.