Closed Thread

[funnynews]

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.

[3x2]

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.

[rramires]

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.

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.

[3x2]

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?

Testnet would be great, release just stable versions and get more NODE users 

[whitecloud]

Block xxx it's relatively easy to tell at NXT which is one per minute.
There may be 10 per day or 1000 per day.

[3x2]

Block xxx it's relatively easy to tell at NXT which is one per minute.
There may be 10 per day or 1000 per day.

True, no empty blocks in NODE with certain block time so we dont know how much time it can take to reach that block height.

[whitecloud]

And yes ... another stop of win client.
Sure to me seemed more stable network with 0.9.1b.

And linux client not remain synchronized.

[rramires]

Idea. Perhaps change the port 19776, eliminate the old client's, trying to sync.

Could have a few different ports.

ex:
v091 = 19776
v094 = 19777
v095 = 19778
v096 = 19779
v097 = 19776 again (assuming no one else is going to open such an old client v091)

[funnynews]

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?

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"

[3x2]

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.

[TheRealSilk]

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

[romawi]

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

[TheRealSilk]

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

[3x2]

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.

[funnynews]

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. 

[Thiball]

I don't get it, it's working just fine for me.

[kevinkk525]

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.

[Paramon]

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/

[starik69]

My linux stuck, while 0.9.1 worked days without problems 

[Thiball]

So just use Windows