It's not that hard to start many masternodes even now (.15.13) - just use bash to implement what start-many does  > ls masternodes/
1.conf 1.dat 2.conf 2.dat 3.conf 3.dat and that loop.sh script could look like this: #!/bin/bash
#### .conf and .dat files must have the same name
masternodesDir="masternodes"
configs="$masternodesDir/*.conf"
echo "Starting masternodes..."
## darkcoind stop
read -s -p "Enter your wallet passphrase:" mySuperSecretPassphrase
echo ""
for conf in $configs
do
echo "Processing $conf..."
wallet="${conf##*/}"
wallet="$masternodesDir/${wallet%%.conf}.dat"
echo "... and corresponding wallet $wallet"
# cp $conf ~/.darkcoin/darkcoin.conf
# cp $wallet ~/.darkcoin/wallet.dat
# darkcoind
# sleep 20
# darkcoind passphrase $mySuperSecretPassphrase 999999
# darkcoind masternode start
# darkcoind stop
# sleep 2
echo "Done"
done
## darkcoind
echo "Yay!" remove "# " and have fun > ./loop.sh
Starting masternodes...
Enter your wallet passphrase:
Processing masternodes/1.conf...
... and corresponding wallet masternodes/1.dat
Done
Processing masternodes/2.conf...
... and corresponding wallet masternodes/2.dat
Done
Processing masternodes/3.conf...
... and corresponding wallet masternodes/3.dat
Done
Yay! (you'll get some more output from darkcoind daemon too but for the sake of simplicity I ran it commented just to show the idea) Yes, it will take more time to start masternodes that way but at the end it doesn't really matter (or if it does you could split masternode files between few machines, use -datadir option and so on) And it's really only one time job. |
|
|
|
What is the entry that I have to do in the .conf to disable the darksend?
I always faked a masternode config to have it disabled but that's an ugly workaround. I guess or hope there is a config parameter for just doing that.
well.. for daemon there is a command line option -disabledarksend=<n> Disable use of automated darksend for funds stored in this wallet (0-1, default: 1) I believe you can use it in conf too (without "-" of course) If i set up a account on Vultr and run a testnet masternode, can i then get rid of the testnet node and run a mainnet node on the same instance?
You need to comment out "testnet=1", regenerate masternodeprivkey and put it in both remote and local config, send 1000 DRK to local wallet and issue masternode start command. And don't forget to open port 9999 instead of 19999. |
|
|
|
Hi
when I try to send drk from my qt wallet I get an eror that says: unable to locate enough darksend denominated funds for this transaction. Probably something stupid on my side .. can someone axplain to me what I am doing wrong?
Thanks
well... I guess you do not have enough denominated funds  If you didn't start mixing - that's normal and to send funds you just need to select "Create Normal Transaction" or "No Preference"  EDIT: ahhh... Minotaur26 was faster  |
|
|
|
Can anyone access Cryptsy?
no  Thought it was only me! I hope their back soon Gox is in the air everywhere I look around Gox is in the air every sight and every sound And I don't know if I'm being foolish....  |
|
|
|
What is the whale doing? Stolen funds or just someone moving about a lot?
Most likely stolen. Just check out the behavior. Always moving the stash to a new address and slowly draining to exchanges and fresh addresses. It looks scripted to run 24/7. Here is where funds are currently parked: https://chainz.cryptoid.info/drk/address.dws?XpE6Yfhd3detzyRpL7YQiGBjRLzHBhrKKY.htmSo now you can follow along until he wises up and Darksends them. i was just tracking this and came here to post but it looks like everyone is already on top of it. looks like the mintpal/moolah/mintgox bot has dumped 70k drk on various exchanges in this last week. i tracked it back to an address on 2014-10-07 with 353,787.01000031 https://chainz.cryptoid.info/drk/tx.dws?595614.htmyou can follow the path down to 286,718.03994322 here... https://chainz.cryptoid.info/drk/address.dws?512845.htmif you follow it you can see the 70k drk being sent to other exchanges this last week. looks like they knew they f'ed up a week ago and have been liquidating. criminal? The fact that there are tracks means one of two things. 1. They are fucking stupid. This is Darkcoin, with that new open source feature called Darksend. or, 2. We need to do some better marketing They were obviously time bound and needed to liquidate their DRK as quickly as possible - you can see by how cheap they were willing to dump. At this stage it would take a long time to anonymize 260k+ DRK as there arent that many people denominating on mainnet yet. 1. If I would hack MintPal and get this amount of DRK I would never sell it for BTC.... Or I would sell some to create panic to buy even more AND 2. We need to do better marketing anyway |
|
|
|
Hey,
I'm trying to setup a MN for Mac and am not sure where to put the .conf file
Any idea?
/Users/<yourusername>/Library/Application Support/DarkCoin |
|
|
|
sooo luckily i moved most of my funds from the old wallet, but i forgot to update a mining address.... so i have some coins in my old wallet (which is encrypted).
If i switch out the new wallet.dat with the old wallet.dat everything works great until i attempt to send coins. Here the client freezes.
I can't dump private key - i get error
I am using the Mac qt v0.10.13.15-beta
any idea how to rescue these coins?
What error are you getting when dumping the private key for the addresses? Is the wallet unlocked? error is (code -4) Maybe that was due to a locked wallet. Now when I am trying again making sure to unlock first. I get rainbow wheel of death. (Same crash that happens when I try to send). Maybe I'll try on windows. EDIT: oh snap ! client came back to life all is well in DrkLand.. Might I suggest that the loading logo/page (which looks great by the way) should not be always on top? this is rather annoying (I cant multitask)! if you are using encrypted wallet and you are getting something like  Private key for address <youraddresshere> is not known (code -4)while trying to dump private key then make sure you unlocked your wallet before by this command walletpassphrase <yourwalletpassphrasehere> 60you can't dump private keys on locked wallet |
|
|
|
Idiots...
Seriously. What are you trying to say? Kristov did a code review. He highlighted some issues, he pointed them out and Evan fixed the vast majority. This guy found something Kristov missed. He tried to exploit it, but the whole thing can be seen on the network. Within a relatively short period of time, he was spotted. 24hrs later a patch is applied around the network. He has identified one exploit. It was closed. It won't be exploited again. It could also highlight other areas that are related that could be worked on. The guy said he was going to donate his winnings. The project is stronger than it was two days ago. This is a small win. +1 and I would say there is one more pro code reviewer now - the "hacker" - and that's really nice because the more attention of such guys we get earlier the faster we get stronger and the more stable/resistant DRK code/architecture will be And yes, he got his 200+ DRK "bounty" for his work which is fine for me |
|
|
|
btw, another way to sync is to get bootstrap.dat and let wallet sync from it (place it in the same folder where wallet.dat is, on mac it's /Users/<your username>/Library/Application Support/Coin2.1/ ). http://c2chain.info/bootstrap.dat (183k+ blocks) That's not the "clean" bootstrap as it should be, that's just renamed blk0001.dat but it should work almost the same (will require few "reorganize" actions but this will happen automagically and will not require any action from you, so it should work fine afaik). It will take a while and gui will not show up until sync is done so it could look like nothing is happening (or even Coin2.1-Qt will be shown as "Not Responding" in Activity Monitor) but just let it run. You might also need to delete blk* files before trying to use this method but I'm not sure about this. In case you are on mac you can make sure that process is running fine by tailing debug.log in Terminal like this: tail /Users/<your username>/Library/Application Support/Coin2.1/debug.log | grep height or tail -f /Users/<your username>/Library/Application Support/Coin2.1/debug.log | grep height "-f" should give you a lot of output (hit "ctrl + C" to stop tailing - I'm sure you don't want these 183k+ lines to be output one by one in next hour or so ) Interesting part there is "height" which is current block being processed. I tested this by myself and on my mac I was able to sync from scratch in about one hour and ten minutes. PS. might be a good idea to place link to bootstrap.dat (or link to this message) in OP Thanks for this!! Just tried this method and it worked a treat! Like you said, took just over an hour to sync. Thanks. You are welcome |
|
|
|
btw, another way to sync is to get bootstrap.dat and let wallet sync from it (place it in the same folder where wallet.dat is, on mac it's /Users/<your username>/Library/Application Support/Coin2.1/ ). http://c2chain.info/bootstrap.dat (183k+ blocks) That's not the "clean" bootstrap as it should be, that's just renamed blk0001.dat but it should work almost the same (will require few "reorganize" actions but this will happen automagically and will not require any action from you, so it should work fine afaik). It will take a while and gui will not show up until sync is done so it could look like nothing is happening (or even Coin2.1-Qt will be shown as "Not Responding" in Activity Monitor) but just let it run. You might also need to delete blk* files before trying to use this method but I'm not sure about this. In case you are on mac you can make sure that process is running fine by tailing debug.log in Terminal like this: tail /Users/<your username>/Library/Application Support/Coin2.1/debug.log | grep height or tail -f /Users/<your username>/Library/Application Support/Coin2.1/debug.log | grep height "-f" should give you a lot of output (hit "ctrl + C" to stop tailing - I'm sure you don't want these 183k+ lines to be output one by one in next hour or so ) Interesting part there is "height" which is current block being processed. I tested this by myself and on my mac I was able to sync from scratch in about one hour and ten minutes. PS. might be a good idea to place link to bootstrap.dat (or link to this message) in OP |
|
|
|
Thanks for your help!
I tried that and deleted the blk files again and this time its stuck on 3.83%.
Zyronx, Can you see if any of the devs can assist oldandgrey UdjinM6 has been good at helping with these issues. Maybe pm him. Well, I tried to recreate the issue starting to sync from scratch and I can't - synced to 10% in 5 minutes... EDIT: hmmm... that's interesting... stucked at 16.36% EDIT2: according to log wallet is getting timeouts while trying to connect to recent known nodes - looks like most people stake for some time and then turn wallets off so there are many offline wallets which was online not so long time ago. Try to add "connect=107.170.168.162" in your Coin2.1.conf (should be in /Users/<your username>/Library/Application Support/Coin2.1 and if it's not - create one). That will tell wallet to connect only to that host which is c2chain.info and I hope it will do the trick for you. EDIT3: btw, once you are done syncing it's better to replace "connect=107.170.168.162" by "addnode=107.170.168.162" so wallet will always try to connect to c2chain.info and will try to discover other nodes too. |
|
|
|
"89.25% of total blocks payed correctly 20%" 0.75% left till enforcement! "90.15% blocks payed, 89.23% of total blocks payed correctly" it's wrong, should say "90.15% blocks payed, 89.23% of payed blocks payed correctly" or 87.41% of total blocks respectively |
|
|
|
Well at least this shit is interesting so as I lose all my money I am entertained.
One of the most expensive entertainment in my life too |
|
|
|
Hi, sorry if this is a dumb question, but about the possibilities of X11 FPGA... How come such a large % of blocks are found by miners not using a known pool? (from chainz.cryptoid.info)  Also how come the % has been increasing steadily...  ...when major pools % like SuchPool has been decreasing?  Why is it unreasonable to assume the unknown % is FPGA or why is it so high? Wouldn't this explain the constant dumping? Is there any info from blockchain analysis about where these coins are going? Or did I miss something obvious.... cheers try this one http://drk.poolhash.org/poolhash.html |
|
|
|
BTW, it's so irritating! I earned 0.01 btc not long ago, and I opened my bitcoin wallet (so I can send it to mintpal and buy dark, LOL) and it's been updating from 6 weeks behind for the past hour and a half. I have a quick connection, but it always takes forever to update the blockchain! And I can't have it running on my windows box because it just hogs up resources all the time. I don't see how anyone can use bitcoin, it's a slug and the depth to which it sucks just cant' be expressed! Over an hour and a half and I'm at 4 weeks behind! Geepers!
Just use MultiBit client  What's that? I'm serious when I say I never leave the drk thread, LOL. I hate it out there, don't even want to know what's going on, thank you, LOL. I rely on all of you to keep me up to date on important things  (oh, except I usually go vote on coins101's polls, LOL) Well, it's been here for quite a while already https://multibit.org/https://github.com/jim618/multibitIt's also mentioned here https://darkcointalk.org/threads/call-for-devs-software-adoption.2195/And DOGE has MultiDoge, btw - was one of the reasons of previous DOGE rise (first scrypt coin to have light wallet - wider adoption) I wish we had MultiDark someday... EDIT: Darkcoin has perfect infrastructure (MNs) to keep full blockchain to let users use light clients mostly |
|
|
|
BTW, it's so irritating! I earned 0.01 btc not long ago, and I opened my bitcoin wallet (so I can send it to mintpal and buy dark, LOL) and it's been updating from 6 weeks behind for the past hour and a half. I have a quick connection, but it always takes forever to update the blockchain! And I can't have it running on my windows box because it just hogs up resources all the time. I don't see how anyone can use bitcoin, it's a slug and the depth to which it sucks just cant' be expressed! Over an hour and a half and I'm at 4 weeks behind! Geepers!
Just use MultiBit client |
|
|
|
Isn't the price supposed to be going up with open source upcoming? Not that I care, but.. you know..
Markets rarely do what is expected of them. look doge, not development, only dog meme and... 325% profit last 30 days, investor speculators are not interested in DRK yetfixed for you |
|
|
|
Also, for some reason, the instance I did not reboot, I was able to update bash with sudo apt-get install bash and I now have the latest, but the instance I rebooted won't update. It says I already have the latest, even after sudo apt-get updates. So... maybe they pulled the repository (probably working on it still) I guess we'll all just have to keep checking to be sure we get the latest updates!?!
do update and then upgrade. Finally check it with bash --version. If it says 4.3+ you're golden. sudo apt-get update
sudo apt-get upgrade
bash --version
Do I have to stop my masternode befored update/upgrade??? No, it's safe to do it live |
|
|
|
Guys, can you please stop quoting trolls? The are on my ignore list and you make them reveal for me again... Thanks |
|
|
|
|
Show Posts
