Upvoted

This one is huge. Wonder how that goes with readers.

Quote from: hammurabi on July 21, 2016, 03:51:43 pm

Quote from: xeroc on July 21, 2016, 01:37:01 pm

the wallet is actually written in HTML/Javascript, that means you can open it up in a browser .. locally .. from from a remote host ..
either way, the private keys stay in your browser and are not sent to any server.

If you cannot protect your private keys, you shouldn't be in the crypto currency space.

It would be valuable to know if the gateway (such as openledger) have some sneaky opportunity to save credentials during account creation?
I think this would be the answer he/she seeks for.

For now we know that openledger officially doesn't store any credentials. But are they able to?

Yes, any given website such as openledger could modify the javascript code they deliver to capture credentials and this is a potential security hole, since the server hosting the web wallet pages could be hacked.

This is why it's safer to run the "light wallet" instead of using a web browser to access your funds. The light wallet is a frozen capture of the web wallet pages.

Back to answering the original question:
While creating a new account with light wallet, does the gateway have any chance of capturing the credentials?

The person asking the question wants to know how to safely store his/her BitShares investment.

(..)
If we can get to the ~ 70,000 SP level I should be able to buy ~ 2M BTS per day. It's not much but if I am constantly spiking low volume exchanges people will notice. And considering the levels of liquidity on the DEX a million or so BTS per day will add up fast.

If the 70k is hit I will see continue to pump BTS and provide liquidity for the duration of the two year SP redemption period. Consider this a social contract, though I'm really asking for nothing more than votes from the community.

If we work together we can substantially increase BTS market cap (...)

While liquidity is in fact needed the way of achieving this goal, as described, isn't appropriate.

Yes, BitShares is hated for lack of Return On Investment, but it is well respected for transparency and stability. Let's not forfeit that with unnecessary and reckless action.


Things are getting much prettier than before without resorting to "pump&dump" methods.
I even think that no such or similar action is required, because BitShares is gaining traction on its own. Let's have a look.

For example:
- the recent post on steemit with screenshot how to trade is actually enough for people to look into trading with BitShares Decentralized Exchange.
- cryptofresh.com is an awesome block explorer and information page. I discovered it just couple days ago and seeing how smooth things works made me buy some extra shares with the thought in my mind  that we are getting ready for taking off
- Moonstone Wallet and PeerTracks are promising and BitShapphire improved a lot on quality of their work
- Xeroc takes care of python libs which allows programmers to play with bots and the whole precious thing we got here
- Success of steem.it is attracting more eyes to ByteMaster's genius work
- OpenLedger and ccdk are doing really great job of kick starting the business


These are things I noticed.
Let others notice and we are good.

ps Sorry for all other BitShares heroes not mentioned. There are more great contributions then that little list.

Bitshares are too difficult to use.

With each release there is something new to learn and only insiders can keep up with that pace.
I am an experienced computer geek, but I have difficulties to keep up with that chaos myself.

Marketing guy made many mistakes like starting bitshares.tv series in 240p! (with a $5 usb camera from before year 2000 I suppose).
Or by repeating over and over how the big world is "ramping up" to use BitShares already. Instead of being short and informative he decided to bore viewers to death.
I stopped watching as these series turned out to be lies to temporarily pump up the price.

I myself tried to use bitshares many times but was unable to due to unusable javascript wallet. I suppose javascript technology was a gamble to make it more popular in web ecosystem. Time will tell if this strategy is right. If BitShares were about to succeed this indeed could speed up future development. But for my typical desktop use I am simply discouraged. Each time I dare to launch the wallet I am praying to the gods, old and new, to keep my keys safe.

From time to time I also try to educate myself more on recent changes in BitShares, but I end up dismissing browser 404 pages or trying to navigate through ocean of useless information regarding obsolete incarnations of previous bitshares projects.

Finally, the graveyard of unfinished BitShares assets doesn't bring comfort to any investor.

Sorry for dropping harsh words. But this is how it is from perspective of potential user.

This one is scary! Balance got missing.

I transferred some BTS from bter to my bitshares wallet more than 24h ago and I still haven't received the funds.
My wallet balance isn't updated!
The transfer itself seems to be completed since I can see it on http://www.bitsharesblocks.com/

Previously I made transfer from bter before and everything was fine.


checked on:
bitshares_client 0.4.24 64bit Linux
bitshares_client 0.4.24.1 64bit Linux

Update: I set up an amd64 DO droplet and VNCed into it to see if I could reproduce this. However, other bugs came up related to buggy VNC set-up that stopped me from really pursuing it.

I also found that commits were made to bitshares after the release was tagged but before binaries were released, so it is possible these bugs were already fixed:
https://github.com/BitShares/bitshares/compare/v0.4.24...master

I'll keep trying to reproduce these errors, but in the mean time I'm building the PPA to include the recent commits.

System automatically catch up the ppa update,
unfortunately after updating nothing changed in regard to the reported errors.
JSON Parse errors and Not connected message still persists.

I am still about to investigate deeper by playing with different network setup.


@josojo question:
I haven't transacted any bitUSD. This is rather irrelevant since these parsing bugs show up even on empty wallet.
My market menu shows everything at 0.00. So I guess some bugs must be there as well.

i just installed BitShares from PPA on 14.10 with an i386 architecture with no problems. Next step I'll make some clean virtual machines and test it there. Hopefully something breaks so we can figure out what is wrong...

Thanks! Looking forward to see the results.
If you have any idea what else I could test feel free to mention it

I am now going to test again with some environmental changes. Like network setup (uPNP?!)
Until now test were performed in similar network environment and using only intel processors.

One more thing, maybe try:

Code: [Select]

$ mv peers.leveldb peers.levedb.old
$ mkdir old
$ mv *.json old
and let the client rebuild them?

$ bitshares_client --version
{
  "blockchain_name": "BitShares",
  "blockchain_description": "The Future of Banking",
  "client_version": "v0.4.24",
  "bitshares_toolkit_revision": "377b57766dfa07e9a95952503217de31636ab9ee",
  "bitshares_toolkit_revision_age": "52 hours ago",
  "fc_revision": "e6b43a6149b8974ba1d3f683b9e01916a841c1de",
  "fc_revision_age": "71 hours ago",
  "compile_date": "compiled on Nov 12 2014 at 00:56:33",
  "boost_version": "1.54",
  "openssl_version": "OpenSSL 1.0.1f 6 Jan 2014",
  "build": "linux 64-bit"
}


After moving *.json to old directory and renaming peers.leveldb.old json parsing errors still persist.
Except I was asked to re-download the recent update from within the Bitshares gui client.

So it happens on:
1. Core i7 Ubuntu 14.04.1 LTS AMD64  (3.13.0-39-generic #66-Ubuntu SMP Tue Oct 28 13:30:27 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux)
2. Inside default VirtualBox 14.10 AMD64 (fresh install, only basic gfx guest extension added for bigger than 640x480 resolution)
3. KVM Guest 14.10 AMD64 (almost fresh install)


I will test 32-bit in a moment or two..