Topic: Closed Thread - page 173. (Read 677685 times)
Is there any ETA for when the features will be released?
is nodepay.com belong to nodecoin ?
@update clients
Version Windows http://nodecoin.com/node_9.4.1b_win.zip
Version Linux http://nodecoin.com/node_9.4.1b_linux.zip
Instructions Linux https://github.com/nodepay/Docs/blob/master/Instructions.md
Version Windows http://nodecoin.com/node_9.4.1b_win.zip
Version Linux http://nodecoin.com/node_9.4.1b_linux.zip
Instructions Linux https://github.com/nodepay/Docs/blob/master/Instructions.md
I made a transaction and i think new client is working well
@update clients
Version Windows http://nodecoin.com/node_9.4.1b_win.zip
Version Linux http://nodecoin.com/node_9.4.1b_linux.zip
Instructions Linux https://github.com/nodepay/Docs/blob/master/Instructions.md
Version Windows http://nodecoin.com/node_9.4.1b_win.zip
Version Linux http://nodecoin.com/node_9.4.1b_linux.zip
Instructions Linux https://github.com/nodepay/Docs/blob/master/Instructions.md
Is the code open source?
Not until It's out of beta.
but you can see source code from earlier version
http://nodecoin.blogspot.com/2014/11/nodecoin-source-code.html
Did I miss something!
Are we on version 7?
Are we on version 7?
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.
sounds reasonable
+1
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"
It's true and it makes sense. I think this issue will be solved with the launch of the test network.
Is the code open source?
Not until It's out of beta.
Is the code open source?
cant wait to see node in fully action. If its like in the white paper explained this will be huge. By the way price is rising, someone bought a nice ammount of it right now.
Buy, buy, buy!
@Thinking aloud
So many people have noticed that the new client has a bug with disconnecting the network. Why this bug appeared if old clients it was not. We rewrote 80% of the code in the module data synchronization, many want to keep old clients because everything is stable. But we must pass this stage , our developers improves Node and a lot of moments will be when it will occur until we release the final release. We develop a Node for large-scale projects and we can't leave things as they are and much better to change the code now than when it will be too late. We listened to You in the future large change in the code will be tested on the test network, but also from the community there isn't a lot of help, for example, the last test POA (only 20 people) showed how much loyal customers
So many people have noticed that the new client has a bug with disconnecting the network. Why this bug appeared if old clients it was not. We rewrote 80% of the code in the module data synchronization, many want to keep old clients because everything is stable. But we must pass this stage , our developers improves Node and a lot of moments will be when it will occur until we release the final release. We develop a Node for large-scale projects and we can't leave things as they are and much better to change the code now than when it will be too late. We listened to You in the future large change in the code will be tested on the test network, but also from the community there isn't a lot of help, for example, the last test POA (only 20 people) showed how much loyal customers
Very true. There were not enough supporters for a testnet earlier, but fortunately now the community has grown to a point where you should not have an issue running a testnet.
I agree, we must pass this stage. But leaving the previous version running in order to withdrawal the Bter and and people may negotiate and you will have all the time in the world to make a new version with calm in testnet.
I'm willing to help test, i believe that the whole community that invested. Just make a call, passing a "GMT time" in which you can follow.
It would be also interesting to stress tests jmeter sending calls to the API and later with a larger volume test coming from different regions as https://www.blitz.io/ or http://loadimpact.com/
@Thinking aloud
So many people have noticed that the new client has a bug with disconnecting the network. Why this bug appeared if old clients it was not. We rewrote 80% of the code in the module data synchronization, many want to keep old clients because everything is stable. But we must pass this stage , our developers improves Node and a lot of moments will be when it will occur until we release the final release. We develop a Node for large-scale projects and we can't leave things as they are and much better to change the code now than when it will be too late. We listened to You in the future large change in the code will be tested on the test network, but also from the community there isn't a lot of help, for example, the last test POA (only 20 people) showed how much loyal customers
So many people have noticed that the new client has a bug with disconnecting the network. Why this bug appeared if old clients it was not. We rewrote 80% of the code in the module data synchronization, many want to keep old clients because everything is stable. But we must pass this stage , our developers improves Node and a lot of moments will be when it will occur until we release the final release. We develop a Node for large-scale projects and we can't leave things as they are and much better to change the code now than when it will be too late. We listened to You in the future large change in the code will be tested on the test network, but also from the community there isn't a lot of help, for example, the last test POA (only 20 people) showed how much loyal customers
Very true. There were not enough supporters for a testnet earlier, but fortunately now the community has grown to a point where you should not have an issue running a testnet.
thanks for the replies ,
I'll wait to take 500000 .
greetings to all
I'll wait to take 500000 .
greetings to all
hi all,
took a month following the currency and 2 days ago I'm trying to mine, I downloaded the latest client update for windows and when I returned to the computer, the portfolio was closed.
the only way to mine is having 500,000 nodes?
the only thing is to leave the wallet open.. or no...
Have I to write some special command?
thanks in advance
took a month following the currency and 2 days ago I'm trying to mine, I downloaded the latest client update for windows and when I returned to the computer, the portfolio was closed.
the only way to mine is having 500,000 nodes?
the only thing is to leave the wallet open.. or no...
Have I to write some special command?
thanks in advance
1st of all there is no mining involved with NODE coin. You forge transactions and you get the transaction fee, to start forging you should have minimum 500k NODE in your account. You dont have to write any special command but you do have to leave open your NODE client.
^^^Yup. There are three barriers you are going to face right now.
1.) We just switched to 0.9.4b and it has bugs. The Devs are working to get them fixed but rest assured that 0.9.1b was stable and the Devs are good they will get the client stable again.
2.) NODE deposits and withdraws are down until the client is stable again. Buy now though because last time this happened there was a rush on the coin as soon as trading was open again.
3.) There is a 500k withdraw limit on BTER but the withdraw limit includes withdraw fees so you will only be able to pull out 494,999 a day. We have asked BTER to raise the limit but have not had any luck yet. When you get to problem 3 come back and let us know someone may be willing to give you a small loan to cover you through the night.
Stick around we are still in Beta but things will get better.
hi all,
took a month following the currency and 2 days ago I'm trying to mine, I downloaded the latest client update for windows and when I returned to the computer, the portfolio was closed.
the only way to mine is having 500,000 nodes?
the only thing is to leave the wallet open.. or no...
Have I to write some special command?
thanks in advance
took a month following the currency and 2 days ago I'm trying to mine, I downloaded the latest client update for windows and when I returned to the computer, the portfolio was closed.
the only way to mine is having 500,000 nodes?
the only thing is to leave the wallet open.. or no...
Have I to write some special command?
thanks in advance
1st of all there is no mining involved with NODE coin. You forge transactions and you get the transaction fee, to start forging you should have minimum 500k NODE in your account. You dont have to write any special command but you do have to leave open your NODE client.
hi all,
took a month following the currency and 2 days ago I'm trying to mine, I downloaded the latest client update for windows and when I returned to the computer, the portfolio was closed.
the only way to mine is having 500,000 nodes?
the only thing is to leave the wallet open.. or no...
Have I to write some special command?
thanks in advance
took a month following the currency and 2 days ago I'm trying to mine, I downloaded the latest client update for windows and when I returned to the computer, the portfolio was closed.
the only way to mine is having 500,000 nodes?
the only thing is to leave the wallet open.. or no...
Have I to write some special command?
thanks in advance
@Thinking aloud
So many people have noticed that the new client has a bug with disconnecting the network. Why this bug appeared if old clients it was not. We rewrote 80% of the code in the module data synchronization, many want to keep old clients because everything is stable. But we must pass this stage , our developers improves Node and a lot of moments will be when it will occur until we release the final release. We develop a Node for large-scale projects and we can't leave things as they are and much better to change the code now than when it will be too late. We listened to You in the future large change in the code will be tested on the test network, but also from the community there isn't a lot of help, for example, the last test POA (only 20 people) showed how much loyal customers
So many people have noticed that the new client has a bug with disconnecting the network. Why this bug appeared if old clients it was not. We rewrote 80% of the code in the module data synchronization, many want to keep old clients because everything is stable. But we must pass this stage , our developers improves Node and a lot of moments will be when it will occur until we release the final release. We develop a Node for large-scale projects and we can't leave things as they are and much better to change the code now than when it will be too late. We listened to You in the future large change in the code will be tested on the test network, but also from the community there isn't a lot of help, for example, the last test POA (only 20 people) showed how much loyal customers
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.
Tried this, everything what I see is login screen with:
"Loading ... Please wait!
Download blocks start. Download block at height: 3941
And goes nowhere.
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.
Tried this, everything what I see is login screen with:
"Loading ... Please wait!
Download blocks start. Download block at height: 3941
And goes nowhere.
Jump to: