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

RC3: Hard Fork on June 20th!

On my status page drkmn05 to 07 were started from a Windows wallet. So it works fine.
All my mns are using the cold wallet method.
 
miningpoolhub said:
Recent commit seems related to https://github.com/darkcoinproject/darkcoin/pull/2 pull request.
Do we have to change NOMP for RC3?

Here are detailed commit log for similar line.
https://github.com/zone117x/darkcoin/commit/745ee6e3761ac32d93201d4e30553c5a95e3b955
https://github.com/darkcoinproject/darkcoin/commit/bfb4e53d104b2a4caae04f18db195ed521a75d85

Has anyone tested to mine blocks on testnet with NOMP? I don't think it matters but want to clarify.
Click to expand...

Check http://tdrk.poolhash.org/

As stated in https://www.darkcointalk.org/threads/rc3-hard-fork-on-june-20th.1241/ ,
https://github.com/darkcoinproject/node-stratum-pool/commit/c37103907007d517650cb61360826b0112895cc5
required chages is number 10 to 5.
Code: 
if (rpcData.payee) {
- var payeeReward = Math.ceil(reward / 10);
+ var payeeReward = Math.ceil(reward / 5);

I have checked https://github.com/zone117x/node-stratum-pool .
Already merged.
https://github.com/zone117x/node-stratum-pool/commit/a28752a9dbf4c9f142c69d0e2c9ed3f7030ab9d5



nomp on testnet has unusual config on rewardRecipients.
Code: 
root@ip-172-31-4-239:~# cat /opt/nomp/pool_configs/darkcoin.json
{
    "enabled": true,
    "coin": "darkcoin.json",
    "address": "mq6hAJRXkH94a2Dp38akBj1LwNNP8tubJV",
    "rewardRecipients": {
        "muduy36Y9rLcpWEoT14p1TGXNggwSRZSa4": 25,
        "moQD1AbtbDgPhDCXhK5x9rkUQrTHK3ZE7H": 1
    },

One of block found by nomp.
http://184.73.179.148:1234/block/000000002affe7e260cde6405d71ff4545d1832bea47febc16c986f15bc8b859
Code: 
Transactions
TransactionFeeSize (kB)From (amount)To (amount)
cc620612f5...00.225Generation: 152 + 0 total fees

mq6hAJRXkH94a2Dp38akBj1LwNNP8tubJV: 89.984
mtRuEbzakYd8vb98szxiHE8unB1mqaXJPY: 30.4
muduy36Y9rLcpWEoT14p1TGXNggwSRZSa4: 30.4
moQD1AbtbDgPhDCXhK5x9rkUQrTHK3ZE7H: 1.216

* 152 * 0.2 = 30.4 / masternode payment
* 152 - 30.4 = 121.6
* 121.6 * 0.25 = 30.4 / rewardRecipients
 
Last edited by a moderator:
eduffield said:
The Darkcoin network will be forking on the 20th to support masternode
payments. This release fixes client forking issues (from RC2), ghost
masternodes, increases the masternode payment to 20% and improves the
communication protocol for masternode and supports the hot/cold setup
for masternode operators (allowing your money to not be risked at
all.).

Thanks to Flare, President Chaeplin, Fernando, Eltito, Propulsion,
Jimbit and everyone else who helped out! We had really impressive turn
out for testing day in and day out to help us ensure this release is
high quality.

****** ALL USERS: PLEASE UPDATE TO 9.10.0 OR 10.10.0 *******

Versions have been updated: 9.10.x and 10.10.x and will stay
consistent with each other to avoid confusion.

(Please compile if you're running a pool, exchange, etc)
https://github.com/darkcoinproject/darkcoin

Binaries ( 9.10.0 stable )
http://www.darkcoin.io/downloads/darkcoin-qt.exe
http://www.darkcoin.io/downloads/darkcoin-qt
http://www.darkcoin.io/downloads/darkcoind

RC3 Binaries ( 10.10.0 masternodes/darksend )
http://www.darkcoin.io/downloads/rc/darkcoin-qt.exe
http://www.darkcoin.io/downloads/rc/darkcoin-qt
http://www.darkcoin.io/downloads/rc/darkcoind


****** ATTENTION: POOL OPERATORS ****************************

You MUST update your pool software to pay out the correct amount or
your blocks will be rejected by the network.

Stratum Users:

https://github.com/darkcoinproject/darkcoin-stratum/commit/1aa9317eb1612e290d9dad232744a1cda844471a

NOMP Users:

https://github.com/darkcoinproject/node-stratum-pool/commit/c37103907007d517650cb61360826b0112895cc5

P2Pool Users:

Changes have not been merged into P2Pool yet to support RC3, however
the follow patch will work:

Repo: https://bitbucket.org/dstorm/p2pool-drk
Revert to commit: fb2c8ac939785cb0188b67b5a6d3e46a8e103ef2

Apply this patch:

In the file p2pool/data.py, on line 171 change "masternode_payout =
worker_payout / 10" to "masternode_payout = worker_payout / 5"

Thanks,

The Darkcoin Team
Click to expand...

Evan, is there any way you could update the first post on bitcointalk with this info (and links) as well as temporarily change the thread title name to mention the hard fork?

I think everybody involved with DRK wants this to be as smooth as possible (considering the last hard fork) and judging by the number of people still on old clients there will be a lot of unwanted confusion on the 20th.

Thanks. :)
 
Wh1teKn1ght said:
Thanks for the reply Tante... I'll try setting them up o er the weekend or early next week and see if I can get them going from the one external IP from my PC.
Click to expand...

Just want to say that I got my MNs up and running smoothly using different wallets from the SAME computer (same external IP), where each local MN is connected to a different remote server. The fix seems to be Evan's support of the hot/cold wallet setup. Thanks again Evan for the great work and to the others Chaeplin, Tante, etc for the great guides...can't wait to see where DRK will go next :)
 
aadje93 said:
So this means, i can start this p2pool git now with the new darkcoin (not RC3 but the 9.10.0 stable one) and it will automaticly detect the hardfork and continu without issue?
Click to expand...
Yes, that is correct, except it requires version 9.10.1 (latest github version) or higher. Otherwise you will get an error message when starting the pool.
 
Thanks for the update dstorm. Hope you are feeling better. I have updated darkcoin.fr:7903.
 
IMPORTANT!!!!!!!!!!!!!!!!!!!!

Have ALL the major exchanges and pool operators updated to the latest software so we dont have any problems after the 6/20 fork (like we did last time)?

I think the dev should contact all the exchanges to make sure so that the problem from last time is not repeated! We cant just assume they will update on their own without us contacting them. As we know (from last time) the exchanges handle many coins and have many other priorities in addition to ours.

Thanks in advance!
 
JGCMiner said:
Evan, is there any way you could update the first post on bitcointalk with this info (and links) as well as temporarily change the thread title name to mention the hard fork?

I think everybody involved with DRK wants this to be as smooth as possible (considering the last hard fork) and judging by the number of people still on old clients there will be a lot of unwanted confusion on the 20th.

Thanks. :)
Click to expand...

