please tell me what blocks you need to register to the dash.conf
I have a problem with the wallet writes the source blocks not found
and a file called dash.conf or darkcoin.conf
thank you
Can you please send me debug.log file from DashCore folder? UdjinM6@dash.org |
|
|
|
Because importing watch-only address doesn't suddenly make you able to spend these funds, you need private keys. how to get private keys my old computer i don't know You need to get wallet.dat from your old computer or find any backup if you made one - wallet.dat holds all your private keys. Anyone who have it can control funds, if you don't have it - you can't. It should be somewhere like C:\Program files\Darkcoin folder. |
|
|
|
Because importing watch-only address doesn't suddenly make you able to spend these funds, you need private keys. |
|
|
|
Bitcoin commentator Willy Woo has called out Roger Ver over his use of Dash to get around Bitcoin’s transaction fees. Ver, a proponent of increasing block sizes considerably in order to increase capacity, yesterday said he had resorted to using altcoin Dash to move his money in order to avoid paying a high Bitcoin transaction fee to process his payment in a short enough time. Responding to Ver’s announcement, Woo was critical. “Ver saves a few bucks on fees using [Dash], loses $30k to volatility. This is why [Bitcoin’s] network effects of liquidity & volatility wins,” he stated. He still loves bitcoin, so I guess he moved them just for an experiment i.e. buy, withdraw, move, deposit, sell. Doubt he lost much. Also, he tweeted that he moved funds "yesterday" and "yesterday" was the day of 30%+ price rise. He probably even earned some but trolls just can't get their math done right.  |
|
|
|
Security alert!There was someone advertising https://github.com/DashNode/NodeMiner/ as an easy way to setup nomp pool node on your Windows machine using Java and earn Dash. We checked the binaries and the only job it was doing is downloading some suspicious executable which mimics as an audio driver and placing it in Startup folder (see full path on screenshot below).  http://imgur.com/a/oZOwGWe think it's a malicious software which can try to steal you funds, so we reported the user to github. We received confirmation that user is under investigation by github staffs now: "Morgan (GitHub Support)" < support@github.com> Re: Report abuse: DashNode Hi there, Thanks for taking the time to let us know. We'll investigate the user. Cheers, Morgan His account was disabled/deleted from github few hours ago. We also dropped all related threads on dash.org/forum and /r/dashpay. User who posted this link on dash.org was banned. If you already downloaded this, please run complete antivirus scan and consider this computer compromised from now. We don't know if it has keyloger inside or what else this exe can do (copy itself, block files etc) but expect the worst case, so do not enter wallet password on this machine until you are pretty sure it's clean! Restore wallet.dat on another clean machine if you need to move funds urgently.
|
|
|
|
Hi there! what's wrong with Electrum-DASH? I can't send my DASH's to other wallets. Even on the oficial site https://electrum-dash.org/ there is not more listed, or a installer (p.d. OS Windows) It has been disabled. DASH wallet has been updated on the website! You should take all DASH off exchanges. As it increases in value, more risk to hackers. You should get a masternode as soon as you get the wallet set up! Sooner the better. I think this time next year a Node will cost over 100k USD! Thanks, but my DASH are in my Electrum wallet, and I wanto to transfer to another adress but I can't, program "say" that I need to up-grade for a newest version but oficial site https://electrum-dash.org/ there is not more listed, or a installer!  Someone now how I can get my DASH's? Same situation here.I think you have to import the private keys in debug command window importprivkey or something like that :/ Thanks, no idea dude! Don't find any installer for electrum DASH wallet, obviously you can't import your wallet backup to a Electrum Bitcoin wallet so.... Guys are working hard on getting stable version out. Windows version is expected to be out in next 24h. Meanwhile you can export private keys from electrum-dash into csv file and import them one by one into Dash Core via "importprivkey" command (you don't have to import every single key btw, just import the ones which are holding some funds). |
|
|
|
BitBar for Dash (if on MAC - u have to get this ; )Tx to @cofresi + UdjinM6 special edition - Install: https://getbitbar.com- Then: bitbar://openPlugin?title=Dash%20Tickers:%20Coinmarketcap%20and%20Poloniex&src=https://raw.githubusercontent.com/UdjinM6/bitbar-plugins/Dash/Dash/dash-btc-poloniex-coinmarketcap.30s.sh http://bitbar.dash.do bump + i extra link How do you guys get this running? I have bitbar installed, but it wont allow me to load shell-scripts at all. Either trying to open the .sh file locally from my computer or with the command above. Is there some settings or option that I have to tweak to get this to load? It looks like a cool script, seems like a bunch of info and lots of fun! Go to http://bitbar.dash.do/ and click the button, Install, done You can check if file is actually in plugin folder by going to Preferences -> Open Plugin Folder or you can download the file directly https://raw.githubusercontent.com/UdjinM6/bitbar-plugins/Dash/Dash/dash-btc-poloniex-coinmarketcap.30s.sh and move it there |
|
|
|
BitBar for Dash (if on MAC - u have to get this ; )Tx to @cofresi + UdjinM6 special edition - Install: https://getbitbar.com- Then: bitbar://openPlugin?title=Dash%20Tickers:%20Coinmarketcap%20and%20Poloniex&src=https://raw.githubusercontent.com/UdjinM6/bitbar-plugins/Dash/Dash/dash-btc-poloniex-coinmarketcap.30s.sh This is awesome. UdjinM6 made it super easy to modify to display USD by default... just change this in the .sh file: printf "%.*f | dropdown=false image=%s\n" 4 $(echo "$infoPoloniex" | grep -A1 last | tail -1) "$iconBase64" # printf "$%.*f | dropdown=false image=%s\n" 2 $(echo "$infoCoinmarketcap" | grep -A1 price_usd | tail -1) "$iconBase64" to # printf "%.*f | dropdown=false image=%s\n" 4 $(echo "$infoPoloniex" | grep -A1 last | tail -1) "$iconBase64" printf "$%.*f | dropdown=false image=%s\n" 2 $(echo "$infoCoinmarketcap" | grep -A1 price_usd | tail -1) "$iconBase64" and you get...  And if you leave them both enabled, they will cycle trough after few seconds |
|
|
|
It is strongly recommended that everybody update to the latest version 12.0.2 as well as the latest sentinel. Moocowmoo's Dashman makes this very quick and easy. The sooner most of the network is on 12.0.2 the earlier enforcement can be reenabled. It will be nice to get InstantSend back and not have to worry about the off-chance of a greedy miner not paying one of my nodes. https://github.com/moocowmoo/dashman12. 1.2  |
|
|
|
But it's not win-win-win when somebody can propose something that exclusively enriches a certain few people, and those certain few people have enough power to make that proposal effective. This is an effective kleptocracy, and I don't think that anybody really wants to be associated with that.
I won't comment on the whole post, but you are mistaken about the meaning of the 10% threshold for approving proposals. It is not realistic for Evan & the rest of the Core team to past a self-serving proposal against the wishes of the rest of the community since the formula for approval is YES VOTES - NO VOTES > 10%. In other words, so long as Evan and Core own less than 54.9% of the MNs (since 54.9% - 45.1% = 9.8%) they can't do anything like you describe above. And no, there is zero evidence that they own even 1000MNs much less than the approx 2400 nodes you would need for that attack. The current system may indeed have yet undiscovered flaws, but a small group of people with a lot of MNs overriding the wishes of the entire community is not one of them. Well, that's certainly much better, but the official Dash wiki says "If that proposal is approved by at least 10% of the masternode network, then at the end of the month a series of "superblocks" will be created. At that time, the block rewards that were not paid out (10% of each block) will be used to fund approved proposals. The network thus funds itself by reserving 10% of the block reward for budget projects." https://dashpay.atlassian.net/wiki/pages/viewpage.action?pageId=84672534Assuming that you're right and the wiki is wrong, well, that certainly alleviates most of my concern, although I have to wonder what threshold have to vote for it to be approved. I.e, what constitutes a quorum of voters -- how many masternodes have to participate in the voting, for a valid vote to be held? And are votes carried over to the next month if they aren't decided? For that matter, there should be 3 options for voters -- YES, NO, and ABSTAIN -- where ABSTAIN voluntarily removes that voter from being counted YES or NO, and thereby reduces the number of votes necessary for a quorum (however defined). In this way, voters can express either a "don't care" opinion (thus voluntarily giving others the power to choose) or a "recusing myself from a conflict of interest" vote. Yep, it probably can be worded out in a better way, so the way it works is actually "at least 10% more of masternodes have to vote yes than no" or smth like that. And yes, ABSTAIN option is implemented in 12.1 https://github.com/dashpay/dash/blob/master/src/governance-vote.h#L22 |
|
|
|
start-missing is a helper command which you should use when your MNs are not in the list at all
If your MNs are already in the list start-missing is NOT going to work for you. If some of your MNs are not in "enabled" state you can use start-disabled to start them all without affecting MNs in "enabled" state.
A bit cryptic to me. What List? If you refer to the MN list in the net itself yes they should be there. I use moocowmoos service. It was telling me to sent the restart after he upgraded to 12.1 at sunday last week. The whole network.conf / start thing newer worked for me. That's why I always went with client.config. So you are telling me I should have used start-disabled? And Icy.. my network / client where I tried to send the start is behind an IPv6 address. Don't think that matters. As I understand it only the remoted MN has to be hosted with a static IPv4. But someone please correct me if I am wrong. It would be a bit troublesome to find an IPv4 net just for starting this. I agree a bit with you here thought that I think IPv6 is important and shouldn't be ignored for too long. The change from IPv4 to IPv6 is running since years and the IPv4 addresses are running out fast. There is no good reason to stay back. It's no burning major point thought. I'm not sure what you mean by network.conf and client.config... probably masternode.conf and dash.conf? Configuring remote masternodes in local dash.conf is no longer supported, you should use local masternode.conf from now. Local dash.conf config is only used for Hot masternodes which is not recommended for mainnet and should only be used on testnet if at all. If you have many masternodes and they are listed in masternode list already but not in enabled state then, yes, you should use start-disabled for them. You can also use start-alias to start each one individually or start-all if you want to start them all regardless of their state. |
|
|
|
Can anyone tell me what is wrong with my MasterNode Dash-Wallet when start-missing simple does not work? No matter what I tried a week ago it always said 0 of 0 successfull started and the masternode status said not started. I use the dash client zip file for windows (not the installer) copied all the content in one single costum named folder and I worked with the client.config start method before. ( For some reason they blocked that start method now. :/) While some got double and tripple the usual pay outs I lost over a week payout by starting them with start-alias Not complaining I am glad I could start it at the end but I just want to know the issue for the next time so I can fix that. If the Dash value rises a payment drop out can become a significant lose in the future. start-missing is a helper command which you should use when your MNs are not in the list at all e.g. you have 10 MNs and you just started remote nodes for few more MNs but haven't issued start yet - new MNs will be in "missing" state and you can easily start them all using start-missing without affecting MNs in "enabled" state. If your MNs are already in the list start-missing is NOT going to work for you. If some of your MNs are not in "enabled" state you can use start-disabled to start them all without affecting MNs in "enabled" state. Make sure to fully sync and verify that wallet recognizes active MNs as "enabled", or otherwise they are going to be restarted too. |
|
|
|
I hope we are not introducing a fork possibility in the future with running
two versions on the same protocol, specifically regarding masternodes.
I remember we had some problems in the past when the masternode network
got largely divided over two different versions on the same protocol and at
some point accidentally forked ?
I don't think they would push it just like that. There wasn't any major changes. https://github.com/dashpay/dash/releases/tag/v0.12.1.1It's mostly for QT users. Yes, 12.1.1 should be fully compatible with 12.1.0 and no, sync issues were not Qt-only, it's a common issue in 12.1.0 which wasn't discovered in testnet due to relatively small number of masternodes there (~100). 12.1.1 also manages so called service connections in a better way (the reason we missed this one is basically the same). With that being said, update is recommended for everyone |
|
|
|
dash-cli masternodelist status | awk '{print $2}' | grep -v ^$ | sed -e 's/,//' | sort | uniq -c
3190 "ENABLED"
309 "NEW_START_REQUIRED"
4 "PRE_ENABLED"
798 "UPDATE_REQUIRED"
60 "WATCHDOG_EXPIRED"A friendly reminder to masternoders: NEW_START_REQUIRED - make sure you issued start-<mode> command from local wallet after you upgraded your remote masternode, you are NOT getting rewards otherwise. WATCHDOG_EXPIRED - make sure you have sentinel installed correctly, you will stop getting rewards after spork14 will be on. UPDATE_REQUIRED - spork10 is on and you are still running an outdated version, so you are NOT getting rewards now. Pls upgrade. |
|
|
|
|
There are few things I think I have to clarify to get everyone understand which sporks are important for payments and stability, what incentives are there, why sporks are enabled in this specific order and at some specific time, and "why don't we enable every spork right now?".
So, there is an incentive...
1) to be in first ~1/3 of updated masternodes because they do not lose their place in queue;
2) to update later (i.e. to be in second 1/3) because it's clear that significant portion of mns is already updated and spork10 will be enabled soon (technically speaking, we don't need majority here and could turn spork10 on as soon as 1/3 was updated but clearly it's much better to have more support and fix issues if any at a smaller scale, so we still give mn owners some time to sort things out, get last payment keeping older mn etc. - spork10 was enabled only after ~2/3 of mns were updated);
3) to update in the last 1/3 because at this time spork10 is enabled and you'll get no more payments running old version.
Imo all incentives and times are aligned well enough here.
Now, when most of mns are finally running new version, mn winners list should start to stabilize. That's the thing we use to figure out parts of coinbase txes and we _need_ it to be consistent before enabling spork8 (which most people are referring as simply "enforcement") because otherwise different nodes could arrive at different voting results and will simply reject "wrong" blocks (and ban "wrong" peers), meaning that network can split in 2+ forks which would mean that:
- we'll have to disable it again to resolve forks i.e. it's going to be the same sitataion as it's now (payments wise);
- masternodes on the "wrong" fork are going to expire if fork will last for too long (3h+) i.e. they are going to lose their place in payment queue on the "right" chain and mn owners will have to spend more time on maintaining them and bringing them back online;
- miners on the wrong fork will waste their money for no reward while they did nothing wrong, they just mined the block they thought should be valid as usual.
Think of an upgrade as of a stress event for the network - for stabilization to happen we have to give it some time to "calm down". Miners did their job amazingly fast this time (kudos to them), mn owners seems to be not so good at updates but, hey, it's only a week since the official release and mn owners are less techy in general I guess.
To sum up, I think that network is doing great so far and the least thing we need is to rush now because of the reason that some mn payments are "stolen" by some miners.
|
|
|
|
I've been trying to find whether there are any special instructions for upgrading MNs hosted remotely on moocowmoo's masternode.me service. So far I haven't found anything, but it seems at least one locally-upgraded wallet (Dash Core version v0.12.1.0 (64-bit)) is running as dashd v0.12.00.58 according to its stats page on mastercode.me
The usual fix for that sort of thing is a "masternode start" command (I think) but it reports:
{
"overall": "Successfully started 0 masternodes, failed to start 0, total 0",
"detail": {
}
}
Suggestions welcome - thanks!
Starting _remote_ masternode using local dash.conf (masternodeaddr option and "masternode start" command) is deprecated now. You should use masternode.conf and "masternode start-alias <alias>" command instead. "masternode start" works for starting _local_ masternode only now which is NOT recommended on mainnet. |
|
|
|
I can not get past the first step on my Mac OSX. I have deleted ALL the .dat files except wallet.dat, so I have the following files in: /Users/user1/Library/Application Support/Dashcore
folder: backups
folder: blocks
folder: chainstate
folder: database
file: dash.conf
file: dashd
file: masternode.conf
file: wallet.dat
I start the new 12.1 and I always get: "Failed to load masternode cache from mncache.dat"
I have tried to follow both set of instructions but can't get past this error
Are you using Dash-Qt? Was there a dialog asking for the folder at first 12.1 qt start? If not, try starting it with -choosedatadir option (open Terminal, type "/Applications/Dash-Qt.app/Contents/MacOS/Dash-Qt -choosedatadir", hit Enter) and make sure it's pointing to the new "DashCore" folder, not to the old one ("Dash"). |
|
|
|
|
Show Posts
