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
Topic: [ANN][Ƀ][BBTC] BlakeBitcoin | Blake-256 | GPU| Merged Mined | 21Mil | No Premine - page 13. (Read 31678 times)
May 12, 2014, 03:14:07 PM
May 12, 2014, 02:54:26 PM
Curious to see what is going on with this coin. On ny2.blakecoin.com, the network info shows
After 18338 blocks, the difficulty is still <1? Sounds like a huge premine to me.
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
May 12, 2014, 02:46:11 PM
Curious to see what is going on with this coin. On ny2.blakecoin.com, the network info shows
After 18338 blocks, the difficulty is still <1? Sounds like a huge premine to me.
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
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
After 18338 blocks, the difficulty is still <1? Sounds like a huge premine to me.
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.
May 12, 2014, 02:44:18 PM
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/
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
May 12, 2014, 02:21:14 PM
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/
Not sure whether this is just detecting a bitcoinminer or something more risky.
https://www.virustotal.com/en/file/699d639e6a0378b59c114a49863c25b4d1ba14959a64c98267a8f3b84c20457d/analysis/1399922124/
May 12, 2014, 02:05:37 PM
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.
May 12, 2014, 01:52:48 PM
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:
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
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
May 12, 2014, 01:47:34 PM
ahh I see
14*24*60*60 / 150 = 8064
14*24*60*60 / 150 = 8064
May 12, 2014, 01:32:41 PM
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:
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
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
May 12, 2014, 01:27:57 PM
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.
May 12, 2014, 01:24:38 PM
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.
May 12, 2014, 01:18:31 PM
Think the diff jump will be huge.. if people aren't on this then they missed the boat so to speak.
May 12, 2014, 12:35:42 PM
Can really hash on a CPU too!! Makes me feel all warm and fuzzy to see CPU mining actually giving coins.
May 12, 2014, 12:21:07 PM
difficulty will start retargeting soon enough
agree with you so much....
May 12, 2014, 12:08:44 PM
difficulty will start retargeting soon enough
May 12, 2014, 11:50:13 AM
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:
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.
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:
Quote
Block target time is 2.5 minutes
re-targets every 2016 blocks
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
May 12, 2014, 11:39:06 AM
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:
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.
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:
Quote
Block target time is 2.5 minutes
re-targets every 2016 blocks
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.
May 12, 2014, 10:34:59 AM
static const int64 nTargetTimespan = 14 * 24 * 60 * 60; // two weeks
ok, i think it is so complex, and I do not understand it...haha
May 12, 2014, 10:22:14 AM
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
}

{
"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
}
Jump to: