Author

Topic: [ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency - page 3489. (Read 9723748 times)

full member
Activity: 197
Merit: 101
which site do you guys use for monitoring yr MN v10.16.11 ?

https://drk.mn/masternodes.html ??

or

https://drk.mn/masternodes-v15.html#mnlistdetail ??

Edit : because my MN wasnt listed on https://drk.mn/masternodes.html but i still got a MN payment
a hour ago and my MN only showed up in https://drk.mn/masternodes-v15.html#mnlistdetail showing
incorrect version v10.15.21

I started my MN from my cold wallet last night from v10.16.10 and again started it from cold wallet v10.16.11
a hour ago. For now my MN is visible on both sites .. but both are still showing incorrect version.
i just hope i'm monitoring the right site, I suspect you all are checking https://drk.mn/masternodes.html  ?

  



drk.mn portchecker/versionchecker does not work properly at the moment. My nodes are all on v0.10.16.11, yet still reported as v0.10.15.21 - but they were all paid during the night Smiley

but which site do you monitor then ? https://drk.mn/masternodes.html ?? or https://drk.mn/masternodes-v15.html ?

https://drk.mn/masternodes.html - it's showing the v16 network, ignore the reported version for the moment.

okay thanks.. here is hoping my MN stays on that site... pfff

It will Wink

Best regards,
flare
sr. member
Activity: 393
Merit: 250
p2pool nodes updated to 101611

EU node: http://eu.p2pool.sk:7903
US node: http://us.p2pool.sk:7903

support decentralized mining, use p2pool.
legendary
Activity: 2548
Merit: 1245
which site do you guys use for monitoring yr MN v10.16.11 ?

https://drk.mn/masternodes.html ??

or

https://drk.mn/masternodes-v15.html#mnlistdetail ??

Edit : because my MN wasnt listed on https://drk.mn/masternodes.html but i still got a MN payment
a hour ago and my MN only showed up in https://drk.mn/masternodes-v15.html#mnlistdetail showing
incorrect version v10.15.21

I started my MN from my cold wallet last night from v10.16.10 and again started it from cold wallet v10.16.11
a hour ago. For now my MN is visible on both sites .. but both are still showing incorrect version.
i just hope i'm monitoring the right site, I suspect you all are checking https://drk.mn/masternodes.html  ?

  



drk.mn portchecker/versionchecker does not work properly at the moment. My nodes are all on v0.10.16.11, yet still reported as v0.10.15.21 - but they were all paid during the night Smiley

but which site do you monitor then ? https://drk.mn/masternodes.html ?? or https://drk.mn/masternodes-v15.html ?

https://drk.mn/masternodes.html - it's showing the v16 network, ignore the reported version for the moment.

okay thanks.. here is hoping my MN stays on that site... pfff
full member
Activity: 197
Merit: 101
which site do you guys use for monitoring yr MN v10.16.11 ?

https://drk.mn/masternodes.html ??

or

https://drk.mn/masternodes-v15.html#mnlistdetail ??

Edit : because my MN wasnt listed on https://drk.mn/masternodes.html but i still got a MN payment
a hour ago and my MN only showed up in https://drk.mn/masternodes-v15.html#mnlistdetail showing
incorrect version v10.15.21

I started my MN from my cold wallet last night from v10.16.10 and again started it from cold wallet v10.16.11
a hour ago. For now my MN is visible on both sites .. but both are still showing incorrect version.
i just hope i'm monitoring the right site, I suspect you all are checking https://drk.mn/masternodes.html  ?

  



drk.mn portchecker/versionchecker does not work properly at the moment. My nodes are all on v0.10.16.11, yet still reported as v0.10.15.21 - but they were all paid during the night Smiley

but which site do you monitor then ? https://drk.mn/masternodes.html ?? or https://drk.mn/masternodes-v15.html ?

https://drk.mn/masternodes.html - it's showing the v16 network, ignore the reported version for the moment.
legendary
Activity: 2548
Merit: 1245
which site do you guys use for monitoring yr MN v10.16.11 ?

https://drk.mn/masternodes.html ??

or

https://drk.mn/masternodes-v15.html#mnlistdetail ??

Edit : because my MN wasnt listed on https://drk.mn/masternodes.html but i still got a MN payment
a hour ago and my MN only showed up in https://drk.mn/masternodes-v15.html#mnlistdetail showing
incorrect version v10.15.21

I started my MN from my cold wallet last night from v10.16.10 and again started it from cold wallet v10.16.11
a hour ago. For now my MN is visible on both sites .. but both are still showing incorrect version.
i just hope i'm monitoring the right site, I suspect you all are checking https://drk.mn/masternodes.html  ?

  



drk.mn portchecker/versionchecker does not work properly at the moment. My nodes are all on v0.10.16.11, yet still reported as v0.10.15.21 - but they were all paid during the night Smiley

but which site do you monitor then ? https://drk.mn/masternodes.html ?? or https://drk.mn/masternodes-v15.html ?
full member
Activity: 197
Merit: 101
which site do you guys use for monitoring yr MN v10.16.11 ?

https://drk.mn/masternodes.html ??

or

https://drk.mn/masternodes-v15.html#mnlistdetail ??

Edit : because my MN wasnt listed on https://drk.mn/masternodes.html but i still got a MN payment
a hour ago and my MN only showed up in https://drk.mn/masternodes-v15.html#mnlistdetail showing
incorrect version v10.15.21

I started my MN from my cold wallet last night from v10.16.10 and again started it from cold wallet v10.16.11
a hour ago. For now my MN is visible on both sites .. but both are still showing incorrect version.
i just hope i'm monitoring the right site, I suspect you all are checking https://drk.mn/masternodes.html  ?

  



drk.mn portchecker/versionchecker does not work properly at the moment. My nodes are all on v0.10.16.11, yet still reported as v0.10.15.21 - but they were all paid during the night Smiley
legendary
Activity: 2548
Merit: 1245
which site do you guys use for monitoring yr MN v10.16.11 ?

https://drk.mn/masternodes.html#mnlistdetail ??

or

https://drk.mn/masternodes-v15.html#mnlistdetail ??

Edit : because my MN wasnt listed on https://drk.mn/masternodes.html#mnlistdetail but i still got a MN payment
a hour ago and my MN only showed up in https://drk.mn/masternodes-v15.html#mnlistdetail showing
incorrect version v10.15.21

I started my MN from my cold wallet last night from v10.16.10 and again started it from cold wallet v10.16.11
a hour ago. For now my MN is visible on both sites .. but both are still showing incorrect version.
i just hope i'm monitoring the right site, I suspect you all are checking https://drk.mn/masternodes.html  ?

  

legendary
Activity: 1260
Merit: 1001
Aw heck, I set masternode=0 in config, started wallet, and sent myself (to new address in same wallet) 1000 coins, but it won't confirm!  It's like in limbo!  UGH!  What a day!
legendary
Activity: 1442
Merit: 1018
If someone writes a detailed guide on how to have more than one masternode within a wallet ill send ya 100DRK for your service.

If you already have masternode wallets, dump the private keys for each one (dumpprivkey MASTERNODE_ADDRESS). Then on the wallet you want to have all the masternode in (make sure it is encrypted), import the private keys (importprivkey PRIVATE_KEY) for each masternode addressed dumped. Close the client. Create a masternode.conf file in the darkcoin data folder with the format below:

ip address of remote masternode:9999 MASTERNODE_GEN_KEY
ip address of remote masternode2:9999 MASTERNODE_GEN_KEY

Then load the new wallet with all the masternode addresses in there, go to the debug command prompt and issue:

masternode start-many PASSPHRASE

Not sure it can get any more detailed then that.

MASTERNODE_GEN_KEY  it that the key from remote or local?

do i still need to enter a key also in the darkcoin.conf?
what do i have to put in the darkcoin.conf for that seup?

Thanks!


You still need to enter it in the remote darkcoin.conf. That masternode gen key is what you generate at the beginning with "masternode genkey". It's the same private key that would go in the darkcoin.conf file on both remote and local the old way. This masternode.conf file is your new local conf in addition to your existing darkcoin.conf with the masternode=1 setting.

Please give an example of the CONF file

ty

Local darkcoin.conf:

Code:
rpcuser=LONG-RANDOM-STRING-fisjfijsfisjfsdwesdfsfdsfsfsdfhis_you_should_change_this
rpcpassword=LONGER-RANDOM-STRINGfisdfisfisjfijsfisjfsdwesdfsfdsfsfsdft_you_should_change_this
rpcallowip=127.0.0.1
listen=0
server=1
daemon=1
logtimestamps=1
addnode=23.23.186.131
masternode=1

Remote darkcoin.conf:

Code:
rpcuser=enter-new-LONG-RANDOM-STRING-fisjfijyou_should_change_this
rpcpassword=enter-new-LONGER-RANDOM-STRING-fissjfijyou_should_change_this
rpcallowip=127.0.0.1
listen=1
server=1
daemon=1
logtimestamps=1
maxconnections=256
masternode=1
masternodeprivkey=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
addnode=23.23.186.131

Local masternode.conf:

Code:
10.10.10.1:9999 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Every masternode would have its own line in the masternode.conf file with the ip address, port, and masternode genkey.
legendary
Activity: 1260
Merit: 1001
"not a capable masternode."

Isn't that the error message when you "break" the masternode by touching the 1000 DRK at the original address?  Have you looked in coin control?

Yes, it's all still in one chunk in the same address, but tomorrow I think I'll set up an entirely new server, new wallets, etc.... and maybe that'll work.  I'm a bit tipsy now, but feeling better, LOL

Besides though, I've never even had to have the local "on" before doing masternode debug on the remote server before.  I always got to that point before even touching the local masternode.  So it shouldn't have to know anything about the original masternode???  Oh heck, I'm going to try this all over again.  I can't sleep with this undone!
legendary
Activity: 1260
Merit: 1001
If someone writes a detailed guide on how to have more than one masternode within a wallet ill send ya 100DRK for your service.

If you already have masternode wallets, dump the private keys for each one (dumpprivkey MASTERNODE_ADDRESS). Then on the wallet you want to have all the masternode in (make sure it is encrypted), import the private keys (importprivkey PRIVATE_KEY) for each masternode addressed dumped. Close the client. Create a masternode.conf file in the darkcoin data folder with the format below:

ip address of remote masternode:9999 MASTERNODE_GEN_KEY
ip address of remote masternode2:9999 MASTERNODE_GEN_KEY

Then load the new wallet with all the masternode addresses in there, go to the debug command prompt and issue:

masternode start-many PASSPHRASE

Not sure it can get any more detailed then that.

MASTERNODE_GEN_KEY  it that the key from remote or local?

do i still need to enter a key also in the darkcoin.conf?
what do i have to put in the darkcoin.conf for that seup?

Thanks!


You still need to enter it in the remote darkcoin.conf. That masternode gen key is what you generate at the beginning with "masternode genkey". It's the same private key that would go in the darkcoin.conf file on both remote and local the old way. This masternode.conf file is your new local conf in addition to your existing darkcoin.conf with the masternode=1 setting.

Hi, yes, I did do that, but it didn't help.  I put it in my conf file for both.  I really think it's something else because I can get other versions to work fine.  I'm surprised though that I'm the only one with the problem??
hero member
Activity: 671
Merit: 500
"not a capable masternode."

Isn't that the error message when you "break" the masternode by touching the 1000 DRK at the original address?  Have you looked in coin control?
legendary
Activity: 1442
Merit: 1018
If someone writes a detailed guide on how to have more than one masternode within a wallet ill send ya 100DRK for your service.

If you already have masternode wallets, dump the private keys for each one (dumpprivkey MASTERNODE_ADDRESS). Then on the wallet you want to have all the masternode in (make sure it is encrypted), import the private keys (importprivkey PRIVATE_KEY) for each masternode addressed dumped. Close the client. Create a masternode.conf file in the darkcoin data folder with the format below:

ip address of remote masternode:9999 MASTERNODE_GEN_KEY
ip address of remote masternode2:9999 MASTERNODE_GEN_KEY

Then load the new wallet with all the masternode addresses in there, go to the debug command prompt and issue:

masternode start-many PASSPHRASE

Not sure it can get any more detailed then that.

MASTERNODE_GEN_KEY  it that the key from remote or local?

do i still need to enter a key also in the darkcoin.conf?
what do i have to put in the darkcoin.conf for that seup?

Thanks!


You still need to enter it in the remote darkcoin.conf. That masternode gen key is what you generate at the beginning with "masternode genkey". It's the same private key that would go in the darkcoin.conf file on both remote and local the old way. This masternode.conf file is your new local conf in addition to your existing darkcoin.conf with the masternode=1 setting.
legendary
Activity: 1068
Merit: 1020
masternode.conf is the darkcoin.conf...I believe.
member
Activity: 109
Merit: 10
If someone writes a detailed guide on how to have more than one masternode within a wallet ill send ya 100DRK for your service.

If you already have masternode wallets, dump the private keys for each one (dumpprivkey MASTERNODE_ADDRESS). Then on the wallet you want to have all the masternode in (make sure it is encrypted), import the private keys (importprivkey PRIVATE_KEY) for each masternode addressed dumped. Close the client. Create a masternode.conf file in the darkcoin data folder with the format below:

ip address of remote masternode:9999 MASTERNODE_GEN_KEY
ip address of remote masternode2:9999 MASTERNODE_GEN_KEY

Then load the new wallet with all the masternode addresses in there, go to the debug command prompt and issue:

masternode start-many PASSPHRASE

Not sure it can get any more detailed then that.

MASTERNODE_GEN_KEY  it that the key from remote or local?

do i still need to enter a key also in the darkcoin.conf?
what do i have to put in the darkcoin.conf for that seup?

Thanks!
legendary
Activity: 1118
Merit: 1002
If someone writes a detailed guide on how to have more than one masternode within a wallet ill send ya 100DRK for your service.

If you already have masternode wallets, dump the private keys for each one (dumpprivkey MASTERNODE_ADDRESS). Then on the wallet you want to have all the masternode in, import the private keys (importprivkey PRIVATE_KEY) for each masternode addressed dumped. Create a masternode.conf file in the darkcoin data folder with the format below:

ip address of remote masternode:9999 MASTERNODE_GEN_KEY
ip address of remote masternode2:9999 MASTERNODE_GEN_KEY

and so on and so forth.

Then load the new wallet, go to the debug command prompt and issue masternode start-many PASSPHRASE.
If someone writes a detailed guide on how to have more than one masternode within a wallet ill send ya 100DRK for your service.

Perhaps this will help:

(Based on https://darkcointalk.org/threads/50-dark-bounty-for-masternode-guide-update.2721/)

Create masternode.conf in your Darkcoin working directory and put in the IP address of your MNs and their privkeys, like below:

192.168.0.1:9999 7qspZZJD3wsPifSzxZGnzo4HhR5Pd9MN2X9kGk4gPZi4LMJSvrE
192.168.0.2:9999 7rDDK21opuSHuu7eV2LdmBAunXWRUhVU3ZVek3frqYisnF4HyJL

Move DRK into your wallet in 1000 DRK increments. Then go to the console and use:

masternode start-many




Thanks to both of you, ill give it a shot tomorrow and see how it works out.
legendary
Activity: 1442
Merit: 1018
If someone writes a detailed guide on how to have more than one masternode within a wallet ill send ya 100DRK for your service.

If you already have masternode wallets, dump the private keys for each one (dumpprivkey MASTERNODE_ADDRESS). Then on the wallet you want to have all the masternode in (make sure it is encrypted), import the private keys (importprivkey PRIVATE_KEY) for each masternode addressed dumped. Close the client. Create a masternode.conf file in the darkcoin data folder with the format below:

ip address of remote masternode:9999 MASTERNODE_GEN_KEY
ip address of remote masternode2:9999 MASTERNODE_GEN_KEY

Then load the new wallet with all the masternode addresses in there, go to the debug command prompt and issue:

masternode start-many PASSPHRASE

Not sure it can get any more detailed then that.
legendary
Activity: 1260
Merit: 1001
Yup, one shows Sunday's date and the other shows Saturday's date (it's still Saturday here)
Make date -u (in case you are on diferent time zone on your server)

Yes maybe this ... look :
2014-11-16 04:03:47 dseep: Signature rejected, too far into the past CTxIn(COutPoint(d09224a0b6b14d967279d32eab50761422622388b2

I remember installing ntp on my remotes, I don't think it's on my local.  I'm slow, and working on this.  I will update if this helps, sorry for the time span!!!  But thanks so far, it's my best bet!
Yes sure it's the remote. I see 4 min less on your remote and the message say : too far into the past
Just put 4 min more on your remote.

Or as root on both : ntpdate ntp.online.net


Well, I was pretty slow putting the info up, LOL.  That could account for it, but now they are both using ntp and I've changed the IP address and the masternode private key, and yet, I still get "not a capable masternode.  I'm at my wit's end.
legendary
Activity: 1120
Merit: 1000
If someone writes a detailed guide on how to have more than one masternode within a wallet ill send ya 100DRK for your service.

Perhaps this will help:

(Based on https://darkcointalk.org/threads/50-dark-bounty-for-masternode-guide-update.2721/)

Create masternode.conf in your Darkcoin working directory and put in the IP address of your MNs and their privkeys, like below:

192.168.0.1:9999 7qspZZJD3wsPifSzxZGnzo4HhR5Pd9MN2X9kGk4gPZi4LMJSvrE
192.168.0.2:9999 7rDDK21opuSHuu7eV2LdmBAunXWRUhVU3ZVek3frqYisnF4HyJL

Move DRK into your wallet in 1000 DRK increments. Then go to the console and use:

masternode start-many

legendary
Activity: 1260
Merit: 1001
Well, last resort, I'm changing my ip addresses and wallets, getting a new masternode key and hopefully this will work.  Damn I hate to do it, but it may be the only hope I have Sad
Jump to: