Namecoin Forum

Sorry. Try now. Thanks, testing now. I think a fix for ArtForz's Geitz Geld attack would be useful before merged mining is activated. Without this a >51% attacker can keep difficulty low while generating blocks fast. With merged mining this means they can attack the namecoin network 'for free' sinc...

vinced wrote:I released version nc0.3.24.62 with a corrected lockin patch from makomk. Please test.

The patch doesn't change the LockinHeight function. Does that matter?

tommy wrote: Do you know if the 0.3.24.61 version has a checkpoint hardcoded into it, and at what block number that checkpoint would be?

It does not have a checkpoint. I asked about if you could build because then you could add a checkpoint yourself.

Can this be hardcoded into the namecoin client software? Please provide an updated client version that will revert back to block 19100 once this attack is over. Run a client that has a recent checkpoint and it'll refuse to accept any chain that was rewritten before that checkpoint. Are you able to ...

nodemaster wrote:Due to the possibly upcoming attack of BitcoinEXpress ( http://bit.ly/poTuzs ) MasterPool will start validating NMC blocks beginning with the next round until further notice. The current block will still be paid out directly.

What do you mean by "validating NMC blocks"?

You can just run two blkmond instances for the long polling, each monitoring the different chains.

There was some discussion with ArtForZ in #namecoin recently about the threatened attack. It looks like the attackers plan is something like: 1) Use a variant of this flaw in bitcoin/namecoin to enable fast generation of blocks from block 10,000 up to the merged mining point. 2) Use their large pool...

I posted this on the bitcointalk thread, but will repeat it here. I've closed trading temporarily on the bit parking exchange. You can still deposit/withdraw. A big risk of a double spend for an exchange is someone buying bitcoin and then rolling back the namecoin transaction. They can repeat this u...

I agree, but have it so that the difficulty changes say 6 or greater blocks after the block that is greater than 2 weeks to stop any time asynchronous errors or shennanigans from creeping in ... i.e. have a hashed time/date-stamp confirming the 'overdue' diff. adjustment at least 6 deep in the chai...

It seems like there should be some way to tell time without using an external time source since one of the tasks of the btc/nmc network is to act as a time-stamping algorithm (this is the concept behind the double-spend solution and what all the hashing is about). It is not a super accurate time so...