Typo?Yes, that's exactly the way it's working, there is now a 'masternode.conf' file with each line containing the masternode-n-addr and masternode-n-privkey.
Look at https://github.com/darkcoin/darkcoin/commit/f088a8f56d3908c140e2e92c65ac33c83783ade2 to get an idea of how it works
v0.10.15 - Onyx Release
- Thread starter eduffield
- Start date
Sure
Anyone interested in giving it a test drive:
CI-builds for v0.10.16.0-gf9d2149
Windows 32bit:
http://bamboo.darkcoin.qa/artifact/DRKW-DEV/JOB1/build-20/gitian-win-darkcoin-bin/32/darkcoin-qt.exe
http://bamboo.darkcoin.qa/artifact/...tian-win-darkcoin-bin/32/daemon/darkcoind.exe
http://bamboo.darkcoin.qa/artifact/...oin-bin/32/darkcoin-0.10.16.0-win32-setup.exe
Mac OS X:
http://bamboo.darkcoin.qa/artifact/...-osx-darkcoin-dist/darkcoin-0.10.16.0-osx.dmg
Linux 32bit:
http://bamboo.darkcoin.qa/artifact/.../gitian-linux-darkcoin-bin/bin/32/darkcoin-qt
http://bamboo.darkcoin.qa/artifact/DRKL-DEV/JOB1/build-19/gitian-linux-darkcoin-bin/bin/32/darkcoind
Linux 64bit:
http://bamboo.darkcoin.qa/artifact/.../gitian-linux-darkcoin-bin/bin/64/darkcoin-qt
http://bamboo.darkcoin.qa/artifact/DRKL-DEV/JOB1/build-19/gitian-linux-darkcoin-bin/bin/64/darkcoind
If I understand the code correctly instead of using "getaccountaddress 0" ANY address with exactly 1000 DRK gets used?Look at https://github.com/darkcoin/darkcoin/commit/f088a8f56d3908c140e2e92c65ac33c83783ade2 to get an idea of how it works
So to start 4 masternodes you'll need to have 4 addresses funded with 1000DRK in your wallet and the masternode.conf file containing 4 lines with masternodeaddr and masternodeprivkey for each MN - and then fire a "masternode start-many" command
Correct - it iterates through your wallet, searching for 1000DRK vins and matches them against the masternode.conf data. But i must confess i don't know how the code will handle order changes...
A brief user guide would be good - do we just run masternode genkey multiple times, how do we tie the masternodeprivkey to the masternodeaddress in the .conf...?
You can do that now. Just has to be a single 1000DRK vin. I think the address 0 thing was for some much earlier version, I usually never bother anymore.
Will migrate my masternodes to the new setup scheme and will capture all i did
Correct, "address 0" was from a early version - the current wallets will use the first 1000DRK found in the wallet, regardless of label.
start-many is a logical extension to this, not stopping at the first 1000DRK vin ^^
This is fantastic news... will definitely be importing my priv keys into one wallet to manage one wallet and one config file when more information is released.
Will there be a limit to how many masternodes can be run in one instance? I can't help but think it just makes it easier for someone to track what's going on (if a loop hole were found)
You still need unique remote instances for each masternode. This just allows all the local wallets and configs to be in one file each instead of a pair for each masternode.
Correct, "start-many" is just a convenience method. The architecture for masternodes does not change.
Just noticed that SV03 was gray (inactive) in here http://drk.poolhash.org/masternode.html
same time my MN:s was reported inactive by uptime robot https://uptimerobot.com
which uses this MN list http://drk.poolhash.org/poolhashrate/blocks/masterstatus.txt
Checked MN:s and they was running just OK, all active, so, problem was SV03.
After 5 mins, SV03 is back active and green.
same time my MN:s was reported inactive by uptime robot https://uptimerobot.com
which uses this MN list http://drk.poolhash.org/poolhashrate/blocks/masterstatus.txt
Checked MN:s and they was running just OK, all active, so, problem was SV03.
After 5 mins, SV03 is back active and green.
Thanks, Flare! When I get home, I will send you another DRK beer!Will migrate my masternodes to the new setup scheme and will capture all i did
Last edited by a moderator:
eta plz got drk kthxbiWill migrate my masternodes to the new setup scheme and will capture all i did
Hi, guys. Was the 0.10.15.13 binary compiled from the v0.10.15.13 branch or the master branch?
if(!darkSendSigner.IsVinAssociatedWithPubkey(vin, pubkey)) {
LogPrintf("dsee - Got mismatched pubkey and vin\n");
pfrom->Misbehaving(100);
return false;
}
This block of code above is missing in the v0.10.15.13 branch but it is in the master branch and v0.10.14.1 branch. Does it have any effect on the disconnect behavior we are seeing in masternodes in the past few days?
EDIT: This block of code is from src/main.cpp
if(!darkSendSigner.IsVinAssociatedWithPubkey(vin, pubkey)) {
LogPrintf("dsee - Got mismatched pubkey and vin\n");
pfrom->Misbehaving(100);
return false;
}
This block of code above is missing in the v0.10.15.13 branch but it is in the master branch and v0.10.14.1 branch. Does it have any effect on the disconnect behavior we are seeing in masternodes in the past few days?
EDIT: This block of code is from src/main.cpp
- Apr 8, 2014
- 1,971
- 1,339
- 1,283
Words can't describe how happy I am right now...Yes, that's exactly the way it's working, there is now a 'masternode.conf' file with each line containing the masternode-n-addr and masternode-n-privkey.
Look at https://github.com/darkcoin/darkcoin/commit/f088a8f56d3908c140e2e92c65ac33c83783ade2 to get an idea of how it works
So to start 4 masternodes you'll need to have 4 addresses funded with 1000DRK in your wallet and the masternode.conf file containing 4 lines with masternodeaddr and masternodeprivkey for each MN - and then fire a "masternode start-many" command
- Apr 8, 2014
- 1,971
- 1,339
- 1,283
Yeah, looking at blocks 155473, 155474, 155481, 155482.
Sidenote, looks like trademybit is on onyx.
They will. They've been prompt at updating when I've messaged them, however, they haven't been on BCT in days so probably haven't seen it.oblox just posted it some seconds before you
we still need miningpoolhub to be dark
I am curious why the blocks above were paid how they were.
Would just two wallets standing by with say 1000DRK in each of them be enough to get anonymisation flowing on mainnet? Or three, scripted to keep juggling amounts of DRK about? Such a sevice could maybe be provided to assist until DS usage became more prevalent?
Have you heard the Story of Alibaba and the 40 thieves? Open Sesame. We should try to relate Darkcoin to Treasure somehow, like Gold. Gold is anonymous but Cash Money isn't, Gold is heavy but Darkcoin isn't. It could help people who wouldn't necessarily reverberate with the word Darkcoin.
We should try to relate Darkcoin to Treasure somehow, like Gold. Gold is anonymous but Cash Money isn't, Gold is heavy but Darkcoin isn't. It could help people who wouldn't necessarily reverberate with the word Darkcoin.
It seems like but my node was also getting not_detected payment once with 0.10.15.13. Also, it seems that we cannot trust the monitoring nodes on poolhash or drk.mn. But, when pool hash shows that my masternode is completely inactive, it often goes from 1 to 0 in the grep result. sv02 from poolhash has a nl status now.