1. The BUIDL_QUESTS

    1. These Rules apply to the BUIDL_QUESTS 2025 (the “BUIDL_QUESTS”).
    2. The BUIDL_QUESTS is a hybrid hackathon event taking place from 21 July 2025 to 20 August 2025.
      1. The Virtual Qualifiers will commence on 21 July 2025 and end on 20 August 2025, 11:59 AM SGT/GMT+8.
      2. The Virtual Finals will take place on 1 September 2025 and end on 15 September 2025, 11:59 AM SGT/GMT+8.
      3. The BUIDL_QUESTS will culminate in an in-person Pitching, Judging, and Closing Ceremony on 30 September 2025 in Singapore (the “BUIDL_QUESTS Finals Premises”).
      4. All shortlisted BUIDL_QUESTS Teams are expected to attend the Virtual Finals and in-person Pitching, Judging, and Closing Ceremony. Failure to attend may result in the forfeiture of the BUIDL_QUESTS Team’s position as a BUIDL_QUESTS finalist and relevant prizes.
    3. Participants are required to wear lanyards for identification at all times within the BUIDL_QUESTS Finals Premises.
    4. Age Restrictions: Participants must be at least 16 years of age. Participants below the age of 18 are required to obtain explicit consent from his or her legal parent/guardian to participate in this BUIDL_QUESTS, and must provide the parent’s/guardian’s details during registration.
    5. Geographical Restrictions: By agreeing to participate in this BUIDL_QUESTS, you possess the residency in a jurisdiction that the BUIDL_QUESTS offers its Services legally and are not on any trade or economic sanctions lists, including, without limitation, the UN Security Council Sanctions List, designated as a “Specially Designated National” by OFAC (Office of Foreign Assets Control of the U.S. Treasury Department) or placed on the U.S. Commerce Department’s “Denied Persons List”. amber.ac and/or Amber Group maintains the right to select its markets and jurisdictions to operate and may restrict or deny the BUIDL_QUESTS access in certain countries at its discretion.

  2. Standards for Projects BUILD_QUESTS 2025

    1. In BUIDL_QUESTS 2025, we seek projects that exemplify the following defining traits, forging new paths of innovation and transformative impact in AgentFi!

      Standards for Exceptional Projects

  3. Teams

    1. Participants are to form BUIDL_QUESTS Teams, and each BUIDL_QUESTS Team must consist of at least one (1) member and shall not exceed five (5) members.
    2. Each BUIDL_QUESTS Team shall appoint one (1) Participant as the BUIDL_QUESTS Team’s representative.
    3. The BUIDL_QUESTS Team’s representative is to submit the list of members in their BUIDL_QUESTS Team to amber.ac, by such date as may be required by amber.ac.
    4. Any person who attempts to participate under multiple identities or uses any scheme, device or artifice to submit multiple entries in violation of any limitation will be disqualified.

  4. Participants’ Code of Conduct

    1. The Participants consist of people from countries around the world, and we expect all Participants to respect the diversity of our community. Content containing illegal or excessive obscene or foul language, excessive violence, nudity, or sexual activity will be flagged and removed. Content that is abusive or likely to be offensive to others may also be flagged and removed.
    2. As the BUIDL_QUESTS is an ongoing process over a period of time, BUIDL_QUESTS Participants, amber.ac, and Amber Group may not be as responsive as you may hope for, due to reasons such as, amongst others, time zone differences, personal commitments outside the BUIDL_QUESTS, and work or education commitments. Therefore, we seek understanding from all involved parties in the BUIDL_QUESTS to respect each individual's boundaries, external commitments, or circumstances. Acts of disrespect to Participants, amber.ac, or Amber Group include, but are not limited to, constant messaging within an unreasonably short period, flooding the BUIDL_QUESTS main channel(s) without providing a reasonable amount of time for responses to be made, use of abusive and/or demanding language, etc.
    3. We value integrity and expect you to represent who you are and your BUIDL_QUESTS Team honestly in your submissions and in any form that we share with you during the BUIDL_QUESTS.
    4. We celebrate makers, creators, developers and want to help each of you who are part of this community grow, and improve your skills. When you share feedback, please keep it constructive. Any content that is abusive, threatening, expresses hatred, or is likely to offend others is unacceptable and may result in the content being removed, the suspension or termination of your account, or disqualification from the BUIDL_QUESTS, at the sole discretion of amber.ac and/or Amber Group.
    5. Do not share or post any personal or private information about yourself or any other person. This includes any photos (unless you have explicit permission to do so), phone numbers, addresses, location details, personal email, and social media profiles.
    6. Our community and platforms help showcase software, participate in virtual challenges and BUIDL_QUESTSs, share your ideas, code, get feedback, and find motivation. Do not upload anything unrelated, explicit, repeatedly post the same thing, or post anything that is not relevant to the event that you are participating in, or send excessive, unsolicited messages to other users.

  5. Project Rules

    1. The hacking period and Submission Period for the BUIDL_QUESTS shall be as follows:
      1. Virtual Qualifiers Period: 21 July 2025, 8:00 PM SGT/GMT+8 to 20 August 2025, 11:59 AM SGT/GMT+8.
      2. Virtual Finals Period: 1 September 2025, 12:00 PM SGT/GMT+8 to 15 September 2025, 11:59 AM SGT/GMT+8
      3. The BUIDL_QUESTS Team’s representative must submit the Team’s Submission to the BUIDL_QUESTS’s submission portal during the official Submission Period.
    2. You and your BUIDL_QUESTS Team are strictly not allowed to submit Submissions that are not created by you or that are not what you have worked on during the period of the BUIDL_QUESTS. If other projects could be great resources, kindly reach out to amber.ac or Amber Group in the community and request to add such projects to the resources.
    3. You and your BUIDL_QUESTS Team are not allowed to work on your project before the hacking period stipulated in Rule 4.a. Each team is required to use version control for their code throughout the course of the BUIDL_QUESTS. Any repositories with single commits of large files without proper history will be assumed to be unqualified unless proven otherwise.
    4. Each Submission will be judged solely on what you and your BUIDL_QUESTS team have worked on during the duration of the BUIDL_QUESTS. Each team is required to share the source code of the Submission on the Submission Portal.
    5. If you or your BUIDL_QUESTS Team are using an existing project, you must credit the project by disclosing all details of the same and outline the improvements made to the project during the official hacking periods in your Submission, provided always that the Intellectual Property Rights of such existing project is exclusively owned by you or a member of your BUIDL_QUESTS Team. The existing project must also not have been previously funded/bonded in other similar accelerator/incubator programmes. Failure to comply with this Rule 4.e may result in the disqualification of you and your BUIDL_QUESTS Team and the team’s Submission.
    6. If someone has helped you or contributed to your Submission, you must credit them in your Submission for their contribution.
    7. Make sure to check the license of any public repository before you use it for your Submission and give the appropriate credit to that repository and the creator in your Submission. You cannot utilize content that violates any third party’s rights (including privacy, personality, moral or intellectual property rights, or that constitutes copyright infringement) unless you have acquired the necessary rights to do so or the content is subject to an open source license.
    8. When making your BUIDL_QUESTS Submission, you must ensure that your Submission adheres to the Fresh Code Rule (as defined below) or that you have the right to use any existing content that forms the whole or a part of your Submission. This includes, without limitation, images, lines of code, or demonstration videos in your Submission.
    9. You must ensure that you have the permission from all persons, venues, and/or entities who worked on or were engaged to work on or contributed in any respect to the Submission or any part thereof. Otherwise, please do not use such material and do not upload the same in your Submission.
    10. The use of generative AI tools, including but not limited to tools for code completion (e.g., GitHub Copilot), chatbots (e.g., ChatGPT), image generation (e.g., Midjourney, DALLE), etc., is approved for the BUIDL_QUESTS as long as no personal, confidential, or restricted information is used with the AI tool. You and/or your BUIDL_QUESTS Team who use AI technologies do so at your own risk. In the event that you and/or your BUIDL_QUESTS Team expose proprietary, sensitive, confidential, or personally identifiable data to an AI tool, amber.ac reserves the right to disqualify you and/or your BUIDL_QUESTS Team from the BUIDL_QUESTS, and any consequences arising thereof shall be solely borne by you and/or your BUIDL_QUESTS Team.
    11. You and your BUIDL_QUESTS team are responsible for ensuring that any code, datasets, or similar assets generated using generative AI tools in your Submission adhere to Rules 4.f to 4.j above.
    12. Any usage of generative AI tools must be specifically credited in your Submission, describing the extent of the use and which parts of the Submission it was used for.

  6. The Fresh Code Rule

    1. All BUIDL_QUESTS Teams should strictly adhere to the fresh code rule, under which the following should be adhered to (the “Fresh Code Rule”):
      1. What can be done before the BUIDL_QUESTS
        1. BUIDL_QUESTS Teams can create wireframes, designs, and user flow.
        2. BUIDL_QUESTS Teams can pre-train models or gather data sets prior to the event.
      2. What must be done during the BUIDL_QUESTS
        1. All code submitted as part of the Submission must be written during the BUIDL_QUESTS and submitted before the expiry of the Submission Period (as per Rule 4.a).
    2. Provided that the Fresh Code Rule is adhered to, Participants and/or their BUIDL_QUESTS Team are allowed to use any coding languages or open-source libraries as part of their Submission.

  7. Intellectual Property Rights

    1. Save as otherwise agreed with the relevant BUIDL_QUESTS Team (including under these BUIDL_QUESTS Rules and the amber.ac Terms of Service), all Intellectual Property Rights subsisting in a BUIDL_QUESTS Team’s Submission shall remain vested in such BUIDL_QUESTS Team.

  8. Prizes

    1. Participants are only eligible to win up to one (1) Main Prize.
    2. The prizes for the BUIDL_QUESTS are denominated in USD or equivalent value of crypto-currency, and include all applicable taxes and fees associated with prize receipt and/or use by the prize recipients. Prize recipients will be required to provide the necessary payment and/or distribution details requested by Amber Group in a timely and accurate fashion to receive the relevant prize.

  9. Removal of Content and Terms

    1. amber.ac and/or Amber Group reserves the right to remove your content and/or block or remove your account from the platform if we believe that you have violated any of the guidelines mentioned above.
    2. You acknowledge and agree that amber.ac and/or Amber Group may refuse registration and subsequent access to you or cancel your participation in the BUIDL_QUESTS or any access if it reasonably determines that you are not eligible to take part in the BUIDL_QUESTS.

  10. Incorporation of General Terms

    1. In addition to these BUIDL_QUESTS Rules, please read our terms of service, privacy policy, and code of conduct for terms that also apply to your participation in the BUIDL_QUESTS.
    2. amber.ac and/or Amber Group reserve the right to modify these BUIDL_QUESTS Rules without prior notice.