BTCD is no more

[ASICHEAD]

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.

[1714789645]

1714789645

[1714789645]

1714789645

[1714789645]

1714789645

[1714789645]

1714789645

[1714789645]

1714789645

[CrimsonPermanentAssurance]

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]

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.

[CrimsonPermanentAssurance]

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]

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]

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]

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

[SHossain]

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]

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.

[4emily]

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





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  

[CrimsonPermanentAssurance]

It sounds like there is no problem if everything is working fine.

[co5hike]

It sounds like there is no problem if everything is working fine.

Yeap, people just like to blow things out of proportion. BTCD is stronger now then ever.

[4emily]

It sounds like there is no problem if everything is working fine.

Thanks - I hope you're right. 

I'll leave it on the basis that at least the devs are aware of it and if it's to do with a server side problem they'll no doubt be dealing with it shortly.

Yeap, people just like to blow things out of proportion. BTCD is stronger now then ever.

You're right of course - some people do like doing that and, from the tech point of view, BTCD is indeed stronger than ever. The price will, I'm sure, soon be fully reflecting that.

btw, I should mention that I've invested what for me is a lot of money in BTCD, hence my concern.

I'd encourage anyone experiencing problems with their wallets to ask for help on the forum. There's always someone willing to help.

[BTCDDev]

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

I haven't spent much time reading the btc code appending the blockchain file so this is my guess as to what's going on, but I've spent plenty of time reading from the file directly.

blk00001.dat is just a file with accepted blocks laid out in sequence. i.e. block0_bits->block1_bits->block2_bits->...

You say that you are synced up now. Would you want the blockchain file to append every block it sees? Probably not, especially after what just happened with all the syncing issues. You'd probably choose to let the chain build for a while before appending a block to the file on disk, to eliminate the risk of a block being rejected later.

In short, it's probably just waiting for 110 confirms to write the latest blocks to disk.

Any advice what to do next?

Hodl for liftoff

Matthew

[4emily]

Thanks - it's the database file (or maybe I should call it folder) that's not updating:



As you see, it's still showing 'Date modified' as 04-Jun-15 2:21PM (which was the date/time I installed the new wallet).

As I understand it, it should be updating like, for example, the blk0001.dat and wallet.dat files are doing.

[Azeh]

Thanks - it's the database file (or maybe I should call it folder) that's not updating:



As you see, it's still showing 'Date modified' as 04-Jun-15 2:21PM (which was the date/time I installed the new wallet).

As I understand it, it should be updating like, for example, the blk0001.dat and wallet.dat files are doing.

Open the Database folder.  There should be a file in there.  Is that file updating?

[CrimsonPermanentAssurance]

I imagine it likely is.

[4emily]

Open the Database folder.  There should be a file in there.  Is that file updating?

I imagine it likely is.

It is

Thanks

[CrimsonPermanentAssurance]

Open the Database folder.  There should be a file in there.  Is that file updating?

I imagine it likely is.

It is

Thanks

Your wallet is (and has been) working perfectly. You should be nothing but smiles.

[4emily]

Your wallet is (and has been) working perfectly. You should be nothing but smiles.

Indeed I am and as further proof of my wallet's perfect functioning, the date/time of the database folder updated (for the 1st time) as I was opening the wallet a few minutes ago:






Curiously, however, when I opened the db folder I found that another file (log.0000000002) had been added:







Viewed from my new panglossian perspective on all things to do with my BTCD wallet, I'm sure that's a good thing