hi.DEV.what is your next plan ?
We are already working on nodepay
about February 20
Topic: Closed Thread - page 123. (Read 677703 times)
We are already working on nodepay
about February 20
hi.DEV.what is your next plan ?
We are already working on nodepay
about February 20
Great +1
hi.DEV.what is your next plan ?
We are already working on nodepay
about February 20
+1 Go Node!
hi.DEV.what is your next plan ?
We are already working on nodepay
about February 20
hi.DEV.what is your next plan ?
We are already working on nodepay
People, please PM me your address for your node and IP so I can identify it on the Peer Explorer.
Do not post your address on the thread, private message it to me to be considered.
How will you check client's uptime?
Edit: I am running cleint 24/7 and have some ideas how to check others uptime. Pm me if you need any help.
It would be helpful if you have an idea of how to check, all I can do at the moment is check manually and after a few days I will verify that it is a 24/7 node.
I believe it is still 9.4.1b for the real network.
Do not post your address on the thread, private message it to me to be considered.
How will you check client's uptime?
Edit: I am running cleint 24/7 and have some ideas how to check others uptime. Pm me if you need any help.
It would be helpful if you have an idea of how to check, all I can do at the moment is check manually and after a few days I will verify that it is a 24/7 node.
ah ok- never mind about giveaway, I have enough an amount of node I feel comfortable with 
but which would be the current version?
Is it still node_9.4.1b_linux.zip ??
If so, I would just restart that on my VPS- I had stopped it when the bug occurred, and somehow missed to restart it again, and also lost track a bit...
but which would be the current version?
Is it still node_9.4.1b_linux.zip ??
If so, I would just restart that on my VPS- I had stopped it when the bug occurred, and somehow missed to restart it again, and also lost track a bit...
I believe it is still 9.4.1b for the real network.
Sorry , I edited my post and sent you a pm.
Could you please check it?
Regards...
Hi,
I had setup a linux node last Friday. And I could not forge a block. Is there sth wrong or do I need some more time for forging ?
Acc #: 9577957835821983512
(Yes , I have more than 500k+ node)
I had setup a linux node last Friday. And I could not forge a block. Is there sth wrong or do I need some more time for forging ?
Acc #: 9577957835821983512
(Yes , I have more than 500k+ node)
We will check.
If the client has been online since Friday You certainly got a blocks. In the next release earned amount will be displayed in the interface.
In ovh you can have a vps with 1gb of ram and 10 gb of hd for 26 euro/year, perfect for nodes
NodeClub and RealCool, Pm'd you 
I replied You
NodeClub and RealSkill, Pm'd you
hi.DEV.what is your next plan ?
 |
