[ANN][Ƀ][BBTC] BlakeBitcoin | Blake-256 | GPU| Merged Mined | 21Mil | No Premine

[BlueDragon747]

static const int64 nTargetTimespan = 14 * 24 * 60 * 60; // two weeks 

[zx]

What exactly a merge mining pool means? I met this thing earlier but never understood what that it is

yes, I do not understand what the dev has said, too...

[zx]

The world does not need Bitcoin clones.

yes, we all need innovative coin ,and love nice and wonderful coin,,,,,

[BlueDragon747]

Merge mining is mining multiple coins as same time
http://bitcoin.stackexchange.com/questions/273/how-does-merged-mining-work

Like Bitcoin+Namecoin etc..

[mikk2k2]

So we expect another diff adjust at 4032...


{
"blocks" : 3255,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00390625,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 18470611,
"pooledtx" : 0,
"testnet" : false
}

[zsnorbi]

So we expect another diff adjust at 4032...


{
"blocks" : 3255,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00390625,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 18470611,
"pooledtx" : 0,
"testnet" : false
}

I am sure it won't be exactly at 4032 at the beggining diff retarget is always laggy on standard retarget

[BlueDragon747]

So we expect another diff adjust at 4032...


{
"blocks" : 3255,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00390625,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 18470611,
"pooledtx" : 0,
"testnet" : false
}

I am sure it won't be exactly at 4032 at the beggining diff retarget is always laggy on standard retarget

I think the target time span is quite big so may take some time to sort itself out

[mikk2k2]

So we expect another diff adjust at 4032...


{
"blocks" : 3255,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00390625,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 18470611,
"pooledtx" : 0,
"testnet" : false
}

I am sure it won't be exactly at 4032 at the beggining diff retarget is always laggy on standard retarget

I think the target time span is quite big so may take some time to sort itself out

{
"blocks" : 4494,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00390625,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 17356005,
"pooledtx" : 0,
"testnet" : false
}

[zx]

static const int64 nTargetTimespan = 14 * 24 * 60 * 60; // two weeks 

ok, i think it is so complex, and I do not understand it...haha

[SteadyAsSheGoes]

I think something is completely wrong with this coin.

I just built the wallet. And it's already at block 8800 now. I'm also seeing like a block per second getting added.

Now I just noticed this:

Block target time is 2.5 minutes
re-targets every 2016 blocks

What?? That means the difficulty gets retargetted every 3.5 days. How can that possibly be right?

Unless I'm missing something here, this is a pretty big fail.

[BlueDragon747]

I think something is completely wrong with this coin.

I just built the wallet. And it's already at block 8800 now. I'm also seeing like a block per second getting added.

Now I just noticed this:

Block target time is 2.5 minutes
re-targets every 2016 blocks

What?? That means the difficulty gets retargetted every 3.5 days. How can that possibly be right?

Unless I'm missing something here, this is a pretty big fail.

The way I see it is that the wallet is just released and has little data to base retarget on and the span for target data as I posted above is huge

I could port my Blakecoin diff algo to it as I designed that to avoid issues like this but the diff is increasing very very slowly 0.00390625 > 0.00589282 

[cinnamon_carter]

difficulty will start retargeting soon enough

[zx]

difficulty will start retargeting soon enough

agree with you so much....

 

[D05GTO]

Can really hash on a CPU too!!  Makes me feel all warm and fuzzy to see CPU mining actually giving coins.

[D05GTO]

Think the diff jump will be huge.. if people aren't on this then they missed the boat so to speak.

[SteadyAsSheGoes]

The way I see it is that the wallet is just released and has little data to base retarget on and the span for target data as I posted above is huge

That still doesn't make any sense. When the difficulty only gets retargetted every 2016 blocks, there is no way this can go well. When the diff is low, it means the block time will be super short when hashes get added. When the diff is high, it'll take forever to get to the next block when the hashrate goes lower.

The whole point of difficulty is to keep the block time reasonably constant. When it only retargets every 2016 blocks, there's no way that can work.

[cinnamon_carter]

You can try , cpu miner for blake 256 algo is on Blake Coin op

Can really hash on a CPU too!!  Makes me feel all warm and fuzzy to see CPU mining actually giving coins.

[bzyzny]

i got a linux qt wallet to compile for this, however the wallet/gui only loads under sudo presently. when i try to run it without sudo, i get two pop up errors:

Code:

Unable to bind to 0.0.0.0:356 on this computer (bind returned error 13, Permission denied)

Code:

Failed to listen on any port. Use -listen=0 if you want this.

any ideas what is causing this?

EDIT:
it works fine if i set listen=0 in the conf file, but i thought this is supposed to be set to 1.
Here is the Linux-QT wallet for BlakeBitcoin. It was compiled on 64bit Linux Mint 16, but should work on many other distributions.
http://www.mediafire.com/download/my3xxizzg8ly0pj/blakebitcoin-qt-linux64.7z

[BlueDragon747]

ahh I see

14*24*60*60 / 150 = 8064 

[Ignatius]

i got a linux qt wallet to compile for this, however the wallet/gui only loads under sudo presently. when i try to run it without sudo, i get two pop up errors:

Code:

Unable to bind to 0.0.0.0:356 on this computer (bind returned error 13, Permission denied)

Code:

Failed to listen on any port. Use -listen=0 if you want this.

any ideas what is causing this?

EDIT:
it works fine if i set listen=0 in the conf file, but i thought this is supposed to be set to 1.
Here is the Linux-QT wallet for BlakeBitcoin. It was compiled on 64bit Linux Mint 16, but should work on many other distributions.
http://www.mediafire.com/download/my3xxizzg8ly0pj/blakebitcoin-qt-linux64.7z

Lower ports are privileged, use a higher port than 356. blakebitcoin.conf port=12356 rpcport=24243