Binance gives miners 28 days to leave its pool before shares stop counting

Binance's published material does not link the closure to its Brazil restriction ^[12], and the sequence invites the link anyway, because the Brazil restriction ^[11] comes first. We'd treat the connection as unproven. A central bank rule explains why one country loses a pool. It takes a separate decision to close a pool, a cloud product, a savings product and an accelerator everywhere ^[3]. The counter-thesis is that a pool fenced off by country was not worth running, which would make Brazil the cause after all. Both readings fit the dates.

The money question is narrower than it looks, or rather it hangs on one adjective. The promise covers eligible prior rewards and balances ^[5], and the coverage does not say who qualifies. We'd expect the word to be boilerplate. A miner reporting a pre-shutdown balance held back would show otherwise.

Records are the one clock that outlasts the cutoff. The page stays up 14 days after 07:00 UTC on Nov. 10 ^[10], and any export of payment statuses has to happen inside that window.

Binance Pool's share of network hashrate is not in the coverage, so the absence of a price reaction in initial reports ^[14] cannot be sized against anything. Repointed hashrate reappears at rival pools. If those pools show no matching rise around Nov. 10, machines were stopped or left behind, and the closure costs miners more than a configuration change.