@update
Yes, there is a disconnection in the network with clients, will fix and release new clients
Topic: Closed Thread - page 174. (Read 677685 times)
Staff, my clients syncronize again.
I did so:
1 - I just deleted the file "peers.db".
2 - I restarted my internet connection (which must have taken a new IP).
3 - I open client.
Who wants to test it?
Why?
Maybe then it connects only with the first of two "dev" servers, and 5.xxx.xx4.65 5.xxx.xx4.108 and no have other clients trying to sync (because of the new IP).
So it would be nice in future versions or change port with each update, or do operation of change after "block nº XXX" is reached.
I did so:
1 - I just deleted the file "peers.db".
2 - I restarted my internet connection (which must have taken a new IP).
3 - I open client.
Who wants to test it?
Why?
Maybe then it connects only with the first of two "dev" servers, and 5.xxx.xx4.65 5.xxx.xx4.108 and no have other clients trying to sync (because of the new IP).
So it would be nice in future versions or change port with each update, or do operation of change after "block nº XXX" is reached.
Back to previous version and return withdrawal Bter + TESTNET is a good idea.
I think a testnet is a great idea and I would be willing to run it just to help but at this point I think we need to push forward to stabilize this version not go back. What is done is done and I'm sure there will be plenty more lessons to learn until we get out of beta. It is important moving forward to keep the trade moving.
Interesting
Gain in volume (sell) but not decreases in price.
Is a good sign.
Gain in volume (sell) but not decreases in price.
Is a good sign.
Therefore it is important to have a public test in "separated network" one week, before going into production.
Better take a little longer to launch the most stable things. Especially when Node integrated in more exchanges.
In nxt they do it with the community helping to test for a while, even has a space just for discussion in this forum: https://nxtforum.org/testnet/
When the release is the new client runs on "old mode" until the block XXX, and Then starts running the "new mode".
Thus the number of bugs on release is very small.
Will two different clients work with NODE? one til certain block height and after that the newer version?Better take a little longer to launch the most stable things. Especially when Node integrated in more exchanges.
In nxt they do it with the community helping to test for a while, even has a space just for discussion in this forum: https://nxtforum.org/testnet/
When the release is the new client runs on "old mode" until the block XXX, and Then starts running the "new mode".
Thus the number of bugs on release is very small.
Testnet would be great, release just stable versions and get more NODE users
I agree, I think it should go back to v0.91, with only the addition of the helpdesk (v0.91h
), releasing Bter withdrawal and then get testnet. When everything is 100% yes relaunch.
I'm stuck with 500,000 nodes in a withdrawal in Bter, and their support said it is waiting for a stable client in order to complete the operation.
Bter email
"Dear Sir,
The node wallet doesn't work well recently. A update with the fix will be release tomorrow according to the NODE team.
Please kindly check your wallet tomorrow when the node releases the new wallet https://bitcointalk.org/index.php?topic=590421.7440
If there is any question, please let us know
Best Regards
Bter.com"
Back to previous version and return withdrawal Bter + TESTNET is a good idea.
Block synchronization not working?
Here also stopped. The network of the previous version was better.
Yes, my client also stopped. Need to restart it, now I see last block is 3936 with my restarted client.
I have no problems on my two clients win and linux. 3936 - last block
Try closing your windows clients and open again. Hangs on "Loading ... Please wait!" for hours.
Just did that. No issues.
So just use Windows
My is windows and the same happens.
for me not. my linux client just verified the whole blockchain the 2nd time in about 40 minutes... and I did not restart the client.
Same on my Linux client http://nodemoney.cloudapp.net/
All OK now.
So just use Windows
My linux stuck, while 0.9.1 worked days without problems 
for me not. my linux client just verified the whole blockchain the 2nd time in about 40 minutes... and I did not restart the client.
Same on my Linux client http://nodemoney.cloudapp.net/
for me not. my linux client just verified the whole blockchain the 2nd time in about 40 minutes... and I did not restart the client.
I don't get it, it's working just fine for me.
People get frustrated in these cases. Releasing just stable versions = gaining more trust from investors. There are always some bugs but if we test NODE client on testnet it can save a lot of headache.
Ok. Now we'll close more stable version, and the next big change will test on testnet network
Awesome. Always happy to test new version but for the moment a stable version like before would be great.
Ok, thanks. I'll wait and help test.
People get frustrated in these cases. Releasing just stable versions = gaining more trust from investors. There are always some bugs but if we test NODE client on testnet it can save a lot of headache.
Ok. Now we'll close more stable version, and the next big change will test on testnet network
Awesome. Always happy to test new version but for the moment a stable version like before would be great.
People get frustrated in these cases. Releasing just stable versions = gaining more trust from investors. There are always some bugs but if we test NODE client on testnet it can save a lot of headache.
Ok. Now we'll close more stable version, and the next big change will test on testnet network
Block synchronization not working?
Here also stopped. The network of the previous version was better.
Yes, my client also stopped. Need to restart it, now I see last block is 3936 with my restarted client.
I have no problems on my two clients win and linux. 3936 - last block
I got stuck on 3935 and after restart now i am on block 3936. More than 2 times happened to me.
Same here on win 7/64
Block synchronization not working?
Here also stopped. The network of the previous version was better.
i also liked the last working version, i am sure silk will correct it. wait for another update
Yes of course, we are working on a stable version
Thank you to all who wrote in support through the client
I agree, I think it should go back to v0.91, with only the addition of the helpdesk (v0.91h ), releasing Bter withdrawal and then get testnet.
When everything is 100% yes relaunch.
I'm stuck with 500,000 nodes in a withdrawal in Bter, and their support said it is waiting for a stable client in order to complete the operation.
Bter email
"Dear Sir,
The node wallet doesn't work well recently. A update with the fix will be release tomorrow according to the NODE team.
Please kindly check your wallet tomorrow when the node releases the new wallet https://bitcointalk.org/index.php?topic=590421.7440
If there is any question, please let us know
Best Regards
Bter.com"
People get frustrated in these cases. Releasing just stable versions = gaining more trust from investors. There are always some bugs but if we test NODE client on testnet it can save a lot of headache. ), releasing Bter withdrawal and then get testnet. When everything is 100% yes relaunch.
I'm stuck with 500,000 nodes in a withdrawal in Bter, and their support said it is waiting for a stable client in order to complete the operation.
Bter email
"Dear Sir,
The node wallet doesn't work well recently. A update with the fix will be release tomorrow according to the NODE team.
Please kindly check your wallet tomorrow when the node releases the new wallet https://bitcointalk.org/index.php?topic=590421.7440
If there is any question, please let us know
Best Regards
Bter.com"
Therefore it is important to have a public test in "separated network" one week, before going into production.
Better take a little longer to launch the most stable things. Especially when Node integrated in more exchanges.
In nxt they do it with the community helping to test for a while, even has a space just for discussion in this forum: https://nxtforum.org/testnet/
When the release is the new client runs on "old mode" until the block XXX, and Then starts running the "new mode".
Thus the number of bugs on release is very small.
Will two different clients work with NODE? one til certain block height and after that the newer version?Better take a little longer to launch the most stable things. Especially when Node integrated in more exchanges.
In nxt they do it with the community helping to test for a while, even has a space just for discussion in this forum: https://nxtforum.org/testnet/
When the release is the new client runs on "old mode" until the block XXX, and Then starts running the "new mode".
Thus the number of bugs on release is very small.
Testnet would be great, release just stable versions and get more NODE users
I agree, I think it should go back to v0.91, with only the addition of the helpdesk (v0.91h
), releasing Bter withdrawal and then get testnet. When everything is 100% yes relaunch.
I'm stuck with 500,000 nodes in a withdrawal in Bter, and their support said it is waiting for a stable client in order to complete the operation.
Bter email
"Dear Sir,
The node wallet doesn't work well recently. A update with the fix will be release tomorrow according to the NODE team.
Please kindly check your wallet tomorrow when the node releases the new wallet https://bitcointalk.org/index.php?topic=590421.7440
If there is any question, please let us know
Best Regards
Bter.com"
Jump to: