Topic: BBQCoin, the coin you want to eat. - page 53. (Read 143487 times)

Hm, maybee you should offer it for a pizza ? 

Hey guys, I'm glad to see BQC still has an active enthusiast community.

Personally I think a gambling site, like a clone of LiteDice, would make BQC a lot more interesting - it would give people something to do with their coins without risking any actual value. I don't have any free to to devote to it though, sorry.

I do have about 2500 BQC in an old wallet if anyone wants/needs them. I'll sell them to the highest bidder (in BTC) if anyone want 'em. If no one cares to pay, I'll divide them among any zero bidders who respond.

the problem seems to be the qt-client. If  a block was found, it takes about 30-60 sec. in cgminer for the "new Block detected on Network" message.
If another Block is found before that it is rejected.
Any suggestions to speed up the notify to the miner ?

This seems strange as I solo on a 7970 and I get blocks but no rejects.

Yeah I know, otherwise no block would be accepted.. but the problem with such a low difficulty with mining on QT-Client is that there is no LP and therefore the miner keeps mining on the block he has just found and rejects it then..

Okay I have used blockhash RPC to get hashes to put into the checkpoints.cpp file and pushed it again to my github repo.

And made a new tarball for my sourceforge files-download page.

-MarkM-

Yes.

Tesla71, BBQCoin uses scrypt like Litecoin. You need to use Reaper or --scrypt with cgminer.

Take a look at the checkpoints in bitcoin, devcoin, groupcoin and so on.

There are more leading zeros as the block number grow, because checkpoints are the difficulty hash.

Possibly though someone hacked the code to use a different hash in BBQcoin for some reason?

EDIT: Looking at litecoin, though, its checkpoints do not have more and more leading zeroes. So maybe litecoin hacked up the checkpoint system and BBQcoin inherited the hack from litecoin.

-MarkM-

[Update] Development and Discussion Forum now online on BBQcoin.org website.

I don't know why that would be the case, I can solo mine BBQcoin just fine with reaper on my 7970.

But I don't solo all the time, I just do it for 20 minutes every few days just to see the network ticking over nicely and to get the difficulty.

It does work perfectly when mining with a cpu you though, which I rotate doing at well.

I think BBQcoin is great, more so without the stresses of exchanges and greed.

I tried a solo mine with a 5970 and the only result was that I am getting more rejectected blocks than accepted because of finding the next block before the network notified the miner of the previous one..
So I think atm its only reasonable to mine with a cpu, even my celeron can find blocks pretty fast

its the PoW that created the block
he told me that the PoW is being used as hash, which is wrong.

i just checked it again and its not the PoW at all, its the block hash:
so markm, seems i was right all the time, just use getblockhash and ul see im right...

Thanks CaptChadd.

I would say that the checkpoints in the source are wrong.

MarkM, did you make the checkpoints for 86425 and 303403? If so, how did you arrive at those hash values?

getblockhash 86425 ---- 5bb676c3ea2d9cdc2589e7fa53874c425317aa9dadf0ae503fb7cf804cab9762

getblockhash 303403 --- 6d7493ffc82a9553cf20ffca41ace762c3e4e7db4fe6f820675cdf387116342f

There match yours from the looks for things.

I am running it on linux, so it will not be the same binary. I built from "official" source committed to by MarkM just 6 days ago though.

CaptChadd, I would be interested to see what your client  says the hashes are for blocks 86425 and 303403.

"Debug window" under Help menu should give you the debug window. Then you click on the Console tab to get to the console.

Enter "getblockhash 86425" and "getblockhash 303403".

Please post your output.

Is it the same one as at bbqcoin.org Windows build?

Thats the one I use and it is upto date right now.

Well, I am telling you, it gets stuck.

I downloaded from https://github.com/Cubox-/BBQCoin and built it from source.


These hashes look suspicious, too many leading zeroes.
 
Here is the block hashes from my client:

I solo mine every few days but only for about 10 or 20 minutes. I just like getting a few blocks now and again and making sure the chain is still running.

Everything seems to be running nice and smooth right now.

It should not get stuck on checkpoints, I think that idea might be mostly superstition.

If someone mines hard to drive the difficulty up I do not know if it has fast adapting like DeVCoin and GRouPcoin or will get stuck at high difficulty a long time like NaMeCoin did way back when.

I think though that litecoin did improve adapting speed at least slightly, else it would be getting stuck at high difficulty each time all the miners go back to bitcoin after heavily mining litecoin during moments when it is momentarliy looking more profitable to mine than bitcoin.

As a largely-ignored coin everyone mining it might be better off to mine no harder than necessary for however many months they can instead of rushing into a period where most of them can't really get any coin as difficulty is way high.

For a long time the main attraction of BBQcoin, GRouPcoin, CoiLedCoin and I0Coin has been they are so ignored you can quietly mine at low difficulty month after month slowly building up a nice stash.

BBQcoin are relatively valuable right now because only people who care about them have them thus might be less inclined to dump them. Once heavy mining happens it will mostly by people looking to dump them, they might make an exchange too, or maybe our not making an exchange will cause them to ignore it longer - if so the longer we can hum away at low difficulty with no exchange the better! Once it has gone through a subsidy halving, or even a few of them, will be plenty time to think about making an exchange to see what they might be worth by then.

-MarkM-

The version that I downloaded a few weeks ago downloaded the whole blockchain fine. With the difficulty so low if someone mines suddenly with a lot of hashing power does that effect the chain at all?