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

[D05GTO]

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.

Oh, I'm just straight cpu mining it from the Wallet.  Working fine and they are flowing on in.

[1713571894]

1713571894

[1713571894]

1713571894

[1713571894]

1713571894

[1713571894]

1713571894

[loaded101]

I've scanned the windows wallet with virustotal and am getting 6 positives for "gen:variant.kazy.364047"

Not sure whether this is just detecting a bitcoinminer or something more risky.

https://www.virustotal.com/en/file/699d639e6a0378b59c114a49863c25b4d1ba14959a64c98267a8f3b84c20457d/analysis/1399922124/

[BlueDragon747]

I've scanned the windows wallet with virustotal and am getting 6 positives for "gen:variant.kazy.364047"

Not sure whether this is just detecting a bitcoinminer or something more risky.

https://www.virustotal.com/en/file/699d639e6a0378b59c114a49863c25b4d1ba14959a64c98267a8f3b84c20457d/analysis/1399922124/

build from git but I would say false positive

[CA Coins]

Curious to see what is going on with this coin.  On ny2.blakecoin.com, the network info shows

Code:

Network Info
Difficulty 	0.02357130
Est Next Difficulty 	3.31476450 (Change in 2 Blocks)
Est. Avg. Time per Block 	1 second
Current Block 	18338

After 18338 blocks, the difficulty is still <1?  Sounds like a huge premine to me.

[zsnorbi]

Curious to see what is going on with this coin.  On ny2.blakecoin.com, the network info shows

Code:

Network Info
Difficulty 	0.02357130
Est Next Difficulty 	3.31476450 (Change in 2 Blocks)
Est. Avg. Time per Block 	1 second
Current Block 	18338

After 18338 blocks, the difficulty is still <1?  Sounds like a huge premine to me.

really slow diff retarget:) public instamining lol

[BlueDragon747]

Curious to see what is going on with this coin.  On ny2.blakecoin.com, the network info shows

Code:

Network Info
Difficulty 	0.02357130
Est Next Difficulty 	3.31476450 (Change in 2 Blocks)
Est. Avg. Time per Block 	1 second
Current Block 	18338

After 18338 blocks, the difficulty is still <1?  Sounds like a huge premine to me.

was released on pool at 0 blocks was no chain at all not even a single premined block!

atm cpu seems best due to pool taking time to process and send blocks to miners  

blocktarget is 8064 e.g 14*24*60*60/150

[ShXnot]

great work BlueDragon
just some question
are these coins in same blockchane?
is it possible to merge these 4 coins wallet too? i mean 1 wallet for all coins

[BlueDragon747]

great work BlueDragon
just some question
are these coins in same blockchane?
is it possible to merge these 4 coins wallet too? i mean 1 wallet for all coins

not same chain work is duplicated and tested against each pplns round per chain and independent although high share can solve all

[valuxin]

Yeah... This coin is VERY strage...

[D05GTO]

Diff is rising.   People should jump on this quick.

[Brewins]

Really great idea of making a blake bitcoin clone, gunna start mining as soon as i have synced up! good work dev!

[Ignatius]

Curious to see what is going on with this coin.  On ny2.blakecoin.com, the network info shows

Code:

Network Info
Difficulty 	0.02357130
Est Next Difficulty 	3.31476450 (Change in 2 Blocks)
Est. Avg. Time per Block 	1 second
Current Block 	18338

After 18338 blocks, the difficulty is still <1?  Sounds like a huge premine to me.

was released on pool at 0 blocks was no chain at all not even a single premined block!

atm cpu seems best due to pool taking time to process and send blocks to miners  

blocktarget is 8064 e.g 14*24*60*60/150

"blocks" : 25297,
"difficulty" : 0.09428520,

Blocks are being mined at a rate of ~1 per second. If 8064 blocks is the retarget time, why is the diff still below 1?

Downloading and trying to run the client now, it cannot sync up to the blockchain, it's processing old blocks more slowly than new blocks are being added. This makes mining impossible. I had 30GHs pointed at ny2 pool through launch and my balance shows ~900 BlakeBitcoins. If the pools aren't finding the blocks, and a new miner can't mine blocks, who has mined the giant sum of outstanding Blakebitcoins thus far?

[D05GTO]

Anyone mining from the wallet is doing A ok.   All the power hashers aren't getting the jump on regular miners as they normally do.  

