Next steps are to test all this, mining included, which requires adding the testnet difficulty adjustment (I didn't see it in the bitcoin testnet code, strange).
Some new errors now : 12:44:49 DEBUG(node) [BlockFilter.cpp:40 virtual bool BlockFilter::operator()(Peer*, Message&)] received block ebdd671a8739da235db5 12:44:49 ERROR(node) [util.cpp:335 error] ERROR: Aux POW parent has our chain ID 12:44:49 ERROR(node) [util.cpp:335 error] ERROR: CheckProofOfWor...
Khal: Thanks for your opinion. I'll do it, just waiting for more input on the names of plugins and methods to create (as I don't want to just invent something myself). I admit that it may be a bit complex to follow where the code should go :p The most complex interactions are related to DNS, here a...
What do you think, do such verification routines have a place inside nmcontrol? Yes, it would help any new implementation and also concentrate efforts on a single point. We need to create pluginNamespaceID.py at least. For generic things which can be in several namespaces, like the "signer" field, ...
I've not yet heard back from Michael, so I'll start implementing things in my own repo for now and use "stock" libcoin. It will be easy to move the files later if Michael is fine with having support for name_* and so on in libcoin itself. @khal: Please let me know in case you already started with t...
- find bitcoin features & patches that should not be used in namecoin I assume we will re-add them in the future? Most of the new Bitcoin features/patches since 0.3.x would be useful in Namecoin. Yes. Some will be activated on the next fork. Wow, great! Yes, presumably libcoin implements testnet di...