One more stupid suggestion I can give to the team today (while having the last few shots).
We are all not eternal, KMD network can survive all of us (yeah, bus joke)
James, please do some kind of hierarchy + post. Stress test would be plausible while the system is still in a newborn state..
I havent seen any stupid suggestions from you, but not sure what you mean by hierarchy + post.
The network was stressed during the week of hacker attacks, once the codebase was strengthened, the attacks appear to have shifted to user level with phishing websites and fake users promising fake returns in slack.
For the record, I never promised any 20x return on SuperNET. In fact, I said I didnt know how long it would take for SuperNET to be completed so SuperNET was sold at book value without any premium for being a growth instrument. After a very long bear market and paying for all the costs along the way, the book value is above the funds raised in the ICO, the trading price is also above the ICO price. Granted it isnt any giant ROI, but considering that we are not completed the roadmap yet it is not a bad interim value.
KMD was sold with only 10% reserved for the KMD team, which is on the low end of ICO's. Financially, it appears that like SuperNET we have a negative burn rate (meaning over time the funds available is growing), so we expect to be able to continue to pay for all development and notary costs for quite a long time. The only big financial issue is the challenge of dealing with the next bear market, whenever it arrives. We are already making plans regarding this to ensure the long term survival of KMD. The biggest troll attack against the ICO was how we could cap the maximum raised at 30,000 BTC. We never said it was a minimum, but it was spun into where we somehow required 30,000 BTC. The total amount raised was less than 10% of that, but it is enough to fund the notary nodes and a conservatively sized development team and a reasonable marketing expenditure. For those that believe good devs grow on trees and it is a matter of spending money to get them, please let me know where the good devs orchard is. Hiring quality devs is not any easy thing and to maintain fiscal responsibility I err on the side of not spending the funds, having the theory that once the money is spent you no longer have it.
KMD is up 2x to 3x in fiat terms (~50% in BTC) from ICO (depending on your bonus level), it isnt 100x and I apologize for that. I know I am not delivering on the 100x ROI promise that I didnt make.
While I have visited Hawaii, I am not living there, nor do I plan to visit it anytime soon.
For BTCD, after it went up 60 fold from when I joined the coin, I did say it would take quite a bit longer for it to 60x again (total 3600x gain). I think we are a quadrupling away from the second 60x gain and for people still holding BTCD or who have converted to KMD at the original cost basis, the gains have been indeed quite good. (over 500x in a bit less than 4 years)
I know people would like to make easy money instantly without any hard thinking. For that you can always play the pump of the day lottery on polo. Unfortunately there is no guarantee you pick the right coin. Bittrex is now getting almost 15% the volume of poloniex, so it can easily support some very large marketcap coins (like WAVES) and there is no urgent need to be listed on poloniex. Of course, more liquidity is always welcome and if we do get listed, that would be a nice thing.
I am managing things as if it was a long term marathon, so things like long term financial viability are much more important than whether it will get pumped to an artificially high price for a short period of time in an unsustainable pump.
That being said, with about 20 coins in the 100 million USD+ marketcap, I would not consider KMD joining it to be any far fetched scenario. For all the issues via GUI, at the komodod level things have been very solid for over six months (ignore the hacker attack week!). If we imagined a solid GUI where people are using native mode (so there are no basilisk issues at all), then it would be a lot less tech support issues.
So the question is if we should disable basilisk mode to eliminate all basilisk tech support issues and force people to use native mode? Fundamentally, using basilisk mode means you are relying on nodes that are not your own and therefore it is less reliable. That means it isnt as reliable as running a native mode locally, so there will be times where it isnt working smoothly.
So if people can view KMD as komodod mode plus GUI with native mode plus GUI with basilisk mode, then the question is if the extra modes has negative value where we are better off disabling it.
I think we should reserve judgement until the revamped Agama is out and then if basilisk mode is still unreliable to strongly consider to force people to use only the native mode.
Did I mention that we are currently testing smartaddresses?
