Author

Topic: [ANN][BLC] Blakecoin Blake-256 for GPU/FPGA With Merged Mined Pools Stable Net - page 154. (Read 409641 times)

legendary
Activity: 1470
Merit: 1001
Use Coinbase Account almosanywhere with Shift card
full member
Activity: 132
Merit: 100
BitCoin
hero member
Activity: 607
Merit: 500
diff has ups and downs. there are few people mining this.
i really like the cool and quiet of VGAs with blake256 because with scrypt, VGAs are working
always at max !
i wish for this algo to replace scrypt Wink
legendary
Activity: 1470
Merit: 1001
Use Coinbase Account almosanywhere with Shift card
Difficulty going up.

Bad news means less coins for my Hashrate.
Good news means lots more miners are hashing it.

Network Info
Difficulty   3042.1137047
Est Next Difficulty   4232.1940059 (Change in 0 Blocks)
Est. Avg. Time per Block   129.38 seconds

 
hero member
Activity: 607
Merit: 500
then i assume that linux wallet has no issues, but we need confirmation, i am not a linux guy Smiley
lets sit at the pool's throne for a while :p
legendary
Activity: 1509
Merit: 1030
Solutions Architect
a rig with 2x5970 total HR 3.8GH, the wallet in the same rig.
it would be useful to have info from linux users if they get the same issues Wink
i wonder about the pool, it isn't a "huge" wallet with a lot of "solo" miners connected? in linux i guess

no its not direct so best way to think of a pool as a distributed miner and it has a normal wallet behind the pool which the pool software submits shares to  

the workers are like your graphics cards they just produce valid hashes and the pool just keeps record of the shares which are used to calculate your reward for that round

payouts are done via json rpc to the wallet by the pool software or cron job

the pool software does have more checks that it is only submitting hashes above a target to the wallet
hero member
Activity: 607
Merit: 500
a rig with 2x5970 total HR 3.8GH, the wallet in the same rig.
it would be useful to have info from linux users if they get the same issues Wink
i wonder about the pool, it isn't a "huge" wallet with a lot of "solo" miners connected? in linux i guess
legendary
Activity: 1509
Merit: 1030
Solutions Architect
i got the same issue with reaper!
the wallet stays behind in block count Sad
only way the pool or a frequent restart of the wallet is necessary!

useful data please, how many rigs per wallet? what sort of hash rate? was the wallet on same rig?

like I said before its hard to find this kind of bug as none of these issues directly link to a bid of code that I can patch  Cry

I will take another look though the code but last time I could not find anything that would cause this  Undecided
hero member
Activity: 607
Merit: 500
i got the same issue with reaper!
the wallet stays behind in block count Sad
only way the pool or a frequent restart of the wallet is necessary!
newbie
Activity: 56
Merit: 0
Hey Guy,

I mined some QQcoin - I was wondering if anybody is interested in trading qqc for blakecoins.
legendary
Activity: 1509
Merit: 1030
Solutions Architect
nevertheless, why this coin has such timestamp or wallet problems? it is a design issue?
i don't know of any other coin having these issues (as far as i know) Smiley

no other coin using blake-256 as far as I know Wink

the timestamp is same rule as Bitcoin for time advancement 2hrs+ max but a lot more nodes on the network so less time difference between nodes?

not sure if it is the wallet or cgminer but it is an open issue

same wallet is used for the pool and that is at ~40GH/s but is python -> wallet not cgminer -> wallet

Blakecoin is using a new algo and I did make more changes than just a clone and rip of POW algo which could create issues  Undecided

for the amount of time Blakecoin has been going we have a lot of features that you cannot do with the Scrypt algo and I will continue to improve the wallet over time  Cool

Edit:
when the wallet locks from cgminer in my tests it leaves no log warnings/errors and happens at random intervals so it is difficult to track down   
hero member
Activity: 607
Merit: 500
nevertheless, why this coin has such timestamp or wallet problems? it is a design issue?
i don't know of any other coin having these issues (as far as i know) Smiley
legendary
Activity: 1509
Merit: 1030
Solutions Architect
what do you mean "ASIC" Huh?
solo is not working correctly. The wallet cannot synchronize with the blockchain (at least twice /day i have to restart it over)
or else all the blocks are orphans Sad
i think they are, i see something like this:
Status: 0/unconfirmed
Date: 12/29/2013 03:20
Source: Generated
Credit: (not accepted)
Net amount: 0.00 BLC
Transaction ID: 109282094ec1641dccc370d51e3d7edd7f4e6fef5e0063935b0ff4feadca0a60

