---
id: <proposal number (same as PR)>
period: <Period number (Integer) (When do you want to submit your proposal)>
title: <The proposal title is a few words, not a complete sentence>
author: <a comma separated list of the author's or authors' name + GitHub username (in parenthesis), or name and email (in angle brackets).  Example, FirstName LastName (@GitHubUsername), FirstName LastName <foo@bar.com>, FirstName (@GitHubUsername) and GitHubUsername (@GitHubUsername)>
email: <Email address to start the contract process >
discussions-to: <Indicating the URL where the proposal is being discussed>
company_name: <Name of the company>
category: <dApps, Tools, Community, Other>
focus_area: <Banking,DEX,Defi,Deployment,Education,Gaming,IDE,Identity,Libraries,Metaverse,Monitoring,Node,NFT,Oracle,Social,Storage,Teal,User Onboarding,Wallet, Other>
open_source: <Yes, No>
funding_type: <Proactive, Retroactive>
amount_requested: <Amount (integer) requested in ALGO, it should be at least 10000>
delivery_date: <project delivery date, in ISO 8601 (yyyy-mm-dd) format>
status: <Draft, Final, Approved>
---

>Proposals that do not include information on all template sections will be rejected.
>Please, before submitting the grant proposal, review the contract template and ensure you're comfortable with its terms.  <a href="https://drive.google.com/file/d/1dsKwQGhnS3h_PrSkoidhnvqlX7soLpZ-/view">Contract Template</a> 

## Abstract
A summary of the project, including how the Algorand ecosystem would benefit  (proactive)/ has benefitted (retroactive) from its implementation.

## Team
Information about the team members and their qualifications, including relevant experience and skills.

## Experience with Algorand
Details about the team's experience with the Algorand protocol and any previous projects built on it.
> eg
    > Using SDKs 
    > Building applications
    > Understanding of DApps
    > Knowledge about the ecosystem
    > Running nodes

## Present Proposal
A detailed plan for the development and implementation of the proposal.

To enhance clarity and accountability, we're asking proposers to detail the maintenance period, availability, and sustainability plans for their projects. This includes information on potential costs and the duration for which services will be offered at no or reduced cost

### Deliverable
Proposals must include clear, non-technical descriptions of deliverables. We encourage the use of multimedia (blog/video) to help explain your proposal's benefits to the community. 

Proposals that do not specify deliverables and a process to check deliverables will be rejected.

## Future Blueprint
> This part can be optional for one-time grants.
A high-level plan, defining an overarching strategic objective and capturing the major steps planned for achieving the project at a greater scale.

> For Milestone-based grants, please refer to <a href="https://github.com/algorandfoundation/ARCs/blob/main/ARCs/arc-0034.md#submit-a-proposal"> How to submit a proposal</a>.

## Benefits for the community
A description of the potential benefits that the proposal could bring to the Algorand community and its users.

## Additional information
Any other relevant details or documentation that the team would like to include in the proposal.
> To prevent malicious links and allow front-end to display links properly, **External Links** should be in this format `<a href="https://arc.algorand.foundation/">ARC</a>`
> To create a new tab when people click on your links, you can use `target="_blank"` like this `<a href="https://arc.algorand.foundation/" target="_blank" >ARC</a>`
