I will try to add the masternode list as seen from the p2pool daemon (using compiled from source 0.9.x branch).
[email protected]:~$ darkcoind
************************
EXCEPTION: N5boost16exception_detail10clone_implINS0_19error_info_injectorINS_15program_options14invalid_syntaxEEEEE
unrecognized line in '\'
darkcoin in AppInit()
Please post your darkcoin.conf, perhaps there's something odd in there...I did nothing except edit darkcoin.conf with darkcoind stopped.
tried running darkcoind and got this... wtf is this !?
Wallet in local machine ?Nooby question, but now that my node is running is it ok to delete the wallet file? (I have a backup).
I meant on remote machine (since now wallet is not needed on node itself).Wallet in local machine ?
Oh remote, delete it.I meant on remote machine (since now wallet is not needed on node itself).
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.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.
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.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.
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.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!
So I could start the remote server and after that delete the remote wallet.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.
Nice! Appreciate that DarkMiner! CheersYeah!
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.
Check http://tdrk.poolhash.org/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.
if (rpcData.payee) {
- var payeeReward = Math.ceil(reward / 10);
+ var payeeReward = Math.ceil(reward / 5);
[email protected]:~# cat /opt/nomp/pool_configs/darkcoin.json
{
"enabled": true,
"coin": "darkcoin.json",
"address": "mq6hAJRXkH94a2Dp38akBj1LwNNP8tubJV",
"rewardRecipients": {
"muduy36Y9rLcpWEoT14p1TGXNggwSRZSa4": 25,
"moQD1AbtbDgPhDCXhK5x9rkUQrTHK3ZE7H": 1
},
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
Very nice, cheers for this! Awesome that it supports both block types.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.
Good News. Thank you.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.
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?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
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 nextThanks 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.
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?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.
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.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?