Pages:
Author

Topic: IMPORTANT: April 1 deadline for BIP16 support - page 2. (Read 3984 times)

newbie
Activity: 53
Merit: 0
Again: if you don't upgrade and are a solo miner, pool operator, or p2pool user you will almost certainly waste time hashing bad blocks after April 1.

This only applies when you include transactions generated by other people (because the old client will not be able to fully verify them).

If you think this statement is incorrect, then please elaborate (with technical details).
legendary
Activity: 1652
Merit: 2216
Chief Scientist
See this thread for BIP16-compatible-backported release candidates:
  https://bitcointalksearch.org/topic/please-help-test-bitcoin-054rc1-and-045rc1-72069

A final 0.6 release candidate will be out very soon, the last issues are being resolved now.

Again: if you don't upgrade and are a solo miner, pool operator, or p2pool user you will almost certainly waste time hashing bad blocks after April 1.
legendary
Activity: 1652
Merit: 2216
Chief Scientist
I'm posting this to both this and the Mining Pools subforum:

To all pool operators, solo miners and p2pool miners; I have an announcement.

As everyone well remembers, we are upgrading the block-validity rule of Bitcoin to support short multisignature addresses. We realize that upgrading the code that you've been using for a long time is at least inconvenient and, for some of you, even painful or scary. But in the case of BIP30, which went into effect with the appropriately safe network support on March 15, it was necessary and in the case of this announcement the long-term benefits will far outweigh the short-term costs of this transition.

Therefore I'd like to announce that support for BIP16 has acquired a majority of mining support needed to prevent a potential permanent fork and will be activated on April 1st as previously planned.

This chart shows support over the last week: http://blockchain.info/P2SH.  Support is well over 70%.

So if you are a pool operator, solo miner, or p2pool miner you need to upgrade your Bitcoin-Qt/bitcoind before April 1st. Running a version of bitcoind earlier than 0.6 release candidate 3 past this date means running the risk of potentially wasting your hashing power mining invalid blocks since earlier versions will accept invalid spends of BIP16 transactions into their memory pools and will put them into blocks considered invalid by the majority.

p2pool users will also need to upgrade to the latest version of p2pool.

If you are a miner connecting to a mining pool, you can ignore this message.

For non-miners: version 0.6 also contains several important bug and denial-of-service fixes, so if you can, upgrade.

Backports of the BIP16 code to earlier releases are available if you are running a patched bitcoind. Patched binaries of older releases will be available soon.
Pages:
Jump to: