I'm missing 500 RC5 blocks from yesterdays results....

[Daaavo]

I'm not sure if this is usual or not (as I've only been doing this for a month and a half) but I seem to be missing 500blocks from yesterdays update. If you look here you can see that I submitted 1728 blocks, but here it only shows 1276 were counted. Will the missing blocks be added tonight???? Has this happened to anyone else?

Thanks for any info.



dave

 

[Dee67]

I'm down 484 myself.. If I'm not mistaken it falls under the category of "it happens" 🙁

 

[BurntKooshie]

This happens from time to time...sometimes it's on D.nets end, sometimes it's because you did some "randoms", and sometimes it's because people who were doing randoms decided to flush 'em before you got yours in, so theirs counted and yours didn't 🙁

 

[Adul]

i am missing 2.5k :|

 

[rc5]

It can also be blamed on some proxies, That's why I flash back dnet directly. ;P

 

[GeoffS]

Down 3k 🙁

 

[Daaavo]

Burntkooshie,

What exactly are randoms???? Is there a way to avoid doing them??

I mean, for some people 500 blocks is nothing. But for me, it's close to 1/3 of my daily output.

Thanks

dave

 

[GeoffS]

Randoms occur when your buff-in is empty and the client starts making up work for itself. If you know this didn't happen, then you may have 'lost' blocks. Before you panic, wait for tonight's update... you may be up 500! 🙂

 

[GrInNer]

I lost 2k when I flushed to a random pproxy... and I'm in a tight run for 31st spot... i could have used them yesterday!! :disgust:

edit: But i got 80 back when Russ flushed to my pproxy to confirm it was up and running 😀 Thanks Russ!!

 

[Polo]

Down 4k... 🙁 And I don't think there are randoms.... 🙁 🙁

 

[JimMc]

Off 500 🙁

 

[AppleTalking]

Well, I'm missing about 1,500 out a total production of 15,800. That's about 10%. Usually they turn up the next night, but sometimes I think they go to that big block pool in the sky.

Nick

 

[JimMc]

The best way to to get credit for all your blocks is too keep a small in-buffer, enough for a day or so, and finish the buffer before you fetch. That will reduce the likelihood that you will crack a block that has been sitting in your buffer for several weeks and is finally cracked by someone that has had it so long Dnet reissued it--I believe if Dnet doesn't get a block back after 90 days or so it reissues it. Whoever flushes it first gets credit for it. The risk is if your cow loses connectivity or the Proxy goes down, it can't fetch and you're doing 100% randoms.

 

[JJWalker]

Will a person who is connected 24/7 to the internet always get 'fresh' blocks??? I mean, if you keep your buffer to a day, when it's finished crunching on those, will the program automatically flush what's in the output buffer and then reload itself with 'good' blocks??

 

[JimMc]

When it flushes depends on the settings in your .ini. Your best chance for "fresh" blocks is full fetches every day, but it is usually not that big a problem, I would guess less of a problem then the chance that you won't be able to connect and you'll sit there all night crackin' randoms.