> For the complete documentation index, see [llms.txt](https://docs.chiliz.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chiliz.com/community/developers-events/chiliz-sports-hackathon-july-2024/tracks-requirements-regulations-and-scoring-criteria.md).

# Tracks, Requirements, Regulations & Scoring Criteria

## The Tracks

1. Fan Utility Projects

* Retail-facing platforms focus on optimally utilizing Fan Tokens for experiences in social, commerce, and live events.

2. SportFi Projects

* DEX, Lending or SocialFi, whether or not if you integrate Fan Tokens directly, along with SportFi infrastructure projects such as Oracles and transaction facilitation tools, are all part of the discussion.

## The Qualification Requirements.

* Operational Smart Contracts: Projects must have functional smart contracts.
* Thematic Connection to Football: Projects must be related to football.

## The Regulations.

* Original Work: All submissions must be original work created during the hackathon period.
* Open Source: Projects must be open source and shared publicly on Durhack.

## The Scoring Criteria.

* Concept: Innovation and originality. (30%).
* Technical Execution: Quality and feasibility of implementation. (50%).
* User Engagement: Potential to attract and engage users (20%).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.chiliz.com/community/developers-events/chiliz-sports-hackathon-july-2024/tracks-requirements-regulations-and-scoring-criteria.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.