aaroncox/vessel

not showing the right wallet values

Closed this issue · 10 comments

on powering up the wallet shows old values and not he new ones , even if you change
the RPC node it won't show the correct value

version i'm using : 2.0 win 64

just installed the newer version 0.2.5 problem is still there

@stresskiller , have you tried changing the RPC node?

one of the major ones has been switched off lately and it's causing quite some services to run into issues.

Had the same problem you described above until I changed the RPC node. See: #69

@fraenk thank you but i just tried that no result ..

Which account and what should the values be? I'm not entirely sure how this could happen, seeing as how the values it reports are the values the RPC nodes provide.

the steemit account is @stresskiller , @bokeh and @macrophotography

it still shows that i have 30 SBD that i already transferd , it used to be up to date when you started the program

Hrm, it really does sound like you're connected to a bad node, but if you changed nodes, that shouldn't be happening. Mind sending me a screenshot of the overview panel so I can see what exactly is being displayed vs what a block explorer shows?

ok here you go

vessel-feedback

From the looks of it (seeing block 18909347 in the lower left), you've lost connection to the blockchain itself. That block is about 19 hours old, and the transfer you did of that SBD is about 15 hours old. That's why it's displaying old information.

Change the Preferred Steem Node server to https://rpc.buildteam.io or https://steemd.privex.io in the settings, it should reconnect, and the balances should be correct.

One of the other features I am going to roll out in the next week or so is a better way for Vessel to realize if it's connected or not, and then provide easier options to reconnect.

https://rpc.buildteam.io seems to work for now already tried:
https://steemd.privex.io
http://api.steemit.com and minnowsupportproject.org before without the right results

0.2.6 was just released a few moments ago - if the issue reoccurs please try again with the updated version!