I created my wallet and both dcrd and dcrwallet work as expected. My OS is MacOS 10.11.6 "El Capitan" and Decred version is 0.8.2. From the command line everything is fine. I giving Decrediton a try, but am not able to use it. After starting it presents an input labeled "Scan for used addresses" and asks for my Private Passphrase. I input my passphrase but nothing happens. This is the info logged: 02:59:05 2017-04-16 [INF] DCRW: Version 0.8.2-beta 02:59:05 2017-04-16 [INF] DCRW: Generating TLS certificates... 02:59:05 2017-04-16 [INF] DCRW: Done generating TLS certificates 02:59:05 2017-04-16 [INF] DCRW: Experimental RPC server listening on 127.0.0.1:9112 02:59:14 2017-04-16 [INF] WLLT: Opened wallet 02:59:15 2017-04-16 [INF] CHNS: Established connection to RPC server 127.0.0.1:9109 02:59:15 2017-04-16 [INF] WLLT: The client has successfully connected to dcrd and is now handling websocket notifications
There doesn't seems to be anything wrong with the messages, in fact your wallet is connected and is ready to use. It says "successful connection to dcrd" .Try checking your balance?
Hi, indeed Decrediton logs a successful connection to the wallet, but I can't go beyond the initial screen with the private passphrase input. In the command line I can issue all the wallet commands with no problem. I've attached a screen capture of the point where I'm stuck at.
Perhaps @ay-p or @jcv can provide further guidance since they mainly work on Decrediton, but as a start: Does your private passphrase have special characters that are typically used in URLs in it like ", &, or ?? Since the released version of Decriton is still alpha, there might be an issue with the way it's encoding the passphrase to send via the RPC. If that is the case, it might be worth trying to recreate from seed with a super simple test passphrase to test.
No symbols, only letters and numbers. The passphrase is 24 letters and digits long. I avoided symbols to make it easier to type the passphrase in the terminal.
I don't have the previous release around at the moment so I forget, does that one ask for two different passwords when you setup? It was pretty confusing and easy to use the wrong passphrase so we don't do that in the upcoming release. If you are comfortable with the command line you can try to run the tools on the cmd line with the same wallet and see if you have the passphrase correct. The actual wallet is in ~/Library/Appication Support/Decrediton/ In the upcoming version decrediton will write out config files for the command line tools to make that easier. Also, for the record, decrediton is fine with crazy symbols in passphrases and other things. I strongly recommend against it since it is way too hard to type, but the software doesn't really care.
Yes, I am comfortable with the command line. I've configured the daemon and the cli wallet with rpc user and password and have also modified Decrediton's config.json accordingly. I am able to issue commands to the wallet in the command line. For instance dcrctl --rpcuser=**** --rpcpass=***************** --wallet list accounts lists the accounts I created in my wallet. Maybe I should clone the repo and debug Decrediton.
I'm a little confused by what you are doing. decrediton runs a copy of the daemon and the wallet itself (although the daemon uses the normal path for saving the blockchain data. So normally you should not need to change the rpc username or password that decrediton uses. So, are you running the daemon and the wallet within decrediton or manually? And if you are running wallet manually, are you sure you are pointing it to the wallet file that decrediton uses? If so, can you unlock the wallet with dcrctl Code: dcrctl --wallet walletpassphrase <YOURPASSPHRASE> 60
You are right about me causing a confusion. When you asked if I am familiar with the command line I just intended to give you an example of what I do with dcrctl, dcrd and dcrwallet. I do stop dcrd and dcrwallet before I launch Decrediton. I modified its config to have the rpc calls with a security layer, just as I did with dcrd and dcrwallet. I wanted Decrediton to use the wallet I created manually and so I created a symbolic link: Code: /Users/aacirino/Library/Application Support/decrediton/mainnet/wallet.db -> /Users/aacirino/Library/Application Support/Dcrwallet/mainnet/wallet.db I thought it would work this way. I don't think Decrediton should replicate an entire wallet that has already been created. I could import my manually created wallet into Decrediton, but I think this is redundant. Other option would be to have Decrediton access the daemon and/or the wallet in the Dcrwallet directory. Is there a way to make dcrwallet and Decrediton to use the same wallet?
In theory I see no reason that wouldn't work although I don't think the symlink way is the best way to go. I would probably keep the wallet.db in the decrediton directory and the use --appdata= option to point to it. Do you have a public and a private passphrase on your wallet? If so, that could be a problem since decrediton just uses one. Also, could you try creating a fresh decrediton wallet with the same passphrase and see if that works. I've never seen decrediton have an issue with a passphrase but if there is some way to trip it up there, I really want to know.
That's it, I didn't know that having both a private and a public passphrase would not work with Decrediton. When I manually created my wallet I used two passphrases, the private and the public. Hopefully, since I am still in the learning process, my wallet has no funds, so I will delete the one I created manually, create a new one with Decrediton and point dcrd and dcrwallet to it as you told. I am planning on moving my cryptocurrencies setup to an old Mac Mini I have. This way I can put my main computer to sleep without stopping the synchronization of the blockchains. Currently I have Decred and Monero blockchains. With dcrd and dcrwallet running in other computer I guess I will not be able to use Decrediton with a single wallet, am I right?
One warning about old mac minis (totally unrelated to cryptocurrencies). I just this weekend had to replace the hard drive in a macmini and I'm pretty sure I've had to do it on every mac mini I've ever had to deal with at least once. I don't know if I'm bad to them or if those drives fail more often than other things, but back your stuff up. Okay, PSA over. If I'm understanding correctly, at the moment, you cannot run decrediton on one box and the wallet and daemon on another. We will probably let you use a daemon at least on another box (similar to something paymetheus does) in the future, but not for the upcoming release.
OK, I will keep Decred in my main computer and move only Monero to the Mini (a 30GB move). I will create a new wallet with Decrediton and point the cli environment to it. Cheers
I should have linked to it last time, but this is the issue I have open about letting one use Paymetheus with a user-supplied daemon instead of the bundled one (which would include one on another computer). Won't begin work on that until after the 1.0.0 release, but you can always follow the issue on github if you want to know if progress has been made: https://github.com/decred/decrediton/issues/251