BitShares Forum
Other => Graveyard => BitShares PTS => Topic started by: wany_hope on December 12, 2013, 11:01:22 pm
-
Hello
I've installed protoshares-qt (from protoshares-0.2.0.zip, "About" shows "ProtoShares version v0.8.5.0-unk-beta") at 29 November and it run since then pretty much constantly (I started mining in the same time - not with built-in miner since it is slow - so PC had to be on all the time).
After short initial trouble with establishing source of blockchain it loaded and worked smoothly showing constant ~8 connections to the network.
The problem is I started to notice that although pool announced payouts in regular intervals and looking at transactions online showed those payouts, only first one showed in the client. I exited the client and immediately run it again and it showed I'm 24hours behind the network (despite it showing all up to date and running a moment ago).
After that incident I had to restart the QT client many times, otherwise it would fall behind.
In debug.log these events look like this:
- first there are many
received block 000....
ProcessBlock: ACCEPTED
CTxMemPool::accept() : accepted ...
- and also
received getdata for: tx ...
Commiting ...
SetBestChain ...
- etc - in other words normal blockchain updates
- but then at some point:
trying connection ...
connected ...
send version message: ...
- or
connection timeout
- and these can go on for hours or even days until I restart the client. All this while the tooltip shows I have multiple active connections to the PTS network.
I've looked on various forums and it seems like I'm not the only one with this problem but I haven't found anyone with the solution or even hint to what might be wrong, so I finally decided to join this forum and share the pain
-
me too
-
Here are some additional nodes:
125.104.78.21:3888
94.174.82.246:3888
118.119.191.83:3888
218.59.222.73:3888
我的已经连接上了。
-
This is a bug in current client, it will be fixed in next update. Right now, close the client and reopen it is the solution.
sry about this.
-
This is a bug in current client, it will be fixed in next update. Right now, close the client and reopen it is the solution.
sry about this.
I just wanted to comment on bugs in the current client. PTS was supposed to be a minimal change to Bitcoin-Qt that wouldn't require a ton of maintenance for these kinds of bugs. I know it is a bit inconvenient but we are relying on volunteers to get the wallet patched. PTS works well enough for its primary purpose of speculating on future BitShares value.... eventually we will have a new wallet. So long as there are simple work-arounds we prioritize delivering BitShares over perfecting PTS.
-
This is a bug in current client, it will be fixed in next update. Right now, close the client and reopen it is the solution.
sry about this.
This is not a solution that works.
Here are some additional nodes:
125.104.78.21:3888
94.174.82.246:3888
118.119.191.83:3888
218.59.222.73:3888
This is!
-
Close and reopen forces the client to update latest blocks.
-
:(i stop at 15128 for 2 days,i dont konw whats the problem.
-
This is a bug in current client, it will be fixed in next update. Right now, close the client and reopen it is the solution.
sry about this.
I just wanted to comment on bugs in the current client. PTS was supposed to be a minimal change to Bitcoin-Qt that wouldn't require a ton of maintenance for these kinds of bugs. I know it is a bit inconvenient but we are relying on volunteers to get the wallet patched. PTS works well enough for its primary purpose of speculating on future BitShares value.... eventually we will have a new wallet. So long as there are simple work-arounds we prioritize delivering BitShares over perfecting PTS.
How are people supposed to even get their Bitshares if they cant get their Protoshare client to sync to blockchain!?
-
I'm now on day 3 of trying to get this client to Sync. Really don't like leaving money on Cryptsy and have to say, this isn't going to have a good effect on newcomers when the wallet not syncing has been a major issue since launch.
Now that the price has jumped to around $20 per share hopefully a functional wallet will be doable.
I've gone through and added every node listed in the sticked section, tried on different computers, disabled my firewall, forwarded ports, turned on UPNP to the Router. Nothing. Has me concerned.
Was about to install a portable Ubuntu but then saw all the threads where they were having the problem on there and Mac OS too.
-
I'm now on day 3 of trying to get this client to Sync. Really don't like leaving money on Cryptsy and have to say, this isn't going to have a good effect on newcomers when the wallet not syncing has been a major issue since launch.
Now that the price has jumped to around $20 per share hopefully a functional wallet will be doable.
I've gone through and added every node listed in the sticked section, tried on different computers, disabled my firewall, forwarded ports, turned on UPNP to the Router. Nothing. Has me concerned.
Was about to install a portable Ubuntu but then saw all the threads where they were having the problem on there and Mac OS too.
maxconnections=1
listen=0
connect=5.9.24.81