zenith-protocol-

ZENIT Protocol is a production-oriented Web3 application split into a Vite frontend and a Node/TypeScript backend API. The README describes it as combining wallet connectivity, blockchain-based transactions, referral systems, matrix participation, user profiles and on-chain interaction into a decentralized ecosystem. Architecture and deployment - Frontend: deployed on Vercel from the frontend/ directory, built with npm run build and output to dist/. - Backend: deployed as a Render Web Service from backend/, built with npm ci && npm run build and started with npm start. - Database: Supabase PostgreSQL, connected via the database connection string from Supabase. - Wallet authentication: Reown AppKit / WalletConnect with BNB Smart Chain. The frontend is intentionally limited to storing the public API base URL and the Reown project ID. JWT tokens, database credentials and other server secrets stay backend-only. Database setup Run the canonical migration 20260913000000_zenit_production.sql. It establishes the backend's wallet-auth and session model, including nonce and session tables. The README warns against running superseded 20260912 ZENIT migrations from older revisions of the repository. Current capabilities and production boundary The application supports real wallet-signature authentication, backend-backed profiles, referrals, matrix data, transactions and withdrawal-request creation. Importantly, it does not claim that a withdrawal is paid on-chain. Real-value settlement would still require a separately deployed and audited smart contract, a transaction processor, a confirmation/indexing process and explicit withdrawal approval rules. This repository is therefore best understood as an application layer and API for a Web3-style platform, with clear separation between frontend, backend and database, and with an explicit statement of what is not yet implemented on-chain.