I am trying to import my old BTSX 0.9.3 wallet and I keep getting this error:

_eccKey_public2.default.fromPublicKeyString(...) is null

What does this mean and how can I fix it?

Unfortunately my experience with bitshares hasn't been a great one since 2.0. I had browser issues with my safari and a particular plugin which caused me to clear my cache. At that time I thought the open ledger password and my brain key were the same thing, so I didn't worry I was confident that my password was assuring the safety of my bitshares as backing up my brain key was only a 'recommendation' unlike now where its become mandatory.

Storing user keys in temporary browser cache is a horrible idea.  I'm amazed that this was not a concern by the devs and they would release 2.0 like this.  My browser clears the cache whenever I close it.  This is a simple checkbox option.  I have not upgraded until I am sure what I am doing is not a danger to myself. Bitshares will never go anywhere if it requires the user to have to read technical manuals to keep their funds safe. Unless it is absolutely fool proof, it will never gain adoption. Preventing the user from losing their funds should be #1 priority.  Its a joke to think that cryptocurrency is safer than your money in the bank. If it is not safe, the price will never stabilize.

This is a huge deal if this is the way it works.  Security is important, but I'm willing to bet the number one way to lose funds is through operator mistake.  In my opinion, preventing the user from losing their own funds is THE most important security issue.

Is this legit? Although I'm not into ethereum this seems like some FUD. I think they can probably have done some work with $18M no? We never know with this crypto journalists.

18M at the time of fundraising.  How much of that value was lost in bitcoin?

Quote from: sschechter on July 30, 2015, 07:09:57 pm

I think arbitrarily burning funds is stupid.  It only makes sense from a value perspective when everyone knows exactly what has been burned.  There is no depreciation if we can't track exactly whats been burned.

Burned BTS are visible in the blockchain, and the client should adjust the total share supply accordingly.

Thanks for clarifying.  If that's the case, burning can serve a purpose 

Unless we generate a constant stream of positive news, there is zero reason for anyone to hold BitShares. They will just move onto the next thing.

Remember the announcement that Overstock was interested in working with BitShares? How did that work out?

Before that last big hack, my previous phone died without warning.  I contacted Bter support and they were able to disable 2FA so I could reinstate it on my new phone.  Unfortunately, that was aeons ago, when they had somewhat of a reputable business.  Keep trying, and you might get lucky.

Ken continues to have my full support and vote (even if I don't agree with 100% of what he does - he does do and try).