Technical Documentation
Technical overview
Nodo’s layers today: shop, Protecta, wallet / P2P, and identity.
Nodo is not a marketplace with a search bar on top. It is a platform with separate contexts that share identity.
Layers
| Layer | Responsibility |
|---|---|
| Shop | Catalog, page, cart, and the WhatsApp order. A designed page when it is agreed. |
| Protecta | Custody of an order’s payment until delivery. |
| Wallet / P2P | USDC on Base; per-trade on-chain escrow; fiat off-chain for P2P. |
| Identity | The account of the person who opens the shop. |
Official clients are web (Next.js), app (React Native: iPhone and iPad), and desktop (Tauri). Logic lives in the API.
Principles
- The shop first — the page and the order do not depend on a feed.
- The account publishes — the person who opens the shop loads the catalog.
- Thin clients — the same API on every surface.
- Little public internals — models, thresholds, and internal names stay unpublished.
Stack (high level)
| Area | Approach |
|---|---|
| API | Node.js service by domain |
| Persistence | PostgreSQL |
| Auth | Session + social providers (Apple / Google) |
| Plan payments | Stripe (Checkout on the web) |
| Page | Next.js, on the shop’s URL |
| Crypto | Privy / external wallet; Base; USDC escrow contracts for P2P |
Operational detail (exact models, weights, internal files) is not part of this public documentation.