This document serves as an agreement and includes all necessary information about your project.
- Project Name: [Name of your project]
- Team Name: [Legal name of your team]
- Payment Address: [Ethereum]
Project Overview 
Overview
Please provide the following:
- If the project name is not self-explanatory, provide a tagline that summarizes it in one sentence.
- Give a brief description of the project.
- Explain how the project relates to or integrates into the Relation Protocol.
- Share why your team is interested in creating this project.
Project Details
We expect teams to have a clear idea of the project’s final state. Therefore, please provide the following (where applicable):
- Mockups/designs of UI components.
- Data models/API specifications for core functionality.
- Overview of the technology stack to be used.
- Documentation of core components, protocols, architecture, etc., intended for deployment.
- Proof-of-Concept (PoC), Minimum Viable Product (MVP), or any relevant prior work or research on the topic.
- Outline any features or implementations that your project will not provide.
Ecosystem Fit
Help us understand where your project fits within the Relation ecosystem and what problems it aims to solve. Address the following questions:
- Where and how does your project fit into the ecosystem?
- Who is your target audience? (For instance, parachain/dapp/wallet/UI developers, designers, your own user base, a specific dapp’s user base)
- What needs does your project address?
Team 
Team Members
- Team Leader: [Name of team leader]
- Team Members: [Names of team members]
Contact
- Contact Name: [Full name of the contact person in your team]
- Contact Email: [Contact email, e.g., contacts@relationlabs.ai]
- Website: [Website of your team]
Team’s experience
Describe the team’s relevant experience. If your project involves development work, highlighting a few notable projects or contributions made by team members in the past would be helpful. For research-related grants, references to previous publications and projects in a related domain would be important.
Team Code Repos
Provide relevant links of your organization’s code repositories:
- Organization Repository: [GitHub link for your organization]
- Project 1 Repository: [GitHub link for project 1 under your organization]
- Project 2 Repository: [GitHub link for project 2 under your organization]
Also provide the GitHub accounts of all team members. If their accounts have no activity, references to projects hosted elsewhere or live are also acceptable.
- Team Member 1: [GitHub link for team member 1]
- Team Member 2: [GitHub link for team member 2]
Development Roadmap 
For each milestone,
- Include a detailed specification of your software. Treat it as a contract to ensure verification of software matching the specification later.
- Include the funding amount requested for each milestone.
- Include documentation (tutorials, API specifications, architecture diagrams, etc.) to ensure widespread usability of the code.
- Provide a test suite including unit and integration tests, along with a guide on how to set up and run them.
- Commit to providing Dockerfiles for project delivery.
- Indicate the duration of each milestone and the number of full-time employees dedicated to each one.
Remember: If deliverables are based on others’ work, comply with the license terms of the respective project, and clearly attribute the work in milestone documentation and source code if applicable. Failure to attribute others’ work will lead to immediate termination.
Overview
- Total Estimated Duration (of the whole project):
- Full-Time Equivalent (FTE):
- Total Costs:
Example of Milestone 1 — Integration of .SOUL Profile
- Total Estimated Duration: 1 month
- FTE: 1
- Costs: 1,000 USD
Example of Milestone 2 — BUIDL of Social DAPP
- Total Estimated Duration: 1 month
- FTE: 3
- Costs: 3,000 USD
Future Plans 
Please include here
- Short-term plans for utilizing, enhancing, promoting, and supporting your project.
- The team’s long-term plans and intentions regarding the project.
Additional Information 
Feel free to include any additional relevant information that is not already part of the application, such as:
- Work you have already completed.
- Financial contributions from other teams to the project.
- Previous grant applications you have submitted.