# Web 3 Hackathon Template ###### tags: `hackathon`, `template`, `BNB` Create your own template and add your "Project.md" file under the Application folder you forked and fill in as much of the information when submitting a pull request. - **Project Name:** Name of your project - **Team Name:** Legal name of your team - **Payment Address:** Binance Smart Chain (BUSD/BNB) payment address. Please also specify the currency. (e.g. 0x8920... (BNB)) > ⚠️ *The combination of your GitHub account submitting the application and the payment address above will be your unique identifier during the Hackathon. Please keep them safe.* ## Project Overview :page_facing_up: If this submission is in response to an RFP, please indicate this on the first line of this section. If this is a submission for a follow-up request (the continuation of an earlier, successful W3F submission), please provide name and/or pull request of said submission on the first line of this section. ### Hackathon Overview Please provide the following: - If the name of your project is not descriptive, a tag line (one sentence summary). - A brief description of your project. - An indication of how your project relates to / integrates into Findora / Yellow Submarine. - An indication of why your team is interested in creating this project. ### Project Details We expect the teams to already have a solid idea about your project's expected final state. Therefore, we ask the teams to submit (where relevant): We do not expect projects to be fully deployed to Findora mainnet - please attach as information in an organized way that is legible. - Mockups/designs of any UI components - Data models / API specifications of the core functionality - An overview of the technology stack to be used - Documentation of core components, protocols, architecture, etc. to be deployed - PoC/MVP or other relevant prior work or research on the topic - What your project is _not_ or will _not_ provide or implement - This is a place for you to manage expectations and to clarify any limitations that might not be obvious Things that do not need to be part of the application: - The (future) tokenomics of your project - For non-infrastructure projects—deployment and hosting costs, maintenance or audits - Business-oriented activities (marketing, business planning), events or outreach ### Ecosystem Fit Help us locate your project in the ZKP landscape and what problems it tries to solve by answering each of these questions: - Where and how does your project fit into the ecosystem? - Who is your target audience (Findora/dapp/wallet/UI developers, designers, your own user base, some dapp's userbase, yourself)? - What need(s) does your project meet? - Are there any other projects similar to yours in the Ethereum / Findora ecosystem? - If so, how is your project different? - If not, are there similar projects in related ecosystems? ## Team :busts_in_silhouette: ### Team members - Name of team leader - Names of team members ### Contact - **Contact Name:** Full name of the contact person in your team - **Contact Email:** Contact email (e.g. john@duo.com) - **Website:** ### Legal Structure *If applicable...* - **Registered Address:** Address of your registered legal entity, if available. Please keep it in a single line. (e.g. High Street 1, London LK1 234, UK) - **Registered Legal Entity:** Name of your registered legal entity, if available. (e.g. Duo Ltd.) ### Team's experience Please describe the team's relevant experience. If your project involves development work, we would appreciate it if you singled out a few interesting projects or contributions made by team members in the past. For research-related submissions, references to past publications and projects in a related domain are helpful. If anyone on your team has applied for a grant for the Findora Foundation previously, please list the name of the project and legal entity here. ### Team Code Repos - https://github.com/<your_organisation> - https://github.com/<your_organisation>/<project_1> - https://github.com/<your_organisation>/<project_2> Please also provide the GitHub accounts of all team members. If they contain no activity, references to projects hosted elsewhere or live are also fine. - https://github.com/<team_member_1> - https://github.com/<team_member_2> ### Team LinkedIn Profiles (if available) - https://www.linkedin.com/<person_1> - https://www.linkedin.com/<person_2> ## Development Status :open_book: If you've already started implementing your project or it is part of a larger repository, please provide a link and a description of the code here. In any case, please provide some documentation on the research and other work you have conducted before Submitting. This could be: - links to improvement proposals or [RFPs](https://github.com/w3f/Grants-Program/tree/master/rfp-proposal) (requests for proposal), - academic publications relevant to the problem, - links to your research diary, blog posts, articles, forum discussions or open GitHub issues, - references to conversations you might have had related to this project with anyone from the Web3 Foundation, - previous interface iterations, such as mock-ups and wireframes. ### Overview - **Total Estimated Duration:** Duration of the whole project (e.g. 2 months) - **Milesstones and costs for full delivery** We recommend that you submit a grant proposal in addition to your hackathon submission if your project intends to continue developing after the deadline of the ZKCircuit (https://form.typeform.com/to/uWokKMwO?typeform-source=www.findora.foundation) ## Future Plans **Please include here** - how you intend to use, enhance, promote and support your project in the short term, and - the team's long-term plans and intentions in relation to it? ## Additional Information :heavy_plus_sign: **How did you hear about the ____ Hackahton?** Web3 Foundation Website / Medium / Twitter / Telegram / Announcement by another team / personal recommendation / etc. Here you can also add any additional information that you think is relevant to this application but isn't part of it already, such as: - Work you have already done. - If there are any other teams who have already contributed (financially) to the project. - Previous hackathons/submissions/grants etc. you may have applied for previously or are currently applying for now.