How prasannaverse13/devmomentum works
Project type and purpose
• This is a full-stack Web3 application (“DevCommit Valuator”) that aggregates on-chain oracle data (FTSO price feeds, FDC attestation) with off-chain GitHub metrics to compute a “momentum score” for open-source projects.
• It consists of a React/TypeScript frontend, an Express.js backend (in-memory store), and integrations with external services (Flare Network oracles, GitHub API, MetaMask/Turnkey wallets).
File structure
• Top-level
– package.json, tsconfig.json, vite.config.ts, drizzle.config.ts (project configs)
– client/ (React frontend)
– server/ (Express backend)
– shared/ (TypeScript schema shared by both client & server)
• Client folder
– src/pages (route-driven pages)
– src/components (UI widgets: dashboard cards, FTSO & FDC widgets, wallet/auth components, shadcn/ui library)
– src/contexts & src/hooks (state management, wallet & repository contexts, utilities)
– src/lib (Ethers.js wrappers for FTSO, FDC, GitHub, Turnkey)
• Server folder
– index.ts (Express app bootstrap)
– routes.ts (API endpoints: add repo, list metrics, issue attestation)
– storage.ts (in-memory data store)
– vite.ts (server-side build integration)
README for technical stack & architecture
• Frontend: React + Vite + TailwindCSS + Chart.js + shadcn/ui
• Backend: Node.js + Express (REST API) + in-memory store (extensible to real DB)
• Blockchain: Ethers.js calls to Flare Coston2 contracts for FTSO & FDC
• Wallets: MetaMask & Turnkey embedded via turnkey.ts + wallet context
a. Main components
• Client (Browser)
• UI Layer: React pages & shadcn/ui components
• Business Logic: hooks, contexts, client/src/lib for interacting with oracles & GitHub
• Wallet Layer: MetaMask & Turnkey provider
• API Server
• Express.js REST endpoints (server/routes.ts)
• In-memory storage (server/storage.ts)
• Shared type definitions (shared/schema.ts)
• External Services
• GitHub API (repository metrics)
• Flare Network (FTSO & FDC smart contracts on Coston2)
• MetaMask / Turnkey (user wallet providers)
b. Relationships & interactions
• Browser → API Server: REST calls to manage tracked repositories and fetch computed scores
• Browser → Flare Oracles: Direct Ethers.js calls (via src/lib/ftso.ts and src/lib/fdc.ts) to fetch real-time data & attestations
• Browser ←→ Wallet: JSON-RPC calls for signing transactions (FTSO attestation, FDC attestation triggers)
• Server → GitHub API: Fetch off-chain metrics if backend augmentation is needed
• Server → Flare Network (optional): Backend-side attestation or data verification
c. Architectural patterns & principles
• Separation of Concerns: UI, business logic, data layer, blockchain interactions all in their own modules/directories
• Context API: Centralized state for wallet & repository contexts in the client
• Library/Connector Layer: src/lib wraps all Ethers.js and HTTP logic for external services
• Shared Schema: Type safety across client & server via shared/schema.ts
• Micro-service-like: Although a monolith, clear boundaries exist between frontend, backend, and external services
d. Key technologies & libraries
• Frontend: React, TypeScript, Vite, TailwindCSS, shadcn/ui, Chart.js
• Backend: Node.js, Express, Drizzle (for potential DB integration), vite-plugin for server
• Blockchain: Ethers.js, Flare Coston2 contracts (FTSO & FDC)
• Wallets: MetaMask, Turnkey Embedded Wallet
Detail without over-complicating
• Shared/schema.ts as a contract between client & server
• Major flows (momentum score calculation, attestation flow) with percent weights or step numbers