Changing merge-mining format for BIP9

domob
Posts: 1083
Joined: Mon Jun 24, 2013 11:27 am
Contact:

Re: Changing merge-mining format for BIP9

Post by domob » Sat Mar 19, 2016 9:45 am

Bitcoin merged BIP9 last week - https://github.com/bitcoin/bitcoin/comm ... fbec6bc5ed. Miners will start to set the corresponding high bit in nVersion as soon as they upgrade (no activation time), but that's not an immediate problem for us as far as I can tell.

Nevertheless, I think we should take this as a motivation to speed up the fork process. The code is already mostly ready in https://github.com/domob1812/namecore/tree/hardfork, just missing regression tests and adding other things to the hardfork (removing the BDB lock limit, getting rid of Namecoin nVersion for transactions is my plan).

Any thoughts? Testing and review of the code is already welcome, of course (as always).
BTC: 1domobKsPZ5cWk2kXssD8p8ES1qffGUCm | NMC: NCdomobcmcmVdxC5yxMitojQ4tvAtv99pY
BM-GtQnWM3vcdorfqpKXsmfHQ4rVYPG5pKS
Use your Namecoin identity as OpenID: https://nameid.org/

biolizard89
Posts: 1932
Joined: Tue Jun 05, 2012 6:25 am
os: linux

Re: Changing merge-mining format for BIP9

Post by biolizard89 » Sat Mar 19, 2016 10:36 am

Since it looks like we need to deal with the hardfork fairly soon, I've set up a GitHub milestone for the nc0.12.0 release. These are all the issues I'm aware of that I think we should consider fixing for the nc0.12.0 release. I'd lean toward releasing the hardfork sometime after nc0.12.0 (let's say nc0.12.1), so that if we discover an issue in nc0.12.0 that prevents people from abandoning 0.3.80, we can get it fixed before the 0.3.80 users get kicked off the network.

https://github.com/namecoin/namecoin-co ... s/nc0.12.0

I'm aware that a significant number of these issues involve me. I will do my best to deal with them ASAP. If anyone disagrees with my evaluation of an issue for this milestone (in either direction), please tag me in the corresponding issue (@JeremyRand).
Jeremy Rand, Lead Namecoin Application Engineer
NameID: id/jeremy
DyName: Dynamic DNS update client for .bit domains.

Donations: BTC 1EcUWRa9H6ZuWPkF3BDj6k4k1vCgv41ab8 ; NMC NFqbaS7ReiQ9MBmsowwcDSmp4iDznjmEh5

domob
Posts: 1083
Joined: Mon Jun 24, 2013 11:27 am
Contact:

Re: Changing merge-mining format for BIP9

Post by domob » Sun Mar 20, 2016 4:59 pm

BTC: 1domobKsPZ5cWk2kXssD8p8ES1qffGUCm | NMC: NCdomobcmcmVdxC5yxMitojQ4tvAtv99pY
BM-GtQnWM3vcdorfqpKXsmfHQ4rVYPG5pKS
Use your Namecoin identity as OpenID: https://nameid.org/

biolizard89
Posts: 1932
Joined: Tue Jun 05, 2012 6:25 am
os: linux

Re: Changing merge-mining format for BIP9

Post by biolizard89 » Mon Mar 21, 2016 3:28 am

Quote from IRC earlier today, which may be of interest.
<qpm> freenode:<btcdrak> qpm: plddr: the first BIP9 deployments are scheduled pretty soon https://lists.linuxfoundation.org/piper ... 12567.html - while the starttime is set to May 1st, code will be released before. And from the CLTV softfork, 20% of miners upgraded to master before any official release.
Jeremy Rand, Lead Namecoin Application Engineer
NameID: id/jeremy
DyName: Dynamic DNS update client for .bit domains.

Donations: BTC 1EcUWRa9H6ZuWPkF3BDj6k4k1vCgv41ab8 ; NMC NFqbaS7ReiQ9MBmsowwcDSmp4iDznjmEh5

domob
Posts: 1083
Joined: Mon Jun 24, 2013 11:27 am
Contact:

Re: Changing merge-mining format for BIP9

Post by domob » Mon Mar 21, 2016 5:36 pm

biolizard89 wrote:Quote from IRC earlier today, which may be of interest.
<qpm> freenode:<btcdrak> qpm: plddr: the first BIP9 deployments are scheduled pretty soon https://lists.linuxfoundation.org/piper ... 12567.html - while the starttime is set to May 1st, code will be released before. And from the CLTV softfork, 20% of miners upgraded to master before any official release.
Yes - the code is actually already submitted (at least the one setting the "flagging" high bits for general BIP9-support, I'm not sure about others). As far as I can tell, this code is not yet an immediate problem for Namecoin - disallowed parent blocks are only those which either set bit 0x100 or have the higher 16 bits exactly equal to 1. Nevertheless, I think that we should try to proceed as fast as possible (without hastening too much and screwing it up). I have disabled the creation of BIP9-signalling blocks from Namecoin itself for the moment, as those would not be valid until the fork is in.
BTC: 1domobKsPZ5cWk2kXssD8p8ES1qffGUCm | NMC: NCdomobcmcmVdxC5yxMitojQ4tvAtv99pY
BM-GtQnWM3vcdorfqpKXsmfHQ4rVYPG5pKS
Use your Namecoin identity as OpenID: https://nameid.org/

Post Reply