BBQCoin Wallet not working

[KCK402]

My BBQCoin wallet says out of sync. It has said this for many hours, any ideas?

-KCK

[1715481682]

1715481682

[1715481682]

1715481682

[Jakewell]

Mine is working pefectly,

all your other wallets are fine?

[Tittiez]

BBQCoin network has almost 400,000 blocks, catching up may take awhile.

Now if we had an online wallet service...

[KCK402]

K. Now it is Synchronizing. Can I accept BBQCoin while it is Synchronizing?

[Jakewell]

the other time i saw a link to download all the BBQ blockchain

[Jakewell]

K. Now it is Synchronizing. Can I accept BBQCoin while it is Synchronizing?

Yeah, of course

[odkrywca]

K. Now it is Synchronizing. Can I accept BBQCoin while it is Synchronizing?

My is still out of sync...

[KCK402]

K. Now it is Synchronizing. Can I accept BBQCoin while it is Synchronizing?

My is still out of sync...

Yeah. same here

[Jakewell]

I will upload the blockchain, so you can download it more fast

[Jakewell]

this is the entire blockchain, in direct fast download

http://www.filedropper.com/newfolder_17

[gotforce]

Add addnode=90.213.198.236 to your .conf file and restart your client

[CaptChadd]

A recent blockchain download will be added to blog.bbqcoin.org.

Do not download a blockchain from other sources, its bad practice and has always known to be since Bitcoin started.

[destruct]

I see what everyone means.. the wallet never connects to the network

[markm]

Are there any well financed major stakeholders-for-the-long-term who will commit to maintaining one or more "stable nodes" 24/7/365.25 for at least the next few years?

The main cause of this problem, for any coin, is the "stable nodes" coded into the software were fly-by-night nodes that no longer exist or no longer have the same IP address, and fly-by-night hostnames that have not been kept up to date in the sense of always resolving to the IP address of an up and running node powerful enough to handle providing large numbers of new users with their initial blockchains all at once 24/7 at reasonable speeds.

Once even just a few such nodes have been identified and coded into the code, everything works fine until they start flying-by-night, which quite possibly tends itself to be motivated by economics: in short they are not being paid enough for the cost of providing and maintaining a stable node to continue to seem worthwhile to them. (Or they are just lazy goldbrickers or outright scammers/crooks...)

In DeVCoin we attempted to solve this problem by paying admins to run such nodes, but even then some folk evidently preferred to just pocket the pay and let the nodes they were being paid to run die. So it might not be an easy problem.

Possibly if all the coins that try to use the LFNET IRC network were to pay the operators of that IRC network, that IRC network might not go down so much, thus the coins would not have to keep trying to fall back on their hard-coded DNS-seed and IP-number fallback nodes, so it would matter less that such fallback nodes seem to like to have flown by night by the time people actually start having to try to fall back to them.

-MarkM-

[destruct]

Add addnode=90.213.198.236 to your .conf file and restart your client

That didn't do anything :/

[master-P]

Add addnode=90.213.198.236 to your .conf file and restart your client

That didn't do anything :/

Add all of these nodes too it'll work:

62.163.9.155:19323
217.22.80.138:19323
217.122.176.76:19323
78.52.33.95:53565
58.60.1.24:61900
210.84.1.23:19323
216.58.23.148:19323
94.195.209.96:19323
85.11.153.119:19323
86.157.191.43:19323
81.3.189.155:19323
69.158.170.114:19323
80.74.157.31:19323

[destruct]

Add addnode=90.213.198.236 to your .conf file and restart your client

That didn't do anything :/

Add all of these nodes too it'll work:

62.163.9.155:19323
217.22.80.138:19323
217.122.176.76:19323
78.52.33.95:53565
58.60.1.24:61900
210.84.1.23:19323
216.58.23.148:19323
94.195.209.96:19323
85.11.153.119:19323
86.157.191.43:19323
81.3.189.155:19323
69.158.170.114:19323
80.74.157.31:19323

Thanks.. Just to double check this goes it bbqcoin.conf in roaming folder right?

Edit: seems to be downloading the block chain. Thanks a million!

[master-P]

Yeah just put addnode=IP address and port for each one.

[magicianliu157]

Add addnode=90.213.198.236 to your .conf file and restart your client

That didn't do anything :/

Add all of these nodes too it'll work:

62.163.9.155:19323
217.22.80.138:19323
217.122.176.76:19323
78.52.33.95:53565
58.60.1.24:61900
210.84.1.23:19323
216.58.23.148:19323
94.195.209.96:19323
85.11.153.119:19323
86.157.191.43:19323
81.3.189.155:19323
69.158.170.114:19323
80.74.157.31:19323

excuse me ,I have add all of the nodes,but My BBQCoin wallet says out of sync....
why? thank you~~

[Meeshka]

I saw this coin is alife, but I canet sync my wallet. Any nodes alive? Added all that I could find to conf file, but seems like none of them is working.
Anybody has the working .conf file, please?