[ANN] ELACOIN fork: retarg @19440 diff .3 |interval calc change? see page 11+

[CryptoMer]

I've been sending some units to the coin for a bit now. Lately, I've found some blocks, but they're immediately rejected. Happened with the last five blocks - gogo solo mining!

Found block for pool 0!
Rejected 00025f9f Diff 27.6K/10234 BLOCK! GPU 0 pool 0
New block detected on network
New block detected on network
New block detected on network
New block detected on network
New block detected on network
New block detected on network
Found block for pool 0!
Rejected 0003089f Diff 21.6K/10234 BLOCK! GPU 1 pool 0

[bubbers214]

Still no blocks for either major pools for the last 2 hours.  Something is going on.

[mat5x]

Still no blocks for either major pools for the last 2 hours.  Something is going on.

thats just reporting error. sometings up with stats reporting, but its paying out shares. this is on all 3 pools (which use the same software)

i am thinking there's a bug with the retargetting inteval changes. i bet at 19400 things clear up nbut i dont know the software well.

maybe one of the 3 pool operators can comment.

WindMaster?

note the negative shares reported on ZeroPool.

zeropool IS finding blocks:

proof-of-work found 
  hash: 000000000f58129f05a2de1c1128eff79dbfb6624ca08ef06ed1615bef8aa1b9 
target: 00000000cce90000000000000000000000000000000000000000000000000000
CBlock(hash=1e314295a5ebd3aa2578, PoW=000000000f58129f05a2, ver=1, hashPrevBlock=381151d6190187646a4e, hashMerkleRoot=9866b6f29a, nTime=1370326748, nBits=1d00cce9, nNonce=2013293824, vtx=1)
  CTransaction(hash=9866b6f29a, ver=1, vin.size=1, vout.size=1, nLockTime=0)
    CTxIn(COutPoint(0000000000, -1), coinbase 04db86ad510109062f503253482f)
    CTxOut(nValue=0.90979200, scriptPubKey=022b9212cea3821d494cd934dde681)
  vMerkleTree: 9866b6f29a

[bubbers214]

Still no blocks for either major pools for the last 2 hours.  Something is going on.

thats just reporting error. sometings up with stats reporting, but its paying out shares. this is on all 3 pools (which use the same software)

i am thinking there's a bug with the retargetting inteval changes. i bet at 19400 things clear up nbut i dont know the software well.

maybe one of the 3 pool operators can comment.

WindMaster?

note the negative shares reported on ZeroPool.

zeropool IS finding blocks:

proof-of-work found  
  hash: 000000000f58129f05a2de1c1128eff79dbfb6624ca08ef06ed1615bef8aa1b9  
target: 00000000cce90000000000000000000000000000000000000000000000000000
CBlock(hash=1e314295a5ebd3aa2578, PoW=000000000f58129f05a2, ver=1, hashPrevBlock=381151d6190187646a4e, hashMerkleRoot=9866b6f29a, nTime=1370326748, nBits=1d00cce9, nNonce=2013293824, vtx=1)
  CTransaction(hash=9866b6f29a, ver=1, vin.size=1, vout.size=1, nLockTime=0)
    CTxIn(COutPoint(0000000000, -1), coinbase 04db86ad510109062f503253482f)
    CTxOut(nValue=0.90979200, scriptPubKey=022b9212cea3821d494cd934dde681)
  vMerkleTree: 9866b6f29a

On http://elc.scryptmining.com/ which was the one I was mining on with about 5500 KH/s there are over 220,000 shares on this current round, which is crazy for a difficulty at just over 1.  And it still shows that I have 9000 unpaid shares, which leads me to believe that the shares are being reported but the blocks aren't actually being found.  I mean, I guess I could be wrong and it's just a stats problem, but it all seems pretty strange.

[mat5x]

I've been sending some units to the coin for a bit now. Lately, I've found some blocks, but they're immediately rejected. Happened with the last five blocks - gogo solo mining!

Found block for pool 0!
Rejected 00025f9f Diff 27.6K/10234 BLOCK! GPU 0 pool 0
New block detected on network
New block detected on network
New block detected on network
New block detected on network
New block detected on network
New block detected on network
Found block for pool 0!
Rejected 0003089f Diff 21.6K/10234 BLOCK! GPU 1 pool 0

likely cuz of the very fast block times we were having when 80MH joined the network when the coin became profitable based on a 0.05BTC deep base because coinChoose values things wrong.

[mat5x]

On http://elc.scryptmining.com/ which was the one I was mining on with about 5500 KH/s there are over 220,000 shares on this current round, which is crazy for a difficulty at just over 1.  And it still shows that I have 9000 unpaid shares, which leads me to believe that the shares are being reported but the blocks aren't actually being found.  I mean, I guess I could be wrong and it's just a stats problem, but it all seems pretty strange.

its a bug with the pool software. welcome to experimental software. (BTC is experimental too, there's no refunds available from the issuing company you bought the software box from.)

i didnt write the pool software and it seems we've uncovered an issue. im sure sufficient logs are available to split out the values properly, i mean i see zero pool giving me proper shares too.
those shares just have to be triggered to be paid out.

at 19400 i have a feeling things will all go back to normal. I think the retargetting interval change confused the pool payout scheduler.

[bubbers214]

On http://elc.scryptmining.com/ which was the one I was mining on with about 5500 KH/s there are over 220,000 shares on this current round, which is crazy for a difficulty at just over 1.  And it still shows that I have 9000 unpaid shares, which leads me to believe that the shares are being reported but the blocks aren't actually being found.  I mean, I guess I could be wrong and it's just a stats problem, but it all seems pretty strange.

its a bug with the pool software. welcome to experimental software. (BTC is experimental too, there's no refunds available from the issuing company you bought the software box from.)

i didnt write the pool software and it seems we've uncovered an issue. im sure sufficient logs are available to split out the values properly, i mean i see zero pool giving me proper shares too.
those shares just have to be triggered to be paid out.

at 19400 i have a feeling things will all go back to normal. I think the retargetting interval change confused the pool payout scheduler.

Makes sense, I guess we shall see when we hit 19400, which at the the hashrate it's going at now, shouldn't be too long.

[Megabit91]

Eb388DYtDQdo2oEm6h9rMBFDZQzHfjQ4Xr

Thanks!!!

[DimaTH]

EgSpKKjW1cGVQJ1Lif2CJLYZ6YZm57k1Ei
thank you!

[CrossFire]

Ednbnoowt3upxM3VjznnbX2zitntHe397f

thx!

[AlbertNik]

EJppteWBZqzdrsQmXiV9d5G1RzRKoEGXLg

[Oktan95]

EaGtxDK4hSNScMK5Ekt8JNXx2DBYBANdmG   

[Hummer487]

EQPyGHWA9BCDFPz14Kaunkt2nH13f2mNUA

[ViktorSk]

EHVXdL4eVSCz9eJ6GLs2KX9fecQXjq4N7E

Thank you!

[OktaLp5]

Ecun64y8XwUi8zvRxQq6uqaZGXtMFKgbWp

[DennGSA]

EahnruF4kd83k9oiGDnczvozTUnGvGiovU

thanks.

[StelsF71]

EdHXCk5EoDg2K3pNAhUuXc5MHuYnbVC2c3

[CubGTX]

EP85VXArNJ1TYh4jFSLF6NqqGf7yJnkU1u

[KovalSp]

ERkdhYPQTSGHMBZkdwoevaMXMpeehHf4zu

Thank you!!!

[AntonW91]

EPgUfzjbLrQw2BtBsxYwy7ejQJ9X8jgZPH

Thanks!