Bitcoin Forum
April 25, 2019, 06:46:48 PM *
News: Latest Bitcoin Core release: 0.17.1 [Torrent]
 
   Home   Help Search Login Register More  
Poll
Question: Do you Accept Komodo ICO conversion vs Reject Komodo ICO conversion and fund new dev team?
Accept - 140 (68%)
Reject - 66 (32%)
Total Voters: 206

Pages: « 1 ... 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 [443] 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 ... 551 »
  Print  
Author Topic: BTCD is no more  (Read 1312717 times)
Azeh
Sr. Member
****
Offline Offline

Activity: 442
Merit: 500


View Profile
June 04, 2015, 02:21:18 PM
 #8841

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.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1556218008
Hero Member
*
Offline Offline

Posts: 1556218008

View Profile Personal Message (Offline)

Ignore
1556218008
Reply with quote  #2

1556218008
Report to moderator
GIminer
Newbie
*
Offline Offline

Activity: 59
Merit: 0


View Profile
June 04, 2015, 03:30:47 PM
Last edit: June 04, 2015, 04:17:50 PM by GIminer
 #8842

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
Sr. Member
****
Offline Offline

Activity: 255
Merit: 250


View Profile
June 04, 2015, 03:46:25 PM
 #8843

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/btcd

I 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
Full Member
***
Offline Offline

Activity: 155
Merit: 102


View Profile
June 04, 2015, 04:11:42 PM
 #8844

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
Hero Member
*****
Offline Offline

Activity: 552
Merit: 500


View Profile
June 04, 2015, 05:03:43 PM
 #8845

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.

▄███▄
███████▄
██████▀██▄
█████▄  ▀██▄
████▀  ▄  ▀██▄
███▄ ▄██▀   ▀
██████▀  ▄█▄
███████▄█████▄
███████████████▄
████████████████▀
█████████▀
███████▀
 ▀███▀
Safein     
.M A K E   I S I M P L E.
A   R E V O L U T I O N A R Y   W A Y   T O   P A Y   O N L I N E
.
[WHITEPAPER]
▬▬▬▬▬▬▬▬▬▬▬▬▬▬

██
██
██
██
██
██
██
██
██
██
██
▄█████████████████████████▄
███████████████████████████
████████████████▀░░░░░▐████
███████████████░░░░░░░▐████
██████████████▌░░░▐████████
██████████████▌░░░▐████████
███████████░░░░░░░░░░░█████
███████████░░░░░░░░░░▐█████
██████████████▌░░░▐████████
██████████████▌░░░▐████████
██████████████▌░░░▐████████
██████████████▌░░░▐████████
▀█████████████▌░░░▐███████▀

██
██
██
██
██
██
██
██
██
██
██
▄█████████████████████████▄
███████████████████████████
███████████████████████████
██████▀███████▀░░░▀▀▀▄█████
█████▌░░▀▀███▌░░░░░░░▄█████
█████▀░░░░░░░░░░░░░░░██████
█████▄░░░░░░░░░░░░░░███████
██████▄░░░░░░░░░░░░████████
███████▄▄░░░░░░░░▄█████████
██████▄░░░░░░░▄████████████
███████████████████████████
███████████████████████████
▀█████████████████████████▀

██
██
██
██
██
██
██
██
██
██
██
▄█████████████████████████▄
███████████████████████████
███████████████████████████
██████████████████▀▀███████
█████████████▀▀▀░░░░███████
████████▀▀▀░░░▄▀░░░████████
█████▄░░░░░▄█▀░░░░░████████
████████▄░█▀░░░░░░█████████
█████████▌▐░░░░░░░█████████
██████████░▄██▄░░██████████
████████████████▄██████████
███████████████████████████
▀█████████████████████████▀

██
██
██
██
██
██
██
██
██
██
██
A
▬▬

█▄▄
██████▄▄
██████████▄▄
██████████████▄▄
██████████████████▄▄
█████████████████████
██████████████████▀▀
██████████████▀▀
██████████▀▀
██████▀▀
█▀▀
.GET IT ON               
Google Play
CrimsonPermanentAssurance
Full Member
***
Offline Offline

