Dates

Hacking starts on Saturday, September 9 at 10:00 Beijing time. You or your team must start the project no earlier than this time. Deadline for submitting the project is Sunday, September 10 at 12:00 pm Beijing time.

Tracks

  • EDUCATION: The Education track pairs hackers with educators, reaching out to all levels of subjects and skills. In addition to Education events, projects aim to increase visibility of technology and to introduce basic skills to the public.
  • HEALTH: The Health track allows hackers to work with various kinds of health related data, as well as connect with mentors from the intersection of health and technology. More than ever, technology today is in a prime position to improve the quality, efficiency, and accessibility of health care.
  • FINANCE: The Finance track targets socio economic problems. Whether it is creating solutions to bridge the income gap, finding ways to serve the underbanked, or creating more accessible financial technology, this track is built on the principle that everyone should have equitable access to financial solutions.
  • ENVIRONMENT: The Energy and Environment track encompasses a technical perspective to deal with large issues impacting energy use, allocation and environmental regulations. This track has many applications, including machine learning for resource extraction, the use of green energy and enforcing environmental policy.

Certificates

Each participant will receive a certificate of participation. Besides, each winner (1st, 2nd, 3rd place) in each track will receive a certificate mentioning their track and place. Certificates will be issued by an American company, Tech Tree Root and DKU Computer Science Club.

Judging Criteria and Winner Selection

Feasibility and Impact

How well does the hack fit the track theme? How well thought-out is the concept itself, with regard to both the problem it aims to solve and the solution that has been proposed?

Innovation

How well does the hack approach the problem from a fresh perspective? Or, does the hack address a unique aspect of the problem that isn't already implemented or developed?

Functionality

How well did the team translate their concept into a working prototype? Is the hack functional, and to what extent? Is it limited to a few examples or test cases, or were you able to operate the hack yourself and use it for its intended purpose?

Overall Presentation

How was the overall presentation of the hack? Did the hackers have a prepared pitch, or was it more off-the-cuff? How convincing was the pitch? How well did the hackers understand the scope of their problem?