Namecoin Forum

Yes. Such blocks will be accepted by the namecoin chain and rejected by the bitcoin chain.

The mm-proxy returns the lowest difficulty of the parent and all the auxs to the getwork request. Any block found above that difficulty is submitted to all the chains. Each chain will accept or reject the block based on its own difficulty. This seems suboptimal. Wouldn't it be more efficient for th...

getdifficulty reports 0.24236496 for me, which I think is roughly consistent with the mining rate I've been getting (about 3-4 blocks per hour at 700-800 khps, and there doesn't seem to be anyone else mining on namecoin testnet). That sounds about right: ;;bc,calcd 800 0.24236496 (01:42:03 PM) grib...

getdifficulty reports 0.24236496 for me, which I think is roughly consistent with the mining rate I've been getting (about 3-4 blocks per hour at 700-800 khps, and there doesn't seem to be anyone else mining on namecoin testnet).

sacarlson: I don't know your configuration, but are you aware of the fact, that you are mining on all blockchains with the difficulty of the parent chain, even if the AUX chain has a lower difficulty? This is because your getworks are for the parent chain and only possible solutions (which might fi...

How can I verify which side of that split I'm mining on? If you use an old client not capable of doing merged minings you'll see a eroor message that you should upgrade. Try: namecoind getinfo I don't see an explicit error message, but it also looks like I've mined most of the blocks in the last da...

it splits the block chain on that block number. So anyone with old clients, and mining with old clients, will be on the old chain from that number. Any new coins they generate will not be valid on the new network. People on the new network will not be able to send coins to people on the old network...

- Visibility of offers. Since domain owners are mostly anonymous it would be pretty difficult to contact them with offers. You could try posting an offer on an auction site but there's little certainty that it will be seen by the domain owner. Also this 'centralization' would allow name sellers to ...

With name_history, it's much more feasible to avoid creating a separate domain for each message. I can name_new/name_firstupdate once, to create a 'username', and then post 'status updates' via name_update. The result is less email and more twitter, but the pricing is considerably more attractive.