If I understand correctly, Droidz is the only CWI coin supporting masternodes (at least in theory)... Is that correct?
Its a pity it missed the masternode train because of broken MN implementation. Most MN coins gained a lot in popularity (and in marketcap too), but Droidz is sleeping as if nothing happened...
Are there plans to fix masternode functionality in Droidz, so it could be actually used, and so Droidz could re-gain some of its popularity? I believe having an MN coin could help CWI short-term, with masternodes being in fashion now, by adding some more visibility to CWI (most people look at a coin only when it goes up in coinmarketcap list). But it would need the fix done soon, too.
hi drays ...
been a while mate
...
quite correct ... but the 'train' that you mention has never really been on our radar - and as you have known how we work - its a slow solid step we always take ...
the code for droidz is being worked on - and the masternodes issue is the least of the worries ... the sync is slow - full of orphans - and we need to make sure that there is a decent cleanup of the code before we even look at the fixes that need to made for any train to be caught
...
but i do agree with you - these things need to be fixed - and in a timely fashion ...
we are working on a few smaller fixes to the code - and will be pushing these fixes to the CWI-Git soon ... testing has proven to be fruitful - and all well so far ... sync is a crap fight at the moment - and that needs to be fixed as a priority ...
a full rebase is more the way we are looking at - rather than continual fixing of issues code - as this is a frankenstein of a codebase at the moment ... we are even considering bringing back PoW - but as mentioned earlier - that may not be a welcome thing for a coin that has been pos for a long time ... we will see ...
tanx for your input ... always welcome as usual ...
#crysx
Got it
. You are probably one of a very few devs here who are focused mostly on the long-term
Yep, the sync is very slow, and wallet is CPU-hungry (it often becomes unresponsive when opened after some time of inactivity.., and returns to normal only when fully synced).
But as far as I have seen, it is the same with the most masternode coins I know - lots of orphans, very slow sync, wallet freezing during sync and eating a lot of CPU - so I suppose that is the effect of being a Dash fork (though I have never installed Dash wallet, so I don't know how it works). The only fast working MN wallet I know is the Bitsend wallet, but even it became not so fast lately.
I actually wanted to offer my help with fixing MN issue (as I have spend about a week debugging this few years back, and found few issues), but if you are going to re-base Droidz, it makes no sense to fix MN. If the code is broken, it is better to re-base, I agree. But we first should make sure the new code will actually be better (will it be forked from Dash again?). I am not sure why this current code would be so much worse than Dash, if it is based on Dash..?
