Im hung on block 1518763. Looks like it is from Sunday. Any luck mining anything lately? I currently have mine running but the client still thinks it is out of sync

user: tspilk
id: 1635

Thanks!

When I am done with my pet project coin I might have some time to fork the current Litecoin source to 'update' BQC. Shoot me a message sometime or on github. I think I posted a comment to a revision you made adding dnsseeds to bbq (user: tspilk)

an example for litecoin is like this


All the public addresses start with L (bbqcoin starts with b) and the private keys start with 6 (bbqcoin starts with Y)

Does anyone know what the private key prefix for this coin is? I cannot seem to calculate it.

Based on what I have seen, Bitcoin uses 0x80 (128 in dec), Litecoin uses 0xb0 (176 in dec)  and according to https://en.bitcoin.it/wiki/List_of_address_prefixes the private key prefix (it uses Y from what I have seen from my testing in private key dumps) Y should correspond to 78 in Dec which is 0x4e. This doesnt seem to work for generation

Does anyone know?

I am converting bitaddress.org to generate BBQcoin paper wallets, brain wallets etc.

Yeah, I read that some guy in this thread knows a guy who is throwing a bbq with bill and wants to make custom physical bbqcoins inside of smoked bbq pork sandwiches

8 connections here

Some miners have been very busy over the weekend

https://dl.dropboxusercontent.com/u/7771567/bbq/difficulty%20last%205000ish.png

Spilk*

Too many forks!

Well the latest fork I was told to work on with updated graphics must have been forked from before he fixed it because it was broken before i just fixed it. So the binaries I posted are functional with the newer graphics

You are mistaken. We may be talking about two different forks of the same code though. The checkpoints applied for block 86425 was 00000b64041067a9cc8ad4b84e6a638ced0513319724bae7ceacbaf97380b4ae and this was the block that was hanging on the latest code when compiled. As can be seen from a search on http://bbqabe.rainbowdashh.tk/search?q=86425 for block 86425, the hash is 5bb676c3ea2d9cdc2589e7fa53874c425317aa9dadf0ae503fb7cf804cab9762.

Correcting this, fixing the block 303403 checkpoint and adding a checkpoint for 350000 upon compiling the client works as expected. I was able to transfer coins in and out of it in my testing and now released the latest.

My changes can be seen here https://github.com/overware/BBQCoin/commit/7fc723d451755a4bb18337546653d88a385f7f43

I have repaired bbqcoin files with the help of figroll. The issue seemed to be incorrect checkpoints which prohibited blocks from syncing past a certain point (since the hash was incorrect, effectively forking the network.)

I am still working on getting functional windows binaries, but I think having linux bbqcoind and bbqcoin-qt is a good step for anyone developing applications for this coin. This should hopefully give you a good jumping off point. (Compiled on Ubuntu 64-bit)


I will keep you posted as more developments are made.

https://dl.dropboxusercontent.com/u/7771567/bbq/BBQCoin-0.02-overware.tar.gz

edit:
here is a better difficulty graph I managed to do using this bbqcoind (and getting more than 3 digits of precision after the decimal like I got from Abe) on a log scale. Using this method on a log scale, I was able to get more detail at the very very low difficulty levels. Clearly we had a miner that dropped out around thanksgiving 2012 as it was pretty constant for a long time.

https://dl.dropboxusercontent.com/u/7771567/bbq/difficulty-log.png

Compare to the standard plot, you see a lot of data is blown away by how huge our difficulty is lately. Anyone doubting this is picking up steam is missing an opportunity.
https://dl.dropboxusercontent.com/u/7771567/bbq/difficulty.png

edit2: added interactive google chart (had to take average of 10 blocks, so 39000 data points instead of 390k as google has hard 400k cell limit )
https://dl.dropboxusercontent.com/u/7771567/bbq/diff.html

I appreciate your constructive feedback

I built bbqcoind and bbqcoin-qt from source for Ubuntu with the latest graphics and stuff from this repo https://github.com/overware/BBQCoin

https://dl.dropboxusercontent.com/u/7771567/bbq/BBQCoin-build-overware.tar.gz

Binaries are included in the bin/ directory

bLuihpiUqn6tfM4X7k2pWwEtgT7JriJEXw

Man, you're getting GRILLED on these coins

bH6bjiAd4QCd5MgdDfRWNv1KpUy2n6TuWw

I plotted the difficulty since gen block.

http://i.imgur.com/r8ZhcSo.png

Since Feb 6.
http://i.imgur.com/9PzopDv.png

Lots of growth!

I just compiled bbqcoind from source and all of my connections are coming from 19323.

Can you please link to the current branch of the source?

edit: My RPC port is functioning on 59332 but the peers are connecting on 19323. I compiled from the source on the first post of this thread (which has updates as of 4 days ago)

We should really consider cleaning up and consolidating all of the downloads to one page on bbqcoin.org. Source, clients, everything. This is what is going to keep BQC going more than anything.

edit2: best I can tell, 19323 is the port for testnet. Cannot find where in the source it is telling it to use that. The only line it doesnt appear as a comment is line 22 of protocol.h:

return testnet ? 58333 : 19323;

I dont do C++ very often but i think that is a conditiona, where if bool testnet = true, 58333 is returned, otherwise 19323. So this is indicating the default port for standard use is coded into the bbqcoin client as 19323. Which is why when you run 'bbqcoind getpeerinfo' all of your peers are connected on port 19323.

However, the port for RPC is different, which is why I was wondering if there is some confusion. This appears to have been discussed in this thread somewhere (post #62)

If its possible, could you provide to source to the bbqcoin pool when it is running? I can try and operate one so we don't have too much isolation of mining resources to one location

1587dySD5FGfoGuofDftgeiTLKBspEJNx6

Thanks!