|
|
|
|
|
|
|
|
|
"Governments are good at cutting off the heads of a centrally
controlled
networks like Napster, but pure P2P networks like Gnutella and Tor seem
to be holding their own." -- Satoshi
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
|
Azeh (OP)
|
 |
June 04, 2015, 01:26:24 AM |
|
Azeh, can you please compile x86 version of the wallet? I have couple of older laptops with licensed XP dusting around. Would be nice to use those for 24/7 node. Thanks in advance.
Ralexvalex1, You'll have to direct that towards Btcddev. |
|
|
|
|
|
CrimsonPermanentAssurance
|
|
June 04, 2015, 02:09:35 AM
Last edit: June 16, 2015, 07:57:51 PM by CrimsonPermanentAssurance |
|
To any Macintosh BTCD wallet newbies, here is a specific guide to get you going:
1. For some reason, the wallet will not open when downloaded with Safari. We have tried this on several machines and several versions, and every Safari download gives you a dead duck of a file, so YOU MUST USE EITHER CHROME OR FIREFOX TO DOWNLOAD THE WALLET (perhaps other browsers work, but we are certain Chrome and Firefox do).
2. Once launching the downloaded DMG file, drag the BTCD app into your "Applications" folder.
3. Open the app and let it fully open. You are only opening it this time to create the system directories necessary to run the wallet. After it opens and the wallet appears, you should then quit the app. The system files have now been created to run the app. Now, we will manually create a .conf file for the app.
4. In our experience, the app will not start to synchronize until you make a .conf file for it. Doing this is easy, but not exactly Mac-intuitive. Here are some directions for success:
5. IF, and only if you know what RPC is and how to use it (most people don't), use the below code for copying (while CHANGING the "rpcuser" and "rpcpassword" to your own, unique values after the equal sign). OTHERWISE, skip this step #5 and move below to step #6 for different code to copy. Following this direction is very important to maintain wallet security, so if you don't know what RPC is, please immediately skip to step #6.
Again, if, and only if you know what RPC is and how to use it, use the below code for copying (while changing the "rpcuser" and "rpcpassword" to your own, unique values after the equal sign). Otherwise, immediately move to step #6. Copy the exact code below to your clipboard by highlighting it and then holding down Command and typing the letter "c" (otherwise known as Command-C). You will then have the code you need for the .conf file copied to your clipboard:
rpcuser=user
rpcpassword=pass
rpcport=14632
port=14631
daemon=1
gen=1
server=1
addnode=107.170.59.196
addnode=146.185.188.6
addnode=74.91.20.250:39997
addnode=54.85.50.15:50288
addnode=107.170.148.50:14631
addnode=65.129.66.246:57762
addnode=31.220.4.41
addnode=98.226.66.65
addnode=193.219.117.63
addnode=62.210.141.204
addnode=128.199.172.165
addnode=192.99.143.114
addnode=178.20.169.208
addnode=195.34.100.2:42038
addnode=5.101.107.239:60056
addnode=ps00.bitcoindark.ca
addnode=ps01.bitcoindark.ca
addnode=ps02.bitcoindark.ca
addnode=ps03.bitcoindark.ca
addnode=ps04.bitcoindark.ca
addnode=ps05.bitcoindark.ca
addnode=ps06.bitcoindark.ca
addnode=ps07.bitcoindark.ca
addnode=ps08.bitcoindark.ca
addnode=ps09.bitcoindark.ca
addnode=ps10.bitcoindark.ca
addnode=ps11.bitcoindark.ca
addnode=ps12.bitcoindark.ca
addnode=ps13.bitcoindark.ca
addnode=ps14.bitcoindark.ca
addnode=ps15.bitcoindark.ca
addnode=ps16.bitcoindark.ca
addnode=ps17.bitcoindark.ca
addnode=ps18.bitcoindark.ca
addnode=ps19.bitcoindark.ca
addnode=ps20.bitcoindark.ca
addnode=107.170.59.196
addnode=146.185.188.6
addnode=74.91.20.250:39997
addnode=54.85.50.15:50288
addnode=107.170.148.50:14631
addnode=65.129.66.246:57762
addnode=31.220.4.41
addnode=107.170.44.31
addnode=101.103.54.206:51222
addnode=120.148.149.13:54338
addnode=184.100.114.11:63310
6. Please skip this step if you opted for the code in step #5. However, if you DO NOT know what RPC is and how to use it (most people don't), please use the below EXACT code for copying...
Copy the exact code below to your clipboard by highlighting it and then holding down Command and typing the letter "c" (otherwise known as Command-C). You will then have the code you need for the .conf file copied to your clipboard. Here is the EXACT code to copy:
addnode=107.170.59.196
addnode=146.185.188.6
addnode=74.91.20.250:39997
addnode=54.85.50.15:50288
addnode=107.170.148.50:14631
addnode=65.129.66.246:57762
addnode=31.220.4.41
addnode=98.226.66.65
addnode=193.219.117.63
addnode=62.210.141.204
addnode=128.199.172.165
addnode=192.99.143.114
addnode=178.20.169.208
addnode=195.34.100.2:42038
addnode=5.101.107.239:60056
addnode=ps00.bitcoindark.ca
addnode=ps01.bitcoindark.ca
addnode=ps02.bitcoindark.ca
addnode=ps03.bitcoindark.ca
addnode=ps04.bitcoindark.ca
addnode=ps05.bitcoindark.ca
addnode=ps06.bitcoindark.ca
addnode=ps07.bitcoindark.ca
addnode=ps08.bitcoindark.ca
addnode=ps09.bitcoindark.ca
addnode=ps10.bitcoindark.ca
addnode=ps11.bitcoindark.ca
addnode=ps12.bitcoindark.ca
addnode=ps13.bitcoindark.ca
addnode=ps14.bitcoindark.ca
addnode=ps15.bitcoindark.ca
addnode=ps16.bitcoindark.ca
addnode=ps17.bitcoindark.ca
addnode=ps18.bitcoindark.ca
addnode=ps19.bitcoindark.ca
addnode=ps20.bitcoindark.ca
addnode=107.170.59.196
addnode=146.185.188.6
addnode=74.91.20.250:39997
addnode=54.85.50.15:50288
addnode=107.170.148.50:14631
addnode=65.129.66.246:57762
addnode=31.220.4.41
addnode=107.170.44.31
addnode=101.103.54.206:51222
addnode=120.148.149.13:54338
addnode=184.100.114.11:63310
7. Now, open a Mac Terminal window. The "Terminal" program can be found in the "Utilities" folder, which by default is in your "Applications" folder. Just navigate there and double click on "Terminal".
8. In the "Terminal" window that appears type EXACTLY the following. Any returns you should hit or pasting needing to be done will be indicated in brackets []. Don't type what is in the brackets. Just do what it says to do when it says to do it in the brackets:
It is important that you follow the case-sensitivity in what you type, as well as put the two spaces where there are spaces. Here is EXACTLY what to type in the "Terminal" window:
cat > BitcoinDark.conf [press RETURN]
[Now, paste the code you copied earlier by holding down the Command key and pressing the letter "v" (otherwise known as Command-V)]
[Now, hold down Control and type the letter "d" (otherwise known as Control-D)]
[You can now quit the Terminal program]
9. Even though it might not seem like it, you just created the .conf file the BTCD wallet will need to synchronize. Now, we have to find that .conf file and put it in the right place...
10. Open a Finder window. While holding down the Option key, click on the "Go" drop-down menu at the top of your screen. Holding the "Option" key down reveals your hidden "Library" folder. Click on this newly-revealed "Library" in the "Go" drop-down menu.
11. Your Finder window should now be displaying all your Library folders. Navigate to "Application Support" and open that folder. Then, navigate to the subheading folder titled "BitcoinDark" and open that folder.
12. Now, go to the "File" drop-down menu at the top of your screen and click on "Open New Finder Window". Drag this new window next to the previous Library window you opened in step #11 so that you can see both Finder windows. In that new window, do a search for the "BitcoinDark.conf" file that you created earlier. Now, drag that newly found BitcoinDark.conf file into the BitcoinDark folder you opened in step #11. Make sure not to put it inside another folder within the BitcoinDark folder. You just want to drag the BitcoinDark.conf file into the main BitcoinDark folder. All files will then be in the correct place for the wallet to function properly.
You can now close all the Finder windows and start up your BTCD app again (which is now in your "Applications" folder). It should start synching pretty quickly. Synching takes a while, so let it sit overnight, if need be. Don't forget to encrypt your wallet! Also, the wallet needs to be "unlocked" to stake. You can unlock the wallet under the "Settings" drop-down menu at the top of your screen in the BitcoinDark wallet.
Enjoy!
|
|
|
|
|
|
4emily
|
|
June 04, 2015, 06:00:54 AM
Last edit: June 04, 2015, 06:50:38 AM by 4emily |
|
In the roaming folder, is the database file supposed to update each time the wallet is open? The reason I ask is because mine hasn't in the last 24+ hours even though the wallet has been opened several times during that time. Here's a recent s/shot:  Ordinarily I wouldn't have noticed but am playing closer attention than normal in view of others' reported difficulties. Thanks in advance for any replies  Just reopened my wallet after approx 6 hours offline; again the database file hasn't updated (still showing date/time as per s/shot above) though the wallet appears to have synched ok: 557360 as at the time of this post (7.00am GMT) Does 557360 sound like the correct block height? If so then I'll assume that the fact the db, for whatever reason, doesn't appear to be updating must be a server side problem and that there's therefore nothing I can do about it locally. Is that correct? Any advice gratefully received. Thanks. |
|
|
|
|
|
ASICHEAD
|
|
June 04, 2015, 08:56:24 AM |
|
I Hodl my BitcoinDark in 6 different wallets, but I didn't have any syncing or other problem with my wallets since the launch until today(thanks to god).  my wallets always syncing very fast and I have 16 active connections. this is my conf file : addnode=107.170.59.196 addnode=146.185.188.6 addnode=74.91.20.250:39997 addnode=54.85.50.15:50288 addnode=186.94.211.104:49543 addnode=107.170.148.50:14631 addnode=65.129.66.246:57762 addnode=31.220.4.41 addnode=98.226.66.65 addnode=193.219.117.63 addnode=62.210.141.204 addnode=128.199.172.165 addnode=192.99.143.114 addnode=178.20.169.208 addnode=195.34.100.2:42038 addnode=5.101.107.239:60056 and there isn't other things. try it and syncing again, I think it will solve your problem.  Note: Every time you try to re syncing , it may take a few minutes to start syncing, so don't worry. |
|
|
|
|
4emily
|
|
June 04, 2015, 12:20:22 PM |
|
Thanks. To restate my concern: although my wallet appears to be syncing ok and indeed staking and mining - see below partial s/shot of today's mining transactions  the database hasn't updated since 5.30pm Tuesday, even though the wallet has been opened several times since then - here's the latest s/shot of the roaming folder  I assume (and perhaps someone who knows would be kind enough to tell me) that the db file is supposed to update each time the wallet is open, in which case the fact that mine isn't dong so would seem to be a problem but is it a server side problem or a local problem with my wallet and if the latter do I need to reinstall the wallet even though the wallet is syncing ok as well as staking, mining, receiving dividends and sending/receiving coins? As before, any advice gratefully received. Thanks [edit] Blockheight showing on my wallet as at 1.27pm (GMT): 557747 |
|
|
|
|
|
ASICHEAD
|
|
June 04, 2015, 12:54:08 PM |
|
Thanks. To restate my concern: although my wallet appears to be syncing ok and indeed staking and mining - see below partial s/shot of today's mining transactions the database hasn't updated since 5.30pm Tuesday, even though the wallet has been opened several times since then - here's the latest s/shot of the roaming folder I assume (and perhaps someone who knows would be kind enough to tell me) that the db file is supposed to update each time the wallet is open, in which case the fact that mine isn't dong so would seem to be a problem but is it a server side problem or a local problem with my wallet and if the latter do I need to reinstall the wallet even though the wallet is syncing ok as well as staking, mining, receiving dividends and sending/receiving coins? As before, any advice gratefully received. Thanks [edit] Blockheight showing on my wallet as at 1.27pm (GMT): 557747 yes, your assume is true. I think you should re syncing your wallet for resolve this problem. |
|
|
|
|
4emily
|
|
June 04, 2015, 01:57:41 PM |
|
Thanks for reply Reinstalled wallet and resynching - 25 active connections and 7% done so should be finished in approx 7.5 hours. Could the problem with the db not updating have been caused by opening the wallet for staking before syncing had finished - I remember doing that recently and immediately realising my mistake and relocking the wallet before the arrow turned green. Nevertheless could that have been the reason for the problem? In any event, it may be an idea to post a warning notice in the op not to stake until synched. |
|
|
|
|
|
BTCDDev
|
|
June 04, 2015, 02:12:42 PM
Last edit: June 04, 2015, 02:32:08 PM by BTCDDev |
|
Hi Everyone,
It seems there has been some issue around block 5550559. Yes, it is coming at a bad time since BitcoinDark has been on an accelerating upward trajectory lately.
If you are stuck, the first thing I would do is to delete your peers.dat and restart BitcoinDark. If that doesn't work, try deleting your blockchain and resyncing.
Many people have been fixing this issue by deleting everything except their wallet and BitcoinDark.conf.
In fact, here are some nodes that seem to be synced:
addnode=192.99.203.53
addnode=198.50.152.135
In fact, I myself have restarted my vps's.
When clear consensus is lost, it takes some time to restore the longest chain. That's just the nature of a blockchain.
crackfoo has informed me that he received the daily BTCD payments from the exchanges, so they are on the correct chain.
Thanks,
Matthew
|
BitcoinDark: RPHWc5CwP9YMMbvXQ4oXz5rQHb3pKkhaxc
Top Donations: juicybirds 420BTCD ensorcell 84BTCD Stuntruffle: 40BTCD
Top April Donations: juicybirds 420BTCD; ensorcell: 42BTCD
|
|
|
|
ASICHEAD
|
|
June 04, 2015, 02:13:44 PM |
|
Thanks for reply Reinstalled wallet and resynching - 25 active connections and 7% done so should be finished in approx 7.5 hours. Could the problem with the db not updating have been caused by opening the wallet for staking before syncing had finished - I remember doing that recently and immediately realising my mistake and relocking the wallet before the arrow turned green. Nevertheless could that have been the reason for the problem? In any event, it may be an idea to post a warning notice in the op not to stake until synched. you're welcome |
|
|
|
|
Azeh (OP)
|
|
June 04, 2015, 02:21:18 PM |
|
James or any mods, feel free to check my work, revise the below Macintosh how-to guide however you see fit, and then post the guide on the front page of this thread and on the website alongside the Windows how-to, should you all wish to use it. Something like this would have helped me a lot in the beginning...
To any Macintosh BTCD wallet newbies, here is a specific guide to get you going:
1. For some reason, the wallet will not open when downloaded with Safari. We have tried this on several machines and several versions, and every Safari download gives you a dead duck of a file, so YOU MUST USE EITHER CHROME OR FIREFOX TO DOWNLOAD THE WALLET (perhaps other browsers work, but we are certain Chrome and Firefox do).
2. Once launching the downloaded DMG file, drag the BTCD app into your "Applications" folder.
3. Open the app and let it fully open. You are only opening it this time to create the system directories necessary to run the wallet. After it opens and the wallet appears, you should then quit the app. The system files have now been created to run the app. Now, we will manually create a .conf file for the app.
4. In our experience, the app will not start to synchronize until you make a .conf file for it. Doing this is easy, but not exactly Mac-intuitive. Here are some directions for success:
5. Copy the exact code below to your clipboard by highlighting it and then holding down Command and typing the letter "c" (otherwise known as Command-C). You will then have the code you need for the .conf file copied to your clipboard.
Here is the code to copy:
rpcuser=user
rpcpassword=pass
rpcport=14632
port=14631
daemon=1
gen=1
server=1
addnode=107.170.59.196
addnode=146.185.188.6
addnode=74.91.20.250:39997
addnode=54.85.50.15:50288
addnode=107.170.148.50:14631
addnode=65.129.66.246:57762
addnode=31.220.4.41
addnode=98.226.66.65
addnode=193.219.117.63
addnode=62.210.141.204
addnode=128.199.172.165
addnode=192.99.143.114
addnode=178.20.169.208
addnode=195.34.100.2:42038
addnode=5.101.107.239:60056
addnode=ps00.bitcoindark.ca
addnode=ps01.bitcoindark.ca
addnode=ps02.bitcoindark.ca
addnode=ps03.bitcoindark.ca
addnode=ps04.bitcoindark.ca
addnode=ps05.bitcoindark.ca
addnode=ps06.bitcoindark.ca
addnode=ps07.bitcoindark.ca
addnode=ps08.bitcoindark.ca
addnode=ps09.bitcoindark.ca
addnode=ps10.bitcoindark.ca
addnode=ps11.bitcoindark.ca
addnode=ps12.bitcoindark.ca
addnode=ps13.bitcoindark.ca
addnode=ps14.bitcoindark.ca
addnode=ps15.bitcoindark.ca
addnode=ps16.bitcoindark.ca
addnode=ps17.bitcoindark.ca
addnode=ps18.bitcoindark.ca
addnode=ps19.bitcoindark.ca
addnode=ps20.bitcoindark.ca
addnode=107.170.59.196
addnode=146.185.188.6
addnode=74.91.20.250:39997
addnode=54.85.50.15:50288
addnode=107.170.148.50:14631
addnode=65.129.66.246:57762
addnode=31.220.4.41
addnode=107.170.44.31
addnode=101.103.54.206:51222
addnode=120.148.149.13:54338
addnode=184.100.114.11:63310
6. Now, open a Mac Terminal window. The "Terminal" program can be found in the "Utilities" folder, which by default is in your "Applications" folder. Just navigate there and double click on "Terminal".
7. In the "Terminal" window that appears type EXACTLY the following. Any returns you should hit or pasting needing to be done will be indicated in brackets []. Don't type what is in the brackets. Just do what it says to do when it says to do it in the brackets:
It is important that you follow the case-sensitivity in what you type. Here is EXACTLY what to type in the "Terminal" window:
cat > BitcoinDark.conf [press RETURN]
[Now, paste the code you copied earlier by holding down the Command key and pressing the letter "v" (otherwise known as Command-V)]
[Now, hold down Control and type the letter "d" (otherwise known as Control-D)]
[You can now quit the Terminal program]
8. Even though it might not seem like it, you just created the .conf file the BTCD wallet will need to synchronize. Now, we have to find that .conf file and put it in the right place...
9. Open a Finder window. While holding down the Option key, click on the "Go" drop-down menu at the top of your screen. Holding the "Option" key down reveals your hidden "Library" folder. Click on this newly-revealed "Library" in the "Go" drop-down menu.
10. Your Finder window should now be displaying all your Library folders. Navigate to "Application Support" and open that folder. Then, navigate to the subheading folder titled "BitcoinDark" and open that folder.
11. Now, go to the "File" drop-down menu at the top of your screen and click on "Open New Finder Window". Drag this new window next to the previous Library window you opened in step #10 so that you can see both Finder windows. In that new window, do a search for the "BitcoinDark.conf" file that you created earlier. Now, drag that newly found BitcoinDark.conf file into the BitcoinDark folder you opened in step #10. Make sure not to put it inside another folder within the BitcoinDark folder. You just want to drag the BitcoinDark.conf file into the main BitcoinDark folder. All files are now in the right place for the wallet to function properly.
12. You can now close all the finder windows and start up your BTCD app again (which is now in your "Applications" folder). It should start synching pretty quickly. Synching takes a while, so let it sit overnight, if need be. Don't forget to encrypt your wallet! Also, the wallet needs to be "unlocked" to stake. You can unlock the wallet under the "Settings" drop-down menu at the top of your screen in the BitcoinDark wallet.
Enjoy!
Excellent!!! Thank you very much for taking the time to write this up. I'll post a link to this on the OP in the Wallet section. |
|
|
|
|
GIminer
Newbie
 Offline
Activity: 59
Merit: 0
|
|
June 04, 2015, 03:30:47 PM
Last edit: June 04, 2015, 04:17:50 PM by GIminer |
|
Hi,
I have a suggestion, a common mistake among the users who aren't tech savvy is to copy/paste literally the part
rpcuser=user
rpcpassword=pass
of the suggested code to make a conf file. Long time ago I did that mistake when I made my first conf file for another coin's wallet.
I know is too noob, but being quite usual mistake and one that can compromise the wallet's security, I strongly suggest to stress that at the Bitcondark.conf's code at the OP.
As example, something like that:
rpcuser=type your user
rpcpassword=type your password
Thanks
|
|
|
|
|
|
BTCDDev
|
|
June 04, 2015, 03:46:25 PM |
|
Hi,
I have a suggestion, a common mistake amongs the who aren't tech savvy happends is to copy/paste literally the part
rpcuser=user
rpcpassword=pass
of the suggested code to make a conf file. Long time ago I did that mistake when I made my first conf file for another coin's wallet.
I know is too noob, but being quite usual mistake and one that can compromise the wallet's security, I strongly suggest to stress that at the Bitcondark.conf's code at the OP.
As example, something like that:
rpcuser=type your user
rpcpassword=type your password
Thanks
I have already implemented automatic BitcoinDark.conf generation in the upcoming BTCD wallet at github.com/jl777/btcdI generates a strong 12 character random password. |
BitcoinDark: RPHWc5CwP9YMMbvXQ4oXz5rQHb3pKkhaxc
Top Donations: juicybirds 420BTCD ensorcell 84BTCD Stuntruffle: 40BTCD
Top April Donations: juicybirds 420BTCD; ensorcell: 42BTCD
|
|
|
|
CrimsonPermanentAssurance
|
|
June 04, 2015, 04:11:42 PM |
|
Hi,
I have a suggestion, a common mistake amongs the who aren't tech savvy happends is to copy/paste literally the part
rpcuser=user
rpcpassword=pass
of the suggested code to make a conf file. Long time ago I did that mistake when I made my first conf file for another coin's wallet.
I know is too noob, but being quite usual mistake and one that can compromise the wallet's security, I strongly suggest to stress that at the Bitcondark.conf's code at the OP.
As example, something like that:
rpcuser=type your user
rpcpassword=type your password
Thanks
So, I am not the most tech savvy person, and the last thing I wish to do is mislead anyone with the guide. Azeh, perhaps make whatever changes need to be made to avoid rpcuser=user rpcpassword=pass from misleading anyone. I also have a few questions... When you type what you are supposed to type in those rpcuser=user, rpcpassword=pass fields, how do you know what your "user" name is and what your "password" is when you first make the wallet? Do you just type random stuff in both fields? If so, do you ever need to access that random stuff or input it later for any reason? Do you even need to remember what you type here or write it down? Is any of what you are supposed to type in those fields based on the same password you use to encrypt the wallet? Please let me know, and we can make the guide more accurate and helpful. I also can make whatever changes I need to for my wallet, because I copied that exact code when making my .conf file! D'oh! |
|
|
|
|
|
ASICHEAD
|
|
June 04, 2015, 05:03:43 PM |
|
Hi,
I have a suggestion, a common mistake amongs the who aren't tech savvy happends is to copy/paste literally the part
rpcuser=user
rpcpassword=pass
of the suggested code to make a conf file. Long time ago I did that mistake when I made my first conf file for another coin's wallet.
I know is too noob, but being quite usual mistake and one that can compromise the wallet's security, I strongly suggest to stress that at the Bitcondark.conf's code at the OP.
As example, something like that:
rpcuser=type your user
rpcpassword=type your password
Thanks
So, I am not the most tech savvy person, and the last thing I wish to do is mislead anyone with the guide. Azeh, perhaps make whatever changes need to be made to avoid rpcuser=user rpcpassword=pass from misleading anyone. I also have a few questions... When you type what you are supposed to type in those rpcuser=user, rpcpassword=pass fields, how do you know what your "user" name is and what your "password" is when you first make the wallet? Do you just type random stuff in both fields? If so, do you ever need to access that random stuff or input it later for any reason? Do you even need to remember what you type here or write it down? Is any of what you are supposed to type in those fields based on the same password you use to encrypt the wallet? Please let me know, and we can make the guide more accurate and helpful. I also can make whatever changes I need to for my wallet, because I copied that exact code when making my .conf file! D'oh! please don't use this in your config file.
///////////////////////////////////////////////
rpcuser=user
rpcpassword=pass
rpcport=14632
port=14631
daemon=1
gen=1
server=1
//////////////////////////////////////////////
Why? Its from the OP, and working perfectly for me. Because inexperienced user will not change "pass" to their unique password and their system could very possibly get compromised. |
|
|
|
|
CrimsonPermanentAssurance
|
|
June 04, 2015, 05:18:50 PM
Last edit: June 04, 2015, 05:36:39 PM by CrimsonPermanentAssurance |
|
please don't use this in your config file.
///////////////////////////////////////////////
rpcuser=user
rpcpassword=pass
rpcport=14632
port=14631
daemon=1
gen=1
server=1
//////////////////////////////////////////////
Why? Its from the OP, and working perfectly for me. Because inexperienced user will not change "pass" to their unique password and their system could very possibly get compromised. Guys and Gals, so that I can get all the guides correct for everyone, including for noobs like me (who are actually not so new), can I please get a few specific answers to each question posted below? I will then revise the guides to make them idiot proof. I am a decent technical writer largely because I am still close to being new at this and can explain things well to less experienced people, as long as I understand all the concepts. Here is what I need specific answers for: When you type what you are supposed to type in those rpcuser=user, rpcpassword=pass fields, how do you know what your "user" name is and what your "password" is when you first make the wallet? I am asking because someone brand new at this (and actually me right now) would wonder how they already have a user name and password when they haven't even done anything yet or signed up for anything anywhere. Do you just type random stuff in both fields? If you just type random stuff, do you ever need to access that random stuff or input it later for any reason? Do you need to remember the random stuff you type in those fields or write it down? If you do need to remember it, why do you need to remember it? Is any of what you are supposed to type in those rpcuser=user, rpcpassword=pass fields based on the same password you use to encrypt the wallet? Does there need to be any congruency between the encryption of your wallet and what you type in those user/password fields? Please let me know SPECIFIC answers to those few simple questions, and I will revise the guide to everyone's satisfaction. Also, thank you to GIminer for pointing this all out. It didn't just help noobs... it helped me, because I have been rolling for a long time with exactly that code that I was supposed to change! I had no idea. |
|
|
|
|
|
BTCDDev
|
|
June 04, 2015, 05:31:44 PM |
|
please don't use this in your config file.
///////////////////////////////////////////////
rpcuser=user
rpcpassword=pass
rpcport=14632
port=14631
daemon=1
gen=1
server=1
//////////////////////////////////////////////
Why? Its from the OP, and working perfectly for me. Because inexperienced user will not change "pass" to their unique password and their system could very possibly get compromised. Guys and Gals, so that I can get all the guides correct for everyone, including for noobs like me (who are actually not so new), can I please get a few specific answers to each question posted below? I will then revise the guides to make them idiot proof. I am a decent technical writer largely because I am still close to being new at this and can explain things well to less experienced people, as long as I understand all the concepts. Here is what I need specific answers for: When you type what you are supposed to type in those rpcuser=user, rpcpassword=pass fields, how do you know what your "user" name is and what your "password" is when you first make the wallet? I am asking because someone brand new at this (and actually me right now) would wonder how they already have a user name and password when they haven't even done anything yet or signed up for anything anywhere. Do you just type random stuff in both fields? If you just type random stuff, do you ever need to access that random stuff or input it later for any reason? Do you need to remember the random stuff you type in those fields or write it down? If you do need to remember it, why do you need to remember it? Is any of what you are supposed to type in those rpcuser=user, rpcpassword=pass fields based on the same password you use to encrypt the wallet? Does there need to be any congruency between the encryption of your wallet and what you type in those fields? Please let me know SPECIFIC answers to those few simple questions, and I will revise the guide to everyone's satisfaction. Also, thank you to GIminer for pointing this all out. It didn't just help noobs... it helped me, because I have been rolling for a long time with exactly that code that I was supposed to change! I had no idea. This is the reason I added a strong random password generation to the upcoming BitcoinDark wallet. Honestly, we ought to just remove rpcuser and rpcpassword fields from the default conf. rpcuser and rpcpassword allow you access to the BitcoinDark functionality from outside code. If you are just using BTCD-qt as a wallet without ever making some program that uses it remotely, you DO NOT need those fields. IF you include rpcuser and rpcpassword, give them both unique, random names. DO NOT EVER use user and pass. Here is a good example: rpcuser=fh3hf3hfhf rpcpassword=m34uvn9u9v424!mvfj4 Basically, if you don't know what RPC is used for, don't include it! Matthew |
BitcoinDark: RPHWc5CwP9YMMbvXQ4oXz5rQHb3pKkhaxc
Top Donations: juicybirds 420BTCD ensorcell 84BTCD Stuntruffle: 40BTCD
Top April Donations: juicybirds 420BTCD; ensorcell: 42BTCD
|
|
|
|
CrimsonPermanentAssurance
|
|
June 04, 2015, 05:47:01 PM
Last edit: June 04, 2015, 07:42:50 PM by CrimsonPermanentAssurance |
|
It seems like this might be problem in other coin's wallets, as well. There are probably tons of people like me using things wrong based off of unclear directions. I think the directions become unclear to new people because the people who wrote those directions are SO knowledgable that they forgot what it is like to know nothing. No foul on their part. It's just the nature of the beast, as all this has become second nature to them.
As BTCD is leading the way in tech, I think it should also strive to lead the way in clear, concise directions so that it becomes accessible to EVERYONE, something it hasn't achieved yet, but it easily could with a little more focus in that direction. Empowering people with the knowledge to use these tools correctly will do just that. It will make it less of a "niche" thing and much more of a mainstream thing. Were it to become a mainstream thing, beyond the sky is the limit.
|
|
|
|
|
|
4emily
|
|
June 04, 2015, 05:51:46 PM |
|
I'm currently in the process of resyncing my wallet and getting some strange results: when the wallet 1st started syncing (about 4 hours ago) the total no. of blocks to be d/loaded (as shown when hovering the mouse over the bottom right hand corner of the wallet) was a figure in the 200,000s not (as it should have been) the 500,000s; after a few blocks that total figure then changed back to a figure in the 500,000s; then a couple of hours later I noticed the total figure to be d/loaded had changed back again to a smaller number - in the 200,000s. I then had to go out, so I left the wallet syncing and got back a few minutes ago to find that the total figure to be d/loaded is now showing as 558020, which I assume is correct. Other strange results are that a couple of the 'sent to' transactions haven't been confirmed although subsequent ones are being; instead these two are still showing as 'conflicted', as per s/shot below  Also, a series of 12 consecutive mined transactions are shown as 'Generated but not accepted' , as shown below  I suppose it is conceivable that these 12 consecutive mined transactions are correctly shown as 'Generated but not accepted' but I certainly don't remember that happening at the time (on the 8 - 10th September 2014) - at most there's usually only one such 'Generated but not accepted' t/action happening at a time, not 12 in a row I'll continue syncing until the wallet is fully synched. In the meantime any advice re the above would be very welcome. Thanks |
|
|
|
|
|
CrimsonPermanentAssurance
|
|
June 04, 2015, 06:05:12 PM |
|
when the wallet 1st started syncing (about 4 hours ago) the total no. of blocks to be d/loaded (as shown when hovering the mouse over the bottom right hand corner of the wallet) was a figure in the 200,000s not (as it should have been) the 500,000s; after a few blocks that total figure then changed back to a figure in the 500,000s; then a couple of hours later I noticed the total figure to be d/loaded had changed back again to a smaller number - in the 200,000s.
I have been experiencing the same thing with the numbers jumping back and forth between the 200,000s and the 500,000s during my re-synch. |
|
|
|
|
|
Poll
