Hackathon Date: 7-8th Oct 2023
- Problem statement: vechain track / BCG track
- Are you applying for the grant with the same project you submitted at the vechain Hackathon: Yes / No
If you select "Yes," please provide:
- Project name:
- Team name:
- GitHub handle:
- College / Employer:
- Payment Address: USDC (ERC 20) payment address. We don't accept payments for the program in other currencies at this stage.
If you select "No," please provide:
- Project name:
- Twitter handle:
- GitHub handle:
- College / Employer:
- Payment Address: USDC (ERC 20) payment address. We don't accept payments for the program in other currencies at this stage.
⚠️ The combination of your GitHub account submitting the application and the payment address above will be your unique identifier during the program. Please keep them safe.
Please provide the following:
- A brief description of the project.
- An indication of why your team is interested in creating this project within the vechain Ecosystem.
- Link to project’s one-pager template (provided by BCG at the Hackathon).
- Link to pitch deck
We expect the teams to already have a solid idea about the project's expected final state. Therefore, we ask the teams to submit (where relevant):
- Mockups/designs of any UI components
- 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
Are there any other projects similar to yours? If so, how is your project different?
- Name of team leader
- Names of team members
- https://<your_domain>
Please describe the team's relevant experience. If the project involves development work, then we'd appreciated it if you can single out a few interesting codes commits made by team members on their past projects.
- https://github.com/<your_repo_1>
- https://github.com/<your_repo_2>
- https://www.linkedin.com/<person_1>
- https://www.linkedin.com/<person_2>
This section should break out the development roadmap into a number of milestones. Since the milestones will appear in the grant contract, it helps to describe the functionality we should expect, plus how we can check that such functionality exists in the product. Whenever milestones are delivered, we refer to the contract to ensure that everything has been delivered as expected.
Below we provide an example roadmap. For each milestone:
- Please indicate the milestone duration, workload in terms of full-time equivalent (FTE) and cost.
- Please be sure to include a specification of the software. The level of details must be high enough so that we are able to verify that the software meets the specification.
- Please note that we require documentation (e.g. tutorials, API specifications, architecture details) in each milestone. This ensures that the code can be widely used by the community.
- Please provide a test suite, comprising unit and integration tests, along with a guide on how to run these.
- Please commit to providing dockerfiles for the delivery of your project.
Milestone 1 | Milestone 2 | Total | |
---|---|---|---|
Estimated Duration | 30 d | 30 d | 60 d |
Full-time equivalent (FTE) | 2 | 1 | 3 |
Cost (up to $ 30,000) | $ 5,000 | $ 10,000 | $ 15,000 |
Number | Deliverable | Specification |
---|---|---|
0a. | License | Apache 2.0 / MIT / Unlicense |
0b. | Documentation | We will provide both inline documentation of the code and a basic tutorial that can interact with the deployed smart contracts and backend service. |
0c. | Testing Guide | The code will have proper unit-test coverage (e.g. 90%) to ensure functionality and robustness. In the guide, we will describe how to run these tests |
1 | Smart Contracts | We will develop smart contracts that will... (Please list the functionality that will be coded for the contracts) . We will open source the smart contract and upload the ABI to B32. |
2 | Backend | "We will create a backend service that will... (Please list the functionality that will be coded for the backend)" |
Number | Deliverable | Specification |
---|---|---|
1 | User Guide | We will provide a user guide or a demo video to show what features have been done. |
... |
As part of the Program, we require that you produce and publish at least one article/tutorial (e.g., on Medium). It should explain your work done as part of the grant.
Please provide a link to your Twitter, YouTube, website or Medium article.
Please include the team's long-term project plans, operation plans and intentions.
Any additional information that you think is relevant to this application that hasn't already been included.
Possible additional information to include:
- What work has been done so far?
- Are there any teams who have already contributed (financially) to the project?
- Have you applied for other grants so far?