BitShares Forum
Main => General Discussion => Topic started by: teenagecheese on January 05, 2015, 03:40:28 pm
-
I know the focus is on the lightweight wallet, but what about the current full wallet? Is is being worked on? When will it be better, any approximate timeline?
For me at least, the full wallet is full of bugs, constantly loses connection, and takes a very long time to sync. It's nearly unusable and I want to use it to trade. This is not a good user experience for a first time user and it makes it much harder to provide liquidity.
-
No ETA.
I3 tend to say nothing about the timeline now,coz everytime they set a timeline,they just can't deliver it.
So,let go.
-
I'm using it to test bitshares-js which is more of the web wallet. As I see things I will try to fix them and let everyone use it on devshares. It will take a while, I have to craft up all these transactions in JavaScript first (as the priority) then I get to use them in the web_wallet as part of the testing. At that time I have a chance to make it better and ultimately put that back into the desktop. This is just me, others may have there own plan too.
-
I am stuck at block 1211638. It won't sync any further than that even though I am on version 0.27.1... Anyone know what to do?
-
I am stuck at block 1211638. It won't sync any further than that even though I am on version 0.27.1... Anyone know what to do?
For how long have you been stuck? you have open connections to other nodes?
-
I am stuck at block 1211638. It won't sync any further than that even though I am on version 0.27.1... Anyone know what to do?
This is from the Troubleshooting part of the WIKI and has worked for me in the past:
If you are getting a "Not Connected" error or having trouble syncing, try the following troubleshooting procedures:
Change how many nodes your client tries to connect to and the maximum it will try to connect to by typing the following command in the console:
network_set_advanced_node_parameters {"desired_number_of_connections":50, "maximum_number_of_connections":100}
If that doesn't work, then try connecting to some nodes manually using the following commands:
network_add_node "107.170.211.129:1700" add
network_add_node "80.240.133.79:1776" add
network_add_node "188.226.195.137:60696" add
network_add_node "76.74.170.79:54200" add
network_add_node "176.9.234.166:1700" add
network_add_node "180.153.142.120:1777" add
network_add_node "162.243.220.142:1777" add
network_add_node "84.238.140.192:42577" add
network_add_node "5.101.106.138:1778" add
network_add_node "69.164.192.144:1700" add
network_add_node "192.168.0.14:1776" add
network_add_node "78.46.32.25:1776" add
network_add_node "192.168.0.12:44327" add
network_add_node "70.114.143.108:1776" add
network_add_node "106.187.91.24:38581" add
network_add_node "106.185.26.162:1981" add
network_add_node "188.138.107.159:1776" add
network_add_node "104.131.136.190:1776" add
network_add_node "95.85.33.16:8764" add
network_add_node "198.199.103.79:1776" add
network_add_node "104.131.234.136:8801" add
-
just add a couple nodes and wait. Then add a couple more, wait. Eventually it should sync.
-
I am stuck at block 1211638. It won't sync any further than that even though I am on version 0.27.1... Anyone know what to do?
Exit the wallet from the file menu , then restart again .
If it doesn't work , see the link below (It's Chinese for now , I'll translate it into English when I have the time . I remember you can read Chinese , right ? ) .
https://bitsharestalk.org/index.php?topic=12941.0 (https://bitsharestalk.org/index.php?topic=12941.0)
-
The weird thing is I already have 10 connections. It looks like when there's a hard fork and the client stops syncing at a specific block. Except that I'm already on 0.4.27.1 so there shouldn't be one.
@btswildpig I already tried deleting appdata, was crashing at reindexing before then. Now I can open the wallet and sync the blockchain all the way until block 1211638.
Will try to add some more nodes and see what happens :)
-
I'm using it to test bitshares-js which is more of the web wallet. As I see things I will try to fix them and let everyone use it on devshares. It will take a while, I have to craft up all these transactions in JavaScript first (as the priority) then I get to use them in the web_wallet as part of the testing. At that time I have a chance to make it better and ultimately put that back into the desktop. This is just me, others may have there own plan too.
Thanks for the answer jcalfee1, that's what I was looking for, just some info. It feels like it is being completely ignored, from a user's perspective (several months and still buggy).
-
I'm using it to test bitshares-js which is more of the web wallet. As I see things I will try to fix them and let everyone use it on devshares. It will take a while, I have to craft up all these transactions in JavaScript first (as the priority) then I get to use them in the web_wallet as part of the testing. At that time I have a chance to make it better and ultimately put that back into the desktop. This is just me, others may have there own plan too.
Thanks for the answer jcalfee1, that's what I was looking for, just some info. It feels like it is being completely ignored, from a user's perspective (several months and still buggy).
We were just discussing in our weekly meeting today that we need to get an updated full client out ASAP, hopefully within a week or so.
-
We have several major improvements done but we want to go through the devshares test upgrade process with this one. So it depends on how quick we can reset devshares and test an upgrade on it. This upgrade should also unlock vesting balances.
-
Thanks for the info. It sounds like soon the wallet will work as it should.