Foundry polls mining clients on BIP-110 signaling

July 18 (Crypto-Information.Web) – Foundry USA Pool is asking its mining shoppers how the pool ought to sign on BIP-110, a proposed short-term Bitcoin tender fork that may prohibit specified data-carrying transaction varieties if activated.

In keeping with Foundry USA Pool’s public useful resource web page, shoppers who’re able to vote are directed to make use of a hyperlink of their electronic mail to entry a voting type. The web page says the voting window will stay open via the signaling-window shut date, forward of block 961,632.

Foundry Ballot Is Pool-Particular

The Foundry ballot is a consumer session for one mining pool. It’s not a network-wide Bitcoin vote, and it doesn’t present that BIP-110 has been adopted, locked in or activated.

Foundry’s position issues as a result of mining swimming pools coordinate block manufacturing for collaborating miners. Crypto-Information.Web’s explainer on Bitcoin mining and mining swimming pools covers how miners and swimming pools take part in block creation.

In a July 18 verification snapshot, mempool.area’s 1-week pool desk listed Foundry USA with 294 of 1,001 attributed blocks, or 29.37%. That’s noticed attributed block share for a shifting window, not actual hashrate.

What BIP-110 Would Do

The canonical BIP-110 specification lists the proposal as Standing: Full, Kind: Specification and Layer: Consensus. Full describes the doc’s standing solely. It doesn’t imply the Bitcoin community has accepted the proposal.

BIP-110 would briefly invalidate a number of transaction varieties throughout its lively interval if enforced. The foundations would prohibit new output scriptPubKeys over 34 bytes and restrict OP_RETURN outputs to 83 bytes. They’d additionally prohibit giant pushdata and witness objects. UTXOs created earlier than activation top can be grandfathered.

Underneath the BIP’s deployment design, the miner-signaling threshold is 1109 of 2016 blocks, or 55%. The necessary signaling window would run from blocks 961,632 via 963,647, with lock-in no later than block 963,648 if the BIP’s guidelines apply.

Tradeoffs and Counterpoints

The BIP’s personal tradeoff part says the proposal might constrain superior smart-contracting designs equivalent to BitVM-like makes use of. It additionally says different soft-fork improve hooks can be unavailable throughout the short-term interval, and a few Miniscript or OP_IF instances could possibly be affected.

Jameson Lopp, whose critique is linked by Foundry as a counterpoint, argued that BIP-110 carries chain-split threat and pockets edge-case threat in his information to the proposal. He additionally raised governance considerations and future-innovation constraints. Lopp argued that current block-space limits and charge markets already constrain undesirable transaction information.

A separate July 18 disclosure from Dathon Pwn reported a regtest replica of a late-upgrade chainstate validation hole towards BIP-110-enforcing Bitcoin Knots v29.3.knots20260508 software program. Crypto-Information.Web situated no maintainer acknowledgement or impartial replica of the BlockSlop report.

Foundry’s voting outcome and last signaling place are unknown. The precise boundary stays block 961,632.

Reporting by Zoran Spirkovski. Enhancing by Crypto-Information.Web.

Sources

Foundry USA Pool – Confirms consumer voting-form entry and the block 961,632 boundary language.https://providers.foundrydigital.com/bip-110_resources

BIP-110 specification – Helps the doc standing, proposed guidelines, UTXO grandfathering, 55% threshold and signaling-window blocks.https://bips.dev/110/

mempool.area mining pool API – Helps noticed attributed block share for Foundry USA within the 1-week pool desk.https://mempool.area/api/v1/mining/swimming pools/1w

Jameson Lopp – Gives named counterarguments linked by Foundry as a counterpoint.https://weblog.lopp.internet/a-laymans-guide-to-bip-110/

BlockSlop – Helps the attributed July 18 Dathon Pwn regtest replica report and its acknowledged scope limits.https://blockslop.dev/