Zedify is a merchant commerce platform giving small businesses — starting with food, fashion,
gadgets, and vehicle sellers — a ready-to-launch storefront with Fiber Network payments built in
from checkout, alongside fiat rails. Rather than requiring every merchant to commission custom
development, Zedify uses a template-based shop builder with owner-controlled theming and
checkout settings (including whether to accept pay-on-delivery), keeping delivery costs low
while still integrating a production Fiber Network Node for real, routed CKB/UDT settlement. The
storefront and dashboard are live today at wt-payments-frontend.vercel.app, backed by our
own production FNN node on CKB testnet. We’re requesting a grant to take this from a working testnet deployment to a mainnet-ready, audited product targeting first Nigeria, then broader emerging-market, merchant adoption.
Detailed Technical Specification
Problem:
Small merchants in markets like Nigeria face two compounding problems: e-commerce tooling
that’s either too expensive or too generic for their category of business, and payment
infrastructure built around card rails with high fees, slow settlement, and no protection against
local currency depreciation.
Solution
● A multi-category storefront template (food, fashion, gadgets, vehicles) with
category-aware product attributes, so merchants get a working store without bespoke
development
● Fiber Network integrated as a first-class checkout option alongside fiat, generating real
invoices against our own production FNN node
● A stablecoin savings feature routing fiat deposits into RUSD (Fiber/CKB-native), USDT,
or USDC — giving users a Fiber-native option for preserving value against currency
depreciation, extending RUSD’s exposure to a mainstream non-crypto-native audience
Architecture:
● Backend: AdonisJS 5 (TypeScript), PostgreSQL/Lucid ORM, deployed on Render
● Frontend: Next.js, deployed on Vercel — live storefront and merchant dashboard, not
just a repo
● Fiber integration: fiber-rpc-js against a self-hosted, production FNN node (v0.9.1),
running persistently via systemd with Biscuit-scoped RPC authentication
● Payment detection: a dedicated polling path (PaymentIndexerService) that queries
our own node’s invoice/payment status directly — correct for Fiber’s off-chain settlement
model, rather than watching an on-chain indexer the way our EVM rail does
Current status (testnet, verified)
● Live merchant storefront and dashboard deployed and publicly reachable at
wt-payments-frontend.vercel.app, wired end-to-end to the backend below — not just a
local demo
● Production FNN node funded, peered with public testnet bootnodes, holding live
ChannelReady payment channels
● Real invoices generated through our own checkout API (not manual CLI), confirmed
structurally valid
● Multiple genuine routed payments between independent nodes settled with status:
Success, confirmed via get_payment
● RUSD configured as a supported settlement asset alongside USDT/USDC
Try it yourself:
If you run fnn-cli or an equivalent Fiber node, you can pay our live storefront for real, right
now:
- Connect to our node — peer address and pubkey are in the backend README.
- Visit wt-payments-frontend.vercel.app, add a product to cart, and choose Fiber at
checkout to get a live fibt… invoice. - Pay it:
fnn-cli payment send_payment --invoice - If routing fails with no path found, open a small direct channel to us (details in the
README) — testnet liquidity can be uneven, but a direct channel guarantees a route. - Confirm settlement with
fnn-cli payment get_payment --payment-hash<payment_hash>— look forstatus: Success.
Need testnet CKB first? The Nervos Pudge Faucet works.
Open items, stated plainly
● A fully external, judge/community-tested routed payment (infrastructure and instructions
are ready — see JUDGE_INSTRUCTIONS.md in the backend repo)
● Liquidity/on-ramp partner selection for the fiat→stablecoin conversion path
● Legal review of the custodial stablecoin savings feature ahead of handling real funds,
given it’s open to any platform user.
Links
● Live storefront & dashboard: www.wt-payments-frontend.vercel.app/
● Frontend repo: github.com/chukwuagoziesolomon/wt-payments--frontend-
● Backend repo: github.com/chukwuagoziesolomon/zedify-server-
We’d genuinely like community members to try the routed payment flow above and tell us where
it breaks.