Last updated September 2026

This list exists because EmpoorioChain has 140 pallets in its live runtime and most of them have never carried a real transaction. Each idea below names the pallets it would use, what already exists, and what the first team would have to build. None of these is a promise of funding; grants exist as a programme description and nobody has yet received one.

Physical networks

Meters that write to the chain

pallet-device-registry, pallet-solar-generation and pallet-mesh-rewards are in the runtime and empty. An operator that registered real meters or solar inverters and wrote their readings as extrinsics would be the first physical network on EmpoorioChain. OmiloOS already ships a mesh-messaging app; PompoOS is a tokenless mesh over Meshtastic that deliberately does not pay for relaying.

What would have to be built:

• An oracle path from the device to the chain that a second party can verify
• A reward policy that pays for useful coverage, not for existing — PompoOS's routing-over-flooding analysis (factor 6,928×) is the cautionary tale

Stablecoins / Payments / Commerce

Pay with the yield, keep the principal

pallet-subscription executes a recurring charge; pallet-emp-staking pays stakers per 24-hour era; pallet-yield-vault issues shares against deposits. Nobody has connected them. A service where a user bonds DMS and a subscription is paid from the era rewards — principal untouched, custody retained — is three existing extrinsics and a UI. The 20 % APY ceiling and the two-validator testnet are the honest limits.

P2P marketplace settled in DUSD

Local classifieds are mostly-offline commerce without settlement. pallet-marketplace lists, pallet-escrow holds DUSD until pallet-logistics records a handover, and eoonia://pay hands the request to the wallet. Empoorio Square Sellers already serves market stalls in production, settling in fiat; the on-chain checkout is the button not yet wired. The first team to wire it on the testnet would settle the ecosystem's first on-chain sale.

End-to-end point of sale

Card fees erode a small merchant's margin. A DUSD checkout on EmpoorioChain costs about 0.000025 DMS per transfer and the merchant can sponsor it with pallet-paymaster so the customer pays nothing extra. What exists: the pallets, the DUSD asset, Eoonia on Android and iOS, five commerce apps with real merchants. What does not: a fiat ramp into DUSD, a merchant dashboard, and any regulatory answer for holding customer stablecoins.

Creator economy

Royalties the transfer itself pays

pallet-nft-royalties applies a creator's share on every resale, on any marketplace, because the runtime does it at transfer time. Combined with pallet-music-nft and pallet-video-nft (batch minting 100 items for 0.0022 DMS; lazy minting at zero cost until claimed) and pallet-creator-studio-fees (up to 50 % off for KryptoOS-verified humans), the primitives for a creator platform exist. EidoOS pays 70 % of pay-per-megabyte video to the creator and has its studio complete; PhoonoS measured its serving cost at $0.12/GiB before promising musicians anything. No creator has yet minted on the public testnet.

Social apps on the chain's own history

GnoosiS is the ecosystem's social layer in production, with agora, circles and did:emp identity. EmpoorioChain's state — who holds which item, who staked, who voted — is a public graph nobody has built on. An app that reads chain state to rank, recommend or gate would need an indexer: EmpooScan's is being repaired, and the indexer work is the prerequisite.

The opportunity lies in treating the deep link as the unit of distribution: a creator's post that mints, a stall's QR that pays, a proposal that votes — each an ordinary extrinsic the wallet decodes and shows with its real fee before signing.

Provenance for machine-made content

More content is generated by machines, and the question of who made what and who gets paid has no good answer. pallet-storage-market holds the bytes with availability verified by an oracle; pallet-uniques or pallet-emp-nft holds the claim; pallet-identity-ssi ties it to a did:empoorio; Ailoos's provenance manifest already records which datasets trained each EmpoorioLM model. A registry that signs a hash of a work with a DID at creation time is small; the hard part is adoption.

AI

Paid data collection with an audit trail

High-quality, unique data is the bottleneck for model training. Ailoos runs a federated loop where phones train on device — verified on a physical POCO F8 Pro after finding the production model had random weights — and rewards are accounted in an on-chain pool that has never paid out. A team that built the data-collection side (consent in pallet-privacy, contribution recorded in pallet-reputation, payment from the AI pool once it pays) would be finishing a circuit that is three-quarters built. The honest starting point is Ailoos's own audit: real, but disconnected.

Games

A game that uses the gaming pallets

pallet-gaming (runtime index 69), pallet-dynamic-nft, pallet-nft-wallet, pallet-randomness, session keys in pallet-account-abstraction and sponsored fees in pallet-paymaster are all in the live runtime and none has real traffic. There is no game in the ecosystem and no Unity or Unreal SDK. The first team to register a game and mint an item will find the gaps; documenting them is worth as much as the game.

What the runtime can guarantee is the record — ownership, traits, royalties. What it cannot is the world; that stays on the studio's servers. Designs that lean into exposed state:

• Less focus on:

Local apps with staked visibility

Empoorio Eats, Manager and Riders are in production in Spain with real merchants and couriers. A discovery layer where a merchant's ranking depends on DMS bonded to its account — pallet-emp-staking already has the bond; pallet-sbt already has non-transferable points — would connect apps with users to a chain with none. Examples:

Asset tokenization

The first regulated asset

pallet-emp-rwa (partitions, issuer controls), pallet-tokenized-fund (NAV accounting), pallet-compliance and pallet-sanctions (holder rules enforced on every transfer) and pallet-identity-ssi (credential requirements) are wired and unused. The on-chain half of a regulated instrument exists; the off-chain half — an issuer with a licence, custody, ramps, an audit — does not. A team that brings the off-chain half and runs a pilot with test assets would be first, and would find the gaps the mainnet gate lists: travel-rule parameters unconfigured, no legal entity, no external audit.

Infrastructure

Identity that reveals only what is needed

KryptoOS registered the first did:empoorio on EmpoorioChain on 14 September 2026 and verifies credentials fully on chain with no issuer server in the loop. Selective disclosure and ZK login are designed and not implemented. A team that shipped a real verifier for one credential — age, residency, KYC tier — used by one real app would take the identity layer from proven-to-work to used. What exists:

• pallet-identity-ssi with DID registration and revocation anchoring
• A Rust crypto core (Ed25519, RFC 8785) with 41 tests and Rust issuer/verifier services
• Server-side Empoorio ID login already in Eoonia Wallet and Ailoos App

An indexer that keeps up with the runtime

EmpooScan's indexer broke when the runtime metadata changed and is being repaired field by field. Every upgrade — 208 to 220 in two weeks — changes the metadata, and any indexer that hardcodes types breaks with it. An indexer that regenerates its decoders from the live metadata at each spec_version, exposes a GraphQL or REST API, and serves the received-transaction history that Eoonia cannot show today would be used by every app in the ecosystem on day one. The public RPC's 10 requests-per-second limit is the reason it must run its own node.