I will try to add the masternode list as seen from the p2pool daemon (using compiled from source 0.9.x branch).
RC3: Hard Fork on June 20th!
- Thread starter eduffield
- Start date
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.
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.
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.
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.
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.
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!
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!
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
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.
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?
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.
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.
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.
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?
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.
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);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
},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 - 30.4 = 121.6
* 121.6 * 0.25 = 30.4 / rewardRecipients
Last edited by a moderator:
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.
https://bitbucket.org/dstorm/p2pool-drk
It supports both block types so you can update now. It will detect when masternode payments start.
Very nice, cheers for this! Awesome that it supports both block types.
Update: Just updated my p2p pool
http://x11p2p.com:7903/
Last edited by a moderator:
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.
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
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.