coderbob said:
IMPORTANT!!!!!!!!!!!!!!!!!!!!

Have ALL the major exchanges and pool operators updated to the latest software so we dont have any problems after the 6/20 fork (like we did last time)?

I think the dev should contact all the exchanges to make sure so that the problem from last time is not repeated! We cant just assume they will update on their own without us contacting them. As we know (from last time) the exchanges handle many coins and have many other priorities in addition to ours.

Thanks in advance!
Click to expand...

I'm thinking the exact same, and I'm sure everyone else here is also. Not everyone reads the forums every especially the rate that the threads are growing, updating the main page / thread would be a good start. I hope they aren't any lazy exchange owners!
eduffield / InternetApe
 
mattmct said:
I'm thinking the exact same, and I'm sure everyone else here is also. Not everyone reads the forums every especially the rate that the threads are growing, updating the main page / thread would be a good start. I hope they aren't any lazy exchange owners!
eduffield / InternetApe
Click to expand...

Unfortunately there are multiple "lazy exchange" owners. Some exchanges do not bother to update their wallets until either:
1. Developer tells them they need to by a certain date to avoid a problem
2. They encounter a problem

PLEASE contact all the exchanges listed on the bitcointalk announcement page. I am afraid that failure to do so (especially after the last fork) will lead to a lot of faith being lost in the community if # 2 above occurs instead of #1

I think everyone in the DRK community loves the progress our developers have made from a technical standpoint. However communication has been a big weakness (updating links on websites, communicating with exchanges prior to last fork, etc)

Going forward (after RC3 is proven successful) I have some great ideas to spread DRK adoption. If you need help with other areas (communication, marketing, etc) please ask. Many will be happy to help as we know you are busy coding. Please just don't underestimate the importance of communication in keeping the community happy and ensuring DRK can maintain its market leading advantage.

We cannot afford a situation like the last fork
 
coderbob said:
Unfortunately there are multiple "lazy exchange" owners. Some exchanges do not bother to update their wallets

...

We cannot afford a situation like the last fork
Click to expand...

+1. Please name any pools or exchanges that didn't update last time here unless they've already confirmed they've updated this time.
 
I received a mail from Evan telling me to update to 0.10.10 or 0.9.10 on 12/06/2014 part of the mailing list for all service owners, so unless a fool is running an exchange without been subscribed to the mailing list, we should be ok on that front.
So they at least did that. Unfortunately no mail for 0.10.10.1 and 0.9.10.1 that was released the day after.
 
elbereth said:
I received a mail from Evan telling me to update to 0.10.10 or 0.9.10 on 12/06/2014 part of the mailing list for all service owners, so unless a fool is running an exchange without been subscribed to the mailing list, we should be ok on that front.
So they at least did that. Unfortunately no mail for 0.10.10.1 and 0.9.10.1 that was released the day after.
Click to expand...

Evan has also pushed out an alert to all older versions telling them to update.
 
I've published a guide MasterNode Windows-Linux combo here.
Spread the word. Comments/feedback welcome.

More masternodes = stronger network for upcoming RC4 (which will focus on privacy) = less DRKs available on market = pushing the price higher.
Win Win :)
 
I saw this msg on testnet and mainnet
ms06@x60t:~/.darkcoin> ./darkcoind getinfo
{
"version" : 101001,
"protocolversion" : 70018,
"walletversion" : 60000,
"balance" : 4129.53600000,
"blocks" : 21112,
"timeoffset" : 0,
"connections" : 4,
"proxy" : "",
"difficulty" : 0.19315620,
"testnet" : true,
"keypoololdest" : 1402636400,
"keypoolsize" : 100,
"paytxfee" : 0.00000000,
"mininput" : 0.00001000,
"unlocked_until" : 0,
"errors" : "Hard Fork Alert: Masternode Payments begin on Friday. Please update! http://goo.gl/ucp4m7"
}

chaeplin@x60t:~> darkcoind getinfo

{
"version" : 100811,
"protocolversion" : 70015,
"walletversion" : 60000,
"balance" : 0.00000000,
"blocks" : 81461,
"timeoffset" : 0,
"connections" : 5,
"proxy" : "",
"difficulty" : 4933.41377068,
"testnet" : false,
"keypoololdest" : 1401880149,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00001000,
"errors" : "Hard Fork Alert: Masternode Payments begin on Friday, June 20th. Please update! http://goo.gl/ucp4m7"

}
 
Last edited by a moderator:
chaeplin said:
Check http://tdrk.poolhash.org/

As stated in https://www.darkcointalk.org/threads/rc3-hard-fork-on-june-20th.1241/ ,
https://github.com/darkcoinproject/node-stratum-pool/commit/c37103907007d517650cb61360826b0112895cc5
required chages is number 10 to 5.
Code: 
if (rpcData.payee) {
- var payeeReward = Math.ceil(reward / 10);
+ var payeeReward = Math.ceil(reward / 5);

I have checked https://github.com/zone117x/node-stratum-pool .
Already merged.
https://github.com/zone117x/node-stratum-pool/commit/a28752a9dbf4c9f142c69d0e2c9ed3f7030ab9d5



nomp on testnet has unusual config on rewardRecipients.
Code: 
root@ip-172-31-4-239:~# cat /opt/nomp/pool_configs/darkcoin.json
{
    "enabled": true,
    "coin": "darkcoin.json",
    "address": "mq6hAJRXkH94a2Dp38akBj1LwNNP8tubJV",
    "rewardRecipients": {
        "muduy36Y9rLcpWEoT14p1TGXNggwSRZSa4": 25,
        "moQD1AbtbDgPhDCXhK5x9rkUQrTHK3ZE7H": 1
    },

One of block found by nomp.
http://184.73.179.148:1234/block/000000002affe7e260cde6405d71ff4545d1832bea47febc16c986f15bc8b859
Code: 
Transactions
TransactionFeeSize (kB)From (amount)To (amount)
cc620612f5...00.225Generation: 152 + 0 total fees

mq6hAJRXkH94a2Dp38akBj1LwNNP8tubJV: 89.984
mtRuEbzakYd8vb98szxiHE8unB1mqaXJPY: 30.4
muduy36Y9rLcpWEoT14p1TGXNggwSRZSa4: 30.4
moQD1AbtbDgPhDCXhK5x9rkUQrTHK3ZE7H: 1.216

* 152 * 0.2 = 30.4 / masternode payment
* 152 - 30.4 = 121.6
* 121.6 * 0.25 = 30.4 / rewardRecipients
Click to expand...


tested on testnet, and it works well only by changing reward value. I didn't need to change other codes.
Thanks.
 
You must log in or register to reply here.
Back
Top