A transaction in a link: eoonia:// deep links

<p>An Empoorio Action is a request for an EmpoorioChain extrinsic expressed as a URL with the eoonia:// scheme. Eoonia Wallet opens it, decodes the call, shows the real fee quoted with payment_queryInfo, and asks the user to sign. Anything that can hold a URL — a QR, a button, a message — can carry one.</p>

<p>The Action is the call: pay this amount of DUSD to this account, mint this item, sign this challenge. The deep link is one way to deliver it. An app can also hand the same call to the wallet through the browser extension's window.injectedWeb3.eoonia, or submit it itself with the Dart SDK.</p>

<p>The link does not touch the merchant's server: the wallet builds and signs the extrinsic and submits it to the public RPC. The merchant learns the result the same way as everyone else — from the runtime event in the finalized block.</p>

<p>Examples of Actions:</p><ul><li>Linking an Eoonia account to Empoorio Warehouse by signing a challenge — live</li><li>Minting an NFT product passport from a warehouse app — live</li><li>Paying a market stall in DUSD by QR, with the seller's paymaster covering the fee — designed</li><li>Claiming a lazy-minted work from a creator's post — designed</li><li>Voting on a governance proposal from a chat message — possible today with the wallet's governance screens</li></ul>

<p>Key benefits include:</p><ul><li>Bringing signable transactions to where users already are.</li><li>No in-app wallet to build: the seed stays in Eoonia, behind the device Keystore or Keychain.</li><li>One review surface: the wallet always shows the decoded call and the real fee.</li><li>A web fallback when the wallet is not installed.</li></ul>

<p>Build the eoonia:// URL with the call parameters, place it behind a button or QR, and listen for the result — the wallet returns submitted / included / finalized, or the app reads the runtime event from its own node. The Dart SDK and the deep-link guide in the Eoonia repository cover the exact format.</p>

<p>The wallet never signs blind: every Action is decoded and shown with the destination, amount and fee before the user approves. The seed never leaves the device. A malicious link can only ask; it cannot sign.</p>

<p>Today the wallet decodes and displays every call. Pending: universal links over HTTPS (the TLS certificate for link.eoonia.com is not yet valid), so links currently rely on the custom scheme with a web fallback; and an allow-list UI for domains a user has approved before.</p>

<p>The link falls back to a web page that explains what was requested and where to get Eoonia for Android or iOS. Nothing is signed and nothing is lost; the request can be reopened once the wallet is installed.</p>

<p>On a phone, the eoonia:// scheme opens the app directly. In a desktop browser without the Eoonia Extension, the fallback page shows a QR code that the phone app can scan.</p>

<p>The eoonia:// scheme is specific to Eoonia. A site that also supports generic Substrate wallets can offer the same call through the injectedWeb3 interface, where the user picks the wallet.</p>

<p>The Eoonia team maintains the scheme, the fallback pages and the SDK support; the commerce apps (Warehouse, Square Sellers, Eats) are the first consumers. Other teams are free to build tooling on the same format.</p>