2012

The competition report can be found Downloadhere (PDF, 496 KB)vertical_align_bottom

Winners

The main results of the competition are as follows:

• Best team: Bart Jacobs, Jan Smans (VeriFast)
• Best student team: Gidon Ernst, Jörg Pfähler (KIV)
• Distinguished user-assistance tool feature: integration of proving and run-time assertion checking in GNATprove (team member: Yannick Moy)
• Tool used by most teams: prize shared between Dafny and Why3
• Best (pre-competition) problem submission: "Optimal Replay" by Ernie Cohen

Challenges

Competition challenges will be posted here. Tentative schedule for August 30th:

• DownloadProblem 1 (ZIP, 2 KB)vertical_align_bottom announced at 14:15 (45 minutes)
• DownloadProblem 2 (ZIP, 67 KB)vertical_align_bottom announced at 15:15 (90 minutes)
• DownloadProblem 3 (ZIP, 731 Bytes)vertical_align_bottom announced at 17:00 (90 minutes)

Solutions

Below are the solutions developed by participants during and after the competition. Solutions may be updated as time goes on. The date indicates last modification of the uploaded files or the link and can be approximate.

• Downloadteam VeriFast (ZIP, 12 KB)vertical_align_bottom (competition solutions, 2012-08-30)
• external pageteam KIVcall_made (2012-09-06)
• Downloadteam GNATprove (GZ, 4 KB)vertical_align_bottom, challenges 1 and 2 (2012-12-07)
• external pageteam KeYcall_made (2013-07-11)

RULES

1. Solutions are to be submitted per email
   
2.  Submissions must state the version of the verification system used (for development versions, internal revision, timestamp, or similar unique id).
3. The main rule of the competition is no cheating is allowed. The judges may penalize or disqualify entrants in case of unfair competition behavior and may adjust the competition rules to prevent future abuse.
4. It is allowed to modify the verification system during the competition. This is to be noted in the solution(s)
5. All techniques used must be general-purpose, and are expected to extend usefully to new unseen problems
6. Internet access is allowed, but using the interget to search for problem solutions is not.
7. Involvement of other people beyond those on the team is not allowed.
8. While care is taken to ensure correctness of the reference implementations supplied with problem descriptions, the organizers do not guarantee that they are indeed correct.

(We acknowledge Geoff Sutcliffe for inspiring/suggesting some of these rules.)