• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

RC5 Launch (MANDATORY UPDATE)

F
chaeplin said:
Just stop darkcoind, update darkcoind(remote and local). start it.
Using local wallet(updated), start masternode.

No need to update ip or key.
Click to expand...

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?
 
stonehedge said:
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.
Click to expand...

I'm green across the board now. Masternode count increasing. All my IPs are active. Looking good.
 
chaeplin said:
eduffield flare
Looks like "enforce_masternode_payments" is gone in getblocktemplate of 101314

Code: 
user@sv3:~> darkcoind getinfo

{
    "version" : 101314,
    "protocolversion" : 70038,

~~~

   "height" : 140427,

    "votes" : [

    ],

    "payee" : "XsZCTymDd4dLWsBNwCSDJqXfdWz3KSejJ6",

    "masternode_payments" : true

}

91314 has
Code: 
   "payee" : "XsZCTymDd4dLWsBNwCSDJqXfdWz3KSejJ6",

    "masternode_payments" : true,

    "enforce_masternode_payments" : false

}
Click to expand...
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.
 
yidakee said:
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?
Click to expand...
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.
 
AjM said:
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.
Click to expand...
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.
 
oblox said:
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.
Click to expand...
I updated my MN:s no problem, old wallets.
Maybe flare can confirm that what i just posted.
 
AjM said:
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.
Click to expand...
I`m not the DEV, but it was my one of the last questions to Flare.
Yes. till you don`t use darksend old wallets are save.
 
All good, market is bleeding money somewhere but not DRK it seems. Our price is flat. Not an issue for all but for traders this is not quite it it feels.
 
AjM said:
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.
Click to expand...

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 ?
 
splawik21 said:
I`m not the DEV, but it was my one of the last questions to Flare.
Yes. till you don`t use darksend old wallets are save.
Click to expand...
Which you shouldn't need to worry about because darksend should automatically be disabled with the masternode=1 setting in the config file, right?
 
yidakee said:
That the thing. Since v.32 the daemon need 1k keypool to denominate without bugs
Click to expand...
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.
 
oblox said:
Which you shouldn't need to worry about because darksend should automatically be disabled with the masternode=1 setting in the config file, right?
Click to expand...
yes it does :)
 
GilAlexander said:
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?
Click to expand...

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.
 
eduffield said:
Hello Everyone,

****** PLEASE UPDATE TO RC5, THIS UPDATE INCLUDES A SPORK (A HARD FORK THAT CAN BE ACTIVATED AT WILL). WHEN 90% OF THE NETWORK HAS UPDATED, IT WILL BE ACTIVATED OR IN 3 WEEKS. *****

RC5 is officially available for download!

This is a large update to the stability of RC5, including:

- Enforcement of masternode payments
- Vastly improved effectiveness of the anonymity provided by Darksend (due to the audit of Kristov)
- Improved speed of Darksend
- Prepared code for open sourcing
- Added Darksend overview screen so users can see what's happening

This is the last release candidate we'll have. Open sourcing will happen in one week! After this, we'll have the community name releases and be doing a 2-3 month release schedule.

For all changes, please see the changelog:
https://github.com/darkcoinproject/darkcoin-binaries/blob/master/CHANGELOG.md

What's next for Darkcoin?

Next we're going to start working on a demo version of Instant Transactions (https://www.darkcoin.io/downloads/InstantTX.pdf). It's going to take a lot of work to lay the foundation, soon
after we'll be calling for some testnet users to try it out and report back.

Other improvements in the works include fixing DOS hardening for the Masternode network and Darksend.

How To Use Darksend (Thanks vertoe!)

Please update to RC5!

Source: Compile if you are running a pool, exchange, etc.

https://github.com/darkcoinproject/darkcoin

9.13.14 (Stable) Binaries: Does not include Darksend

Windows.exe: https://raw.githubusercontent.com/d...in-binaries/master/darkcoin-0.9.13.14-win.zip
Windows installer: https://raw.githubusercontent.com/d...ies/master/darkcoin-0.9.13.14-win32-setup.exe
Mac OSX: https://raw.githubusercontent.com/d...in-binaries/master/darkcoin-0.9.13.14-osx.dmg
Linux: https://raw.githubusercontent.com/d...naries/master/darkcoin-0.9.13.14-linux.tar.gz

10.13.14 (RC) Binaries: Includes Darksend - Masternode Operators

Windows .exe: https://raw.githubusercontent.com/d...inaries/master/rc/darkcoin-0.10.13.14-win.zip
Mac OSX: https://raw.githubusercontent.com/d...inaries/master/rc/darkcoin-0.10.13.14-osx.dmg
Linux: https://raw.githubusercontent.com/d...es/master/rc/darkcoin-0.10.13.14-linux.tar.gz

Thanks to everyone who submited tickets and tested the system tirelessly! We couldn’t have done it without all of you.

Thanks,

The Darkcoin Team
Click to expand...

Thank you Evan! Great work testers! Very exciting times indeed...
 
* 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'
 
Last edited by a moderator:
You must log in or register to reply here.
Back
Top