I feel very much out of touch with development since the latest rollback. The latest setback changed things, but an updated longer term timeline was not provided. Can we have an updated tentative timeline for future improvements from the dev team? It would be good to have this I think as I feel a bit in the dark.
- How is the masternode payment testing going?
- When can we expect masternode payments on main net?
- When can we expect further anonimity?
- When can we expect removal of 10 DRK darksend limit?
https://darkcointalk.org/threads/rc3-relaunch-strategy-and-testing.1482/I agree and feel that investors need more information (especially technical info) in order to gauge the current risk of investing.
I sold all my holdings during the second fork attempt rollback but have bought back 1/2 of my position after getting the last limited update. I am reluctant to pull the trigger on the other 1/2 until I know more. Evan please remember to keep the investors informed. Thanks!
As an investor I would rather have Evan working to get RC3 out as soon as possible than worry about posting minor updates in this ANN thread. It is not like information is not available or scattered about. The current status can be easily inferred by reading the following thread (note this is not the same link as above).
https://darkcointalk.org/threads/rc3-prelaunch-testing.1523/Thanks the link, it provided a bit more info (I had to crawl this forum to figure out why darkcointalk.org does not load in my browser - SSL issue).
I agree with most people here, Evan should be busy coding! In fact the technical innovations in darkcoin are amazing and the primary reason why I bought in. But the business/PR side of darkcoin is a bit of a shambles. It would be great if there were some other folks on the communications team.
On another note. Can anybody explain what exactly is meant by "enforcement" of masternode payments, what exactly is it doing and how is it done? It seems glossed over a bit on darkcointalk and I couldn't find the details anywhere. thanks
I'm not very technical so the actual mechanism of action might be off, but here's my understanding:
Soonish, Evan will release new binaries which will code for MN payments. However, any pools that are still using the old binaries (which don't require MN payments) will still be able to publish their blocks like normal, even though they aren't paying MNs. At some point once the code is verified to be working right and there are no forking issues, etc., Evan will send a command to the network to "enforce" the new protocol changes (MN payments) which will cause blocks from non-updated/non-complying pools to be rejected.
Consequently, for the time being, pools could choose to be greedy and not pay MNs as they are supposed to. However, once any kinks are ironed out, such pools will find their work rejected by the network and will therefore be compelled to switch to the updated version, which will include MN payments.
Apparently your effectiveness & prediction skills suck as bad as your trolling.
be happy" 
