BTCD is no more

[CrimsonPermanentAssurance]

Ok new question, how do I get the QT to connect to the network?

I have had the Safari problem (though I didn't realize that would cause the problem until your posts). I am going to try to get the QT up, and if I get that far, I will probably be able to help you set up the conf file. Stand by. Also, thanks for posting. You might have just fixed the major hurdle I have been dealing with.

[CrimsonPermanentAssurance]

Ok new question, how do I get the QT to connect to the network?

Wow, for the first time in months, I am looking at a BTCD wallet open on a Mac! You have just posted something very important to all Mac users. Also, thanks to the person who posted that this didn't work in Safari. The original download appears to be essential that it be done in Firefox. It DOES NOT WORK when downloaded through Safari. Let me work a bit on getting the conf file up, and then I will post how to get that working for you.

[CrimsonPermanentAssurance]

Now, I have questions. Thanks to some recent posts and downloading the Mac wallet through Firefox (the one linked all the way back on page 1 of this thread), I am, for the first time, watching a BTCD wallet open on a Mac.

It does not appear to be synching, however, or connecting to any nodes.

Upon saving a text file with the original conf posted on page 1 of this thread, naming it BitcoinDark.conf, and putting it in the Application Support/BitcoinDark folder, BTCD app gives me an error when trying to open and then won't open.

Upon deleting that file, the wallet opens again, but it does not synch or connect to any nodes.

Upon looking at the version # in the debug window, I see BitcoinDark-Qt version v1.0.0.0-g32a928e.

Questions:

Is the correct version for Mac posted on page 1 of this thread? Again, it is BitcoinDark-Qt version v1.0.0.0-g32a928e

Is the BitcoinDark.conf text file I saved supposed to be nested deeper in the Application Support/BitcoinDark folder? Just so people can see what was in that text file, these are the exact contents I pasted in there:

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

After removing the offending BitcoinDark.conf text file I saved in Application Support/BitcoinDark folder, here is what I see when I open the Application Support/BitcoinDark folder:

blk0001.dat
A folder titled "database" and in that folder is a file titled "log.0000000001"
db.log
debug.log
peers.dat
A folder titled "txleveldb" and in that folder are the following files: 000005.sst, 000006.log, CURRENT, LOCK, LOG, LOG.old, and MANIFEST-000004
wallet.dat

Can someone please help me and the other people on here with specific instructions on how to save the .conf file, what EXACTLY to paste into it, what to call it, and where EXACTLY to put it so that we can synch?

Also, it would be nice to have a link to the most recent Mac wallet if the one on page 1 of this thread isn't the most current Mac wallet.

Thanks in advance from ALL Mac users for any help.

James, I feel we made significant headway with the realization that anyone downloading the wallet with Safari will end up with a dead duck. It needs to be downloaded with Firefox. I have listed all files and directories created above when the wallet actually does open. Now, if you can deliver us the last bit of info we need to synch, it would be greatly appreciated, as my coins have been stuck on exchanges for months (because I had nowhere else to send them), and I have yet to experience the thrill of staking. Your spending a little time on this will help ALL Mac users who have had continual problems, and will most likely lead to even greater support from that entire community for solving this problem. PLUS, I will write a detailed and simple how-to for all Mac users. Your help would really be appreciated. Thanks!

[jl777]

Now, I have questions. Thanks to some recent posts and downloading the Mac wallet through Firefox (the one linked all the way back on page 1 of this thread), I am, for the first time, watching a BTCD wallet open on a Mac.

It does not appear to be synching, however, or connecting to any nodes.

Upon saving a text file with the original conf posted on page 1 of this thread, naming it BitcoinDark.conf, and putting it in the Application Support/BitcoinDark folder, BTCD app gives me an error when trying to open and then won't open.

Upon deleting that file, the wallet opens again, but it does not synch or connect to any nodes.

Upon looking at the version # in the debug window, I see BitcoinDark-Qt version v1.0.0.0-g32a928e.

Questions:

Is the correct version for Mac posted on page 1 of this thread? Again, it is BitcoinDark-Qt version v1.0.0.0-g32a928e

Is the BitcoinDark.conf text file I saved supposed to be nested deeper in the Application Support/BitcoinDark folder? Just so people can see what was in that text file, these are the exact contents I pasted in there:

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

After removing the offending BitcoinDark.conf text file I saved in Application Support/BitcoinDark folder, here is what I see when I open the Application Support/BitcoinDark folder:

blk0001.dat
A folder titled "database" and in that folder is a file titled "log.0000000001"
db.log
debug.log
peers.dat
A folder titled "txleveldb" and in that folder are the following files: 000005.sst, 000006.log, CURRENT, LOCK, LOG, LOG.old, and MANIFEST-000004
wallet.dat

Can someone please help me and the other people on here with specific instructions on how to save the .conf file, what EXACTLY to paste into it, what to call it, and where EXACTLY to put it so that we can synch?

Also, it would be nice to have a link to the most recent Mac wallet if the one on page 1 of this thread isn't the most current Mac wallet.

Thanks in advance from ALL Mac users for any help.

James, I feel we made significant headway with the realization that anyone downloading the wallet with Safari will end up with a dead duck. It needs to be downloaded with Firefox. I have listed all files and directories created above when the wallet actually does open. Now, if you can deliver us the last bit of info we need to synch, it would be greatly appreciated, as my coins have been stuck on exchanges for months (because I had nowhere else to send them), and I have yet to experience the thrill of staking. Your spending a little time on this will help ALL Mac users who have had continual problems, and will most likely lead to even greater support from that entire community for solving this problem. Your help would really be appreciated. Thanks!

"/Users/<yourusername>/Library/Application Support/BitcoinDark"

The above is the directory
The following is a BitcoinDark.conf file that works for me:

Code:

rpcport=14632
port=14631
daemon=1
server=1
addnode=107.170.59.196
addnode=146.185.188.6
txindex=1

I also had some problems at first, but with the two addnode lines it cleared right up. Now I have a peers.dat so maybe these addnode are not active. i think the key is to find a few solid nodes to solve this and the community public privacyServers will permanently solve issues like this

Safari is broken for some reason, we need to warn people about that

James

[id10tothe9]

Ok new question, how do I get the QT to connect to the network?

Wow, for the first time in months, I am looking at a BTCD wallet open on a Mac! You have just posted something very important to all Mac users. Also, thanks to the person who posted that this didn't work in Safari. The original download appears to be essential that it be done in Firefox. It DOES NOT WORK when downloaded through Safari. Let me work a bit on getting the conf file up, and then I will post how to get that working for you.

I used Chrome to download mine, it works there too.

[id10tothe9]

..
So, just to be clear, this is what you are telling me to try:

1. Open a blank text file.

2. Paste this exact code into the blank text file:

rpcport=14632
port=14631
daemon=1
server=1
addnode=107.170.59.196
addnode=146.185.188.6
txindex=1

3. Save that text file with the exact name "BitcoinDark.conf" and place it in the directory "/Users/<yourusername>/Library/Application Support/BitcoinDark"

..

but make sure it's not saved as a text file, you do that by choosing save as, and then from the drop down menu, choose all files instead of text file. you can verify that by looking at the file on the folder, shouldn't be like a text file and when you double click it does not use the Text Editor automatically.
sometimes it still saves it as a text file, then you need to create a new one from the "file" button of the already opened text and repeat the process.

edit: I did the same now since I had too many rejected blocks. I noticed you should still add a username and password (random values, not same as your wallet password) then it works. Also I think you can use vim from the terminal to create the file and save it as .conf

[id10tothe9]

sorry answered in the edit above:
edit: I did the same now since I had too many rejected blocks. I noticed you should still add a username and password (random values, not same as your wallet password) then it works. Also I think you can use vim from the terminal to create the file and save it as .conf

does that solve the problem?

[CrimsonPermanentAssurance]

sorry answered in the edit above:
edit: I did the same now since I had too many rejected blocks. I noticed you should still add a username and password (random values, not same as your wallet password) then it works. Also I think you can use vim from the terminal to create the file and save it as .conf

does that solve the problem?

So, upon following the above procedure, when I try to open the wallet, I get:

BitcoinDark-Qt quit unexpectedly.

This doesn't happen when I remove the "homemade" BitcoinDark.conf file I created with text editor and then renamed to BitcoinDark.conf out of the application support/BitcoinDark folder.

With that file removed, the wallet opens but does not synch.

Is using the text editor the correct way to make the .conf file?

Also, at least I now have the wallet opening without the .conf file, which is more than I have ever been able to do. Can the .conf file be created from within the console? I can now access the console for the first time, so I have that going for me.

If it can be created from the console, what do I type and where do I type it to make it work?

Also, I was able to rename the .rtf file with a different extension, .conf, from the "get info" section of the .conf text file, but whenever I go to open the BitcoinDark.conf file it opens text editor. There is no "save as" option. Only a "save" option, so the only way to rename the file I have found to BitcoinDark.conf instead of BitcoinDark.rtf is by doing a "get info" on the file and renaming it to BitcoinDark.conf from there. Then, the filename and extension appear to change. Then I still get the BTCD Quit error upon trying to open the BTCD app. Is there a better program I should be using to make the .conf file?

[CrimsonPermanentAssurance]

"Also I think you can use vim from the terminal to create the file and save it as .conf"

Sorry for being a bit daft, but what would I type in the terminal to do the above?

I don't understand what you mean in the above quote (and most Mac users probably won't understand either).

