📢 Welcome to the Mercury Hackathon: All About NFTs! Join our Hackathon Slack Channel to qualify on our leaderboard to stand a chance to win FIL tokens and many more!

Navigation Bar

All about Mercury Hackathon: All About NFTs

🔮 Overview

👾 Tracks & Challenge Statements

🏆 Prizes & Awards

🗓 Schedule & Events

🏅 Judges

🎓 Mentors

⚖️ Judging Criteria

🌱 Submission Requirements

📚 Resources

Hackers Directory

🔗 Free Agents' Directory

📖 Teams' Directory

Hackers Leaderboard

🎁 Leaderboard

Getting Started as a Hacker At Mercury Hackathon: All About NFTs

💎 Hackers Checklist

👥 Team Formation Guide

🤝 Team Registration Guide

⬆️ Submission Guide

🖼 Projects Gallery

💬 FAQs

👮 Code of Conduct

🆘 Need Help?

Community Channel (JOIN HERE ⬇️)

🆒 Slack

Submissions Requirements 🌱

🚨 PLATFORM IS OPEN FOR SUBMISSIONS ON 18 OCTOBER AT 00:00PM UTC +08:00 AND CLOSES ON 1 NOVEMBER, 00:00AM UTC +08:00

Each team will have to submit the below artifacts onto virtual.hackathon.io by October 31, 11:55PM UTC +08:00. (We will use the submission time shown on the system as reference)

Mandatory artifacts

A. Project Description x1

This is a detail description of your team's project which should contain the following:

• Name and summary of the project
• Names/pseudonyms of team members and contact information (e.g. GitHub handle, email address, etc)
• The actual challenge statement you are submitting for and an overview of what problem is being addressed
• How the project uses IFPS and/or Filecoin and/or Flow (depending on which track you are going for)

B. 3 minute Pitch Video x1

This is a recorded pitch of your team introducing your project and solution. The pitch video should cover at least the following:

• Name of your project
• Overview of design, novelty/originality, technical complexity, daily/mass usability and impact of project (these are the judging criteria!)
• Brief demo to demonstrate the use of IPFS and/or Filecoin and/or the integration between Filecoin and Flow in some form

C. GitHub Repo Link x1

Each team to appoint 1 (one) person to create the team's GitHub repo and share the access with the team to collaborate on. During submission, the team needs to submit the link to this GitHub Repo which can be accessible to the judges.

D. List of Tech Stack Used x1

This is a list of tech stack used by the team to build your project

E. Project Demo Link

This is the URL to the live working environment of the solution you have developed

<aside> ☝ A detailed guide on how to upload your submissions onto virtual.hackathon.io will be uploaded onto the Submission Guide page nearing to the hackathon - keep a look out!

</aside>