Post
Topic
Board Announcements (Altcoins)
Re: [ANN][SUPERCOIN] Unique Most Advanced Anonymous Trustless Multisig Technology
by
supercointeam
on 18/10/2014, 18:30:12 UTC
It's good that dev will release the code, so supercoin goes back to the open source based coin. What worries me is that lacking of a qualified dev will not help supercoin in a lead position. Other hype coins can easily copy the code and sell their "stories". Only with a strong dev who is capable of taking over can keep the leading edge of the supercoin. I don't see any now. If none, then what's the point to release the code to other coins?? better keep the code secret.

I guess that is why the dev did so in the first place. Maybe the dev should not release the code until a new, preferably full-time developer/team takes over.

Or, the old team could step back up and take Super to the moon Smiley

Let's face it, the original devs are the most qualified to maintain & continue to develop the technology. The issue has always been lack of public awareness and refusal to accept options that bring more attention to Super.

On a positive note: The wallet is staking like crazy(I'm getting 30 Super per hour) and currently showing 7 anonymous nodes available for SuperSend anon transactions.

Well believe me, if I had time to continue developing, I would do it. No one has more affection to the coin, as I am the one who spent most time on this coin, not spent the time to talk, but countless hours to design and code and test the coin. But unfortunately I have my work and my responsibilities. So I can not continue developing the coin.

What I want:
1. make supercoin back to open source based coin
2. hope some qualified people from community can take over the code

As some people expressed the concerns about other coins copy-paste the code, I share the same concerns, that's why I did not publish yet the code.  I am in a dilemma now. If no qualified people to take-over, the publication of code will do no good to supercoin, but I also want the supercoin be open source, so community can maintain and develop the code.

So this is my decision:
a. I won't publish the code until community have someone qualified to take over the code.
b. If there's a qualified person (need to have a track record), I will send him the code 1 week before I make it publicly in git.



+1