Namecoin Forum

BitcoinEXpress wrote: I didn't buy any, seriously.

I confirm he didn't buy any from the bitparking exchange using the login or IP address he used previously.

Davincij15 wrote:where is the source code for merged-mine-proxy?

https://github.com/vinced/namecoin/blob ... mine-proxy

I'll bet we could come up with heuristics for namecoind to detect "unusual" network activity and notify the user. Examples would include long side chains and abrupt changes in network hash rate. I do this on my exchanges now. I detect if an attempt is made to rewrite the block chain past the deposi...

vinced wrote: You have copies of all the blocks even if there is an attack, so you can always go back to the last block before the attack started.

This doesn't help exchanges and merchants who suffer loss in physical goods or other currencies during an attack.

JohnDoe wrote:So will lockins + merged mining be the full extent of the "fix" or is there a more elaborate solution in the works?

There needs to be a fix for the time warp mining exploit as well.

Well Coinhunter didn't know of a way to bloat the chain either and stated it couldn't be done, "Time Traveling" in the block chain wasn't possible till two days ago and now you are saying it's impossible to invalidate a lock in? I didn't say it was impossible, I said I know of no way. Perhaps you d...

I see we are getting Coinhunter level cocky are we DoubleC? I didn't expect that from you. I don't care about using NMC anywhere, ever. If your interested in averting all of this peacefully you know how to contact me directly. Just stating what I believe to be the truth. I know of no way to break a...

Right now if I wanted to I could kick in 68 gh/s by myself and literally stop your lock in dead in the tracks. But I said I wouldn't make a move till 19101 and that's the way it will be. ;) Not really, you'd overrun the people who are not using a locked in client. Those that are locked in will cont...

BTW I will upgrade tomorrow any docs on how to lockin. You just need to update to the latest git to get the lockin to block 18940. Lockins can be added by looking at namecoin.cpp, in the LockinHeight and Lockin methods. You add the height of the new locking, and the hash for the block at that height.

vinced wrote: Sorry. Try now.

I can confirm the latest master with the checkpoints works fine. I downloaded a clean block chain with it. I also tested that it correctly rejected bad blocks at those heights.