# Builder Program As the testnet progresses enthusiastically, we will collaborate with top global developer communities and conduct online workshops. Our core team members will lead developers to explore Ola, deploying a variety of interesting dApps on our testnet using Ola-lang. Developers who deploy any type of contract on Ola will be entitled to the Discord Role "Ola Builder," receive an "Ola Builder NFT," and share a portion of the future Ola tokens among other perks. ## **FAQs** If you need further help with dApp development or deployment, don't hesitate to pin us in the Ola [community](http://discord.gg/vDFy7YEG6j) or email us at . ### **How to apply for the Community Builders Program?** You are expected to provide a comprehensive project overview, details about your or your team's background, and an application [proposal](https://forms.gle/M5symJi1e23MwK8D7). ### **What incentives are included in the Community Builders Program?** Qualified projects will be rewarded with special Discord roles, NFTs, OVPs, and future Ola tokens among others. ### **How will the rewards and incentives be distributed?** NFTs and OVPs will be distributed following the conclusion of the Ola testnet events. Ola tokens will be distributed after the TGE. ### **What types of projects get incentives?** Projects must contain open-source elements that are built on the Ola network. We do not provide tokens for non-developer-related contributions. *** ## **Criteria** Applications are accepted on a rolling basis and assessed on team quality, project uniqueness, and potential impact on the Ola ecosystem. This selection process will be conducted via a vote by Ola core team members and the Ola community.The following aspects will be taken into consideration for evaluating applications: * *User Experience* - How seamless is it for contributors to use? Projects that are intended for an end-user (not Infrastructure & Tooling) are required to have a UI. * *Architecture* - How robust is the technical architecture? How well is it defined? * *Functionality* - How many different things can you do as an end user? * *Impact* - Does the tooling or infrastructure provide valuable insights for contributors? * *Novelty* - How unique is tooling or infrastructure? Is it differentiated? --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://ola-2.gitbook.io/ola-community-hub/community-loyalty-program/builder-program.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.