Many device networks begin on their own ledger and later move to a general chain for liquidity and security. OmilooS made the second choice first. This post is why, and what it costs.
The case for a dedicated ledger
A device network's transactions are small, frequent and boring: a reading every few minutes, a relay proof per packet batch. A dedicated ledger can tune block size, fees and validator set for exactly that and nothing else.
The case for EmpoorioChain
The pallets already exist as first-class runtime modules. Device registry, telemetry, proof of relay, mesh rewards, energy market, solar generation — six pallets at runtime indexes 102–107, with their trait dependencies documented. A dedicated chain would rebuild them.
Attestation is shared. A device registered in pallet-device-registry is a device to the whole ecosystem: an Ailoos training node can be attested by the same mechanism; a Ouranoos storage node too. One registry, one attestation model.
Fees are designed for exactly this traffic. A native transaction costs 0.000025 DMS on the testnet; a telemetry report is in the same range. State rent keeps the per-byte cost flat as the device set grows; batch calls consolidate many readings into one extrinsic. A paymaster can sponsor a device's fees so a gateway never runs out of gas.
Payment is in the ecosystem's token. Rewards from pallet-mesh-rewards land in the same DMS a user spends at a Square Sellers stall or stakes with a validator. No wrapped token, no bridge, no second economy.
Downstream markets are on the same chain. Attested clean generation is the natural upstream of pallet-carbon-credits; energy trading is pallet-energy-market. On a dedicated ledger those would be bridges.
The trade-offs, honestly
- Shared block space. A burst of telemetry competes with everyone else's transactions. The DAG mempool's deterministic ordering and the parallel executor mitigate it; a dedicated chain would not have the problem.
- Shared upgrade cadence. OmilooS cannot ship a runtime change on its own schedule; the IoT pallets follow the chain's upgrade policy and timelocks.
- Shared risk. Two validators today, zero fault tolerance — a fact OmilooS inherits.
- Deferred providers. Two IoT traits are still bound to no-op implementations. On a dedicated chain OmilooS would own that timeline; here it is on the chain's list.
Where it stands
OmilooS is in internal testing on Google Play. Modbus telemetry works; the BLE/LoRa mesh works with a mock for P2P signing; no reading has yet been attested on the public testnet. The chain side is wired. The first attested inverter reading, with its block number, is the milestone.
What this page is not
It is not a migration announcement from another network, and OmilooS has no foundation, no token of its own and no hotspot fleet. It is one app, six pallets and a choice about where to settle — made early, for reasons that are written down.
Based on ARCHITECTURE.md, FEE_MODEL_AND_LOW_COST_STRATEGY.md, the OmilooS release notes and DECENTRALIZATION_REPORT.md.