Tableau de censure des pools de minage
Réponse rapide
Seulement deux pools de ce tableau ont des incidents de filtrage de transactions OBSERVÉS et datés qui ont survécu au tri des faux positifs : F2Pool (adresses sanctionnées par l'OFAC, reconnu par son fondateur en novembre 2023, re-signalé pour des blocs de décembre 2024) et OCEAN (une politique de données ouverte basée sur Knots concernant la taille des OP_RETURN et les inscriptions, à son lancement de décembre 2023 — que son propre protocole DATUM permet désormais à chaque mineur de contourner). MARA Pool a censuré des transactions sanctionnées en mai 2021 et a publiquement fait marche arrière en un mois. Tous les autres pools : aucun filtrage observé — y compris trois (Foundry, ViaBTC, SBI Crypto) signalés par b10c puis blanchis comme faux positifs de déplacement de frais. Une adresse américaine, un formulaire KYC ou le mot « conforme » dans le marketing sont un risque INFÉRÉ, pas un incident, et ce tableau ne confond jamais les deux.
La résistance à la censure en pratique : les transactions filtrées finissent quand même confirmées — juste dans le bloc de quelqu'un d'autre. Le correctif structurel, ce sont les templates contrôlés par le mineur : le DATUM d'OCEAN est en ligne aujourd'hui ; le Job Declaration de Stratum V2 ne l'est surtout pas. Si cela compte pour vous, minez là où vous construisez le template, ou exploitez votre propre pile solo.
observed incident daté, source citée none-observed étudié, rien trouvé (incl. faux positifs blanchis) unknown aucune étude ne couvre ce pool A/B/C grade de preuve
| Pool | Filtrage | Incidents (datés) | Politique OP_RETURN / données | KYC | Template | Échappatoire aujourd'hui | Juridiction | Grade |
|---|---|---|---|---|---|---|---|---|
| F2Pool | observed | 2023-11 — b10c/miningpool-observer identified four F2Pool blocks (Sep-Oct 2023) missing OFAC-sanctioned transactions; co-founder Chun Wang acknowledged running a transaction-filtering patch and said it was disabled 'for now'. (b10c observation #8 (b10c.me/observations/08-missing-sanctioned-transactions/)) 2025-01 — b10c reported fifteen OFAC-sanctioned transactions missing from about nine F2Pool blocks mined in December 2024, concluding F2Pool might be filtering again; all were later mined by other pools. (b10c observation #13 (b10c.me/observations/13-missing-sanctioned-transactions-2024-12/)) |
standard-core — Has mined non-standard/oversized OP_RETURN and inscription data — its observed filtering is OFAC-address-specific, not a data policy. | no | pool-controlled | None in production. | China-origin (co-founder Chun Wang); operating entity offshore/undisclosed | A |
| The only pool with a founder-acknowledged sanctions filter, applied intermittently. At its hashrate share this delays rather than prevents confirmation — the filtered transactions were mined by others in later blocks. | ||||||||
| MARA Pool | observed | 2021-05 — Marathon directed its hashrate to an OFAC/AML-compliant pool and mined its first 'clean' (censored) block in early May 2021, filtering sanctioned transactions. (Marathon press release + Bitcoin Magazine, May 2021) 2021-05 — After community backlash, Marathon announced in late May 2021 it would stop filtering and move all miners to standard Bitcoin Core 0.21.1 — the reversal is the canonical precedent that public censorship costs a pool more than it earns. (CoinDesk / The Block, May 31 2021) |
standard-core — Post-2021 reversal. | unknown | pool-controlled | None; MARA Pool is largely MARA's own fleet. | United States (MARA Holdings, Fort Lauderdale FL; Nasdaq: MARA) | A |
| Historic, self-declared OFAC censorship — publicly abandoned within about four weeks. Listed as the reversed case, not a current filterer. | ||||||||
| OCEAN | observed | 2023-12 — At launch (running Bitcoin Knots), OCEAN's default template filtered Ordinal inscriptions and rejected Samourai Whirlpool CoinJoin / BIP47 notification transactions whose 46-byte OP_RETURN exceeded the 42-byte datacarrier limit; Samourai publicly called it censorship and OCEAN acknowledged the inscription filtering. (news.bitcoin.com + atlas21.com, Dec 2023) |
filters — Knots-based DEFAULT template restricts OP_RETURN size and inscriptions — a data policy, not OFAC-address filtering. Since Sep 30 2024, DATUM makes the restriction miner-overridable: each miner can build its own template. | no | miner-controlled | DATUM — live since Sep 30 2024: the miner runs the DATUM Gateway against their OWN bitcoind and builds their own block template while keeping pooled TIDES payouts. The strongest real escape hatch on any pool today. | United States (Delaware; co-founded by Luke Dashjr) | A |
| Non-custodial, no KYC (payout address only), coinbase-paid rewards. Its filtering is a spam/data-policy stance the pool is open about — and the only 'filtering' incident on this scorecard that the affected miner can individually override. | ||||||||
| AntPool | none-observed | — | standard-core — Mines inscriptions and large OP_RETURN data. | no | pool-controlled | None in production; SV2 working-group member, no live miner job declaration. | China-origin (Bitmain-affiliated); operating entity offshore/undisclosed | B |
| b10c's 2021 Taproot observation (some pre-activation P2TR spends not mined by F2Pool and AntPool) was standardness behavior before lock-in, not sanctions filtering. No OFAC filtering observed. | ||||||||
| Binance Pool | none-observed | — | standard-core | yes | pool-controlled | None. | Global/ambiguous (no single disclosed domicile) | C |
| Mining requires a KYC'd Binance account. No documented transaction-filtering incident; occasional exchange-pool empty/near-empty blocks are propagation-latency behavior, not censorship. | ||||||||
| BitFuFu | none-observed | — | unknown | yes | pool-controlled | None (cloud-mining / hosted model). | Singapore (BitFuFu Inc., Nasdaq: FUFU) | C |
| Primarily a listed cloud-mining service; KYC required. No documented filtering. | ||||||||
| Braiins Pool | none-observed | — | standard-core | no | pool-controlled | Stratum V2 transport is live (encryption, less stale work) and BraiinsOS+ ships a native SV2 client — but the SV2 Job Declaration protocol that would let a miner build its own template is not a confirmed generally-available customer option as of mid-2026. Honest status: SV2 efficiency yes, miner-side template selection not yet. | Czech Republic (Braiins Systems, Prague; formerly Slush Pool) | B |
| Authored the SV2 spec. Claims of full job-declaration support overstate today's practical status; treat the JD escape hatch as not yet real here. | ||||||||
| EMCD | none-observed | — | unknown | no | pool-controlled | None documented. | Self-stated Hong Kong HQ; mixed-region infrastructure (Europe, Kazakhstan, elsewhere) | C |
| No KYC for basic mining (states AML monitoring). Jurisdiction is a blended self-report, not a single clean domicile. | ||||||||
| Foundry USA | none-observed | — | standard-core — Mines standard templates including large OP_RETURN/inscription transactions; no published filtering policy. | yes | pool-controlled | None native today — FPPS, the pool builds the template; no Stratum V2 job declaration in production. | United States (Rochester, NY; Digital Currency Group subsidiary) | B |
| b10c's Sep-Oct 2023 sweep flagged one Foundry block missing an OFAC-sanctioned transaction but ruled it a false positive (fee-displaced), and Foundry later mined the same sanctioned addresses. Compliance risk here is INFERRED from US jurisdiction + KYC onboarding, not observed behavior. | ||||||||
| Luxor | none-observed | — | standard-core | no | pool-controlled | None native (FPPS, pool-built template). | United States (Luxor Technology, Seattle WA) | B |
| US company reported to operate without mandatory miner KYC. No filtering observed; compliance risk is INFERRED from jurisdiction only. | ||||||||
| NiceHash | none-observed | — | standard-core | tiered | pool-controlled | None for hashpower sellers — NiceHash is a marketplace: the BUYER directing the rented hashrate picks the pool and therefore the template policy. | Slovenia (NiceHash / H-BIT d.o.o.) | B |
| Hashrate broker rather than a classic block-building pool; KYC tiers by activity/withdrawal volume. | ||||||||
| Poolin | none-observed | — | standard-core | no | pool-controlled | None. | China-origin (Hong Kong / Singapore registrations) | C |
| Greatly diminished since its 2022 withdrawal freeze; no filtering study covers current Poolin. | ||||||||
| Public Pool | none-observed | — | standard-core — Hosted instance templates come from the project's own Bitcoin Core node. | no | miner-controlled | Self-host: fully open source with one-click Umbrel/Start9 deployment — the miner runs their OWN node and fully controls the template. The most accessible run-your-own-template path for Bitaxe/home miners. | US-based maintainer; MIT-licensed, self-hostable | B |
| The censorship-resistance value is in self-hosting against your own node. | ||||||||
| SBI Crypto | none-observed | — | standard-core | unknown | pool-controlled | None documented. | Japan (SBI Crypto Co., SBI Holdings subsidiary) | B |
| b10c's Jan 2025 analysis attributed an SBI block's missing sanctioned transaction to block-weight reservation / fee displacement, NOT filtering. Regulated Japanese parent implies an INFERRED compliance posture only. | ||||||||
| Solo CK (solo.ckpool.org) | none-observed | — | standard-core — Operator states the pool does not filter any transactions and uses default Bitcoin Core selection. | no | pool-controlled | Self-host: ckpool-solo source is public, so you can run your own instance against your own bitcoind for full template control. The hosted endpoint builds a Core-default, unfiltered template for you. | Operated by developer Con Kolivas (Australia) | B |
| No registration or KYC; solo reward model. 'Pool-controlled' is technically true of the hosted endpoint even though the rewards are solo. | ||||||||
| SpiderPool | none-observed | — | unknown | unknown | pool-controlled | None documented. | Asia-origin (INFERRED); operating entity not clearly disclosed | C |
| Fast-growing FPPS pool. No filtering study covers it; the jurisdiction is inference, not a filing. | ||||||||
| ViaBTC | none-observed | — | standard-core | no | pool-controlled | None in production. | China-origin; operating entity offshore/undisclosed | B |
| One flagged block in b10c's Sep-Oct 2023 sweep was concluded a false positive (transaction too young / fee-displaced); ViaBTC later mined the same sanctioned addresses. | ||||||||
| WhitePool | none-observed | — | unknown | yes | pool-controlled | None documented. | Europe (WhiteBIT exchange; launched Aug 2024) | C |
| Exchange-operated FPPS pool inside a KYC'd exchange ecosystem. No filtering or template-transparency data available. | ||||||||
| Carbon Negative | unknown | — | unknown | unknown | pool-controlled | None documented. | UNKNOWN (operating entity undisclosed) | C |
| Insufficient public information — recorded as unknown rather than guessed. | ||||||||
| KuCoin Pool | unknown | — | unknown | yes | pool-controlled | None documented. | Seychelles (KuCoin exchange entity) | C |
| Exchange-tied pool with mandatory KYC; minor hashrate, no transparency data. | ||||||||
| Mining Squared | unknown | — | unknown | unknown | pool-controlled | None documented. | UNKNOWN (operating entity not reliably documented) | C |
| Operator and jurisdiction could not be verified from primary sources — recorded as unknown. | ||||||||
| SECPOOL | unknown | — | unknown | unknown | pool-controlled | None documented. | Asia (INFERRED); operating entity undisclosed | C |
| No transparency data; jurisdiction inferred only. | ||||||||
| Ultimus | unknown | — | unknown | unknown | pool-controlled | None documented. | UNKNOWN (Asia-origin INFERRED); operating entity undisclosed | C |
| Self-describes as 'compliant' — a marketing claim that might imply OFAC/AML alignment (INFERRED). No incident data exists either way. | ||||||||
Données ouvertes (CC BY 4.0) : CSV · JSON · API : /wp-json/dc/v1/pool-censorship
Produits, réparations et guides connexes
- comment D-Central diagnostique les réparations ASIC
- bibliothèque de dépannage ASIC
- manuels ASIC et guides de réparation
- hashboards de remplacement
- cartes de contrôle ASIC
- blocs d’alimentation ASIC
- hashboard de remplacement pour la famille S19
- carte de contrôle de remplacement C52
- bloc d’alimentation APW12 pour S19
- comparer les specs dans la base de mineurs ASIC
- comparer les specs des mineurs ASIC
- base de mineurs ASIC
- services de réparation ASIC
- specs et rentabilité de l’Antminer S19
- acheter un Antminer S19 testé
- guide d’entretien Antminer S19
- service de réparation Antminer S19
- specs de l’Antminer S21
- Bitmain Antminer S21
- guide d’entretien Antminer S21
- puce BM1370BC pour S21 Pro
Dernière révision: 27 juillet 2026.
