Important
I have some bad news. Unfortunately, I need to make everyone download a new binary (or source code) again. I found a flaw in my logic that could lead to a potential attack against the chain. Technical details in the next paragraph. Basically, some people might have been able to start mining on the real chain ahead of time. So I need to patch up the code to prevent that. I will make another post when source and binaries are ready. Really sorry about this, but it's good that I caught this.
Here's the technical details for those of you that understand and care. I locked down the genesis block such that only the genesis hash is checked in and you need to provide the genesis time and genesis nonce in order for the client to run. But if you modify the code, you can easily bypass this check. So you can start working on the chain by building on the genesis hash. I previously thought about this, so I found one block and locked that block hash into the code. Even if you start building a chain against the genesis block, you won't be able to correctly find the first block that matches the block hash in the code. Your chain will be rejected by all the other clients because the block hash won't match. This is all good, EXCEPT I accidentally left a client running on the real chain in the open. So if someone modifies the code to run against the genesis block, their client can request block 1 from me. And once they do that, they can start building their chain against that in secret. I am not 100% sure that someone is doing this, but I checked the logs and noticed a connection from a few unknown IP addresses AND I saw a few getdata calls that were requesting for blocks. Since it's possible that the blocks have been sent out, I will need to patch the code to lock another block in. This time I will find the 2nd block in private, and lock that in. I figure it's better to be safe.
I have some bad news. Unfortunately, I need to make everyone download a new binary (or source code) again. I found a flaw in my logic that could lead to a potential attack against the chain. Technical details in the next paragraph. Basically, some people might have been able to start mining on the real chain ahead of time. So I need to patch up the code to prevent that. I will make another post when source and binaries are ready. Really sorry about this, but it's good that I caught this.
Here's the technical details for those of you that understand and care. I locked down the genesis block such that only the genesis hash is checked in and you need to provide the genesis time and genesis nonce in order for the client to run. But if you modify the code, you can easily bypass this check. So you can start working on the chain by building on the genesis hash. I previously thought about this, so I found one block and locked that block hash into the code. Even if you start building a chain against the genesis block, you won't be able to correctly find the first block that matches the block hash in the code. Your chain will be rejected by all the other clients because the block hash won't match. This is all good, EXCEPT I accidentally left a client running on the real chain in the open. So if someone modifies the code to run against the genesis block, their client can request block 1 from me. And once they do that, they can start building their chain against that in secret. I am not 100% sure that someone is doing this, but I checked the logs and noticed a connection from a few unknown IP addresses AND I saw a few getdata calls that were requesting for blocks. Since it's possible that the blocks have been sent out, I will need to patch the code to lock another block in. This time I will find the 2nd block in private, and lock that in. I figure it's better to be safe.
Ok, I checked in a fix and uploaded a new Windows client. Please check first post.
