<@CHAOSiTEC> so, today we gained alot of wisdom, and we are working on a new way to implement masternode payments, that will work... (my idea) :-p
and a bit later...
<@CHAOSiTEC> ive come up with a new solution for masternodes payment, we are working on that now
New dev on the job helping Evan, no ETA was given.
waou ... I thought the current RC3 solution has been extensively tested for weeks on testnet, and suddenly, after two hours following another botched, evan realizes that he needs more development for yet ANOTHER solution AND additional support?
the main net HAS to be stable, we cannot have side forks poping up here and there for longer than 1 block (i.e. orphant blocks) period anything else = unstable network. no solution can be garantied as several things can go wrong, there has been more work on darkcoin than 99% of all altcoins out there, we want things to be perfect, with no risk to the network, nor your money.
not everything can be tested to perfection in limited testnet scenarios, remember those games you used to play, having strange bugs here and there, those games where playtested for hours and hours, but some stuff can slip through...
I won't qualify myself as an absolute expert, but in 2013 even bitcoin, in a perfect normal and stable context, had a concurrent blockchain for many blocks - that naturally got orphaned and was then abandoned. And as you mentioned, in 4 weeks testing, devs could miss things - after only one hour, how could evan determine that the not-so-surprising forks won't get naturally orphaned? The main code just branched out, for christ sake.