Topic: BTCD is no more - page 109. (Read 1328507 times)

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.

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.

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

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).

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?

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.

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

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?

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.

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.

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  

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.

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

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.

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!

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.

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

you're welcome