Activity: 155
Merit: 102


View Profile
June 04, 2015, 05:18:50 PM
Last edit: June 04, 2015, 05:36:39 PM by CrimsonPermanentAssurance
 #8846

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
Sr. Member
****
Offline Offline

Activity: 255
Merit: 250


View Profile
June 04, 2015, 05:31:44 PM
 #8847

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
Full Member
***
Offline Offline

Activity: 155
Merit: 102


View Profile
June 04, 2015, 05:47:01 PM
Last edit: June 04, 2015, 07:42:50 PM by CrimsonPermanentAssurance
 #8848

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
Hero Member
*****
Offline Offline

Activity: 577
Merit: 500


View Profile
June 04, 2015, 05:51:46 PM
 #8849

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  Smiley
CrimsonPermanentAssurance
Full Member
***
Offline Offline

Activity: 155
Merit: 102


View Profile
June 04, 2015, 06:05:12 PM
 #8850


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.
ASICHEAD
Hero Member
*****
Offline Offline

Activity: 552
Merit: 500


View Profile
June 04, 2015, 06:27:04 PM
 #8851


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.
Don't worry,this is no problem.
today,I create the new wallet for test and I experiencing the same thing. but now wallet is synced and work very well.

▄███▄
███████▄
██████▀██▄
█████▄  ▀██▄
████▀  ▄  ▀██▄
███▄ ▄██▀   ▀
██████▀  ▄█▄
███████▄█████▄
███████████████▄
████████████████▀
█████████▀
███████▀
 ▀███▀
Safein     
.M A K E   I S I M P L E.
A   R E V O L U T I O N A R Y   W A Y   T O   P A Y   O N L I N E
.
[WHITEPAPER]
▬▬▬▬▬▬▬▬▬▬▬▬▬▬

██
██
██
██
██
██
██
██
██
██
██
▄█████████████████████████▄
███████████████████████████
████████████████▀░░░░░▐████
███████████████░░░░░░░▐████
██████████████▌░░░▐████████
██████████████▌░░░▐████████
███████████░░░░░░░░░░░█████
███████████░░░░░░░░░░▐█████
██████████████▌░░░▐████████
██████████████▌░░░▐████████
██████████████▌░░░▐████████
██████████████▌░░░▐████████
▀█████████████▌░░░▐███████▀

██
██
██
██
██
██
██
██
██
██
██
▄█████████████████████████▄
███████████████████████████
███████████████████████████
██████▀███████▀░░░▀▀▀▄█████
█████▌░░▀▀███▌░░░░░░░▄█████
█████▀░░░░░░░░░░░░░░░██████
█████▄░░░░░░░░░░░░░░███████
██████▄░░░░░░░░░░░░████████
███████▄▄░░░░░░░░▄█████████
██████▄░░░░░░░▄████████████
███████████████████████████
███████████████████████████
▀█████████████████████████▀

██
██
██
██
██
██
██
██
██
██
██
▄█████████████████████████▄
███████████████████████████
███████████████████████████
██████████████████▀▀███████
█████████████▀▀▀░░░░███████
████████▀▀▀░░░▄▀░░░████████
█████▄░░░░░▄█▀░░░░░████████
████████▄░█▀░░░░░░█████████
█████████▌▐░░░░░░░█████████
██████████░▄██▄░░██████████
████████████████▄██████████
███████████████████████████
▀█████████████████████████▀

██
██
██
██
██
██
██
██
██
██
██
A
▬▬

█▄▄
██████▄▄
██████████▄▄
██████████████▄▄
██████████████████▄▄
█████████████████████
██████████████████▀▀
██████████████▀▀
██████████▀▀
██████▀▀
█▀▀
.GET IT ON               
Google Play
CrimsonPermanentAssurance
Full Member
***
Offline Offline

Activity: 155
Merit: 102


