Most blockchain payment announcements describe a protocol and hope merchants arrive. Empoorio started from the other end: there are merchants, riders and customers using its apps every day, and the chain is being connected underneath them. This post is the honest map of that stack.
What is in production
| App | Package | Play status | What it does |
|---|---|---|---|
| Empoorio Eats | com.gnoosis.empoorioeats | Production, v13.3.23 | Customer app: order from restaurants and shops, track delivery |
| Empoorio Manager | com.gnoosis.empooriorestaurant | Production, v3.3.26 | Merchant app: register a restaurant, menus, opening hours, bank details, orders, multi-location accounts |
| Empoorio Riders | com.gnoosis.empooriorider | Production, v3.3.15 | Courier app: receive dispatches, navigate, deliver |
| Square Sellers | com.gnoosis.empooriosquaresellers | Production, v1.0.3 | Sellers app for shops and stalls |
| Empoorio Warehouse | com.empoorio.warehouse | Production, v19 | Warehouse-as-a-service and WMS (see the KomvoOS posts) |
These share one backend (Firebase, project empooriofood) and one dispatch mechanism: when a merchant confirms an order, the system writes a dispatch to a connected rider's document, and the rider's app picks it up. An inventory in August 2026 walked every screen of the four logistics apps and found 232 of 279 features connected to a real backend (83 %); the remaining 47 are listed by name as mock, decorative or unfinished, and are being closed or removed.
How they settle today
In fiat, through conventional payment rails inside the apps. This is worth saying plainly because the previous version of this page described a crypto payment protocol that did not exist here. The apps are real, the orders are real, and the money moves the way a customer expects from any delivery app.
The on-chain path
EmpoorioChain has the primitives a payment stack needs as native pallets — escrow, subscriptions, a marketplace, logistics, a paymaster for sponsored fees, stablecoins — and the ecosystem's wallet, Eoonia, is the bridge between the apps and the chain:
- Wallet linking is live in Empoorio Warehouse: an app account is bound to an Eoonia account through a challenge–response signature (the same protocol Ailoos uses), persisted server-side. No private key ever touches the app.
- Deep links (
eoonia://) let an app hand a payment request to the wallet and receive the result — the mechanism designed for checkout in DMS or DUSD. - DUSD, the ecosystem's dollar-pegged stable asset, is the unit a merchant would price in; its relationship to DMS for gas is fixed in the canonical tokenomics (about 1.54 DMS per DUSD at the sale price).
- Fee target: a transfer should cost around $0.001; the measured testnet fee for a native transfer is 0.000025 DMS.
What is not live: paying for a meal in DMS. The wallet link and the NFT flows exist in Warehouse; checkout in DMS is the next integration, and it will be announced when a real order has settled on the live chain, not before.
Why build it this way
A payments chain without merchants is a demo. Merchants without a settlement layer are a conventional app. Empoorio has the second and is building toward the first, in public, with the order of operations visible: apps first, wallet link second, on-chain checkout third.
Based on the Google Play Developer API (verified 2026-09-08), the four-app feature inventory (2026-08-07) and TOKENOMICS.json.