How pixelpow/findmyblock-pool works
Project Type & Purpose
• This is a single-page web interface (React + Tailwind CSS) for an anonymous Bitcoin solo mining pool.
• It does not contain its own mining backend; instead it relies on the external “public-pool” service for all mining protocol, pool management, and blockchain interactions.
• The front-end visualizes real-time stats, device monitoring, mining challenges, and handles user stratum connections.
File Structure Analysis
– Top-level files (package.json, postcss.config.js, tailwind.config.js) configure the build system and CSS pipeline.
– src/ folder holds all React source code:
• components/ – hundreds of presentational and container components (charts, dashboards, modals, panels).
• data/ – static data (e.g., challenges definitions).
• hooks/ – custom React hooks (e.g., useFearGreed).
• index.js + App.js – application entry point.
– No backend or API server code, confirming this is purely a front-end codebase.
README Insights
• Tech stack: React 19, Tailwind CSS, Framer Motion, Recharts.
• Architecture call-out: Miners → public-pool backend → FindMyBlock interface → Browser
• Backend requirement: public-pool server on port 23334 (hosts Stratum/WebSocket & REST API).
Main Components
a. External Bitcoin Miners (hardware, e.g., BitAxe, AvalonNano3)
b. public-pool Backend Service (Stratum/WebSocket server + REST API)
c. FindMyBlock React SPA (running in the user’s browser)
d. Third-party services (optional): Blockchain explorer APIs if used for difficulty & hashrate data
e. Static Hosting/CDN (serves the built SPA)
Interactions & Data Flows
• Miners ↔ public-pool (Stratum protocol over TCP/WebSocket for job assignment, share submission).
• React SPA ↔ public-pool (WebSocket or HTTP polling for real-time pool stats, network stats, difficulty).
• React SPA ↔ public-pool (REST API calls for user/device registration, challenge data).
• React SPA internal data flow:
– Custom hooks (e.g., useFearGreed) pull data from API endpoints.
– Components subscribe to hook state to render charts (Recharts), animations (Framer Motion), UI (Tailwind CSS).
Architectural Patterns & Design Principles
– Single-Page Application (SPA) with client-side routing/state.
– Component-based UI (presentational vs. container components).
– Unidirectional data flow (hooks → component props → render).
– Separation of concerns: styling (Tailwind), animation (Framer Motion), charting (Recharts), data fetching (hooks/API).
– Externalized backend allows front-end to remain stateless and anonymous.