RC5 Launch (MANDATORY UPDATE)
- Thread starter eduffield
- Start date
It takes some time for the masternode network to stabilise - i would not be concerned before tomorrow.
Sounds good to me. Thanks Flare. Thats what gut feeling said...but you know I like to see things perfectly 
Did you restart masternode using cold wallet ?Sounds good to me. Thanks Flare. Thats what gut feeling said...but you know I like to see things perfectly
Yes, but then nodes appeared for a while and then dropped off.
I'm going to double check that my configs are fine and do what Flare suggested and let things settle.
Chaeplin, on this version, do we need to remake IP and genkey? Or just update server daemon and masternode start locally ?
eduffield flare
Looks like "enforce_masternode_payments" is gone in getblocktemplate of 101314
91314 has
Looks like "enforce_masternode_payments" is gone in getblocktemplate of 101314
Code:
[email protected]:~> darkcoind getinfo
{
"version" : 101314,
"protocolversion" : 70038,
~~~
"height" : 140427,
"votes" : [
],
"payee" : "XsZCTymDd4dLWsBNwCSDJqXfdWz3KSejJ6",
"masternode_payments" : true
}
Code:
"payee" : "XsZCTymDd4dLWsBNwCSDJqXfdWz3KSejJ6",
"masternode_payments" : true,
"enforce_masternode_payments" : false
}Just stop darkcoind, update darkcoind(remote and local). start it.
Using local wallet(updated), start masternode.
No need to update ip or key.
F
Yes, but if in the future we're going to use RC5 QT's to manage funds, then RC4 wallet will have only a keypool of 100, and apparently incompatible with RC5 QT's... and might even corrupt. So a masternode CAN be activated just remote, but to be safe, you must create RC5 wallet and regenerate IP, 1k address and genkey, right?
I'm green across the board now. Masternode count increasing. All my IPs are active. Looking good.
This moved to the "getcheckpoint" command
Code:
{
"synccheckpoint" : "00000000000f13643da08d79382fa78ae2a57abb4c436fd23962308cdaa00ad7",
"height" : 140405,
"timestamp" : 1411393927,
"subscribemode" : "enforce",
"enforcing" : "off"
}Yeah, guys, but for RC5, one must update the local wallet too (because of future enforcement on v.10) - so anyone before .v32 MUST first update local wallet to the new 1k keypool, right?
In essence, you can activate the remote RC5 daemon fine and quick now, but in a few weeks you'll need an RC5 ready wallet on your local wallet, when for example you want to cash out.
In essence, you can activate the remote RC5 daemon fine and quick now, but in a few weeks you'll need an RC5 ready wallet on your local wallet, when for example you want to cash out.
I think (if remember right) in local mn wallet have DS disabled and therefore no need to 1000 keys and no corruption danger.
Dev correct me if needed.
This is what I am looking for clarification as well. If I can just update and start the masternodes on the new RC5 client after updating the remote daemons to RC5 without having to send the 1000 dark to a new RC5 generated address and doing the genkey all over again.
Because my wallet was generated and funded pre v32.
I updated my MN:s no problem, old wallets.
Maybe flare can confirm that what i just posted.
That the thing. Since v.32 the daemon need 1k keypool to denominate without bugs, but with masternode=1, that is disabled.
What happens when you use a RC4 wallet with 100 keypool on a v.9 RC5 QT to manage funds ?
v.9 doenst need 1k, so it is safe, but what if you use v.10 to load an RC4 wallet ?
Which you shouldn't need to worry about because darksend should automatically be disabled with the masternode=1 setting in the config file, right?
Yes, you are talking about MN:s wallet, right?
That can be deleted when updating MN:s, but i am talking about windows local cold wallet.
- Apr 8, 2014
- 1,971
- 1,339
- 1,283
After updating I have all green indicators on http://drk.poolhash.org/masternode.html, my mn's ip listed in "darkcoind masternode list" and I got message "successfully started masternode" in cold wallet. I have "inactive 0%" status on https://drk.mn/masternodes.html. Is there something to worry about?
Next question: in .13.14 wallet on win7x64 I cannot view masternodes list and count ({} and 0). What to do?
Next question: in .13.14 wallet on win7x64 I cannot view masternodes list and count ({} and 0). What to do?
I had that too. Left it a while and it soon corrected itself. I think the various masternode monitoring sites only update themselves periodically and also, the number of masternode changes will take a while to propagate around.
* Updating Masternode *
1) stop darkcoind (locl and remote)
2) Update darkcoind(locl and remote)
3) remove peers.dat(locl and remote)
4) Start darkcoind(locl and remote)
Check drkcoind status using 'darkcoind getinfo' and 'darkcoind masternode current'
Compare block no and current masternode with http://drk.poolhash.org/masternode.html
(Updated every 3 mins, wait a litle)
If current ip is equal to ip in masternode.html, do 5). If diffrent, restart darkcoind, check 4)
5) Start Masternode using local wallet. Your MN will be listed in http://drk.poolhash.org/masternode.html with in 3 min.
6) After 30 mins, check http://drk.poolhash.org/masternode.html , MN is still updated
coloum : 'lastseen minutes'
1) stop darkcoind (locl and remote)
2) Update darkcoind(locl and remote)
3) remove peers.dat(locl and remote)
4) Start darkcoind(locl and remote)
Check drkcoind status using 'darkcoind getinfo' and 'darkcoind masternode current'
Compare block no and current masternode with http://drk.poolhash.org/masternode.html
(Updated every 3 mins, wait a litle)
If current ip is equal to ip in masternode.html, do 5). If diffrent, restart darkcoind, check 4)
5) Start Masternode using local wallet. Your MN will be listed in http://drk.poolhash.org/masternode.html with in 3 min.
6) After 30 mins, check http://drk.poolhash.org/masternode.html , MN is still updated
coloum : 'lastseen minutes'
Last edited by a moderator: