Topic: [ANN] ELACOIN fork: retarg @19440 diff .3 |interval calc change? see page 11+ - page 10. (Read 10053 times)

ES8PY56nPwwzqp6YMZr3VX44AHfZNbwoKa

EQ7z4k56qTxGPJ2XAF9b9o6u2Nobsw6iKT
thanks!

EV1w2Pc49vXvwG6uH3ppRp7vrszb1EANYV

EUpi5qu1jFH2BjRYzChCFUoQVLpcfgLTnJ

tnx!

EVsjoepfRgQ8Vo1bUpRrZupE4SuC93yJMh

Many thanks.

EHamitRrQ6W5K4jbYuya8pUwNnea3gUL87

Thank you!!

EK2HYvJhd4hHKSU8vdDZWWRxEh5epJbAaa

EVusVVrv3xfJGGX4Rcfce7Wv1ahP8RkVuK   

haha nice!  0.959 is all miiiiiiiiiiiine!

i just solved a block for the pool  

but nearmiss gets the loot!

No, the hashrate reported by clients is an estimate. Im not sure what its based on. Look at the actual block timestamps going back and make your own estimate, along with how the weather, the FED's announcement of QE4 and the price of tea in china will affect recent block hashing rates

grep "new best" debug.log is handy in that respect, and you can even do  grep 'new best' debug.log | tr -s " " "," >> blocktimes.csv and import it into a spreadsheet and play with the numbers. Then make some deep pronouncement about hashrates and difficulty.

When you've figured that out, go make a mint on TRC cuz I cant figure out why the diff STILL goes up and down. Its a weird social phenomenon.

I see about .8 to 1.2 hrs per block, but luck works too, we had a 4 minute block this morn and a 4 hour. So who knows. And hashrates are coming on and offline constantly. Make a guess.

If you read the code, the max retarg downwards is /16, and it will likely be that becasue of the slow blocktimes back 135 blocks, so we're looking at 4.32556 /16 = .27 diff. that will be 16x faster blocks than .8 to 1.2 hrs average, so something like 3 to 4.5 minutes, but no one knows.


understatement. yes, thats the whole reason for this. if it HAD made it to 24 it woulda been ok, but its like a rocket failing to achieve orbit. so close yet so far.

sent 1.0 to EPgVazGU13FrKUedcTVARR52vfnoF9aFgN
sent 1.0 to EemVzD8FRBvjpxEDTLGzqvVZG2HTRttUYa

4343004

anyone got an idea how long it will take to clear these three blocks? and is that hash rate i see correct?

That part wasn't us... It was Milkshake.
The fixes we're us

you should have done this from the start. waiting for dificulty 24 before the first reward doubling was stupid 

EemVzD8FRBvjpxEDTLGzqvVZG2HTRttUYa

thank you!

thanks,

3 blocks to go!!

i'm on the right chain right?

{
"blocks" : 17817,
"currentblocksize" : 3048,
"currentblocktx" : 13,
"difficulty" : 4.32556970,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 4343004,
"pooledtx" : 13,
"testnet" : false
}

EPgVazGU13FrKUedcTVARR52vfnoF9aFgN

Thanks!

sent 1.0 to EZWrr4BXKgDd7bv3cbzDR1994Ay7uV4tJq
sent 1.0 to ETYvanvSSXUYqe8FXewTUh1vdPAwmFtZXN
sent 1.0 to ETsndFoMJebKfFwHA3BhNQdvuaxwnKM78N
sent 1.0 to EPPvBtENxA5BYaGVQ6AsYfS32tT6mxPFMg
sent 1.0 to EKnaMqTzZ4iANobSKaTtiZbxHv4pMZRa6A
sent 1.0 to EcWGYswy3HxYsEQyCoWgQEeb4tdjQtJ5hR
sent 1.0 to EatFXHKRBGbppevWk7aKRNguXuZPfW83RW
sent 1.0 to ETDHHrzwskHR55xaZKsAi6f4BufFibtHcp
sent 1.0 to EYr5e4sQXiaRj32kpMeFLhEFJanCKPRgis
sent 1.0 to EQaXdXpaBLWuz6Rxgo8EVGVw4B4jqHNzdV
sent 1.0 to EbZRjYoK3tfhSuw3uy7NU17LJhq6DHkPR6
sent 1.0 to EHsZxmpAAfFDq2vZ51xCS8qNam7gKbD8cd
sent 1.0 to ES37eTmAJ5jbdw4qWqn288r3y4VrFzBUqE
sent 1.0 to EbFny7GUgUYMVrDygBmDtQQbVF8oRzDC9Y
sent 1.0 to EP1wpBRKscs9tUBtCrnbEuYCXzYnNC929w
sent 1.0 to ETtZBKtFSZc1xNGmGcnUa9YmQXoW4WQtVs
sent 1.0 to Ebi9N6iR4VZVY5H9jwTUWGY9GsnD5pRgg9
sent 1.0 to EUYmDg5Z5LJgUSuCgQC7ekP6E2cQyGZ8VQ
sent 1.0 to EZ6RT2nL2zJ6XbVmLFzKtnJFSVZBtYna6i
sent 1.0 to EUdnYtDyuDrQ8ER7Dh96yonSJXU1J6qmhz

addnode as per the wiki and see 2nd post in this thread.

finally yay!!!


me, me, meeeeee!!!!!

EUdnYtDyuDrQ8ER7Dh96yonSJXU1J6qmhz