Cruncher Project

Cruncher Project
- Fetches WUs from a key producer to work on or to "crunch" them
- Sends back the results to the key producer
  - Returned results contain the global project identifier
  - ... participant's local identifier
  - ... and croos-project participant identifier
- Uses the "hub" for communication
- Uses open data-interchange document formats
  - XML Descriptors
    - Test units
    - Work units
    - Crunching result
    - Profile creation
    - Profile update
- Requires a participant to register
  - The participant must be idenfyable in case of he/she "wins" the crunching contest
    - The participant can be asked if his/her identity should be revealed
  - Provides some protection against fakers
    - A CAPTCHA should be included in registration form
    - Double opt-in is highly recommended
  - The participant can desire which cruncher project he/she is joining
    - Abuse of the (opened) key producer may be limited
    - Abuse can happen by crunching a real message
    - Abuser can be reported
    - The abuser can only use the "hub" for communication, not every running cruncher
- Allows the participant to create a profile
- The acutual used encryption algorithm is not important
- Is the first application for the "hub"
- General
  - Cross-Project Participant Identifier
    - Identifies the participating user globally
    - Is being delivered with every result and request for more WUs
    - Can be made public and used in e.g. statistic pages
    - Short: CPPI
  - Global Project Identifier
    - Every cruncher is a "computing project"
    - Is a global identifier for all cruncher projects
    - Notation is in hex-decimal and at more than 40 characters long
    - Short: GPI
  - Local Participant Identifier
    - Is project's local identifie
    - This identifies the participant in the project together with the CPPI
    - Short: LPI
  - The Key Producer
    - Holds the encrypted message
    - Produces work units (WUs) for crunchers
    - Marks WUs "in progress" and attaches who is working on
    - Handles returned results and marks all completed WUs as 'done'

Cruncher Project
- Fetches WUs from a key producer to work on or to "crunch" them
- Maybe self-procudes test-units
  - They are mainly used for development of the cruncher itself
- Sends back the results to the key producer
  - Returned results contain the global project identifier
  - ... participant's local identifier
  - ... and croos-project participant identifier
- Uses the "hub" for communication
- Uses open data-interchange document formats
  - XML Descriptors
    - Test units
    - Work units
    - Crunching result
    - Profile creation
    - Profile update
- Requires a participant to register
  - The participant must be idenfyable in case of he/she "wins" the crunching contest
    - The participant can be asked if his/her identity should be revealed
  - Provides some protection against fakers
    - A CAPTCHA should be included in registration form
    - Double opt-in is highly recommended
  - The participant can desire which cruncher project he/she is joining
    - Abuse of the (opened) key producer may be limited
    - Abuse can happen by crunching a real message
    - Abuser can be reported
    - The abuser can only use the "hub" for communication, not every running cruncher
- Allows the participant to create a profile
- The acutual used encryption algorithm is not important
- Is the first application for the "hub"
- General
  - Cross-Project Participant Identifier
    - Identifies the participating user globally
    - Is being delivered with every result and request for more WUs
    - Can be made public and used in e.g. statistic pages
    - Short: CPPI
  - Global Project Identifier
    - Every cruncher is a "computing project"
    - Is a global identifier for all cruncher projects
    - Notation is in hex-decimal and at more than 40 characters long
    - Short: GPI
  - Local Participant Identifier
    - Is project's local identifie
    - This identifies the participant in the project together with the CPPI
    - Short: LPI
  - The Key Producer
    - Holds the encrypted message
    - Produces work units (WUs) for crunchers
    - Marks WUs "in progress" and attaches who is working on
    - Handles returned results and marks all completed WUs as 'done'