..A server I rented didn't have crontab installed so this isn't always a no brainer...
If you don't have crontab installed, try this: apt-get update
apt-get upgrade
apt-get install cron Then you need to reboot for the cron process to take effect. Add your crontab with crontab -e or sudo crontab -e Then activate your crontab. I think sudo service cron restart Then to stop you need to edit the crontab and then restart the cron service. Seems more complicated to me. |
|
|
|
How to start dashd automatically again after it crashed. run: add line: */1 * * * * /home/dashuser/mn_watch.sh >/dev/null 2>&1 use any editor you like and save this as "mn_watch.sh" file in user "dashuser" home directory: #!/bin/bash
if [ -z `pidof dashd` ]; then
/home/dashuser/dashd
fi
add executable flag: PS. Use appropriate username, not "dashuser" from my example  I also assumed that dashd is located in your user home directory, change path if needed. PPS. not tested but should work  EDIT: ooops, tested and fixed  This seems like the perfect solution to my all of my MN problems, But I am 5 and dont understand this, tryed but did not work, Can someone make a video for 5y olds  Putting a 10 dash bounty on this  .. if anyone is interested  (send me a priv message if you want to collect the bounty, I rarely scan every page here) No offense, but that's as easy as it gets. The only substitute is using whatever text editor you have on your instance to actually create the script file (vi, nano, joe, etc). Actually, crontabs may require a restart or server reboot. Might also need to run with sudo crontab -e if running server as root. A server I rented didn't have crontab installed so this isn't always a no brainer. Icebucket, try this: Copy code below and paste into mn_watch.sh file. Type nano mn_watch.sh, paste with right click, and control x, y, enter to save. Change dashuser to your user name. #!/bin/bash
#run with: screen -dm /mn_watch.sh
#stop with: screen -ls to find number and screen -X -S 11111 kill
while true; do
if [ -z `pidof dashd` ]; then
echo Dashd is not running trying to start
/home/dashuser/dashd
sleep 600
else
echo Dashd is Running
sleep 600
fi
done
type: chmod +x mn_watch.sh You can test it by running: ./mn_watch.sh It will stop working as soon as you logout though, so we need to install screen to have it run in the background. Run this to install screen. (Assuming you are running Ubuntu.) apt-get install screen to start with screen type: screen -dm /mn_watch.sh This will run forever, so if you want it to stop type screen -ls and get the number replace that with the 11111 below. screen -X -S 11111 kill I set this up to run every 10 minutes, just because it will be a pain if you are updating and every minute it tries to restart dashd. If you want to run with UdjinM6's suggestion with the crontab start with a */10 for 10 minutes so you don't have to stop the crontab everytime you update your node. |
|
|
|
Nice to see the numbers match here :
masternodes =2524
Onward and forward to 3000 active masternodes !
whats happened to the other 500 masternodes, they can't all be waiting to buy back in, why so slow ?! BUY-BACK IN?? Who said they sold :-P Thank you to the Bitcoin doubters. I picked up another node cheap. I am sure we will be over 3000 in no time once the good news of .49 is shown to all. Only using 220MB of ram on this release. |
|
|
|
now that there is no donation address, can we not just import the dumped priv key from the cold wallet payment address to another unsafe hot wallet, I tried this and imported the priv key into the new wallet, and seems to work fine.
If you send within the hot wallet from the imported address to another address within the same wallet, this will make the payment balance of the 1k cold wallet disappear but will keep the 1k bounty intact.
So, effectively the 2 wallets are twinned by 1 mutually exclusive address.
wondering is this a 100% secure way of receiving masternode payments to an unsafe hot wallet, as the priv key for the 1k is still safe in the cold wallet that never has to be started up, am I missing anything, anyone ?
This is intriguing. So let me lay this out graphically so I can understand. Original MN Wallet New Wallet 1000 coins in key A Dump private key A Import private key A Send funds from key A to key B Key A has 0 coins Key B has 1000 coins Rewards deposit in Key A Rewards deposit in key A Edit: Yep, you are almost there, but the private key must be the change payment address and not the 1k address, they are different. And when you import the key to the new wallet, if it had 1 dash before, it will now add 1 dash to the hot wallet and remain in the cold wallet at the same time (twinned, so to speak, until moved to another address) And my question still stands, is there any security threat for the cold wallet by sharing only one private key between 2 wallets to use as a donation address,
anyone, please ??Hmmm. A little confused, but I do want to know how you can do it. Could you explain with my diagram above where the change payment and 1k address start and end up? |
|
|
|
now that there is no donation address, can we not just import the dumped priv key from the cold wallet payment address to another unsafe hot wallet, I tried this and imported the priv key into the new wallet, and seems to work fine.
If you send within the hot wallet from the imported address to another address within the same wallet, this will make the payment balance of the 1k cold wallet disappear but will keep the 1k bounty intact.
So, effectively the 2 wallets are twinned by 1 mutually exclusive address.
wondering is this a 100% secure way of receiving masternode payments to an unsafe hot wallet, as the priv key for the 1k is still safe in the cold wallet that never has to be started up, am I missing anything, anyone ?
This is intriguing. So let me lay this out graphically so I can understand. Original MN Wallet New Wallet 1000 coins in key A Dump private key A Import private key A Send funds from key A to key B Key A has 0 coins Key B has 1000 coins Rewards deposit in Key A Rewards deposit in key A Am I close on this? I think the original wallet would then be your hot wallet with spendable rewards. The new wallet would have the 1000 coins and would stay cold. Do both wallets need the same password? Seems like something that could pose a problem. |
|
|
|
Thanks Tungfa. New show for me. Favorite quotes(paraphrased): If Bitcoin can't survive XT maybe something better will come along. (I know, I know...) Miners don't want to fork because it can open up double spends or orphan blocks. (spork anyone?) It would be so cool to have a little Dash icon with "The XT Alternative" on this show. FYI, you can watch it at 1.5X speed if you enable the html5 player and click on the gear icon in the player. Enable html5 player here: www.youtube.com/html5 |
|
|
|
....Regarding your second comment. For standard payments, the miners confirm the blocks based on the transaction queue. Instantx adds 5 confirms via masternodes and it would fail back to a standard payment if something happens. For mixing, this is done before a transaction is sent and if a problem happens it just keeps trying different masternodes until a mixing is complete.
I'm still not clear on InstantX in the event of a fork event. Say, one confirmation locks the transaction, but it happens during a fork, which ends up not being the longest chain. Which fork do the MNs follow? Being a high volume payment system, you could end up with thousands or millions of transactions on different forks? Its probably not much different to any fork event. Longest chain wins(or correct spork). The transaction would wait in queue until the next block on the longest chain and default to a standard 1x confirmation on next block. |
|
|
|
One exists, one doesn't. Lightning is centralized by design. It's something like a centralized ledger that is capable of pushing out finalized transaction states to the real ledger at anytime. Drawbacks: - It screws with the UTXO set, because you can't tell where the money actually is in the system - It's 100% centralized and could be prone to regulation. I've seen them talk about this and they say if the centralized node starts to whitelist addresses or something to that effect, they'll just start another one. - It's incredibly complicated and will be prone to errors for the first year or two - It's not really that useful if you're paying different people with every transaction you do. It's more useful for subscriptions or companies that are paying each other all of the time. - There's probably more, but I lost interest The masternode network is decentralized by design and can pretty much do anything a centralized system can do but in a completely decentralized and stable way, including fixing all of these issues with scalability they're having in a much more elegant way. This is very informative thanks. Mike Hearn just published an excellent OpEd in arstechnica, which in part discusses the Lightning Network: http://arstechnica.com/business/2015/08/op-ed-why-is-bitcoin-forking/Thanks....I found a link to another article on it I hadn't seen before. https://medium.com/@octskyward/the-capacity-cliff-586d1bf7715eActually, the last link is essential reading. It raised a question or two on some issues I hadn't considered before. The first one relates to back-ups. Lightning network hubs: what's the fail over plan? Does data just get lost? What happens to MNs when they are holding a transaction and one or more gets taken down? Nothing, I guess. The MNs just select another group to complete a transaction, because users funds are still in their control during mixing. Isn't the lighting network debt based like a credit card. It uses an internal network to transfer funds and settles with bitcoin right? So there should be a risk if the Bitcoin payment gets rejected(double spend or something). The lightning network would have to charge a fee(x%) for the possibility of a lost transaction, just like a credit card. So why is this any better than using a credit card? You get the fees and still deal with a centralized agency. It wouldn't surprise me if visa or mastercard were behind lightening. With DASH you you get the speed and tiny transaction costs, plus decentralized, anonymous, credit based, etc.... Regarding your second comment. For standard payments, the miners confirm the blocks based on the transaction queue. Instantx adds 5 confirms via masternodes and it would fail back to a standard payment if something happens. For mixing, this is done before a transaction is sent and if a problem happens it just keeps trying different masternodes until a mixing is complete. |
|
|
|
Thanks Sub-Ether. Maybe there should be a check of used keys(n) during shutdown. It adds the keypool=n+1000 in the config file to generate more keys. If backups are done on startup and each mix uses 200 keys, this should always keep a valid backup(even up to 4 or 5 mix sessions). EDIT: I added keypool=2000 in my config and it didn't changed my wallet size. I had to run keypoolrefill to get the wallet to change size. Suggestion: Set keypool as needed to keep 1000 free addresses. On shutdown run keypoolrefill and backup wallet. Thats a good idea, have a counter for the number of keys used, and when the limit is near there could be a warning to backup your wallet - useful if doing a lot of mixing. We had a discussion about the keypool problem here: https://dashtalk.org/threads/darksend-to-seed-or-not-to-seed.4925/#post-54501Thanks Pille. It looks like the discussion in May wanted to incorporate a seed for mixing. Although, this could work it would be changing a lot of how the wallet works. Now that we have automatic backups, changing the keypool size and refilling keys should be a much simpler change. There was a term called reserve keys in earlier versions of Bitcoin, but sounds like that is no longer used. We basically, want 1000 reserve keys and keypoolrefiill to run before backups. We also need this for merchants with many transactions not just for mixing. |
|
|
|
One exists, one doesn't. LOL. Isn't the big problem that lightning depends on this coin that uses a monster 45GB blockchain(and that could grow 8x faster) that has no paid support or fair way to decide on any changes. |
|
|
|
when I type: cp /home/Desktop/dash-0.12.0/bin/dash-qt /home/Desktop/
it says: cp: cannot stat ‘/home/Desktop/dash-0.12.0/bin/dash-qt’: No such file or directory
Totally frustrating. I absolutely appreciate all the assistance though.
You might want to try this instead: cp ~/Desktop/dash-0.12.0/bin/dash-qt ~/Desktop/ The tilde replaces your home folder with the current user's home folder ;-) Alright. When I type what you suggest.... I get no errors. wouldn't typing: ./dash-qt --reindex be what follows next? If it does... I get the: No such file or directory error still. So close. Type: cd ~/ cd Desktop ./dash-qt --reindex YES !! Each command worked. The core wallet launched. It says I have zero dash.... but also says that it is 1 year and 16 weeks behind. So thankful for the help. Going to see where I end up after the sync. Grapevine, it looks like SirHikmat figured out that the file type is reported as a shared library and it should be an executable. https://dashtalk.org/threads/v12-release.5888/page-26#post-64304Hopefully, the next update will fix this and you will just be able to double click on the dash-qt. |
|
|
|
Can't thank you enough. Enormous [digital] high five to Solarminer... and everyone else that lent a hand. fixed it for you - and that is actually called a 'wi-five' :-P i friend of mine asked me where he can find the update button in his wallet. Good question... [/quote] Nice MB. Like it. About the update button, how about a check on startup and if you need to update it asks if you want to update? I would suggest an auto update option added for masternode owners. Something like adding auto-update=yes in the config file. Should be easy right? LOL. |
|
|
|
If I generate a new receive address on a wallet and send funds to it. Then load an old wallet, it still gets the transaction. Just the label of that transaction won't come through. If all the inputs/outputs of mixing go through the blockchain an old wallet version should still get the inputs. Is there something else that causes this to fail? Maybe the wallet can't allow a send and receive from the same wallet when it syncs old transactions? Can this be fixed?
Requiring a backup after mixing doesn't seem like a production level solution.
Backup wallets keep 1000 unused addresses. If your mixing used up those addresses, then a backup will not show any of the addresses generated afterwards, and with nearly 1000 coins, you probably have gone through many of those addresses Thanks TS. Ahh. Not so easy to fix that. Crowning, thanks for your input too. Any chance we can force a wallet backup after mixing? Or maybe just add a note near the darksend mixing rounds/amount option or a dialog ok box that warns you to backup your wallet after mixing? But you can increase the number of keys made with keypool in the config at wallet startup so using keypool=100000 for example. Satoshi said that each key uses 1k, so normally only 1 megabyte space used for default 1000, you could easily increase it to 100,000 keys and still only use 100 megabytes, I imagine loadup and wallet encryption may be a little slow. https://bitcointalk.org/index.php?topic=1414.0Thanks Sub-Ether. Maybe there should be a check of used keys(n) during shutdown. It adds the keypool=n+1000 in the config file to generate more keys. If backups are done on startup and each mix uses 200 keys, this should always keep a valid backup(even up to 4 or 5 mix sessions). EDIT: I added keypool=2000 in my config and it didn't changed my wallet size. I had to run keypoolrefill to get the wallet to change size. Suggestion: Set keypool as needed to keep 1000 free addresses. On shutdown run keypoolrefill and backup wallet. |
|
|
|
when I type: cp /home/Desktop/dash-0.12.0/bin/dash-qt /home/Desktop/
it says: cp: cannot stat ‘/home/Desktop/dash-0.12.0/bin/dash-qt’: No such file or directory
Totally frustrating. I absolutely appreciate all the assistance though.
You might want to try this instead: cp ~/Desktop/dash-0.12.0/bin/dash-qt ~/Desktop/ The tilde replaces your home folder with the current user's home folder ;-) Alright. When I type what you suggest.... I get no errors. wouldn't typing: ./dash-qt --reindex be what follows next? If it does... I get the: No such file or directory error still. So close. Type: cd ~/ cd Desktop ./dash-qt --reindex YES !! Each command worked. The core wallet launched. It says I have zero dash.... but also says that it is 1 year and 16 weeks behind. So thankful for the help. Going to see where I end up after the sync. Fantastic, your welcome. Wait until it syncs. Next time to start just type: ./dash-qt The list command is LS not IS, use lowercase though. This Linux 101 session is over, on to talk about Dash again. |
|
|
|
when I type: cp /home/Desktop/dash-0.12.0/bin/dash-qt /home/Desktop/ it says: cp: cannot stat ‘/home/Desktop/dash-0.12.0/bin/dash-qt’: No such file or directory Totally frustrating. I absolutely appreciate all the assistance though. You might want to try this instead: cp ~/Desktop/dash-0.12.0/bin/dash-qt ~/Desktop/ The tilde replaces your home folder with the current user's home folder ;-) Alright. When I type what you suggest.... I get no errors. wouldn't typing: ./dash-qt --reindex be what follows next? If it does... I get the: No such file or directory error still. [/quote] So close. Type: cd ~/ cd Desktop ./dash-qt --reindex |
|
|
|
Thanks TS. Ahh. Not so easy to fix that.
Crowning, thanks for your input too. Any chance we can force a wallet backup after mixing? Or maybe just add a note near the darksend mixing rounds/amount option or a dialog ok box that warns you to backup your wallet after mixing?
Crowning actually put in the function of a backup. If you look in your dash folder, you'll find a backup folder and that will have the last backup (I think at shutdown) of your wallet. It's really awesome to have that! Especially when you're air headed as I am, LOL. The backup is cool. I guess I was thinking it did a backup on startup, which now that I think about it wouldn't make sense. If it backs up at shutdown, then we are good. |
|
|
|
Anyone knows how to run the latest version of Dash on Ubuntu 14.04?
I get these files and can't open them. I'm kind of an ubuntu noob...
Just go to directory where qt is using terminal and execute it. For instance, i keep my dash-qt on a desktop. So open terminal and type cd /home/Desktop ./dash-qt --reindex Hi. I tried the above suggestion and I get the error: No such file or directory Any ideas what's causing that? Wild guess, you are using 32-binaries on a 64-bit system? if so, you need to have 32-libraries present to run them. I am definitely using 64-binaries on a 64-bit system. Thank you though. The files are in subfolders in your image. This will copy to your desktop first. (Desktop may or may not be capitalized) cp /home/Desktop/dash-0.12.0/bin/dash-qt /home/Desktop/ cd /home/Desktop ./dash-qt --reindex when I type: cp /home/Desktop/dash-0.12.0/bin/dash-qt /home/Desktop/ it says: cp: cannot stat ‘/home/Desktop/dash-0.12.0/bin/dash-qt’: No such file or directory Totally frustrating. I absolutely appreciate all the assistance though. Do you have the .tar.gz version of the file open in those windows? You need to uncompress the dash-qt. You should just be able to drag dash-qt in that window to an open space on your desktop. Then try the cd /home/Desktop and ./dash-qt --reindex Otherwise, from the command line. Try cd ~/ this should put you in /home/. Type ls. This will list the files. cd Desktop and ls and cd dash-0.12.0 one folder at a time until you see the dash-qt. Then type ./dash-qt |
|
|
|
Anyone knows how to run the latest version of Dash on Ubuntu 14.04?
I get these files and can't open them. I'm kind of an ubuntu noob...
Just go to directory where qt is using terminal and execute it. For instance, i keep my dash-qt on a desktop. So open terminal and type cd /home/Desktop ./dash-qt --reindex Hi. I tried the above suggestion and I get the error: No such file or directory Any ideas what's causing that? Wild guess, you are using 32-binaries on a 64-bit system? if so, you need to have 32-libraries present to run them. I am definitely using 64-binaries on a 64-bit system. Thank you though. The files are in subfolders in your image. This will copy to your desktop first. (Desktop may or may not be capitalized) cp /home/Desktop/dash-0.12.0/bin/dash-qt /home/Desktop/ cd /home/Desktop ./dash-qt --reindex |
|
|
|
If I generate a new receive address on a wallet and send funds to it. Then load an old wallet, it still gets the transaction. Just the label of that transaction won't come through. If all the inputs/outputs of mixing go through the blockchain an old wallet version should still get the inputs. Is there something else that causes this to fail? Maybe the wallet can't allow a send and receive from the same wallet when it syncs old transactions? Can this be fixed?
Requiring a backup after mixing doesn't seem like a production level solution.
Backup wallets keep 1000 unused addresses. If your mixing used up those addresses, then a backup will not show any of the addresses generated afterwards, and with nearly 1000 coins, you probably have gone through many of those addresses Thanks TS. Ahh. Not so easy to fix that. Crowning, thanks for your input too. Any chance we can force a wallet backup after mixing? Or maybe just add a note near the darksend mixing rounds/amount option or a dialog ok box that warns you to backup your wallet after mixing? |
|
|
|
I was using a backup computer with a wallet copied prior to darksend mixing a few coins. I updated to .45 and then .46. Now it won't find 2 transactions. None of the backups will show the transactions either. I tried all the repair tools(thank you Crowning) and it seems that something happened to the wallet and backups at the same time. I put a good wallet on this computer and the transactions show up.
The main computer I use with the latest wallet shows the transactions, transactions are in the block chain, and the old backups on that computer work as expected. The only difference is the main computer mixed the coins after the wallet was transferred to the backup computer.
Coincidence that wallet and backups failed at the same time? Or is there a problem with backups after mixing and we should be backing up wallets anytime we mix coins?
That last part... because mixing generates new addresses, your wallet may not contain them with where coins are currently parked so always backup post-mixing. If I generate a new receive address on a wallet and send funds to it. Then load an old wallet, it still gets the transaction. Just the label of that transaction won't come through. If all the inputs/outputs of mixing go through the blockchain an old wallet version should still get the inputs. Is there something else that causes this to fail? Maybe the wallet can't allow a send and receive from the same wallet when it syncs old transactions? Can this be fixed? Requiring a backup after mixing doesn't seem like a production level solution. |
|
|
|
|
Show Posts
