bitcoin-mining-pool-architectures
Mining pool reward schemes: PPS, FPPS, PPLNS, PPS+, Score, prop. Block generation queue, share variance, payout cycles. Solo mining vs pooled. USE WHEN: comparing pools, designing reward systems, understanding miner economics.
What this skill does
# Pool Architectures & Reward Schemes Pools allow many miners to collectively find blocks. Differences are in how rewards are distributed. ## Reward schemes ### PPS (Pay-Per-Share) Miner gets fixed payment per accepted share. Pool absorbs all variance: - Pro: predictable income for miners. - Con: pool needs cash reserve to cover bad-luck periods. Fee: typically 4-5% to compensate pool variance risk. ### FPPS (Full Pay-Per-Share) PPS but miner also receives proportional share of **transaction fees** beyond just the subsidy. Most popular scheme as of 2024-2025. Fee: 2-3%. ### PPLNS (Pay-Per-Last-N-Shares) Reward = block_reward × (your_shares_in_last_N / total_shares_in_last_N). - Pool doesn't pay until block found. - Miners experience variance directly. - Discourages pool-hopping (you must mine consistently to be in the N window). Fee: 1-2% (lower because pool doesn't bear variance risk). ### PPS+ PPS for subsidy + PPLNS for fees. Hybrid. ### Score (deprecated / niche) Older scheme that decayed share scores over time. Largely replaced by PPLNS. ### Proportional Reward = your_shares / total_shares_this_round × block_reward. Vulnerable to pool-hopping; rarely used. ## Pool block-finding Pool's core function: 1. Construct block templates. 2. Distribute work to miners (Stratum V1 or V2). 3. Verify share submissions. 4. When a share is also a block (≤ network target), submit to network. 5. Distribute rewards per scheme. ## Variance considerations A solo miner finding a block: - Expected time = network_time × (network_hashrate / your_hashrate). - For 100 TH/s on 800 EH/s network: 8000 days = 22 years. Pooled: - Get reward proportional to your hashrate share, daily/hourly. - Variance reduced. ## Pool centralization risks - **51% attack**: top pools by hashrate can theoretically reorg. - **Censorship**: pools have OFAC-compliance pressure. - **Selfish mining**: pool with > 25% hashrate could selfish-mine. Mitigations: - Stratum V2 (miners choose own tx). - Decentralized pools (P2Pool, Ocean Datum). - Solo mining (CKPool, Public-Pool). ## Major pools (2025) - **Foundry USA** — largest by hashrate. - **AntPool** (Bitmain) — second. - **F2Pool** — historical leader. - **Braiins Pool** (formerly Slush Pool) — SV2-capable. - **ViaBTC**, **MARA Pool**, **Luxor**. - **Ocean** — non-custodial; decentralized template via Datum. ## See also - [pow/SKILL.md](../pow/SKILL.md) - [stratum-v1/SKILL.md](../stratum-v1/SKILL.md) - [stratum-v2/SKILL.md](../stratum-v2/SKILL.md) - [decentralized-pools/SKILL.md](../decentralized-pools/SKILL.md)
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.