How about this? I will write up a beautiful, perfectly-described process that helps all Mac users everywhere with BTCD if someone can describe the exact procedure, exact code, and exact text to paste into a .conf file, including the exact procedure to save that file.

If someone gets me working, I will happily do that for the community. I have been trying for months.

[jl777]

"Also I think you can use vim from the terminal to create the file and save it as .conf"

Sorry for being a bit daft, but what would I type in the terminal to do the above?

I don't understand what you mean in the above quote (and most Mac users probably won't understand either).

How about this? I will write up a beautiful, perfectly-described process that helps all Mac users everywhere with BTCD if someone can describe the exact procedure, exact code, and exact text to paste into a .conf file, including the exact procedure to save that file.

If someone gets me working, I will happily do that for the community. I have been trying for months.

you might need a rpcusername and password

Code:

rpcuser=user
rpcpassword=password
rpcport=14632
port=14631
daemon=1
server=1
addnode=107.170.59.196
addnode=146.185.188.6
txindex=1

copy the above
open a terminal in the Mac
type
cat > BitcoinDark.conf
<paste command>
control-d

now you have a pure text file and this is exactly the .conf file I have that is working fine, other than the user/password
for testing you can even leave that
make sure the filename is exact

[id10tothe9]

+1, better than vim

[CrimsonPermanentAssurance]