Generally speaking, the Node project is not just a Cryptocurrency, - it's rather a payment system with integrated crypto technology.
Cryptocurrency is just a part of the master project.
People, please PM me your address for your node and IP so I can identify it on the Peer Explorer.
Do not post your address on the thread, private message it to me to be considered.
How will you check client's uptime?
Edit: I am running cleint 24/7 and have some ideas how to check others uptime. Pm me if you need any help.
It would be helpful if you have an idea of how to check, all I can do at the moment is check manually and after a few days I will verify that it is a 24/7 node.
I believe it is still 9.4.1b for the real network.
Do not post your address on the thread, private message it to me to be considered.
How will you check client's uptime?
Edit: I am running cleint 24/7 and have some ideas how to check others uptime. Pm me if you need any help.
It would be helpful if you have an idea of how to check, all I can do at the moment is check manually and after a few days I will verify that it is a 24/7 node.
ah ok- never mind about giveaway, I have enough an amount of node I feel comfortable with
but which would be the current version?
Is it still node_9.4.1b_linux.zip ??
If so, I would just restart that on my VPS- I had stopped it when the bug occurred, and somehow missed to restart it again, and also lost track a bit...
but which would be the current version?
Is it still node_9.4.1b_linux.zip ??
If so, I would just restart that on my VPS- I had stopped it when the bug occurred, and somehow missed to restart it again, and also lost track a bit...
I believe it is still 9.4.1b for the real network.
Too bad that my server, which ran around 6 month, is offline since yesterday because i canceled it.
People, please PM me your address for your node and IP so I can identify it on the Peer Explorer.
Do not post your address on the thread, private message it to me to be considered.
How will you check client's uptime?
Edit: I am running cleint 24/7 and have some ideas how to check others uptime. Pm me if you need any help.
It would be helpful if you have an idea of how to check, all I can do at the moment is check manually and after a few days I will verify that it is a 24/7 node.
I believe it is still 9.4.1b for the real network.
Do not post your address on the thread, private message it to me to be considered.
How will you check client's uptime?
Edit: I am running cleint 24/7 and have some ideas how to check others uptime. Pm me if you need any help.
It would be helpful if you have an idea of how to check, all I can do at the moment is check manually and after a few days I will verify that it is a 24/7 node.
ah ok- never mind about giveaway, I have enough an amount of node I feel comfortable with
but which would be the current version?
Is it still node_9.4.1b_linux.zip ??
If so, I would just restart that on my VPS- I had stopped it when the bug occurred, and somehow missed to restart it again, and also lost track a bit...
but which would be the current version?
Is it still node_9.4.1b_linux.zip ??
If so, I would just restart that on my VPS- I had stopped it when the bug occurred, and somehow missed to restart it again, and also lost track a bit...
I believe it is still 9.4.1b for the real network.
Hi,
I had setup a linux node last Friday. And I could not forge a block. Is there sth wrong or do I need some more time for forging ?
(Yes , I have more than 500k+ node)
I had setup a linux node last Friday. And I could not forge a block. Is there sth wrong or do I need some more time for forging ?
(Yes , I have more than 500k+ node)
hi.DEV.what is your next plan ?
We are already working on nodepay
hi.DEV.what is your next plan ?
can someone post the link of the spreadsheet with the test account# so that i know whom i can send some test nodes? I did not save that link after the last test.
you can send me some)
11469001324502140635
No, this is a private giveaway for people running nodes on the real network. This has nothing to do with the test.
Make things clear:
This giveaway is not being done by the NODE team, it's by supporters of NODE.
How will you check client's uptime?
Edit: I am running cleint 24/7 and have some ideas how to check others uptime. Pm me if you need any help.
i.m running a private node too
id: 11686605939444917029
pd: i´m running a vps with node_9.4.1b_linux.zip version and it sometimes stop of updating blocks and i have to restart manually
do we have some update or fix for this?
id: 11686605939444917029
pd: i´m running a vps with node_9.4.1b_linux.zip version and it sometimes stop of updating blocks and i have to restart manually
do we have some update or fix for this?
ok so I will be giving out some NODE rewards to those running private nodes for the network.
PM your node's address and account, I will send you some NODE for helping out after I verify.
Not sure yet how much I will send but depends on how many people want to join the rewards .
edit: There might be a delay before giving out the NODE, I am working out how to verify that people consistently have their node running.
edit: I would like to add that I will not be rewarding the 2 or 3 accounts that have been forging the most blocks, I am doing this to give private nodes a gift for helping the NODE team with this project
PM your node's address and account, I will send you some NODE for helping out after I verify.
Not sure yet how much I will send but depends on how many people want to join the rewards .
edit: There might be a delay before giving out the NODE, I am working out how to verify that people consistently have their node running.
edit: I would like to add that I will not be rewarding the 2 or 3 accounts that have been forging the most blocks, I am doing this to give private nodes a gift for helping the NODE team with this project
sorry for losing track- I had been running 0.9.4.1 or ..something .. on a DigO Droplet, but I switched it off because I had thought there would be a new version on the way...
is this about running a testnet node with the testnet client mentioned above?
Or is there a new version of mainnet out?
If it is about testnet, I would run that, just let me know
No, this is a private giveaway for people running nodes on the real network. This has nothing to do with the test.
Make things clear:
This giveaway is not being done by the NODE team, it's by supporters of NODE.
ah ok- never mind about giveaway, I have
but which would be the current version?
Is it still node_9.4.1b_linux.zip ??
If so, I would just restart that on my VPS- I had stopped it when the bug occurred, and somehow missed to restart it again, and also lost track a bit...
Jump to: