![]() ![]() ![]() Go to the extracted contents and run "dogecoin-qt.exe".ĭepending on your security settings, you may asked if you want to run this file. This guide will be updated to reflect this soon. Just install the wallet like a normal program instead. Note: version 1.5.1 onward uses an installer instead of zipped file. This can be done by right clicking the file and selecting "extract all" or something similar. Once downloaded, navigate to the downloaded file and extract the file contents. It should start downloading the latest wallet in a zip file. On the official site click the Windows option. Pick your operating system below to continue with the local wallet guide. (A large transaction may pull from multiple addresses, which may result in multiple "change" addresses). This may create a new address for you, so also back up your wallet after ~100 transactions or after very large transactions. Similar to how you receive a $5 and four $1's if you give someone a $10 bill to pay for something that cost $1, sometimes you receive Doge back from a transaction. If you create many addresses yourself (going beyond the initial 100) or manually add private keys (such as via paper wallet), these additional keys will not be saved in the original backup, so you must make a new backup.Īnother scenario that creates new addresses is called "change". As a result, the frequency of backups depends on how many addresses you create. When you first run the local wallet, it creates 100 key pairs for you (with a public key revealed each time you hit "new address") and saves them all in the first backup you make. That way, you can't spend your coins then restore from a backup to get them back.Įach secret key is paired with a public key (the receive address). What am I doing wrong - why isn't my Dogecoin daemon accepting RPC requests (or any from-an-actual-browser HTTP requests, for that matter)?Įdit: Also, I can verify that the daemon is caught up with the blockchain.Your wallet does not actually save the coins themselves, but a secret key that gives you ownership of coins in the blockchain. To the end of the config file, but that didn't change the behavior at all. I've tried adding the line rpcallowip=127.0.0.1 (I know the username and password I typed there are insecure those are temporary until I can at least make a connection.) ![]() I have my ~/.dogecoin/nf file as such: server=1 Similarly, making an RPC request via a PHP script, and then accessing that script in a browser, makes the browser wait for 30 second before PHP spits out an error stating that the maximum execution time of 30 seconds was exceeded. Directly connecting to the web browser sit and wait for data. The daemon doesn't refuse the connection (and I can verify that it does refuse the connection if I use a port other than 22556) instead, the connection hangs, with no data being sent to the client making the HTTP request. However, passing RPC requests to it through HTTP does not work. I can also pass commands to it directly via the Ubuntu terminal, like so: dogecoind getinfo It's listening on port 22556, as verified by netstat. I have the dogecoin daemon running successfully on Ubuntu, started with this command: dogecoind -daemon ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |