I'd say off hand, any work on helping NodeCoin run is an issue for the Devs, any work on promoting and sharing would come under the MC's remit, but Inf-Com should be thinking long and hard about the amazing things that NodeCoin can do for the network, and how to capitalize on that
Hmmm... How could such a simple thing have such a widespread impact? What have I created?
The nodecoin is out of the lab, and clearly it has resonated strongly with some primal need for everyone to get tangible positive feedback. I expected it would work as originally intended, but I didnt expect such a strong amount of emotions I am seeing.
Anyway, the nodecoin pool server is still running and other than my lack of Windows support (sorry bill), and lack of POST support, i didnt see any other bugs. So I will continue on the following development path:
1. Add asset inventory verification (applies for multigateway also)
2. Add Ddos protection of pool server using guardian servers (applies for multigateway also)
3. Save pool earnings state to recover from in case of pool server restart
4. refactor parsing code (applies to all my projects)
5. release nodeminer beta, convince clientdevs to incorporate nodeminer into their client as checkbox option
6. restructure multigateway to handle fragmented multisig wallets for deposit
7. add queue handling for all the internal multigateway paths
8. refactor multigateway to allow easily adding new bitcoind forks, maybe even use a little oop
9. install half a dozen bitcoind forks and add support for all of them in a day (this is my goal as far as time to add new bitcoind fork)
10. release multigateway for brutal testing and take a weekend day
James