Quote from: travis72682 on October 10, 2014, 09:15:37 PM

Quote from: cryptzo on October 10, 2014, 09:13:20 PM

Quote from: bitkokos on October 10, 2014, 09:00:01 PM

Quote from: wiser on October 10, 2014, 08:56:22 PM

Quote from: furcoin on October 10, 2014, 08:50:53 PM

With so much iterative updates/forks I feel like this was a very "beta" project and almost feel like a new "alpha" product should be launched with free ICO coins given to those who invested previously. seedCoin2.0? lol Anywho, I still look forward to 6 more days of growth.

This is crypto, not something guaranteed.

NXT had a lot of issues with the wallet even a couple months after it launched. But it's working well now and the coin is going places, and early adopters will probably benefit handsomely.

The main dev here answers questions promptly and applies fixes in a reasonable amount of time.

I think those are good signs.

NXT is doing well because they hired James (jl777)

And I'm gaining valuable experience. It's not like I can't figure out solutions to the problems when they crop up. I can solve any problem. But it is much more difficult to anticipate a problem that hasn't happened yet when you're building on someone else's code.

Still, I wasn't as careful as I needed to be with the fixes we had earlier in the week, because every fix I make is extremely time sensitive given the nature of the coin. Once growth is past, I'll have time to test things more vigorously, and invite people to participate in beta testing on a larger network.

This was a relatively simple fix that I was actually able to test on the main network. It resulted in an orphaned block unfortunately, but it allowed me to verify that the numbers worked as expected in an extremely short period of time.

didnt you fix the issue of under 1 seed not staking right earlier this week? did you not test it?

Yeah. I fixed the issue of them not staking at all. But I missed the amount they actually staked for, since they staked so rarely in accelerated testing. Blocks are flying by, and I was more concerned that they were staking at all. I rushed myself through 3 test runs trying to make them work right without disrupting the time scale and I missed that detail.