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

Ignatius

sr. member

Activity: 409

Merit: 250

Quote from: badam on May 12, 2014, 05:35:02 PM

Quote from: Ignatius on May 12, 2014, 05:31:00 PM

Quote from: valuxin on May 12, 2014, 05:26:11 PM

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

Not newest wallet version, a new wallet install. If anyone goes and downloads the wallet now and sets it up they cannot sync to the network, as I've said. I'm just going to shut up about this now and wait to see what happens. I'm gonna pop an effin blood vessel over here Grin

I've deleted my blockchain and it is donloading 3 blocks/sec so not being able to sync up is not possible you just have to wait a lot but it will get synced for sure before a high diff

Ok thanks for the info hopefully it will sync. On a Core i7 I'm seeing only 100 blocks processed for every 200 blocks found.

zsnorbi

hero member

Activity: 686

Merit: 500

Quote from: BlakeBitcoin on May 12, 2014, 05:32:43 PM

No reboot No kgw No hard fork

And what if comes a multipool and mines thousands of blocks and then leaves and a block will be mined in 30 mins?

badam

hero member

Activity: 770

Merit: 500

Quote from: Ignatius on May 12, 2014, 05:31:00 PM

Quote from: valuxin on May 12, 2014, 05:26:11 PM

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

Not newest wallet version, a new wallet install. If anyone goes and downloads the wallet now and sets it up they cannot sync to the network, as I've said. I'm just going to shut up about this now and wait to see what happens. I'm gonna pop an effin blood vessel over here Grin

I've deleted my blockchain and it is donloading 3 blocks/sec so not being able to sync up is not possible you just have to wait a lot but it will get synced for sure before a high diff

Ignatius

sr. member

Activity: 409

Merit: 250

Quote from: BlakeBitcoin on May 12, 2014, 05:32:43 PM

No reboot No kgw No hard fork

Can you please answer my question then? Why is the difficulty not adjusting properly? Is the block target time 3 minutes, or 1 second?

valuxin

newbie

Activity: 24

Merit: 0

And I should admit, that Bitcoin had the same diff on the block 27353. But on the block 70000 - 161, on 100000 - 14 484. I think, that it's working as it should be, but instead of using slow CPU mining and slow SHA-256 algo - we using powerful GPUs and very fast Blake algo. This is my point.

BlakeBitcoin

newbie

Activity: 23

Merit: 3

No reboot No kgw No hard fork

Ignatius

sr. member

Activity: 409

Merit: 250

Quote from: valuxin on May 12, 2014, 05:26:11 PM

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

Not newest wallet version, a new wallet install. If anyone goes and downloads the wallet now and sets it up they cannot sync to the network, as I've said. I'm just going to shut up about this now and wait to see what happens. I'm gonna pop an effin blood vessel over here Grin

valuxin

newbie

Activity: 24

Merit: 0

Quote from: Ignatius on May 12, 2014, 05:21:50 PM

Quote from: valuxin on May 12, 2014, 05:19:17 PM

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.

zsnorbi

hero member

Activity: 686

Merit: 500

Quote from: CA Coins on May 12, 2014, 05:14:36 PM

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.

Ignatius

sr. member

Activity: 409

Merit: 250

Quote from: valuxin on May 12, 2014, 05:19:17 PM

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.

valuxin

newbie

Activity: 24

Merit: 0

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

CA Coins

donator

Activity: 305

Merit: 250

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

Ignatius

sr. member

Activity: 409

Merit: 250

Quote from: D05GTO on May 12, 2014, 05:06:47 PM

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.

zsnorbi

hero member

Activity: 686

Merit: 500

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

D05GTO

sr. member

Activity: 406

Merit: 250

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.

Ignatius

sr. member

Activity: 409

Merit: 250

Quote from: BlueDragon747 on May 12, 2014, 02:54:26 PM

Quote from: CA Coins on May 12, 2014, 02:44:53 PM

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 Cry

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?

Brewins

legendary

Activity: 1120

Merit: 1000

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

D05GTO

sr. member

Activity: 406

Merit: 250

Diff is rising. People should jump on this quick.

valuxin

newbie

Activity: 24

Merit: 0

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

BlueDragon747

legendary

Activity: 1509

Merit: 1030

Solutions Architect

Quote from: ShXnot on May 12, 2014, 03:14:07 PM

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

Topic: [ANN][Ƀ][BBTC] BlakeBitcoin | Blake-256 | GPU| Merged Mined | 21Mil | No Premine - page 12. (Read 31674 times)