I am looking for clarity on this myself...but, from what I understand this is the reason for the delay...I suppose it makes sense, as a fork....this is also true of say

Litecoin and Bitcoin ..in that litecoin is a fork...I suppose it depends on how open DASH devs are with Helium devs....on keeping them in the loop..it is not a big

deal with LTC and BTC but it may be a big deal for DASH devs just not liking forks like Helium or something.

But yeah, clarity on the holdup, a timeline on the supposed 'fix' needed by dash devs ....would be helpful..even if it is just a 'ballpark' this summer of 2018 as a guess

The next DASH developmental milestone would require considerable reworking of existing code. Rather than release Helium on the existing DASH codebase and then face a possible fork and a lot of rewriting of code they have chosen to wait. This is a logical choice, but shouldn't have been sprung on the community who invested in SPR to get into the airdrop expecting a much more imminent release.

You should also be aware that there will be some waiting period after the DASH update while our devs actually code and test Helium. I'm expecting a Q3 2018 release. Q2 would be a nice surprise.

Well I'm definitely glad to see that team members are giving updates, but they need to be making sure they're coming to Bitcointalk so the majority of the project's followers can see...

Need a(nother) community manager?

Even if the majority of your followers are in slack, you should still update your thread for the few people who still don`t want to use slack for privacy purposes.

So Dash has 3 security bugs that were discovered during the bounty. Dash has a large development team to fix those bugs. Helium has been financed out of pocket by the developers. Since Helium does not yet have the funds to hire a large development team, they were waiting for Dash to release the update to save months of development time and costs.

 Things have changed though, from what I understand, Helium will launch soon but remain Dash compatible until after the security patch can be added. Then it will branch out. Helium needs to gain steam so the treasury can start funding a core development team.

ok, i hope that this Helium is now on a right highway
my D3s are waiting this start 

I can have understanding for slow start, but I received today mail from Cryptopia about unsuccessful login attempt. It says that after third one, account will be locked. Advice is using exclusive e-mail address for Cryptopia.
Too much time passed, not knowing how long it will take more. Give us any kind of wallet (paper one is good enough) to move the coins from exchange. It is bad practice keeping them so long there.

 That will be decided by the Masternodes. Given that POW is a dead end, I imagine it will go POS eventually, or something else if new tech arises. But that is not on the roadmap at the moment. I think many of us are hoping to revolutionize development speed, transaction speed, and the services offered by the platform. It's been discussed modifying the governance to make it more dynamic, but changes need to be approved by the Masternodes. So early on is a critical time, w can only hope that a stagnant culture doesn't develop within the governance.

link on HOW to get masternodes when it happens again please (or at least the process)

bit confused...how the heck do you get 1,000 HLM to run a masternode, if there is no HLM yet? (befuddled)

So do you setup up the masternode FIRST in some manner and THEN when HLM hits ..fund it after the fact? (in order for them to keep track of nodes?)

thanks...

brad


edit: ok Spreadcoin? or has this ship sailed?