where can i check the Tid?

other miners but not mining blake. they are not having issues with timestamp

I have the same issue lost more than a thousand of BLC to this. Main reason I use pool.

Switched back to pool again today

if you are not 2hrs+ UTC/GMT, timestamp on the block should get accepted

I do run a couple of rigs with 4x cm1 boards, 2x cgminer per wallet solo 24/7 ~ 6.4GH/s but the wallets are on different rigs which might help

for anyone who is having issues then it makes sense to use a pool, I will try to get another pool up for the new year  Cool
legendary
Activity: 1470
Merit: 1001
Use Coinbase Account almosanywhere with Shift card
what do you mean "ASIC" Huh?
solo is not working correctly. The wallet cannot synchronize with the blockchain (at least twice /day i have to restart it over)
or else all the blocks are orphans Sad
i think they are, i see something like this:
Status: 0/unconfirmed
Date: 12/29/2013 03:20
Source: Generated
Credit: (not accepted)
Net amount: 0.00 BLC
Transaction ID: 109282094ec1641dccc370d51e3d7edd7f4e6fef5e0063935b0ff4feadca0a60

where can i check the Tid?

other miners but not mining blake. they are not having issues with timestamp

I have the same issue lost more than a thousand of BLC to this. Main reason I use pool.

Switched back to pool again today
legendary
Activity: 1509
Merit: 1030
Solutions Architect
ok, but the wallet issues are related to solo mining?
i will try to leave the wallet as it is without solo to see if syncronization will be ok.
thanks

yeah its a combo issue, wallet is fine on its own


wow, something of a miracle but my 7970 just found 2 blocks in a row, within 0.1 seconds of each other.

Lucky  Cheesy

edit:
reaper or cgminer?
hero member
Activity: 607
Merit: 500
ok, but the wallet issues are related to solo mining?
i will try to leave the wallet as it is without solo to see if syncronization will be ok.
thanks
legendary
Activity: 1509
Merit: 1030
Solutions Architect
what do you mean "ASIC" Huh?
solo is not working correctly. The wallet cannot synchronize with the blockchain (at least twice /day i have to restart it over)
or else all the blocks are orphans Sad
i think they are, i see something like this:
Status: 0/unconfirmed
Date: 12/29/2013 03:20
Source: Generated
Credit: (not accepted)
Net amount: 0.00 BLC
Transaction ID: 109282094ec1641dccc370d51e3d7edd7f4e6fef5e0063935b0ff4feadca0a60

where can i check the Tid?

block explorer on OP

I have reported cgminer+wallet can have issues, if you can when solo mining use reaper it is stable with gpu solo 24/7

the max I can run is 2x cgminer per wallet

Edit:
I can only reproduce this issue with cgminer and not reaper or the python based miners  Huh
hero member
Activity: 607
Merit: 500
what do you mean "ASIC" Huh?
solo is not working correctly. The wallet cannot synchronize with the blockchain (at least twice /day i have to restart it over)
or else all the blocks are orphans Sad
i think they are, i see something like this:
Status: 0/unconfirmed
Date: 12/29/2013 03:20
Source: Generated
Credit: (not accepted)
Net amount: 0.00 BLC
Transaction ID: 109282094ec1641dccc370d51e3d7edd7f4e6fef5e0063935b0ff4feadca0a60

where can i check the Tid?
legendary
Activity: 1470
Merit: 1001
Use Coinbase Account almosanywhere with Shift card
Well all my miners are showing local time UTC -8 (Los Angeles)
Code:
[2013-12-28 20:35:02] Icarus 2: Share found 3896e23c
[2013-12-28 20:35:04] Icarus 2: Share found 94a626b2

ASIC and GPU miners are fine. FPGA starts out ok mined blocks are broadcast and confirmed but after a number of hours a block will have 0 confirmation hours later. closing wallet then reopening it causes 0 conf blocks to disappear but new blocks found will be confirmed.

Normally see this first thing in the morning after waking up.
Jump to: