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

Seems network is now syncing correctly, haven't had a fork in a while 8-)

I am working on setting up the pool but I need to wait for p2pool code because I cannot properly port blake hash function...

Any news of a possible mining pool?

Thank You 

184.171.247.23 <--Shared GBit

Good advice I use -t 7 for my i7 2600k

I will re look at the current budget I have set for Blakecoin and think about adding more server nodes over the next few weeks unless someone wants to volunteer any fixed IP nodes for the network?

When using the 0.8.5 wallet I had several issues with disconnections to the network. What has helped me to keep the wallet 'online' has been to reduce the amount of hashing, and keep 1-2 cores from mining and use them solely for other purposes.

so for a 8 core cpu, I have run the miner with t -6

The reasoning was that it is better keep the wallet online rather than hashing away only to find 10 orphaned blocks.

I have chosen to use the same approach with 0.8.6, but now the difficulty is so high so I have only got one orphaned block in the past 3-4 days.

I had a network fork yesterday, block generation rate and difficulty dropped significantly (to around 122) and I mined two blocks, which then became orphans when I finally got a connection to the main block chain.

Due to a reboot, I've currently only got 7 connections (usually I see 10, which is still quite low)

One block is awaiting confirmation, hope its not going to be orphaned too 


This is my config

pi@raspberrypi ~/.blakecoin $ cat blakecoin.conf
listen=1
gen=0
rpcallowip=127.0.0.1
rpcallowip=192.168.1.*
rpcuser=x
rpcpassword=x
rpcport=8772
server=1
daemon=1
addnode=162.243.133.80
addnode=162.243.14.130
addnode=146.185.135.24

thought I had the stuck wallet fixed in 0.8.6?

it is possible that the network had a longer chain and rejected the blocks  

please keep reporting any issues I do always look at them and add it to my list to help improve Blakecoin  

also if you find a solution to a problem please post as it may help others  

qt-blakecoin behave not stable, as it stucked sometimes and do not load new blocks from other peers, until restart.
maybe it stucked on your pc and you got forked chain? or maybe someone stucked qt was restarted and has chain longer than yours?

just my thoughts

Strange that you got so many, only a couple of them are even close to each other 

check the system time make sure it is a correct as Blakecoin is a little more sensitive to timing still would give you a warning if it was too far out

I take it you are on quite a fast internet connection, if you could check your ping to the main nodes that can help me identify any latency issues but will still look into it before the next wallet update

{
    "version" : 80600,
    "protocolversion" : 70001,
    "walletversion" : 60000,
    "balance" : X,
    "blocks" : 5823,
    "timeoffset" : 0,
    "connections" : 14,
    "proxy" : "",
    "difficulty" : 652.91740049,
    "testnet" : false,
    "keypoololdest" : 1381326818,
    "keypoolsize" : 101,
    "paytxfee" : 0.01000000,
    "errors" : ""
}




    {
        "account" : "",
        "address" : "BeTgK5VJzLZ5ZiNZ4DqVP152FUdaYbTQn4",
        "category" : "orphan",
        "amount" : 25.00026122,
        "confirmations" : 0,
        "generated" : true,
        "txid" : "0d03506fd37df099cb496e8812a1d1724fd7d5d970fd3e7db4266a0116c1d0e9",
        "time" : 1381849041,
        "timereceived" : 1381849043
    },
    {
        "account" : "",
        "address" : "BaSCpzGEDBzzzceXfZwQScGwddCGjSosCw",
        "category" : "orphan",
        "amount" : 25.00018503,
        "confirmations" : 0,
        "generated" : true,
        "txid" : "da903b16002f44300269e22f98cc4be97961c596423ec55fa0ac62e5d134e6aa",
        "time" : 1381857366,
        "timereceived" : 1381857370
    },
    {
        "account" : "",
        "address" : "BcqcDYRPgB1H4fZvTjTSbmugnURFngbP8L",
        "category" : "orphan",
        "amount" : 25.00018507,
        "confirmations" : 0,
        "generated" : true,
        "txid" : "76957ccbcaf2a30352373d3c35dd8b04be4b3523281beba19dccf76b68f39947",
        "time" : 1381858017,
        "timereceived" : 1381858021
    },
    {
        "account" : "",
        "address" : "BX1KExbrwUeBUCukmkv98bp4mPU3L2RW5P",
        "category" : "orphan",
        "amount" : 25.00013109,
        "confirmations" : 0,
        "generated" : true,
        "txid" : "495d47a9a513f2a0c352b537ff947102529275610f388de9f626ddb1622e7dfc",
        "time" : 1381866216,
        "timereceived" : 1381866218
    },
    {
        "account" : "",
        "address" : "Bbg8LAipcHGPfGMoFyRcLJtuXsZWTwWSYu",
        "category" : "orphan",
        "amount" : 25.00013110,
        "confirmations" : 0,
        "generated" : true,
        "txid" : "25f1fca01fc3503ba96c3d9e47793684ff62791c06ab8ccb0489ce0d3323c9e5",
        "time" : 1381866387,
        "timereceived" : 1381866388
    },
    {
        "account" : "",
        "address" : "BkvsXw95yH5ZtArhitv4WaTHFmdC6ZLQYi",
        "category" : "orphan",
        "amount" : 25.00013111,
        "confirmations" : 0,
        "generated" : true,
        "txid" : "b09d3fcf5cfdb8ac6a673a592976f2f82069a9dec2f11f852cf16f8dc232f3a0",
        "time" : 1381868498,
        "timereceived" : 1381868501
    },
    {
        "account" : "",
        "address" : "BpBJNCujED9HkJMxQAa9emeuSHLBwdaJoH",
        "category" : "orphan",
        "amount" : 25.00013114,
        "confirmations" : 0,
        "generated" : true,
        "txid" : "86b3017f67935d516da46ecae2eb9791f1d931ea4e9b9bbdd886f64fc4f2eaa7",
        "time" : 1381871425,
        "timereceived" : 1381871426
    },
    {
        "account" : "",
        "address" : "Bs4FWtsQqwHj5sULadpt8QA3zPL9PhxGRS",
        "category" : "generate",
        "amount" : 25.00029756,
        "confirmations" : 175,
        "generated" : true,
        "blockhash" : "000000000025674bfbcc178948ad319addc92931ebe5bda657b6ab71562ff1ca",
        "blockindex" : 0,
        "blocktime" : 1381888738,
        "txid" : "630cbbc2e61b289de0cbe0daed67aa61f174e01076767662a5cfe594892f5e06",
        "time" : 1381888738,
        "timereceived" : 1381888740
    },
    {
        "account" : "",
        "address" : "BZkqiWwG8FmUNPrPsqWDsurYwrcD3v8g6v",
        "category" : "immature",
        "amount" : 25.00025786,
        "confirmations" : 115,
        "generated" : true,
        "blockhash" : "0000000000686b79ef9556e4b8beb09538b3783946c890e14bd428ab5d66065d",
        "blockindex" : 0,
        "blocktime" : 1381902368,
        "txid" : "7cae612b2dd47f188996a648f8bb5285d76c16f28ded2a9bde51534f22238128",
        "time" : 1381902368,
        "timereceived" : 1381902370
    },
    {
        "account" : "",
        "address" : "BiqEeCjVbk8fNNcNpDAbY2Q5XoWSxDZKe3",
        "category" : "immature",
        "amount" : 25.00019437,
        "confirmations" : 74,
        "generated" : true,
        "blockhash" : "000000000006c6752380f25ad9911bb79f9559309b82c0d1ecc6bc573553f04a",
        "blockindex" : 0,
        "blocktime" : 1381910591,
        "txid" : "b1dcf1f5ae494e472cf81d106a1206d41bf05138b5a55149c754e8a5be260bf9",
        "time" : 1381910591,
        "timereceived" : 1381910593
    }



About 120MH/s.

did you update to 0.8.6?

how many connection are you getting and what block are you on?

also 6 blocks what is you hashing power?

I only got 2 blocks from about 90Mh/s last night 

Eh 6 orphans in a row, what's going on.

One has to be really lucky now that the diff is over 800 again.

1st day did the standard 25Mhz(~600) and found 1 block overnight last night did 50MHz(~1000) but didn't find any. Tested and it is producing valid hashes but was just not lucky last night

The current build was quite quick (just an hour or so), but I've been running one overnight to try to get a better FMAX and its still stuck at phase 4 with a hundred or so routes to go (and then it will start all over again at phase 5 to try to improve the timing). I think I'm going to abort it and try another setting on the dial ... this is the frustrating thing with the Xilinx devices, it takes many, many long compilations to get a good result, and its all chance (just like mining hashes really).

You should be getting better than one block in two days. Did you do the frequency characterization? The default build runs at 25MHz, but it should clock up to 55MHz or more. Just make sure its returning good hashes (all zeros for the last 8 hex digits). I get around 1250 diff=1 (old diff=256) hashes per 24 hours (and perhaps 2 to 4 of these will be accepted, yay!)

the difficulty push on Blakecoin was within 2 days of release on this forum!

Mr Big is quite a solid amount of hashing power not sure about it being FPGA have you tried to build a design with Xilinx ISE?, it often takes longer than this to even build a decent high Fmax design with Xilinx ISE let alone program it to the boards, I was amazed kramble was able to do it so fast but he did base it on his current FPGA Litecoin miner

Well i believe a large power on rented cpu farms like EC2 could be possible
But this is far beyond the hashpower of cpu's
This is more like a large gpu farm, then again bfl had sold fpga devices which was pretty fast
For instance some on bitminter had almost 200 Gh fpga power

On quark many people switched to mine them on EC2 rentals as well that gave us a dent in receiving coins as well
But even with some who rented hundreds of contracts i got minimal 4 to 12 blocks on my cpu's on a day.

However since i do not have any fpga and no miner which i can use on gpu, i will forget about this coin.
In my view the coin is no longer a point of interrest to me

The happy few who got in early and those getting the coins now are laughing their asses off.

Its basically the same as a premined coin, a few persons getting all the coins and all others get close to nothing.

Your wrong there IT does hurt the coin

Don't be grumpy, dude, you're doing an excellent work!  I don't think that several days (when someone mines with big EC2 or his own unreleased miner) will make any harm to the coin.