"Also I think you can use vim from the terminal to create the file and save it as .conf"

Sorry for being a bit daft, but what would I type in the terminal to do the above?

I don't understand what you mean in the above quote (and most Mac users probably won't understand either).

How about this? I will write up a beautiful, perfectly-described process that helps all Mac users everywhere with BTCD if someone can describe the exact procedure, exact code, and exact text to paste into a .conf file, including the exact procedure to save that file.

If someone gets me working, I will happily do that for the community. I have been trying for months.

you might need a rpcusername and password

Code:

rpcuser=user
rpcpassword=password
rpcport=14632
port=14631
daemon=1
server=1
addnode=107.170.59.196
addnode=146.185.188.6
txindex=1

copy the above
open a terminal in the Mac
type
cat > BitcoinDark.conf
<paste command>
control-d

now you have a pure text file and this is exactly the .conf file I have that is working fine, other than the user/password
for testing you can even leave that
make sure the filename is exact

Okay, I will try that when I get back from a quick bite. I will let you know if it worked soon. Thanks for the help!

[bitkokos]

How can I see how many btcd I have in my wallet address without looking in my wallet?
eg through block explorer.
I found 3 block explorers. 1 is not working and two do not show my address, only transactions etc.
I just want it to check "mined" btcd from staking while I am not at home

thanks

[CrimsonPermanentAssurance]

James,

Here is what you said to do:

rpcuser=user
rpcpassword=password
rpcport=14632
port=14631
daemon=1
server=1
addnode=107.170.59.196
addnode=146.185.188.6
txindex=1

copy the above
open a terminal in the Mac
type
cat > BitcoinDark.conf
<paste command>
control-d

So, I opened a terminal and tried to follow your directions and nothing happened. I believe the issue might be with the directions.

Do I hit return anywhere?

Do I paste the command after hitting return?

Do I hold down the control key and then press the letter "d" (doing that just makes a "^d" appear in the pasted code).

Or do I type the words "control-d" after pasting the command and hitting return?

Could you please update your directions to include wherever you might hit return, as well as tell me where the file will be after doing all this?

Please assume the audience knows absolutely nothing about using the terminal.

[jl777]

James,

Here is what you said to do:

rpcuser=user
rpcpassword=password
rpcport=14632
port=14631
daemon=1
server=1
addnode=107.170.59.196
addnode=146.185.188.6
txindex=1

copy the above
open a terminal in the Mac
type
cat > BitcoinDark.conf
<paste command>
control-d

So, I opened a terminal and tried to follow your directions and nothing happened. I believe the issue might be with the directions.

Do I hit return anywhere?

Do I paste the command after hitting return?

Do I hold down the control key and then press the letter "d" (doing that just makes a "^d" appear in the pasted code).

Or do I type the words "control-d" after pasting the command and hitting return?

Could you please update your directions to include wherever you might hit return, as well as tell me where the file will be after doing all this?

Please assume the audience knows absolutely nothing about using the terminal.

copy means to use the mouse to select the text and do a copy command to get it in the clipboard

cat > BitcoinDark.conf<return>
<paste command><return>
<control-d key>

the control-d is to hold down the control key and press 'd' at the same time

[jl777]

the debugging went pretty smooth so far. after a few silly errors one node sent a UDP API to another, the other node got it, but it was a bit confused and the sending node crashed

not bad for first time test of new code, so hopefully all the onion layering is ported properly.

over the months the API tokenization has gotten a bit confusing, so it is time to clean that up and make it easy for debugging the application level state machines. This is routine work and requiring of no magic, but it still has to be done. So after some nice meal and latte I will get this done and hope to be able to announce later tonight some success of inter-node comms using SuperNET API protocol.

