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

Reverting RC3 Masternode Payments Fork

eduffield

Core Developer
Since launching the masternode payments a few intermittent forks have popped up on the network. This is not as serious as last time, but is still a concern for the Darkcoin network, so we're reverting the changes for the time being while we discover the cause and do further testing.

Please update to either 10.10.2 or 9.10.2. Thanks!

https://www.github.com/darkcoinproject/darkcoin

https://www.darkcoin.io/downloads/darkcoin-qt.exe
https://www.darkcoin.io/downloads/darkcoin-qt
https://www.darkcoin.io/downloads/darkcoind

https://www.darkcoin.io/downloads/rc/darkcoin-qt.exe
https://www.darkcoin.io/downloads/rc/darkcoin-qt
https://www.darkcoin.io/downloads/rc/darkcoind
 
I'm curious if the error was caused from people running different builds of the master node?
How would the network validate that a master node is up-to-date with the latest build, in addition to config file specifications?
 
darkcoin_logo_140x140.png


DarkCoin Mac OS X Update v0.9.10.2
updated 20 June 2014

URL: https://www.dropbox.com/s/04eg847wca9541t/DarkCoin-Qt-MacOSX-0.9.10.2.zip (on darkcoin.io shortly)
zip shasum: 260dee24f45a8bc6ae0ed1df2463e71a377efc4f
tips: XtwzEuurDTNeVK5a26AzzZDdVkkPkAQ7Eu

R5R4ZQO.png
 
Do we need to also revert this change in p2pool?

"In the file p2pool/data.py, on line 171 change "masternode_payout =
worker_payout / 10" to "masternode_payout = worker_payout / 5"
 
This is a very noob question, but I followed chaeplin's guide for setting up an ec2 instance.
I ran the following command when it was still 10.10.1:

git clone https://github.com/darkcoinproject/darkcoin.git
into /usr/local/src/

how do I revert/update to 10.10.2?

I've tried running the same command but I get the following error:
"fatal: destination path 'darkcoin' already exists and is not an empty directory."
 
This is a very noob question, but I followed chaeplin's guide for setting up an ec2 instance.
I ran the following command when it was still 10.10.1:

git clone https://github.com/darkcoinproject/darkcoin.git
into /usr/local/src/

how do I revert/update to 10.10.2?

I've tried running the same command but I get the following error:
"fatal: destination path 'darkcoin' already exists and is not an empty directory."
I just downloaded the pre-compiled binaries in this post over the binaries on my system worked like a charm. But if you must recompile from git, I would assume you need to delete the existing git clone directory, try "sudo rm -R /usr/local/src/darkcoin" and then rerun your git clone command.
 
This is a very noob question, but I followed chaeplin's guide for setting up an ec2 instance.
I ran the following command when it was still 10.10.1:

git clone https://github.com/darkcoinproject/darkcoin.git
into /usr/local/src/

how do I revert/update to 10.10.2?

I've tried running the same command but I get the following error:
"fatal: destination path 'darkcoin' already exists and is not an empty directory."
I guess you need this https://www.darkcointalk.org/threads/how-to-set-up-ec2-t1-micro-ubuntu-for-masternode-part-3-3.262/
 
I'm curious if the error was caused from people running different builds of the master node?
How would the network validate that a master node is up-to-date with the latest build, in addition to config file specifications?

The protocolversion is increased for newer masternode versions, which makes the protocol incompatible. The only versions capable of joining the network were 0.10.10.0 and 0.10.10.1 - all other versions were ignored.
 
Last edited by a moderator:
The protocolversion is increased for newer masternode versions, which makes the protocol incompatible. Only versions capable of joining the network were 0.10.10.0 and 0.10.10.1 - all other versions were ignored.
When can I tryout to be on the dev team or test team?
 
When can I tryout to be on the dev team or test team?

Whenever you want: Setupsome masternodes, join testnet, solomine and try to reproduce the problem we encountered in mainnet. I have some older, oudated RC versions at hand, so if someone needs one:

darkcoind-v0.10.7.3-beta
darkcoind-v0.10.8.0-3-g30e06b8-beta
darkcoind-v0.10.8.10-1-g7da5afc-beta
darkcoind-v0.10.8.2-beta
darkcoind-v0.10.8.4-beta
darkcoind-v0.10.8.5-2-g8e508af-beta
darkcoind-v0.10.8.5-beta
darkcoind-v0.10.8.8-beta

1000 tDRK available on demand :smile:
 
Whenever you want: Setupsome masternodes, join testnet, solomine and try to reproduce the problem we encountered in mainnet.
1000 tDRK available on demand :smile:
sounds great, how does that work? Should I put it on my server, generate address, get the test coins and off I go? :)
 
./darkcoind --reindex

Why revert ? ... just ignore, if another pool/exchanger not follow dev instruction .. its only need time .. they are following soon
 
Last edited by a moderator:
Sorry for newbie stuff: How do I start with testing the MN? Have 1k darkcoins to set up the MN but prefer to start with test coins before running it for real
 
added
addnode=23.23.186.131
addnode=50.16.206.102
addnode=50.19.116.123
addnode=98.165.130.67
addnode=54.242.50.205
addnode=50.17.98.53
addnode=54.225.43.37

and downloaded it very fast and all working now. Never thought about adding p2pool.darkcointalk.org and darkcoin.io lol

Maybe make some piece of code that automaticly connects to darkcoin.io. Then forking problems should be lot less as everyone is kind of forced to connect to the right wallet.
 
Back
Top