[RC5] What happens when the key is found?
Rubinic, Dave F.
david_rubinic at merck.com
Thu Jan 6 16:06:07 EST 2000
Towards the end of the contest, 1.5 days is a really long time to be
holding on to blocks. With a couple days to go, whenever I am connected
live I set the buffers to flush every block as its completed, and get small
blocks. That way the possibility of someone duplicating the work and
slipping in the finished block before me is much smaller. That runs about
every 10-15 minutes for me.
If that's too much flushing, even every hour or so would be better.
> From: Robert A. Rosenberg[SMTP:bob.rosenberg at digitscorp.com]
> Sent: Wednesday, January 05, 2000 2:55 PM
> To: rc5 at lists.distributed.net
> Cc: rc5 at lists.distributed.net
> Subject: Re: [RC5] What happens when the key is found?
> At 10:52 PM 01/03/2000 +0100, Jakob Paikin wrote:
> >As a fairly new participant (I haven't seen a project completed yet) I'm
> >curious about what exactly happens when the key is found (for instance in
> >the CSC project):
> >* Is the candidate key verified automatically or does someone from d.net
> >need to intervene?
> >* Would a candidate key be identified at once or only when stats etc. are
> >* Will the official proxyservers inform the clients that the project is
> >finished when blocks are flushed or only when new blocked are fetched?
> And my question - When/If blocks are going to get reissued for CSC will
> that process be at random or will the order be such that the reissued
> blocks will be issued in the same order as they originally were? It seems
> to me to be unjust that a person who was issued an original block [which
> happens to contain the looked for block] just before the start of the
> recycling can get beaten by someone who gets that block (as a recycle)
> after the start of recycling. IOW: If on average it takes a block 1.5 days
> to get returned (The blocks issued on day X are not expected to have been
> all returned before day X+4) than there should be a 1.5 day wait for day X
> blocks to get reissued (unless you run out of 3 day old blocks before
> >Jakob Paikin
> >Copenhagen, Denmark
> >To unsubscribe, send 'unsubscribe rc5' to majordomo at lists.distributed.net
> >rc5-digest subscribers replace rc5 with rc5-digest
> To unsubscribe, send 'unsubscribe rc5' to majordomo at lists.distributed.net
> rc5-digest subscribers replace rc5 with rc5-digest
To unsubscribe, send 'unsubscribe rc5' to majordomo at lists.distributed.net
rc5-digest subscribers replace rc5 with rc5-digest
More information about the rc5