BOS HACKS
  • ⚒️About BOS Hacks
  • 🎉Winners
  • ⁉️FAQ
  • Hacker Manual
    • 🕑Schedule
    • ⚖️Hackathon Rules
    • 📝Registering
    • 🏆Prizes & Bounties
    • 📥How to Submit
    • ✅Evaluation Matrix
    • 🫂Finding A Team
    • 🧑‍🏫Mentors
      • 💌For Mentors
    • 👩‍⚖️Judges
    • 🏨Venues
      • 🌉NEAR SF
      • 🗽NEAR NYC
    • 📚Resources
    • 📜Code of Conduct
  • Support
    • 💸Sponsors
      • 🗳️Example Bounty
    • 🤝Community Partners
Powered by GitBook
On this page
  1. Hacker Manual

Hackathon Rules

Build without limits, but follow the rules please.

PreviousScheduleNextRegistering

Last updated 1 year ago

These are the hackathon rules, please respect them without exception.

  • Maximum of 4 people per team.

  • All code for projects must be written during the event.

  • You can fork other existing components but you must make significant changes

  • Anyone can enter before the submission deadline.

  • The judges' decision is final in determining the winning projects for prizes and awards.

  • Please comply with any other rules and additional instructions from BOS HACKS organizers.

  • Please respect our

Submission Requirements

  • All projects must be submitted via hackathon platform at https://nearbuilders.com/boshacks-submit

  • All components must be published to mainnet (if you need tokens contact the dev token fairy on the and all your teammates must be referenced in the component metadata.

  • You must submit your submission with a demo

⚖️
Code of Conduct
Build DAO telegram