How damianotobasco/moredashboard works
Project type and purpose
• Full-stack, real-time crypto dashboard built in React/TypeScript (Vite/Tailwind)
• Serverless “backend” via Supabase Functions (Token Data, Transfers)
• Integrates on-chain data (PulseChain RPC) and off-chain APIs (DexScreener, Moralis)
Main components
A. Frontend (Client Browser)
• React app (src/)
• UI components: Dashboard, PriceChart, BurnInfo, TokenHolders, TransfersTable, TradingModule
• UI library bits: ButtonDemo, GlassPanel, KpiCard, shiny-text, shooting-stars (src/components/ui)
• Hooks & utilities: useDataFetching, useSwap, formatters, mockData
• Blockchain helper: wagmi.ts, contracts.ts in src/lib
• Wallet connection: WalletConnect.tsx
• Build toolchain/config: Vite, Tailwind, PostCSS, ESLint, TypeScript
B. Backend (Supabase Functions)
• token-data function (supabase/functions/token-data/index.ts)
• transfers function (supabase/functions/transfers/index.ts)
• (Optionally) Supabase Postgres DB (migrations/20250428015327_navy_dune.sql)
C. External Services
• PulseChain RPC (via VITE_PULSECHAIN_RPC)
• DexScreener API
• Moralis API (optional)
Relationships & data flow
1) User’s Browser loads React app (index.html → main.tsx)
2) React components retrieve data via two parallel paths:
a. Direct on-chain calls (Wagmi → PulseChain RPC)
• TokenInfo, PriceChart, BurnInfo, TradingModule for real-time on-chain state
b. HTTP calls → Supabase Functions
• /token-data → aggregates holders, price history, burn stats
• /transfers → pull transfer history, paginated data
Both Supabase Functions in turn may query PulseChain RPC, DexScreener, Moralis, and/or Postgres DB.
3) React displays updated metrics, charts, tables.
4) TradingModule uses wagmi + user’s wallet (WalletConnect) to submit trades to the chain.
Architectural patterns & principles
• Component-driven UI (React) with separation of “dumb” UI vs data hooks
• Serverless “microservices” (Supabase Functions) for data aggregation
• Immutable on-chain source of truth + optional caching in Supabase/Postgres
• Environment-driven configuration (VITE_… variables)
Detailing Technologies & Config
• Frontend: Vite (vite.config.ts), Tailwind (tailwind.config.js), PostCSS, ESLint
• Code: TypeScript, React (TSX), custom hooks, supabase-js (for functions auth)
• Deployment: npm run dev/build → dist/ → static host
• Env vars: VITE_PULSECHAIN_RPC, VITE_TOKEN_ADDRESS, VITE_BURN_ADDRESS, VITE_MORALIS_API_KEY, VITE_DEXSCREENER_API_KEY