Pool doesn't work?
What algo do you mine
All i see is every pool is working.
I messed sup Groestl with Myriad-groestl
That why suprnova is did not received any block.
Topic: [ExaByte] [EXB] [Sha256-Scrypt-Groestl] [PoW] [Pool please update last source] - page 7. (Read 12132 times)
May 25, 2015, 05:56:51 PM
What algo do you mine
All i see is every pool is working.
I messed sup Groestl with Myriad-groestl
That why suprnova is did not received any block.
May 25, 2015, 05:51:15 PM
Myriad-Groestl Pool now live: https://exbg.suprnova.cc
May 25, 2015, 05:48:01 PM
Pool doesn't work?
May 25, 2015, 05:44:07 PM
May 25, 2015, 05:38:57 PM
sell 2000=0.15btc to pm
May 25, 2015, 05:33:56 PM
Block time is 30 seconds.
That is problem.
It will be set soon.
this is Myriad-Groestl
Sorry no to put it into OP
That is problem.
It will be set soon.
this is Myriad-Groestl
Sorry no to put it into OP
Dev pls add all the pools to the op
May 25, 2015, 05:29:45 PM
May 25, 2015, 05:28:22 PM
Block time is 30 seconds.
That is problem.
It will be set soon.
this is Myriad-Groestl
Sorry no to put it into OP
That is problem.
It will be set soon.
this is Myriad-Groestl
Sorry no to put it into OP
Ah lol..
Okay i've relaunched the pool with Groest-Myriad algo
May 25, 2015, 05:27:58 PM
yeah, I'm unable to mine this with scrypt algo. Tried solo and also on private NOMP 
May 25, 2015, 05:26:34 PM
Block time is 30 seconds.
That is problem.
It will be set soon.
this is Myriad-Groestl
Sorry no to put it into OP
That is problem.
It will be set soon.
this is Myriad-Groestl
Sorry no to put it into OP
May 25, 2015, 05:19:28 PM
Groestl is not accepting blocks, though hashing is correct:
ThreadRPCServer method=submitblock
ERROR: CheckProofOfWork(algo=2) : hash doesn't match nBits
ERROR: CheckBlock() : proof of work failed
ERROR: ProcessBlock() : CheckBlock FAILED
Please switch to the other algos.
I use GRS algorithm SOLO is accepted block! It could be that the pool was too small.ThreadRPCServer method=submitblock
ERROR: CheckProofOfWork(algo=2) : hash doesn't match nBits
ERROR: CheckBlock() : proof of work failed
ERROR: ProcessBlock() : CheckBlock FAILED
Please switch to the other algos.
Solo works, its getwork, but stratum (submitblock/getblocktemplate) doesn't seem to work
May 25, 2015, 05:14:10 PM
Groestl is not accepting blocks, though hashing is correct:
ThreadRPCServer method=submitblock
ERROR: CheckProofOfWork(algo=2) : hash doesn't match nBits
ERROR: CheckBlock() : proof of work failed
ERROR: ProcessBlock() : CheckBlock FAILED
Please switch to the other algos.
I use GRS algorithm SOLO is accepted block! It could be that the pool was too small. ThreadRPCServer method=submitblock
ERROR: CheckProofOfWork(algo=2) : hash doesn't match nBits
ERROR: CheckBlock() : proof of work failed
ERROR: ProcessBlock() : CheckBlock FAILED
Please switch to the other algos.
May 25, 2015, 05:11:14 PM
Groestl is not accepting blocks, though hashing is correct:
ThreadRPCServer method=submitblock
ERROR: CheckProofOfWork(algo=2) : hash doesn't match nBits
ERROR: CheckBlock() : proof of work failed
ERROR: ProcessBlock() : CheckBlock FAILED
Please switch to the other algos.
ThreadRPCServer method=submitblock
ERROR: CheckProofOfWork(algo=2) : hash doesn't match nBits
ERROR: CheckBlock() : proof of work failed
ERROR: ProcessBlock() : CheckBlock FAILED
Please switch to the other algos.
May 25, 2015, 05:10:20 PM
I'm soloing groestl and getting all rejects.
May 25, 2015, 05:08:40 PM
Every prior multi-algo coin I was in at launch on did the same thing with diff. It was always a long time for diff to catch up. One tried to offset this by making the block time 10 or more minutes, but even that didn't slow down the first 1000 blocks much.
May 25, 2015, 05:08:00 PM
I'm soloing scrypt and getting all rejects. It appears as if the difficulty is set to a groestl diff.
May 25, 2015, 05:07:01 PM
lol:
{
"version" : 1000001,
"protocolversion" : 70001,
"walletversion" : 60000,
"balance" : 0.00000000,
"blocks" : 1334,
"timeoffset" : -1,
"connections" : 9,
"proxy" : "",
"pow_algo_id" : 2,
"pow_algo" : "groestl",
"difficulty" : 0.33812475,
"difficulty_sha256d" : 109.33604442,
"difficulty_scrypt" : 0.04531963,
"difficulty_groestl" : 0.33812475,
"testnet" : false,
"keypoololdest" : 1432586969,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"errors" : ""
}
i guess this one is dead already...
but i like the idea.. relaunch it with a working diff readjustment and it will be fine.
{
"version" : 1000001,
"protocolversion" : 70001,
"walletversion" : 60000,
"balance" : 0.00000000,
"blocks" : 1334,
"timeoffset" : -1,
"connections" : 9,
"proxy" : "",
"pow_algo_id" : 2,
"pow_algo" : "groestl",
"difficulty" : 0.33812475,
"difficulty_sha256d" : 109.33604442,
"difficulty_scrypt" : 0.04531963,
"difficulty_groestl" : 0.33812475,
"testnet" : false,
"keypoololdest" : 1432586969,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"errors" : ""
}
i guess this one is dead already...
but i like the idea.. relaunch it with a working diff readjustment and it will be fine.
May 25, 2015, 05:02:03 PM
Difficulty retarget depend on algorithm that finds that block.
So what is the block time then?
Diff has to be calculated over all algos or it doesn't really make any sense...
May 25, 2015, 04:58:59 PM
Difficulty retarget depend on algorithm that finds that block.
This is the diff on sha256 "difficulty" : 0.00032395, to low , and damn a lot of orphan blocks
May 25, 2015, 04:58:04 PM
Difficulty retarget depend on algorithm that finds that block.
Jump to: