Merxet

Demo

About

Merxet is an end-to-end encrypted retail protocol built on Hedera. It lets merchants sell products online and offline through a simple checkout, with payments handled on Hedera, private messages and sensitive order data protected by end-to-end encryption. Beyond distributing QR codes offline, sellers can create online storefronts for their product catalogs and customize them with the Merxet AI agent. Each store can have a short, unique ENS name, and sellers can verify themselves through World Selfie Check. Buyers use the Merxet app as a personal shopping cart with a built-in Hedera wallet. They can shop across different stores and pay with supported tokens, including HBAR and USDC. What makes Merxet different? 1. Decentralized commerce with private order data. Sensitive order data is encrypted and stored on-chain. Only the buyer and seller can decrypt it. 2. Transparent payments with predefined rules. Merxet's public payment protocol on Hedera uses escrow and predefined settlement rules, giving buyers and sellers a clear view of how payments are handled, without unexpected holds, extra platform fees, or verification delays. 3. A fast, affordable way to start selling. Upload your products, generate QR codes for offline sales, and create an online storefront with AI customization, all within Merxet. Merxet brings Hedera into everyday commerce, helping merchants start selling while giving buyers and sellers greater privacy, transparency, and control.

How it's made

We built Merxet around a simple flow: a seller publishes a catalog and can create an online storefront for a traditional online shopping experience or share QR codes for offline purchases. Buyers place their orders, and payment stays in escrow until the order is completed. The seller portal, buyer app and storefront template use React, TypeScript, Vite and Tailwind. Node.js and Express services handle chain indexing, storefront generation and agent orders. The commerce MVP runs on Hedera Testnet. Hedera does most of the work. Our Solidity contract, built with Hardhat and OpenZeppelin, manages catalogs, HBAR and token payments, escrow, settlement and refunds. Order details and delivery messages are encrypted in the browser with AES-GCM, with the encryption key wrapped separately for the buyer and seller using ECIES. We store the ciphertext in HFS and send small references and hashes through HCS. A Mirror Node sync service indexes the public state so the apps can load order history quickly. This lets us use the same network for payments, storage and messaging without putting delivery addresses in plaintext on-chain. Most of the recent work went into letting sellers build their own shops. A seller describes the design they want, and the builder sends their brief, catalog and existing template to OpenAI's Responses API. It returns structured file edits. Each build runs in a disposable Railway sandbox, where we run type checks, lint, a production build and Playwright browser checks. The model can change the presentation, while catalog loading and checkout links stay protected. Sellers preview a revision before publishing it and can roll back later. Bunny Storage holds the source, built files and an append-only journal, so the builder can recover its state without a SQL database. We added ENSv2 on Ethereum Sepolia for readable shop names such as coffee.merxet.eth. Resolver records link the name to the storefront, catalog and Hedera seller account. The backend handles registration gas, so sellers can claim a name from their existing Hedera session. Buyers see a name only after its records have been verified. That gives the shop a recognizable identity while keeping payments on Hedera. World Selfie Check is an optional seller badge. A wallet signature links the check to the seller's account, and a separate service verifies the proof with World. It stores verification metadata in SQLite, without storing selfies or raw proofs. Demo and sandbox badges are labeled separately; the badge is a person-presence signal, not a business guarantee. For AI-assisted shopping, our MCP server lets an agent prepare an order through a custom x402 flow and return an approval link or QR code. The buyer still reviews and signs in their browser wallet. Redis stores the quotes, and confirmation checks the matching Hedera transaction evidence.