# \[Proposal, rejected\] Build DAO: NDC Funding Request (March 2024)
**URL:** https://gov.near.org/t/proposal-rejected-build-dao-ndc-funding-request-march-2024/38130
**Category:** Build DAO
**Tags:** ndc-funding-request
**Created:** [February 18, 2024, 12:32am UTC](https://gov.near.org/t/proposal-rejected-build-dao-ndc-funding-request-march-2024/38130 "2024-02-18T00:32:55Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@jlwaugh](https://gov.near.org/u/jlwaugh)
#### Post date: [February 18, 2024, 12:32am UTC](https://gov.near.org/t/proposal-rejected-build-dao-ndc-funding-request-march-2024/38130/1 "2024-02-18T00:32:55Z")
# Empowering Builders
> **[Build DAO](https://www.nearbuilders.org/)**
>
> Support Systems for Open Web Projects
Thanks to financial support via NEAR Digital Collective (NDC), we are building a sustainable development economy, generating paid opportunities for all kinds of contributors to get involved with open web projects and communities.
**Read our January report:**
> [@Build DAO: Monthly Report (January 2024)](http://gov.near.org/t/build-dao-monthly-report-january-2024/38129):
>
> This post summarizes the impact of Build DAO so far this year. Overview In just over a month, we’ve gone from one core team to five teams explicitly dedicated to scaling the operations, efficiency, and sustainability of our initiatives. Every day, we become more dynamic and impactful to the future of NEAR. What problem does Build DAO solve? Builders often struggle to navigate our complex ecosystem. They can participate in a hackathon, read the docs, and reach a “Hello World” moment. Still, i…
## TOTAL AMOUNT — $50,000 in March
For next month, we are seeking funds to support existing projects and activate more builders. Below is a breakdown of the costs with relevant information about each program.
→ **[Detailed Budget Spreadsheet](https://docs.google.com/spreadsheets/d/11Qq6D-rJa1w9qd7ybHq3kVVJg2V52TaYE9mgxbtzbZs/edit?usp=sharing)**
## Background / Context
### Proposal for Q1
> [@\[Approved\] Build DAO: NDC Budget Subcategory code HOM-004P-1-1-1 Ecosystem](http://gov.near.org/t/approved-build-dao-ndc-budget-subcategory-code-hom-004p-1-1-1-ecosystem/36919):
>
> 1. General Information Organization Name: Build DAO Proposal Title: Funding Open Web Development Cooperatively Background DAO created May 4, 2023 Entity formed August 25, 2023 Category: Ecosystem Grassroots initiative to support builders 2. Previous Funding Over the past few months, Build DAO processed $41k from NEAR Foundation (via DevHub, Regional Communities, and other programs). 3. Relevant Links [Website](https://nearbuilders.com) | [Gateway](https://nearbuilders.org) Social Media Distribution Channels: [Near Social](https://near.social/mob.near/widget/ProfilePage?accountId=build.sputnik-dao.near)[X / Twitter](https://x.com/nearbuilders)[Telegr…](https://nearbuilders.com/tg-builders)
### Previous Requests
**January**
> [@\[Approved\] Build DAO: NDC Funding Request (January 2024)](http://gov.near.org/t/approved-build-dao-ndc-funding-request-january-2024/37433):
>
> This post outlines how [Build DAO](https://nearbuilders.org) will activate and retain builders with funding to support open web projects and communities. Please share any feedback. Summary Following the approval of our proposal to NDC, we would like to share this request for $25k to fund the Build DAO community program in January. Detailed Budget → [NDC Funding Request — Build DAO (January 2024)](https://docs.google.com/spreadsheets/d/1zmZeZB1iJbE7tbQoigWS4HSO-nNyv8E1hqTXDah-a44/edit?usp=sharing)Objectives and Key Results These strategic goals help us align toward success on a mission to widen ecosystem adoption and s…
**February**
> [@\[Approved\] Build DAO: NDC Funding Request (February 2024)](http://gov.near.org/t/approved-build-dao-ndc-funding-request-february-2024/37706):
>
> NDC Funding Request Total Amount: $50,000 in February → [Detailed Budget Spreadsheet](https://docs.google.com/spreadsheets/d/19_7qIAYWarnm1WYH_uoi2IxihvZUOchf0E0AVHA2VpM/edit?usp=sharing)Background / Context Proposal for Q1 Previous Request PROGRAMS Enginearing: $32,500 We are building necessary support systems to retain BOS developers. Our strategy is to cultivate open web projects that generate meaningful opportunities for contributors. Project Link Update(s) Amount [everything.dev](https://everything.dev) + [bos-workspace](https://github.com/orgs/NEARBuilders/bos-workspace)[Plan](https://github.com/orgs/NEARBuilders/projects/5)[Jan 4](https://near.social/mob.near/widget/MainPage.N.Post.Page?accountId=efiz.near&blockHeight=109623192), [Jan 8](https://near.social/mob.near/widget/MainPage.N.Post.Page?accountId=efiz.near&blockHeight=110034272) $4,500 [Archetype](https://archetype.computer)[Proposal](http://gov.near.org/t/proposal-archetype-funding-request/37606)[Jan 15](https://near.social/mob.near/widget/MainPage.N.Post.Page?accountId=archetype-org.near&blockHeight=110500860) $7,000 [Hyperfiles](https://hyperfiles.org)[Proposal](http://gov.near.org/t/proposal-hyperfiles-funding-request-february-2024/37557) …
## PROGRAMS
### Enginearing: $27,500
| Project | Link | Updates | Amount |
| --- | --- | --- | --- |
| [everything.dev](https://everything.dev) | [Request](https://near.social/mob.near/widget/MainPage.N.Post.Page?accountId=plugrel.near&blockHeight=112322430) | [Feb 13](https://near.social/mob.near/widget/MainPage.N.Post.Page?accountId=efiz.near&blockHeight=112796033), [Feb 6](https://near.social/mob.near/widget/MainPage.N.Post.Page?accountId=efiz.near&blockHeight=112274627), [Jan 23-28](https://near.social/mob.near/widget/MainPage.N.Post.Page?accountId=efiz.near&blockHeight=111578177), [Jan 22](https://near.social/mob.near/widget/MainPage.N.Post.Page?accountId=efiz.near&blockHeight=111087390), [Jan 16](https://near.social/mob.near/widget/MainPage.N.Post.Page?accountId=efiz.near&blockHeight=110572794), [Jan 8](https://near.social/mob.near/widget/MainPage.N.Post.Page?accountId=efiz.near&blockHeight=110034272), [Jan 4](https://near.social/mob.near/widget/MainPage.N.Post.Page?accountId=efiz.near&blockHeight=109623192) | $5,000 |
| [Open Web SDKs](https://github.com/nearbuilders/sdks.near) | [About](https://near.social/mob.near/widget/MainPage.N.Post.Page?accountId=sdks.near&blockHeight=109924527) | [Jan 11-15](https://near.social/mob.near/widget/MainPage.N.Post.Page?accountId=mattb.near&blockHeight=110498728), [Jan 15-20](https://near.social/mob.near/widget/MainPage.N.Post.Page?accountId=mattb.near&blockHeight=110839931), [Jan 20-23](https://near.social/mob.near/widget/MainPage.N.Post.Page?accountId=mattb.near&blockHeight=111154026), [Jan 23-26](https://near.social/mob.near/widget/MainPage.N.Post.Page?accountId=mattb.near&blockHeight=111414017), [Jan 27-29](https://near.social/mob.near/widget/MainPage.N.Post.Page?accountId=mattb.near&blockHeight=111645967), [Jan 30 - Feb 4](https://near.social/mob.near/widget/MainPage.N.Post.Page?accountId=mattb.near&blockHeight=112049474), [Feb 4-8](https://near.social/mob.near/widget/MainPage.N.Post.Page?accountId=mattb.near&blockHeight=112418221), [Feb 8-14](https://near.social/mob.near/widget/MainPage.N.Post.Page?accountId=mattb.near&blockHeight=112783118), [Jan 11](https://near.social/mob.near/widget/MainPage.N.Post.Page?accountId=mattb.near&blockHeight=110177721), [Jan 15](https://near.social/mob.near/widget/MainPage.N.Post.Page?accountId=mattb.near&blockHeight=110498728) | $2,500 |
| [Archetype](https://archetype.computer) | [Request](http://gov.near.org/t/proposal-archetype-package-management/38050) | [Jan 15](https://near.social/mob.near/widget/MainPage.N.Post.Page?accountId=archetype-org.near&blockHeight=110500860), [Jan 15-22](https://near.social/mob.near/widget/MainPage.N.Post.Page?accountId=archetype-org.near&blockHeight=111143906), [Jan 23-30](https://near.social/mob.near/widget/MainPage.N.Post.Page?accountId=archetype-org.near&blockHeight=111784781) | $7,000 |
| [Hyperfiles](https://hyperfiles.org) | [Request](http://gov.near.org/t/proposal-hyperfiles-funding-request-february-2024/37557) | [Jan 5](https://potlock.org/hyperfiles-personas), [Jan 19](https://near.social/mob.near/widget/MainPage.N.Post.Page?accountId=flowscience.near&blockHeight=110822377), [Jan 26](https://near.social/mob.near/widget/MainPage.N.Post.Page?accountId=flowscience.near&blockHeight=111391760), [Feb 4](https://near.social/mob.near/widget/MainPage.N.Post.Page?accountId=flowscience.near&blockHeight=112135899) | $3,000 |
| [Dragonverse](https://x.com/NearDragonverse) | [Request](https://near.social/mob.near/widget/MainPage.N.Post.Page?accountId=rhymetaylor.near&blockHeight=112322517) | [Jan 12](https://x.com/NearDragonverse/status/1745864394427232606?s=20), [Jan 23](https://x.com/NearDragonverse/status/1749941944388628984?s=20), [Feb 16](https://x.com/NearDragonverse/status/1758611174306812109?s=20) | $5,000 |
We will continue working with `jass.near` to build infrastructure and tooling. To facilitate coordination, our team is expanding capacity for project support by hiring `imagin.near` to design and implement better systems. Plus, we plan to reserve $5,000 for additional requests.
### Communities: $17,000
- [Developer Relations Program](https://near.social/mob.near/widget/MainPage.N.Post.Page?accountId=dawnkelly.near&blockHeight=112399077) ~ $12,000
- [Builder Education Program](https://nearbuilders.org/resources) ~ $5,000
### Operations: $5,500
- [Project Support Program](https://near.social/mob.near/widget/MainPage.N.Post.Page?accountId=imagin.near&blockHeight=112515560) ~ $5,000
- Miscellaneous Expenses ~ $500
## PROCEDURE
Our processes involve hiring developers, reviewing contributions, and funding projects based on [updates](https://www.nearbuilders.org/buildhub.near/widget/app?page=feed&tab=updates) and [requests](https://www.nearbuilders.org/buildhub.near/widget/app?page=proposal&tab=request) via the `#build` [feed](https://www.nearbuilders.org/feed) of Near Social.
Thanks for your consideration!
#### **NEAR Builders Cooperative**
[james@nearbuilders.org](mailto:james@nearbuilders.org)
---
### Author:  [@Dacha](https://gov.near.org/u/Dacha)
#### Post date: [February 18, 2024, 4:12am UTC](https://gov.near.org/t/proposal-rejected-build-dao-ndc-funding-request-march-2024/38130/2 "2024-02-18T04:12:57Z")
Thank you for your proposal.
I have reviewed the details provided and have several inquiries:
1. Regarding the allocation of reserve funds, which are subject to council members’ voting on future proposals, an additional $5,000 is proposed. However, it appears that the Build DAO previously allocated $3,500 in January, yet the funds have not been distributed or reported by the DAO treasurer. Could you please clarify the necessity for an additional $5,000?
2. It is noted that $5,000 is requested for the development of low-code builder tools by open-source contributors (@efiz.near & collaborators) and $7,000 for the team of developers (@archetype-org.near) working on package management solutions. Could you elaborate on the significance of these initiatives for Near users like myself?
3. The proposal involving $5,000 for @openwebacademy.near to develop examples, tutorials, and workshops for builders lacks specific Key Performance Indicators (KPIs). Could you please include measurable KPIs such as the number of examples, tutorials, workshops, and expected outcomes?
4. Similarly, the proposal to hire @imagin.near to develop a support system for builders and their projects also lacks clarity regarding outcomes and KPIs. Could you please provide more detailed information?
5. $5,000 Could you please use this form [Near Digital Collective Grassroots DAOs, projects, individual contributors funding, onboarding and operations guide v1 - #2 by Dacha](http://gov.near.org/t/near-digital-collective-grassroots-daos-projects-individual-contributors-funding-onboarding-and-operations-guide-v1/36951/2) for
[Post by Rhyme Taylor | Near Social](https://near.social/mob.near/widget/MainPage.N.Post.Page?accountId=rhymetaylor.near&blockHeight=112322517) . It’s hard to understand OKRs
Overall, most initiatives seem to be geared toward supporting Build DAO development and its projects.
Thank you
---
### Author:  [@jlwaugh](https://gov.near.org/u/jlwaugh)
#### Post date: [February 21, 2024, 5:05am UTC](https://gov.near.org/t/proposal-rejected-build-dao-ndc-funding-request-march-2024/38130/3 "2024-02-21T05:05:04Z")
Hey, thanks for your feedback!
I appreciate the opportunity to answer these questions. Below each one is my response.
* * *
> (1) Regarding the allocation of reserve funds, which are subject to council members’ voting on future proposals, an additional $5,000 is proposed. However, it appears that the Build DAO previously allocated $3,500 in January, yet the funds have not been distributed or reported by the DAO treasurer. Could you please clarify the necessity for an additional $5,000?
In January, that $3500 went toward implementing [Keypom trial accounts](https://x.com/jassification/status/1747986075291906512?s=20) in our forkable / reusable gateway example, launching the [Build North America](https://near.social/mob.near/widget/MainPage.N.Post.Page?accountId=dawnkelly.near&blockHeight=112399077) DevRel program, and introducing a modular [component library](https://nearbuilders.org/library) for builders.
The $5000 in reserves this month used to fund this [Forefront](https://near.social/forefront_tak.near/widget/Forefront.Widget.Platform) analytics dashboard.
Looking ahead to March, we have additional projects in the works:
- [Themed Component Libraries](https://near.social/devhub.near/widget/app?page=post&id=3043)
- [Rust API](https://github.com/Harmonic-Guild/near-api-rs)
- [JS in Rust](https://github.com/petersalomonsen/quickjs-rust-near) ~ Rust contracts with a JavaScript runtime
- [Ariz](https://ariz.no) ([roadmap](https://github.com/orgs/arizas/projects/9))
- [NearBadger](https://github.com/NEARBuilders/nearbadger-verifiers-api)
- [On-chain Editor](https://everything.dev/?page=editor)
- [Canvas](https://draw.everything.dev) ~ powered by tldraw
- [Video](https://everything.dev/?page=video) ~ powered by Livepeer
- [Maps](https://everything.dev/?page=map) ~ powered by Mapbox
* * *
> (2) It is noted that $5,000 is requested for the development of low-code builder tools by open-source contributors (`efiz.near` & collaborators) and $7,000 for the team of developers (`archetype-org.near`) working on package management solutions. Could you elaborate on the significance of these initiatives for Near users like myself?
These products improve quality of experience for NEAR builders and increase utility of the blockchain operating system. Ultimately, such initiatives contribute to widening ecosystem adoption and sustaining development of community resources.
### [bos-workspace](https://github.com/nearbuilders/bos-workspace) ([GitHub](https://github.com/orgs/NEARBuilders/projects/5))
_CLI tool + environment for local BOS development_
- helps Node.js developers overcome the learning curve of BOS
- offers an expanding list of evolving tools for building open web apps
- integrates familiar solutions like VS Code, GitHub, NPM, and Typescript
- enables usage of custom SDKs, packages, and libraries, resulting in better user experiences
**Users:** [Build DAO](https://github.com/NEARBuilders/gateway), [PotLock](https://github.com/PotLock/bos-app), [Proof of Vibes](https://github.com/proofofvibes/vibes-components), [DiscoverBOS](https://github.com/nearbuilders/discoverbos), and [QuestVerse](https://github.com/Quest-Protocol/questverse-monorepo)
### [everything.dev](https://everything.dev) ([GitHub](https://github.com/near-everything/viewer))
_common structure for open web apps ~ unified frontend paradigm_
Everything provides a way to put it all together, so **anyone can build on the open web** using NEAR, and everyone can help each other. This allows Build DAO to expand its communities to include more diverse groups. On-chain type systems make it easier for non-developers to create widgets and other things, leveraging available templates, libraries, modules, and frameworks.
### [Archetype](https://archetype.computer) ([GitHub](https://github.com/archetype-org/attestation-registry))
_global type registry, curation system, and metadata layer_
This project aims to secure cross-chain composability, which would protect safety and give users peace of mind when interacting with open web solutions. Also, their team is connecting NEAR builders with communities in relevant ecosystems like Urbit and Ethereum. This may help to strengthen our position as leaders in the space.
* * *
> (3) The proposal for `openwebacademy.near` to develop examples, tutorials, and workshops for builders lacks specific Key Performance Indicators (KPIs). Could you please include measurable KPIs such as the number of examples, tutorials, workshops, and expected outcomes?
The main goal of this collaboration is to empower Build DAO contributors with training and educational content focused on the open web stack, fostering a robust community of NEAR builders.
You can review this new [post](https://near.social/mob.near/widget/MainPage.N.Post.Page?accountId=izcc.near&blockHeight=113178724) by `izcc.near` (on-chain), outlining their KPIs:
- **Participation Rate:** number of qualified builders taking part in educational programs
- **Completion Rate:** percentage of participants who successfully complete the bootcamp
- **Repository Engagement:** usage of resources and contributions by influential NEAR builders
- **Community Growth:** growth of the NEAR Buidlers community within Build DAO over time
- **Project Contributions:** number of projects initiated or enhanced by program participants
### Deliverables
- 5x tutorials: guides covering various aspects of open web development
- 3x written tutorials: step-by-step walkthroughs of complex technical processes
- 8x technical infographics
- “Zero to Builder” bootcamp playbook, syllabus, and evaluation rubrics
- Slides and material used in workshops and bootcamps
- Bootcamp session recordings
- Workshop session recordings
Here is a [sneak peek](https://x.com/_Irvinggg/status/1760033390462459988?s=20) of a resource they are putting together now… 👀
* * *
> (4) Similarly, the proposal to hire `imagin.near` to develop a support system for builders and their projects also lacks clarity regarding outcomes and KPIs. Could you please provide more detailed information?
The current plan is to measure success by tracking the number of active builders contributing to relevant projects. As the Build Support Lead, Thom will design and implement a recruitment and onboarding system involving dev agencies and talent houses.
Overall, this program would improve operations and bolster usability of resources. Below are some objectives and metrics we discussed with `imagin.near` and the support squad:
### Accountability → Coordination + Productivity
**Build Stewards** cultivate successful projects and communities.
- _ **Metric** – How many builders post ideas, updates, or questions via the #build feed?_
### Talent Recruitment → Onboarding + Capacity
**Build Tasks** bring skilled contributors to NEAR and the open web.
- _ **Metric** – How many developers are hired by NEAR Builders Cooperative?_
### Quality of Experience → Learning + Retention
**Build Resources** facilitate development of apps, components, gateways, etc.
- _ **Metric** – How many people feel empowered to build something on their own?_
* * *
> (5) Could you please use [this form](http://gov.near.org/t/near-digital-collective-grassroots-daos-projects-individual-contributors-funding-onboarding-and-operations-guide-v1/36951/2) for the Dragonverse proposal? It’s hard to understand OKRs.
I’ve shared that request with their team, led by Rhyme Taylor and Jeff Gold.
Since then, we have discussed these goals and metrics:
### Objectives:
- users really having fun!
- generating awareness
- activating more game builders
### Key Results:
- lots of people playing Dragonverse and enjoying the gameplay
- custom BOS gateway for gaming deployed on web4 (with docs)
- reusable incubator game components added to a library
* * *
Please let us know any other info that you need. Thanks!