View Profile
June 04, 2015, 07:37:51 PM
 #8852

Quote

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


So, you are suggesting that those two lines simply be deleted from the suggested code at the beginning of this thread in the OP?

Is it true that I don't need those two lines in my .conf?

Can I can simply remake my .conf file without them, overwrite my original .conf file and go back to business as usual without making any other changes or needing to reinstall my wallet?
BTCDDev
Sr. Member
****
Offline Offline

Activity: 255
Merit: 250


View Profile
June 04, 2015, 07:48:37 PM
 #8853

Quote

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


So, you are suggesting that those two lines simply be deleted from the suggested code at the beginning of this thread in the OP?

Is it true that I don't need those two lines in my .conf?

Can I can simply remake my .conf file without them, overwrite my original .conf file and go back to business as usual without making any other changes or needing to reinstall my wallet?


Open your BitcoinDark.conf, delete rpcuser and rpcpassword, take out server=1, and save it. Then restart BitcoinDark.

BitcoinDark: RPHWc5CwP9YMMbvXQ4oXz5rQHb3pKkhaxc
Top Donations: juicybirds 420BTCD ensorcell 84BTCD Stuntruffle: 40BTCD
Top April Donations: juicybirds 420BTCD; ensorcell: 42BTCD
CrimsonPermanentAssurance
Full Member
***
Offline Offline

Activity: 155
Merit: 102


View Profile
June 04, 2015, 07:57:38 PM
 #8854

Quote

Open your BitcoinDark.conf, delete rpcuser and rpcpassword, take out server=1, and save it. Then restart BitcoinDark.

Thank you, Matthew!

Azeh, I will update the how-to for Macintosh to reflect this. I will also mention what to do if the user wishes to use RPC.

Maybe don't post it yet until I do that tonight.
CrimsonPermanentAssurance
Full Member
***
Offline Offline

Activity: 155
Merit: 102


View Profile
June 04, 2015, 08:01:38 PM
 #8855

Last question from me for a bit:

Does anyone know the most recent version of the Macintosh wallet?

I downloaded this version from the official website yesterday... v1.0.0.0-g32a928e

It seems like the same one I was using a while ago, and I just want to make sure I am on the most recent version, as well as make sure the website links to the most recent version.

Is v1.0.0.0-g32a928e the most recent Macintosh wallet version?
GIminer
Newbie
*
Offline Offline

Activity: 59
Merit: 0


View Profile
June 04, 2015, 08:39:20 PM
 #8856

Last question from me for a bit:

Does anyone know the most recent version of the Macintosh wallet?

I downloaded this version from the official website yesterday... v1.0.0.0-g32a928e

It seems like the same one I was using a while ago, and I just want to make sure I am on the most recent version, as well as make sure the website links to the most recent version.

Is v1.0.0.0-g32a928e the most recent Macintosh wallet version?

Sorry, I cannot talk about the Mac wallet, but on Windows v1.0.0.0-g32a928e it's lastest (or at least last time I checked, and is the one that I'm running without any problem since 27/05).
BTCDDev
Sr. Member
****
Offline Offline

Activity: 255
Merit: 250


View Profile
June 04, 2015, 08:51:59 PM
 #8857

The wallet is not sync how to do

Hi,

Sorry you are having this problem. Try deleting peers.dat from your BitcoinDark folder and restarting BitcoinDark. If that doesn't work, you may have to delete everything in the folder except wallet.dat and BitcoinDark.conf and let it resync.

Matthew

BitcoinDark: RPHWc5CwP9YMMbvXQ4oXz5rQHb3pKkhaxc
Top Donations: juicybirds 420BTCD ensorcell 84BTCD Stuntruffle: 40BTCD
Top April Donations: juicybirds 420BTCD; ensorcell: 42BTCD
SHossain
Member
**
Offline Offline

Activity: 112
Merit: 10


View Profile
June 04, 2015, 09:10:22 PM
 #8858

