Yes, absolutely. The faster they get on the right chain the better, we are sending notifications to all exchanges. |
|
|
|
Please check the hash for the block 523412 - should be 000000000000e54f036576a10597e0e42cc22a5159ce572f999c33975e121d4d $ dash-cli getblockhash 523412
000000000000e54f036576a10597e0e42cc22a5159ce572f999c33975e121d4d |
|
|
|
Looks like we have some inconsistency in masternode winners right now. If you are running a MN and haven't yet update to 0.12.0.58 please do asap https://www.dash.org/downloads/Thank you. |
|
|
|
Each month we're gaining momentum, we started at about $13k/mo in October 2015 and currently next month we're going to have over $100k to spend. Let me get this straight. Dash development network budget is now over $1 Million per year at current valuations ??!! Incredible. That's a budget for everything network does, not only development. Fixed it for you  |
|
|
|
So that list is there forever, and it cannot be gotten rid of unless I download a whole new wallet copy?
If that is the case I will have to be careful of what I type in there for comments.
If you're very careful, and you don't care about keeping any bitcoin addresses that you currently have in your wallet, there is a way to remove all transactions from your wallet without re-downloading anything. - Create a backup of your wallet (let's call that backup_1).
- Be very careful to store backup_1 somewhere that you won't accidentally erase, lose, or overwrite it.
- Shut down Bitcoin Core
- Delete the wallet.dat that is in the bitcoin data directory
- Start Bitcoin Core back up
- Bitcoin Core will generate a new wallet.dat with new bitcoin addresses and no transactions at all
- In the "Receive" tab, choose "Request payment" to get a bitcoin address from this wallet.
- Save this bitcoin address somewhere that you won't lose it.
- Create a backup of your wallet (let's call that backup_2).
- Be very careful to store backup_2 somewhere that you won't accidentally erase, lose, or overwrite it.
- Shut down Bitcoin Core
- Replace the wallet.dat that is in the bitcoin data directory with a copy of backup_1
- Start Bitcoin Core back up
- You will see all your old addresses and transactions again.
- Create a new transaction sending your entire balance to the address that you created and saved earlier in these instructions (be sure to include a good transaction fee)
- Wait until the transaction has 1 confirmation
- Shut down Bitcoin Core
- Replace the wallet.dat that is in the bitcoin data directory with a copy of backup_2
- Start Bitcoin Core back up
- Wait for it to establish peers and synchronize
- You will have a wallet that has only 1 transaction received (and none sent) and your wallet will have the entire balance that you sent from backup_1 in that transaction.
Note: If you make a mistake and accidentally lose, delete, or overwrite your copy of backup_1 or backup_2 at the wrong time, it will be possible to PERMANENTLY lose access to ALL bitcoins that you had. Nobody will be able to help you recover those bitcoins. They will be gone forever. If you choose to follow these instructions, please be VERY CAREFUL. I disclaim all and any guarantees, undertakings and warranties, expressed or implied, and shall not be liable for any loss or damage whatsoever (including human or computer error, negligent or otherwise, or incidental or consequential loss or damage) arising out of or in connection with any use or reliance on the information or advice in this post. The user must accept sole responsibility associated with the use of the material in this post, irrespective of the purpose for which such use or results are applied.
Although every effort has been made to verify the accuracy of the information contained in this post, I disclaim all liability for any error, inaccuracy in, or omission from the information contained in this post or any loss or damage suffered by any person directly or indirectly through relying on this informationCould optimize few steps using a bit safer option "-wallet=somefile.dat" imo e.g. start with "-wallet=wallet_new.dat", create new address addr1, start as usual, send funds to addr1, start with "-wallet=wallet_new.dat" again and make sure funds arrived (and confirmed, optionally). Rename wallet.dat to wallet_old.dat, rename wallet_new.dat to wallet.dat, start as usual and confirm funds are there. |
|
|
|
yeah, that's a great way for spammers to collect emails EDIT: or to find targets to attack  |
|
|
|
Hi UDJ, stable at 4 connections now and in orange on the bar scale.
One other question that bothers me; transactions are coming in, staking is happening, coin count is going up but transactions are not appearing in the transaction screen or the summary screen. This has only happened since the 2.1.3.1 upgrade and last transaction is dated as 14th April 2016.
Any ideas as to what is going wrong?
Nope, no idea.. I've never seen anything like that. Try starting a new wallet and transferring all funds there maybe? |
|
|
|
I'm on 2.1.3.1
Ok then, do u have the blockexplorer listed as a node? not sure, current nodes in coin2.1.conf.txt - ... File name should be Coin2.1.conf Thanks UDJ & KA, file name changed but no effect once restarted, still only 3 active connections. Mined transactions still coming in but not logging in transaction history or control panel. Will keep mining but not working as well as it did last year. Peers come and go so probably many of them obsolete, that should fix itself if you keep wallet running for some time. c2chain has 8 connections right now for example: 96.127.136.18 185.122.59.70 106.186.24.50 72.208.71.8 209.222.15.235 118.122.228.166 83.5.196.4 110.200.71.51 |
|
|
|
I'm on 2.1.3.1
Ok then, do u have the blockexplorer listed as a node? not sure, current nodes in coin2.1.conf.txt - ... File name should be Coin2.1.conf |
|
|
|
BOTH Ethereum forks are worth more than Dash right now.
Pffff  Consider 72 million of coins premined in Ethereum (Classic) and look at that marketcap again. PS. btw I don't understand why coinmarketcap.com doesn't treat ICO coins as "** Significantly Premined" but, oh, well... |
|
|
|
http://www.coindesk.com/russia-ministry-finance-bitcoin-foreign-currency/"Can Russian citizens have a wallet and pay bitcoins in those countries where it is allowed? Why not? Therefore, we are formulating the law in such a way in order to allow
buying cryptocurrencies for foreign operations and allow Russian citizens sell bitcoins for profit reasons in foreign countries," he said. Moiseev also clarified that, at present, there is nothing preventing the use of bitcoin domestically, and that the intent isn’t to limit development of blockchain technology, but prevent
its use from threatening the ruble. Good news for our Russian friends .. at least i think it is  Interesting... Sounds like a good news but I can never trust in good will of my government Banks for example should fill a form with some personal information every time someone is exchanging more then $500. I wonder how they are going to apply this rule to crypto |
|
|
|
мне вообще вот интересно, это не тот ли человек который закупался 25к на эксмо, и о какой анонимности тут можно думать Тут можно думать об анонимности тех направлений, куда он эти средства будет отправлять после перемешивания К вопросу о скорости VS анонимность - да, тут, к сожалению, нужны какие-то разумные компромисы и не все простые решения подходят. При всех улучшениях все равно будет некоторая "тормознутость" в силу интеркактивного характера самого принципа перемешивания (необходимости наличия онлайн хотя бы некоторого количества пользователей, перемешивающих такие же номиналы). В 12.1 часть ограничений по скорости будет снята (не в ущерб анонимности) и одновременно будет добавлен ряд улучшений алгоритма в части анонимности (хочется верить, что тоже не в ущерб скорости - потестируем, посмотрим).  |
|
|
|
A small detail for Moocowmoo's awesome masternode.me pages if a user uses dash.conf instead of masternode.conf then this masternode start-missing "My wallet password"
results in: {
"overall" : "Successfully started 0 masternodes, failed to start 0, total 0",
"detail" : {
}
}
instead masternode start "My wallet password"
has to be used. Masternode successfully started
Also you might think of placeing a note somewhere that when your wallet password contains spaces you have to put it into those " ". Thank you for your masternode service. General notice: Please do not use dash.conf for local settings of your remote masternode, use masternode.conf even if you have 1 masternode only. Or at least make sure you have commented out masternode=1 in dash.conf (or changed it to masternode=0) when you done. Otherwise masternode will restart every time you start your local wallet i.e. it will drop to the end of the payment queue. |
|
|
|
Dear all, for convenience and on popular demand we have created a Dash PPA for Ubuntu - so installation on Ubuntu Linux is much easier now. Just do sudo add-apt-repository ppa:dash.org/dash
sudo apt-get update
sudo apt-get install dashd dash-qt and your Dash wallet is ready to use  Enjoy Even though I build from sources 99% of a time that's a nice option. Good job! |
|
|
|
наверно это действительно так.
поставил лимит 2000 - пошло дальше.
но больше 2000 - поставить не удается! - ограничение программы
но там указано что можно задать параметр из административной консоли, который перекроет настройки программы
где можно узнать про увеличение параметра суммы darksend?
Да, видимо, ограничение в 2000 DASH встроено специально, для защиты пользователей (от потери средств при миксинге) с небольшим опытом. Приглашаю вас на https://www.dash.org/forum/topic/Русский-russian.27/Один из разработчиков Dash - русскоязычный. Уж он то точно сможет дать исчерпывающие ответы по этому и остальным вопросам. было бы здорово получить ответ в этой теме на этом форуме alex-ru все правильно разъяснил про проценты, добавить нечего. Про ограничение тоже подтверждаю: да, 2000 - это искусственное ограничение для GUI клиента. Задать значение от 2 до 999999 можно через параметр "anonymizedashamount". Например, чтобы поставить 10000: "-anonymizedashamount=10000" в командной строке ярлыка либо добавить строчку "anonymizedashamount=10000" в файле dash.conf Перечень и описание всех параметров можно посмотреть, выбрав в меню кошелька Помощь -> Опции командной строки |
|
|
|
Looks like the network nodecount is closing in on 3900.
possibly 4000 by the end of the month ... #crysx It makes me think MN count is merely a time function, not much related to market activity. Of course, I can be wrong. Also it should increase at least 4 MNs a day not to fall behind the coin emission and to not decrease the MN percentage of whole supply. hmm i guess you are wrong ... coin emission is about 2k a day ... so 2 new mn a day ... or am i wrong? https://chainz.cryptoid.info/dash/#!overview Seems like somewhere in between. 3.88 * 770 = 2987.6  There is 576 block per day and give 5*0.93*0.93=4.3 Dash per block (two time reduction of 7%) ~2476 Dash per day Let me jump in Every single block at current difficulty is always at min reward so: 5*13/14*13/14*0.9 = ~3,88 DASH per block - not 7% but 13/14 to be exact - 10% goes to superblocks With DGW3 we are somewhere around 540~550 blocks per day in reality instead of 576 so: (540~550)*3.88 = 2095~2134 DASH per day EDIT: Ahh, right, if we calculate avg rate rather then actual "normal" coin production, we should count superblocks here too so to be as much precise as possible: 2095~2134 + (whatever amount of 5*13/14*13/14*576*30*.1 = ~7449 DASH is generated every 16616 blocks for approved budgets)/(number of days that took to generate these 16616 blocks i.e. 16616/(550~540) = 30.2~30.7) |
|
|
|
After watching polo lending market, the last two days, my interpretation is that these sells are mostly margin based, has someone else observed it, or even more insight?
That can be the cause. Since Dash can be margin-traded it is profitable in both directions for traders. And it seems to be easier to cause a long downtrend than a rise now. Especially when there is no demand. But also I don't get the purpose of the sell wall at 0.015. It's obvious price won't go there anytime soon. Then why doesn't he move it lower or sell into buy orders? All the support walls were either dumped into or mostly moved to 0.006 or pulled.I think you actually nailed it and that's exactly the purpose - to accumulate more Dash at lower, more comfortable (for buyer) prices. That sell wall is actually quite reassuring |
|
|
|
tok, multiple posts in a row can be considered to be spam by moderators here iirc |
|
|
|
FYI: Eric just fixed it |
|
|
|
How many GB is the dash blockchain? I fear that a 8GB sd card is not enough for a raspberry.
$ du -sh .dash/
1.9G .dash/ |
|
|
|
|
Show Posts