[zsnorbi]

I hope dev knows well that he will have to fork the coin to lower the retarget time

[Ignatius]

Anyone mining from the wallet is doing A ok.   All the power hashers aren't getting the jump on regular miners as usual.  

I have wallets synced which I launched earlier in the day, and new wallets I am attempting to setup which can not sync.

I've mined at the wallet solo from 2 locations with cpu and gotten 0 blocks.

I've mined at the merged pool and gotten very few blocks.

I've mined against my own merged pool and gotten 0 blocks.

Now anyone who downloads the wallet and wants to mine, can't, period. The blocks are being generated at ~1 per second so a new client cannot sync up.

Why if the network is moving at 1 block per second would the difficulty not be above 1 after 3 retargets? Something is way off here.

[CA Coins]

I don't mind hoarding the large eye candy when I type ./blakebitcoind getbalance, but this sounds like a failed launch to me.

Blockcount 26164
Difficulty: 0.09428520

The difficulty retarget is totally off.  There is a new block every second and the difficulty is about the same as it was 8000 blocks ago.  Mining is basically about who has the network speed to add a new block instead of actually solving the block.
Whether it is a premine or a public instamine, this blockchain is not very useful. I suggest reboot now

[valuxin]

I have no problems with mining solo with standart wallet. I'm using the next settings:

Code:

listen=1
gen=0
maxconnections=180
rpctimeout=30
rpcallowip=127.0.0.*
rpcallowip=192.168.1.*
rpcport=243
rpcuser=user
rpcpassword=pass
server=1
daemon=1
addnode=146.185.135.24
addnode=162.243.14.130
addnode=188.226.213.85
addnode=107.170.140.27

[Ignatius]

I have no problems with mining solo with standart wallet. I'm using the next settings:

Code:

listen=1
gen=0
maxconnections=180
rpctimeout=30
rpcallowip=127.0.0.*
rpcallowip=192.168.1.*
rpcport=243
rpcuser=user
rpcpassword=pass
server=1
daemon=1
addnode=146.185.135.24
addnode=162.243.14.130
addnode=188.226.213.85
addnode=107.170.140.27

Then you haven't downloaded a new wallet and tried to sync up recently?

New wallets at multiple locations can not sync up because blocks are being created faster than a new client can process them.

Why after 3 difficulty retargets is the difficulty still below 1, on a coin with a block time target of 3 minutes?

What I am saying is that if you got the wallet earlier today and synced up then you are fine as an early adopter. If you are one of these late adopters who wants to pick it up a mere hours later, you can't.

[zsnorbi]

I don't mind hoarding the large eye candy when I type ./blakebitcoind getbalance, but this sounds like a failed launch to me.

Blockcount 26164
Difficulty: 0.09428520

The difficulty retarget is totally off.  There is a new block every second and the difficulty is about the same as it was 8000 blocks ago.  Mining is basically about who has the network speed to add a new block instead of actually solving the block.
Whether it is a premine or a public instamine, this blockchain is not very useful. I suggest reboot now

Most of all i agree with you however i don't think rebooting would solve the problem, moreover it would be worse. There are around 100 miners mining this coin right now and those would be really angry if their coins would just disappear overnight. Of course as a current miner i am defending my point. The right solution i think would be an imidiate hard fork with kgw implemented at block 50.000 so  it should be taken as a mined ipo, that early miners got some more shares.

[valuxin]

I have no problems with mining solo with standart wallet. I'm using the next settings:

Code:

listen=1
gen=0
maxconnections=180
rpctimeout=30
rpcallowip=127.0.0.*
rpcallowip=192.168.1.*
rpcport=243
rpcuser=user
rpcpassword=pass
server=1
daemon=1
addnode=146.185.135.24
addnode=162.243.14.130
addnode=188.226.213.85
addnode=107.170.140.27

Then you haven't downloaded a new wallet and tried to sync up recently?

New wallets at multiple locations can not sync up because blocks are being created faster than a new client can process them.

Why after 3 difficulty retargets is the difficulty still below 1, on a coin with a block time target of 3 minutes?

What I am saying is that if you got the wallet earlier today and synced up then you are fine as an early adopter. If you are one of these late adopters who wants to pick it up a mere hours later, you can't.

I'm using the newest wallet both on my Windows workstation and Ubuntu mining rig (for ubuntu compiled it from git). No problem.