ExploreBTCD block explorer's database now syncing slowly. Sorry for the issues going on, but I'm working hard to get it fully working asap. Please find the BTCD Top 500 rich list here https://techloverhd.com/2015/06/bitcoindark-rich-list-top-500/ this is updated to the latest block.
ASICHEAD
Hero Member
*****
Offline Offline

Activity: 552
Merit: 500


View Profile
June 04, 2015, 09:24:53 PM
 #8859

The wallet is not sync how to do
If your first time to use this wallet and you don't have a .conf file
1. open a notepad file.
2. copy this codes to clipboard and past to notepad 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
addnode=192.99.203.53
addnode=198.50.152.135
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


3. save notepad file with name BitcoinDark.conf (you should save file as type all files, not as type text documents).
4. you should past this file in C:\users\your user folder\App Data\BitcoinDark
5. you should restart your wallet and wait for wallet syncing.

▄███▄
███████▄
██████▀██▄
█████▄  ▀██▄
████▀  ▄  ▀██▄
███▄ ▄██▀   ▀
██████▀  ▄█▄
███████▄█████▄
███████████████▄
████████████████▀
█████████▀
███████▀
 ▀███▀
Safein     
.M A K E   I S I M P L E.
A   R E V O L U T I O N A R Y   W A Y   T O   P A Y   O N L I N E
.
[WHITEPAPER]
▬▬▬▬▬▬▬▬▬▬▬▬▬▬

██
██
██
██
██
██
██
██
██
██
██
▄█████████████████████████▄
███████████████████████████
████████████████▀░░░░░▐████
███████████████░░░░░░░▐████
██████████████▌░░░▐████████
██████████████▌░░░▐████████
███████████░░░░░░░░░░░█████
███████████░░░░░░░░░░▐█████
██████████████▌░░░▐████████
██████████████▌░░░▐████████
██████████████▌░░░▐████████
██████████████▌░░░▐████████
▀█████████████▌░░░▐███████▀

██
██
██
██
██
██
██
██
██
██
██
▄█████████████████████████▄
███████████████████████████
███████████████████████████
██████▀███████▀░░░▀▀▀▄█████
█████▌░░▀▀███▌░░░░░░░▄█████
█████▀░░░░░░░░░░░░░░░██████
█████▄░░░░░░░░░░░░░░███████
██████▄░░░░░░░░░░░░████████
███████▄▄░░░░░░░░▄█████████
██████▄░░░░░░░▄████████████
███████████████████████████
███████████████████████████
▀█████████████████████████▀

██
██
██
██
██
██
██
██
██
██
██
▄█████████████████████████▄
███████████████████████████
███████████████████████████
██████████████████▀▀███████
█████████████▀▀▀░░░░███████
████████▀▀▀░░░▄▀░░░████████
█████▄░░░░░▄█▀░░░░░████████
████████▄░█▀░░░░░░█████████
█████████▌▐░░░░░░░█████████
██████████░▄██▄░░██████████
████████████████▄██████████
███████████████████████████
▀█████████████████████████▀

██
██
██
██
██
██
██
██
██
██
██
A
▬▬

█▄▄
██████▄▄
██████████▄▄
██████████████▄▄
██████████████████▄▄
█████████████████████
██████████████████▀▀
██████████████▀▀
██████████▀▀
██████▀▀
█▀▀
.GET IT ON               
Google Play
4emily
Hero Member
*****
Offline Offline

Activity: 577
Merit: 500


View Profile
June 05, 2015, 01:42:38 AM
 #8860

Following the earlier reinstallation of the wallet it's now fully synched but, as per earlier posts, the database file is still not updating.  Huh





However, as it was doing prior to the resynch, the wallet itself continues to work properly, including staking, mining, and sending/receiving.




So basically I've gone round in a circle and ended up where I started off.

Is anyone-else experiencing the same phenomenon? - A db file that doesn't update but the wallet nevertheless functioning ok?

Any advice what to do next?

Thanks again for any help  Smiley
Pages: « 1 ... 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 [443] 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 ... 551 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!