Tku. New so sry but how do I open the console? The directions in docs just said "Goto Tools" -> Debug Console...I can't find the "Tools"Open the console, type in keypoolrefill 500000 wait a long time, when finished, close the wallet, make a backup of the wallet.dat file start wallet again and mix.
Window -> ConsoleTku. New so sry but how do I open the console? The directions in docs just said "Goto Tools" -> Debug Console...I can't find the "Tools"
Thanks Mono. Yes, it was an old doc. I'm good.Yes & being a POW vet (BTC mostly) but a new DASH fan, I'm taking it slow & easy. I'll go searching unless you are willing to point me. Tx.
Thanks Bridgewater! This helps a lot. Any tips on switching to HD?The "create a bajillion keys" solution is a bit overkill, IMO.
The wallet automatically creates new addresses when it runs out during mixing. It also automatically creates a temporary backup when it creates this new set of keys. You can simply uncheck the box in the Settings>Coinjoin menu to remove the warning when it does this and the auto-creation experience will be seamless.
I think the only risk here is the rare event that the wallet or the computer crashes and that auto-backup somehow fails or gets corrupted, and you haven't closed and reopened the wallet in a while (which auto-creates a full backup of the wallet.dat each time you do).
Speaking from personal experience, I have for years allowed the wallet to auto-create during mixing without notifying me and without closing/reopening the wallet (or manually creating a wallet.dat backup [File>Backup Wallet]) and have experienced many computer crashes, power failures, etc while the wallet is mixing and have never lost keys.
Since then, I've switched to HD mode so all keys are determined from a single seed, just so there's no more concern about using newly created addresses before fully backing up the wallet. This is a more elegant solution to creating a bajillion keys, as you can always recover all addresses with the seed phrase, even if you lose your wallet.dat backups.
See here for details how to do this:
Advanced topics — Dash latest documentation
Coin control, HD wallets, multisig, multiple wallet files using the Dash Core walletdocs.dash.org
Yeah the interface for HD is not super friendly yet, so there are a few things to look out for.Thanks Bridgewater! This helps a lot. Any tips on switching to HD?
--usehd=1 --mnemonic="" --mnemonicpassphrase=""
upgradetohd "optionally input your own bip39 mnemonic here" "apply a mnemonic passphrase for better security here"
upgradetohd "" "hdwalletsarebetterwithpassphrases" "shinyobjects"
dumphdinfo
Thank you BW. I was hesitant to proceed due to a lack of understanding as although the current documentation is adequate, it needs more detail in the steps and their explanation. Your reply (& the others previously) answered the open questions I had. Such expositions would be a good addition to the current docs. Giving new members comfort to proceed like this ensures community growth and further success of DASH which IMHO is a great POW project. Bravo.Yeah the interface for HD is not super friendly yet, so there are a few things to look out for.
One is that you still have to use your wallet passphrase like normal, even in HD mode. Your wallet.dat is encrypted on the computer with the wallet passphrase, and it doesn't have anything to do with your HD mnemonic or mnemonic+optional passphrase. You'll still enter the wallet's passphrase when unlocking for privatesend--er, coinjoin--or sending funds.
There are multiple ways of getting to HD. If you're starting from scratch with no wallet.dat, you can use theflags when starting dash-qt from the command line, as outlined in the document I linked above.Code:--usehd=1 --mnemonic="" --mnemonicpassphrase=""
Or you can simply create a new wallet from the currently-open wallet by going to File>Create Wallet, and then within that wallet, go to the console and typeCode:upgradetohd "optionally input your own bip39 mnemonic here" "apply a mnemonic passphrase for better security here"
If you don't input your own existing bip39 mnemonic from somewhere else, leaving the quotations empty will result in the wallet auto-creating a mnemonic for you. This is what most people will do, and they will be confused because the wallet doesn't show you the mnemonic it chose for you during the wallet creation (usehd) or conversion (upgradetohd) process.
So for example, say you created a new wallet, encrypted it with the passphrase "shinyobjects" and then went to the console and typed, The wallet will auto-generate a mnemonic and combine it with your manually specified mnemonic passphrase (in this case "hdwallesarebetterwithpassphrases") to create the seed. but you won't know what your mnemonic is until you tell the wallet to spit it out. So you'll have to use theCode:upgradetohd "" "hdwalletsarebetterwithpassphrases" "shinyobjects"
command in the console to show it.Code:dumphdinfo
Again, this is all just for the setup. After you write down your mnemonic and mnemonic passphrase somewhere safe, you'll never have to use them again unless something happens and you lose your wallet.dat or wallet passphrase.
One more thing to remember: if you upgrade an existing wallet to HD, I don't think previously generated addresses will be part of the hierarchy, so if you do lose your wallet and all wallet.dat backups and need to recover from the mnemonic (or mnemonic+mnemonicpassphrase), any funds you still had in those old pre-HD addresses will be gone. So it's probably best to make a new wallet and send everything from the old wallet to the HD one,
I will pass that on internally as well, which docs were you reading? We're always looking to improve themThank you BW. I was hesitant to proceed due to a lack of understanding as although the current documentation is adequate, it needs more detail in the steps and their explanation. Your reply (& the others previously) answered the open questions I had. Such expositions would be a good addition to the current docs. Giving new members comfort to proceed like this ensures community growth and further success of DASH which IMHO is a great POW project. Bravo.
I see! We've gone ahead and added a link at the top of the documentation at docs.dash.org that should link to the forum in future, thanks for the feedbackGreat stuff. I was working off the current documentation (which is good but assumes a level of knowledge beyond most newbie's ken) but I was looking for clarification b/c as above, I knew I was not adept enough to proceed. Initially (before I found y'all) it was the only info I could find (Reddit, I believe) & yes, it was an (old) post on PSend (er CJ) which was no help b/c it made reference to old controls on the D-Core wallet so I knew I was off track which sent me out to search again. Making this forum (which is what I was seeking) more apparent somewhere in the basic intro docs for those on the way in may be helpful. (and it is certainly possible I missed something as I was on boarding but I'm usually not such a dope ; ). Thanks y'all.
That's kinda it (wait and the more rounds the longer)Nice. That'll work well M. While we're on it, is there a good explanation of what to expect as a user after submitting to a mix? (besides wait awhile & the more rounds the longer it'll take?)
As a user I think being patient is the main thing to do. The process is dependent on other people doing the same thing so it may be slower or faster depending on that. If you want to get into the nuts a bolts a bit, there's a more in-depth explanation in the dev docs that covers what the wallet does and how messages are sent around (see that page here).The docs explain what's going on logically well but they could use some more nuts & bolts visibility on what to do/expect as a user.
For ex., (& I am surmising here) once a target amount is entered & sent for mixing, various much smaller denomination amounts will be split off and submitted serially for mixing sessions which do not occur continuously so expect periods of inactivity (= the CJ Balance you see on screen will appear static at times) but your submitted amount is in queue for mixing and will continue to participate in mixing sessions until your target amount is met.
I think mainly it's just a matter of how long it will take. If your machine is on a lot it matters less because it can just run in the background.Also, what are the pros/cons of submitting big vs small target amounts?
The coinjointarget in the settings menu does not at once send that amount for mixing. It doesn't do anything except ensure that the wallet keeps creating denominations from available funds and mixing them (to your selected number of rounds) until the mixed balance is higher than the target.Nice. That'll work well M. While we're on it, is there a good explanation of what to expect as a user after submitting to a mix? (besides wait awhile & the more rounds the longer it'll take?)
The docs explain what's going on logically well but they could use some more nuts & bolts visibility on what to do/expect as a user.
For ex., (& I am surmising here) once a target amount is entered & sent for mixing, various much smaller denomination amounts will be split off and submitted serially for mixing sessions which do not occur continuously so expect periods of inactivity (= the CJ Balance you see on screen will appear static at times) but your submitted amount is in queue for mixing and will continue to participate in mixing sessions until your target amount is met.
Also, what are the pros/cons of submitting big vs small target amounts?