How mempool/mining-pools works
Project type and purpose
• This is not a full-stack application but an open-source data repository for “mining pools” definitions.
• Its sole purpose is to maintain and validate JSON files (pools-v2.json, pools.json) that describe Bitcoin mining pools (names, links, regex tags, payout addresses).
• Downstream services (not in this repo) like the mempool backend fetch and use this data at runtime to tag blocks by pool.
File structure
• Top-level files
– LICENSE
– README.md (project description, contribution guide)
– pools.json (legacy list)
– pools-v2.json (authoritative, JSON schema with coinbase_tags, payout_addresses, slugs)
– dupes.sh (helper script to detect duplicates)
• .github/workflows/validate-json.yml
– CI pipeline to lint/validate JSON after each commit.
• No source code—this repo is purely data + validation.
README for additional insights
• Describes how to add or update mining pools, slug conventions, regex matching logic, payout address matching.
• Points to mempool backend code that:
– Fetches latest JSON on startup (configurable URLs)
– Parses regexes to assign blocks to pools
– Optionally re-indexes blocks when JSON changes
• Provides examples and guidance for contributors.
Elements
• Clear labels for each component (GitHub Repo, CI Pipeline, Backend Fetcher, Pools-Parser, DB, API, Frontend)
– commit → CI → merge
– backend startup → fetch JSON
– parser → database
– API → frontend
– Backend components in another
– Frontend/UI in yet another