Do you need one on the free tier and then pay full fee for the other ?
Yes.You may register multiple accounts but you'll need multiple phones, cards (may use virtual cards) and that is forbidden by rules.
Topic: [ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency - page 3500. (Read 9723748 times)
November 15, 2014, 11:35:05 AM
You may register multiple accounts but you'll need multiple phones, cards (may use virtual cards) and that is forbidden by rules.
November 15, 2014, 11:34:47 AM
Masternode Update
There's a few possible reasons that some of you are getting delisted.
1. You're not connected to enough peers on the new network (I've confirmed this to be the case on 2 of 3 of the nodes I've looked at)
2. The ping messages in the previous version weren't working correctly and nodes weren't delisted when they should have been. Your setup might not be correct, in this case it would have worked last time.
3. You used start-many, which had a bug in the ping timestamp (fixed in 10.16.17)
To figure out which one you are:
1.) Delete peers.dat (both remote and local)
2.) Start the masternode remotely, afterward you can type "masternode start" on the hot node and it should say "remotely started masternode". If it says "not capable", then you'll need to debug what the problem is.
You can also also try 10.16.7 (this version will ONLY connect to new peers):
Linux 64:
http://bamboo.darkcoin.qa/artifact/DRKL-DEV/JOB1/build-38/gitian-linux-darkcoin-bin/bin/64/darkcoin-qt
http://bamboo.darkcoin.qa/artifact/DRKL-DEV/JOB1/build-38/gitian-linux-darkcoin-bin/bin/64/darkcoind
Windows:
http://bamboo.darkcoin.qa/browse/DRKW-DEV-36/artifact/JOB1/gitian-win-darkcoin-dist/darkcoin-0.10.16.7-win.zip
There's a few possible reasons that some of you are getting delisted.
1. You're not connected to enough peers on the new network (I've confirmed this to be the case on 2 of 3 of the nodes I've looked at)
2. The ping messages in the previous version weren't working correctly and nodes weren't delisted when they should have been. Your setup might not be correct, in this case it would have worked last time.
3. You used start-many, which had a bug in the ping timestamp (fixed in 10.16.17)
To figure out which one you are:
1.) Delete peers.dat (both remote and local)
2.) Start the masternode remotely, afterward you can type "masternode start" on the hot node and it should say "remotely started masternode". If it says "not capable", then you'll need to debug what the problem is.
You can also also try 10.16.7 (this version will ONLY connect to new peers):
Linux 64:
http://bamboo.darkcoin.qa/artifact/DRKL-DEV/JOB1/build-38/gitian-linux-darkcoin-bin/bin/64/darkcoin-qt
http://bamboo.darkcoin.qa/artifact/DRKL-DEV/JOB1/build-38/gitian-linux-darkcoin-bin/bin/64/darkcoind
Windows:
http://bamboo.darkcoin.qa/browse/DRKW-DEV-36/artifact/JOB1/gitian-win-darkcoin-dist/darkcoin-0.10.16.7-win.zip
OK
Already upgrade one :
341 wget http://bamboo.darkcoin.qa/artifact/DRKL-DEV/JOB1/build-38/gitian-linux-darkcoin-bin/bin/64/darkcoind
344 ./darkcoind stop
345 cd .darkcoin/
346 ls -ltr
347 rm peers.dat
348 cd ..
349 ls -ltr
350 rm darkcoind
351 mv darkcoind.1 darkcoind
352 chmod u+x darkcoind
353 ./darkcoind
Start it localy, listed ok on all my MN, will monitor if it still listed after one hour or two.
If ok, will upgrade all.
EDIT : well I'll upgrade another (forgot to delete peer.dat on local =))
November 15, 2014, 11:34:17 AM
strange flat pricemove on cryptsy ...
November 15, 2014, 11:32:20 AM
Can anyone tell me of you can get 2 nodes up on the Amazon free tier ?
Do you need one on the free tier and then pay full fee for the other ?
How does it work ?
November 15, 2014, 11:23:28 AM
Masternode Update
There's a few possible reasons that some of you are getting delisted.
1. You're not connected to enough peers on the new network (I've confirmed this to be the case on 2 of 3 of the nodes I've looked at)
2. The ping messages in the previous version weren't working correctly and nodes weren't delisted when they should have been. Your setup might not be correct, in this case it would have worked last time.
3. You used start-many, which had a bug in the ping timestamp (fixed in 10.16.17)
To figure out which one you are:
1.) Delete peers.dat (both remote and local)
2.) Start the masternode remotely, afterward you can type "masternode start" on the hot node and it should say "remotely started masternode". If it says "not capable", then you'll need to debug what the problem is.
There's a few possible reasons that some of you are getting delisted.
1. You're not connected to enough peers on the new network (I've confirmed this to be the case on 2 of 3 of the nodes I've looked at)
2. The ping messages in the previous version weren't working correctly and nodes weren't delisted when they should have been. Your setup might not be correct, in this case it would have worked last time.
3. You used start-many, which had a bug in the ping timestamp (fixed in 10.16.17)
To figure out which one you are:
1.) Delete peers.dat (both remote and local)
2.) Start the masternode remotely, afterward you can type "masternode start" on the hot node and it should say "remotely started masternode". If it says "not capable", then you'll need to debug what the problem is.
November 15, 2014, 11:13:33 AM
Updated my MNs yesterday night, stopped and restarted masternodes from local wallet, checked they were online, all good. Wake up to see they are all not showing up in any list whatsoever, have to restart from local wallet. Kind of annoying, wish there was a way to know how to prevent this or automate them restarting correctly.
Can you do a "getpeerinfo" and send me the results (from the hot node)? [email protected]
I can see on https://drk.mn/ how the "Last Seen" rises for some MNs and after 1h10min the MN disappears..
Just sort'em by the "Last seen" and you'll see..
That's normal..it checks every hour and 10 minutes..so it resets status then. Mine has been on there the whole time since last night..it could just be a propagation issue as Evan has mentioned.
November 15, 2014, 11:08:43 AM
November 15, 2014, 10:59:20 AM
Updated my MNs yesterday night, stopped and restarted masternodes from local wallet, checked they were online, all good. Wake up to see they are all not showing up in any list whatsoever, have to restart from local wallet. Kind of annoying, wish there was a way to know how to prevent this or automate them restarting correctly.
Can you do a "getpeerinfo" and send me the results (from the hot node)? [email protected]
I can see on https://drk.mn/ how the "Last Seen" rises for some MNs and after 1h10min the MN disappears..
Just sort'em by the "Last seen" and you'll see..
November 15, 2014, 10:56:50 AM
sent too
November 15, 2014, 10:56:18 AM
Updated my MNs yesterday night, stopped and restarted masternodes from local wallet, checked they were online, all good. Wake up to see they are all not showing up in any list whatsoever, have to restart from local wallet. Kind of annoying, wish there was a way to know how to prevent this or automate them restarting correctly.
Can you do a "getpeerinfo" and send me the results (from the hot node)? [email protected]
Sent.
November 15, 2014, 10:52:39 AM
Updated my MNs yesterday night, stopped and restarted masternodes from local wallet, checked they were online, all good. Wake up to see they are all not showing up in any list whatsoever, have to restart from local wallet. Kind of annoying, wish there was a way to know how to prevent this or automate them restarting correctly.
Can you do a "getpeerinfo" and send me the results (from the hot node)? [email protected]
Sent.
November 15, 2014, 10:41:03 AM
Updated my MNs yesterday night, stopped and restarted masternodes from local wallet, checked they were online, all good. Wake up to see they are all not showing up in any list whatsoever, have to restart from local wallet. Kind of annoying, wish there was a way to know how to prevent this or automate them restarting correctly.
Can you do a "getpeerinfo" and send me the results (from the hot node)? [email protected]
November 15, 2014, 10:39:56 AM
Updated my MNs yesterday night, stopped and restarted masternodes from local wallet, checked they were online, all good. Wake up to see they are all not showing up in any list whatsoever, have to restart from local wallet. Kind of annoying, wish there was a way to know how to prevent this or automate them restarting correctly.
+1Same problem here. Very annoying, and it hasn't happened like this before.
November 15, 2014, 10:37:57 AM
Updated my MNs yesterday night, stopped and restarted masternodes from local wallet, checked they were online, all good. Wake up to see they are all not showing up in any list whatsoever, have to restart from local wallet. Kind of annoying, wish there was a way to know how to prevent this or automate them restarting correctly.
Had mine running since last night and it is still on the list (and got paid this morning). I'm sure Evan will figure it out sooner than later.
November 15, 2014, 10:27:05 AM
Updated my MNs yesterday night, stopped and restarted masternodes from local wallet, checked they were online, all good. Wake up to see they are all not showing up in any list whatsoever, have to restart from local wallet. Kind of annoying, wish there was a way to know how to prevent this or automate them restarting correctly.
November 15, 2014, 09:50:13 AM
I think v.16.6 dropping from list may be a cosmetic bug. I reverted 2 nodes back to 15.21 and when I grep all the IP's, they show up as :1, but issuing the same list on 16.6 shows as empty. From a local VM on 16.6, brings back all IP's as :0
I updated and got payed within 2 hours, just dont know if before or after it dropped from the list.
Anyone else can confirm this please?
It could very well be. Yesterday I was paid in a masternode in 16.5 when it didn't show itself in its own masternode list, but appeared in other lists. Today I have received a payment in a masternode in 16.6 that had been restarted some time before and was not in lists sometime after, but I'm not sure when it dropped, so I can't be sure.I updated and got payed within 2 hours, just dont know if before or after it dropped from the list.
Anyone else can confirm this please?
Good to hear!
November 15, 2014, 09:42:48 AM
Monoprix just announced they're going to be accepting Bitcoin.
=huge.
WOW!!!
I'm still waiting for Tesco to get with the times. They practically have their own whole financial ecosystem already, Tescocoin is all but a formality.
November 15, 2014, 09:38:10 AM
Everything look good from my side
snip
Some nodes are down:snip
Quote
Total Masternodes: 298 = 298 actives + 0 inactives (Last refresh: Sat Nov 15 2014 14:39:20)
from https://drk.mn/masternodes.htmlmns dropped out after 45min
edit: lets wait few hours. Similar things has been happening during updating the network
Everything appears to be OK, there's just some propagation issues on the network. If you're having trouble, try deleting your peers.dat and start the masternode again.
I deleted peers.dat and restarted my masternode yesterday, but still dissapear from time to time and have to start it again with my local wallet.
November 15, 2014, 09:28:46 AM
Monoprix just announced they're going to be accepting Bitcoin.
=huge.
WOW!!!
November 15, 2014, 09:26:54 AM
Everything look good from my side
snip
Some nodes are down:snip
Quote
Total Masternodes: 298 = 298 actives + 0 inactives (Last refresh: Sat Nov 15 2014 14:39:20)
from https://drk.mn/masternodes.htmlmns dropped out after 45min
edit: lets wait few hours. Similar things has been happening during updating the network
Everything appears to be OK, there's just some propagation issues on the network. If you're having trouble, try deleting your peers.dat and start the masternode again.
Jump to: