RC3: Hard Fork on June 20th!

elbereth

Active Member
Dash Support Group
Mar 25, 2014
456
480
133
Costa Rica
dashninja.pl
Dash Address
XkfkHqMnhvQovo7kXQjvnNiFnQhRNZYCsz
I will try to add the masternode list as seen from the p2pool daemon (using compiled from source 0.9.x branch).
 

yidakee

Well-known Member
Foundation Member
Apr 16, 2014
1,812
1,168
283
I did nothing except edit darkcoin.conf with darkcoind stopped.

tried running darkcoind and got this... wtf is this !?

[email protected]:~$ darkcoind
************************
EXCEPTION: N5boost16exception_detail10clone_implINS0_19error_info_injectorINS_15program_options14invalid_syntaxEEEEE
unrecognized line in '\'
darkcoin in AppInit()
 

flare

Administrator
Dash Core Team
Moderator
May 18, 2014
2,286
2,404
1,183
Germany
I did nothing except edit darkcoin.conf with darkcoind stopped.

tried running darkcoind and got this... wtf is this !?
Please post your darkcoin.conf, perhaps there's something odd in there...
 

yidakee

Well-known Member
Foundation Member
Apr 16, 2014
1,812
1,168
283
There was... damn lag to Singapore playing tricks again... I have no clue why or how, I put a "/" with before the beginning comment.
 

darkness

Member
Mar 9, 2014
39
8
48
Nooby question, but now that my node is running is it ok to delete the wallet file? (I have a backup).
 

chaeplin

Active Member
Core Developer
Mar 29, 2014
749
356
133
Nooby question, but now that my node is running is it ok to delete the wallet file? (I have a backup).
Wallet in local machine ?
If you have a backup wallet.dat, you can delete the wallet.dat in local machine.
Before that, make sure darkcoind/darkcoin-qt is not running on your local-machine,
stop darkcoind/darkcoin-qt first,
check again backup is safe.
 

AlexGR

New Member
May 24, 2014
26
21
3
I'm worried that the fork is a bit on "autopilot" and we'll have many on the wrong forks. People won't just update because they are in sync with our own bubble-reality of DRKness where we monitor these things 24/7 - they have lives to run.

1. There's too little exposure on the fact that there will be a fork. The title of bitcointalk thread should be changed to something like "hardfork on 20th, please update..." until the fork is done.

2. The first post on bitcointalk must also change with the announcement and the proper link (.1 I presume)

3. If announcements have been sent out already to exchanges etc regarding .0, they must be re-notified about .1 - if the two versions are incompatible and create fork issues.

4. Whatever else needs to be done - you add it in the list.
 

flare

Administrator
Dash Core Team
Moderator
May 18, 2014
2,286
2,404
1,183
Germany
3. If announcements have been sent out already to exchanges etc regarding .0, they must be re-notified about .1 - if the two versions are incompatible and create fork issues.
The versions .0 and .1 are not incompatible and will not create fork issues - nevertheless all miners/pools should be on .1 for the voting to be evenly distributed. Miners with .0 will cause unpaid blocks, since their votes have a higher a probabilty not to get confirmed by network.
 

DrkMiner

Member
Jun 7, 2014
204
63
88
Hi,
If a Hot setup is used and and encrypted wallet is uploaded to server, how risky is it?
The wallet is has a 25 characters encryption. Bash history is deleted.

Tried to do the hot cold, but could not make it run.
My local cold wallet is on windows xp (yeap old laptop).
Seen instructions on the forum, but they all use Linux cold pc.
Tried to use the Console in the Debug tab of the program...

When I setup masternode=1 it downloads the testnet3 info. I that okay? (the node is not for testing)

What windows version of the cold wallet?
Any info on how to do it on windows wallet would be appreciated.
Thanks!
 

darkness

Member
Mar 9, 2014
39
8
48
Hi,
If a Hot setup is used and and encrypted wallet is uploaded to server, how risky is it?
The wallet is has a 25 characters encryption. Bash history is deleted.
If you can run a hot wallet then do it but after it's running just delete the wallet file (stop darkcoind, delete wallet, start darkcoind - as chaeplin helped me with earlier in the thread). Obviously have a backup of the wallet first.

Version should be 10.10.1
 

vertoe

Three of Nine
Mar 28, 2014
2,573
1,652
1,283
Unimatrix Zero One
Hi,
If a Hot setup is used and and encrypted wallet is uploaded to server, how risky is it?
The wallet is has a 25 characters encryption. Bash history is deleted.
Thanks!
Whatever you do, the moment you enter your wallet passphrase to start the masternode on the server an attacker might be able to steal the passphrase sniffing ps or proc.
 

DrkMiner

Member
Jun 7, 2014
204
63
88
Oh remote, delete it.
Remote should holding 0 DRK.
Stop darkcoind, detele the wallet.dat, start darkcoind.
Darkcoind will make a new empty wallet.dat.
So I could start the remote server and after that delete the remote wallet.
Stop it and restart it again ?

Restart with out wallet passphrase?
 

mattmct

Member
Mar 13, 2014
259
92
88
Sounds like a lot of people are running well with the cold wallet. I'm going to give that a try now on my next master node.

Similar as DrkMiner above I only have windows computers locally (apart from my mining rig, but don't really want to use that for this), I've yet to see anyone say they have started the cold masternode via a local windows computer......if anyone has, please chime in!

Right now, I'm thinking I'll install a live USB unbutu on my computer, and use that.
 

DrkMiner

Member
Jun 7, 2014
204
63
88
  • Like
Reactions: mattmct

mattmct

Member
Mar 13, 2014
259
92
88
Yeah!
Managed to use a windows PC for the cold wallet.
Follow chaeplin's guide https://www.darkcointalk.org/threads/how-to-set-up-ec2-t1-micro-ubuntu-for-masternode-part-2-3.241/
For the commands in the guide:
darkcoind masternode genkey
darkcoind masternode start passphrase_of_wallet

Use the windows wallet. Open wallet then goto Help > Debug window > Console tab

Enter masternode genkey (omit darkcoind) click Enter.
Copy the key
Enter masternode start passphrase_of_wallet.
Nice! Appreciate that DarkMiner! Cheers :) That will save me some time :). I'll give this a try tomorrow (via windows :)). ... oh, I assume you used the beta version for the windows as well yeah?
 

elbereth

Active Member
Dash Support Group
Mar 25, 2014
456
480
133
Costa Rica
dashninja.pl
Dash Address
XkfkHqMnhvQovo7kXQjvnNiFnQhRNZYCsz
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.
 
  • Like
Reactions: mattmct

miningpoolhub

New Member
Mar 9, 2014
12
1
3

chaeplin

Active Member
Core Developer
Mar 29, 2014
749
356
133
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.
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:
[email protected]:~# 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:

JGCMiner

Moderator
Moderator
Jun 8, 2014
364
217
113
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
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. :)
 
  • Like
Reactions: mattmct and flare

Wh1teKn1ght

New Member
May 11, 2014
32
5
8
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.
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 :)
 
  • Like
Reactions: mattmct

aadje93

New Member
May 23, 2014
37
4
8
P2Pool update is now available. Sorry about the delay. I have been sick for almost two weeks.
https://bitbucket.org/dstorm/p2pool-drk

It supports both block types so you can update now. It will detect when masternode payments start.
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?
 

dstorm

New Member
May 9, 2014
15
19
3
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?
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.