The enforcing fork remains stuck at Bitcoin’s full mining difficulty as mandatory signaling proceeds with little hashpower support. Bitcoin’s BIP-110-enforcing branch stalled at block 961,633 on Sunday after producing only two blocks, while the non-enforcing chain advanced to 961,721, widening the gap to 88 blocks. According to the BIP-110 monitor, updated at 10:19 am UTC, the branch’s latest block had been mined about 12 hours earlier. Ocean records show that a pseudonymous mining group called Roughnecks produced the branch’s first two blocks using Ocean’s Decentralized Alternative Templates for Universal Mining (DATUM) mining protocol. The divergence began after BIP-110 entered mandatory signaling at block 961,632 on Saturday. Only 51 of the preceding 2,016 blocks, or 2.53%, signaled support. During this window, BIP-110 nodes reject blocks that do not signal through version bit 4, while ordinary Bitcoin nodes accept both signaling and non-signaling blocks. Read more
The rules, effective Jan. 1, 2027, cover transactions above $10,000 sent to overseas providers or self-custody wallets, along with other transfers flagged for review. Brazil’s central bank will require virtual asset service providers (VASPs) to place precautionary holds of up to 24 hours on certain transfers to foreign platforms or self-custody wallets as part of new measures aimed at preventing fraud. On Friday, the Banco Central do Brasil (BCB) said the requirement will apply to funds received above $10,000, either in a single transaction or based on a customer’s total transactions in a day. Providers must also hold other transfers requiring further scrutiny under their risk-management policies. The rules take effect on Jan. 1, 2027. Providers must notify customers of holds and keep records of fraud incidents, attempted fraud and corrective actions. A VASP may complete its assessment and release a transfer before the 24 hours expire, provided that it follows parameters set out by the central bank. Read m...
Foundation and Citadel21 reported drained Lightning nodes, but the total amount stolen and number of affected operators remain unknown. BTCPay Server has temporarily restricted public remote connections to Lightning Network nodes running Lightning Network Daemon (LND) software after attackers exploited a critical vulnerability to obtain credentials and move funds. BTCPay said the restriction prevents external wallets such as Zeus from connecting through a BTCPay Server domain or Tor onion address on Docker deployments. BTCPay said Lightning payments can continue and that it plans to restore the remote-access option when it considers it safe. Version 2.4.2 installs LND version 0.21.1 and automatically regenerates the macaroon credentials on standard BTCPay installations. The project advised operators to check for unauthorized payments, unexpected channel closures, unfamiliar peers and discrepancies in their onchain or Lightning balances. Read more
The deployment milestone tests whether enforcing nodes can sustain the change amid limited miner signaling and discussion of a hard-fork fallback. Bitcoin Improvement Proposal 110 entered its mandatory-signaling phase at block 961,632 on Saturday, with miners signaling support in just 51 of the preceding 2,016 blocks, or 2.53%, well below the 55% threshold required for early activation, according to the BIP-110 monitor. Starting at block 961,632, nodes enforcing BIP-110 began rejecting blocks that did not set version bit 4, while ordinary Bitcoin nodes continued accepting both signaling and non-signaling blocks. A minority BIP-110 branch subsequently emerged, but quickly fell behind the dominant chain. The low signaling rate makes a sustained rival chain unlikely without substantially greater miner participation. With relatively little mining support, a BIP-110 branch could advance slowly or stop producing blocks altogether. Read more