Block version changes
Block version changes
Yesterday F2Pool switched from Version3 to Version4 blocks (block versions 0x10103 and 0x10104, respectively). If I understand the BIP rules correctly this doesn't lead to any problems for Namecoin Core users. What about Namecoin-Qt?
Re: Block version changes
This is BIP65, which was recently committed to Bitcoin Core and merged to Namecoin Core. It won't have any effect at all until 75% of hash rate update. Even then, it will only have an effect in very specific situations. Upgrade is only required once 95% of the hash rate produce version 4 blocks, and even then only miners really need to update. Others are degraded to SPV security, but can continue to use any old client/wallet. This is true both for old Namecoin Core versions and for Namecoin-Qt. (Namecoin-Qt is already in this state, so there won't be any change at all for users of the old client.)
BTC: 1domobKsPZ5cWk2kXssD8p8ES1qffGUCm | NMC: NCdomobcmcmVdxC5yxMitojQ4tvAtv99pY
BM-GtQnWM3vcdorfqpKXsmfHQ4rVYPG5pKS
Use your Namecoin identity as OpenID: https://nameid.org/
BM-GtQnWM3vcdorfqpKXsmfHQ4rVYPG5pKS
Use your Namecoin identity as OpenID: https://nameid.org/
Re: Block version changes
Meanwhile one of the EclipseMC servers ("US1"), myBTCcoin pool and four different P2Pool miners created V4 blocks.
Is it worth the effort implementing ACCT? And how much effort would this mean?
BIP65 opens up the possibility of developing an Atomic Cross-Chain Transfer (ACCT) feature (I'm not sure if Ian Knowles' ACCT AT is directly related to this).domob wrote:This is BIP65,
Is it worth the effort implementing ACCT? And how much effort would this mean?