this is using the public IP disclosed privacyServers, so the probabilistic stuff is for after the easy routing is stable.

once BTCDdev gets me the few changes, then it should be ready for larger scale testing, but we need to verify that the packet traffic is under control first.

As soon as these system level issues are done, then while it is being tested, I can finalize the application level code, eg. Teleport.

James

[positivehigh]

James is too active again. Looks like its really near... Hodl on your breath...

[CrimsonPermanentAssurance]

copy means to use the mouse to select the text and do a copy command to get it in the clipboard

cat > BitcoinDark.conf<return>
<paste command><return>
<control-d key>

the control-d is to hold down the control key and press 'd' at the same time

Holy Bjeezy, it's working!

Sorry, James. You might think I am a total idiot for asking so many questions. For some reason, I wasn't having a .conf file made by the terminal, but on the third try in terminal, it finally appeared.

Anyhow, THANK YOU for hanging in there with me!

Also, it took a while leaving it open to start synching, but it's finally synching.

IT'S ALIVE!!!

I will post a how-to tonight.

Three last questions:

Question 1: There are a LOT more nodes listed in the .conf code given on page 1 of this thread, however, mine appears to be working with the simpler code you gave me above with just two nodes added. Is it the more nodes listed the merrier (as in I should also add those other nodes), or will I be fine with the simpler version you gave me?

Question 2: Your simpler code you just gave me ends with the line "txindex=1," a line which is nowhere to be found in the original code on page 1 of this thread. Is that line important, and should it be added to the original code on page 1 of this thread?

Question 3: Is the Mac wallet link on page 1 of this thread the most recent Mac wallet available? I want to make sure if I start sending myself coins from exchanges that I actually get them.

[jl777]

copy means to use the mouse to select the text and do a copy command to get it in the clipboard

cat > BitcoinDark.conf<return>
<paste command><return>
<control-d key>

the control-d is to hold down the control key and press 'd' at the same time

Holy Bjeezy, it's working!

Sorry, James. You might think I am a total idiot for asking so many questions. For some reason, I wasn't having a .conf file made by the terminal, but on the third try in terminal, it finally appeared.

Anyhow, THANK YOU for hanging in there with me!

Also, it took a while leaving it open to start synching, but it's finally synching.

IT'S ALIVE!!!

I will post a how-to tonight.

Three last questions:

Question 1: There are a LOT more nodes listed in the .conf code given on page 1 of this thread, however, mine appears to be working with the simpler code you gave me above with just two nodes added. Is it the more nodes listed the merrier (as in I should also add those other nodes), or will I be fine with the simpler version you gave me?

Question 2: Your simpler code you just gave me ends with the line "txindex=1," a line which is nowhere to be found in the original code on page 1 of this thread. Is that line important, and should it be added to the original code on page 1 of this thread?

Question 3: Is the Mac wallet link on page 1 of this thread the most recent Mac wallet available? I want to make sure if I start sending myself coins from exchanges that I actually get them.

A1: more nodes is better, unless some of the additional nodes are giving conflicting info, then it would make it take longer to sync up. I think the best is to start with a few and then add some more little by little if it isnt syncing with the few.

A2: txindex is not actually supported, you can leave that out, I just have it out of habit from other coins

A3: I do not know if the Mac version is changed. I dont think so, my version is v1.0.0.0-g32a928e
As long as you have the wallet.dat (make backups!!) then your coins are on the blockchain and regardless of version you will be able to get the coins. To be safe, you can do:

dumpprivkey <address>

in the debug console. <address> is of course the BTCD address. This will give you a bunch of random letters/numbers. This is the magic that allows access to your funds! Keep it super safe. If you are dealing with large amounts, making a print out, or take a pic with enough resolution so you can always recover it. Then make sure you keep super safe the image with your private key

James

[CrimsonPermanentAssurance]

A1: more nodes is better, unless some of the additional nodes are giving conflicting info, then it would make it take longer to sync up. I think the best is to start with a few and then add some more little by little if it isnt syncing with the few.

A2: txindex is not actually supported, you can leave that out, I just have it out of habit from other coins

A3: I do not know if the Mac version is changed. I dont think so, my version is v1.0.0.0-g32a928e
As long as you have the wallet.dat (make backups!!) then your coins are on the blockchain and regardless of version you will be able to get the coins. To be safe, you can do:

dumpprivkey <address>

in the debug console. <address> is of course the BTCD address. This will give you a bunch of random letters/numbers. This is the magic that allows access to your funds! Keep it super safe. If you are dealing with large amounts, making a print out, or take a pic with enough resolution so you can always recover it. Then make sure you keep super safe the image with your private key

James

You rock. Thanks for getting us less code savvy people running smoothly. It is greatly appreciated.