[Proposal to House of Merit, rejected] NDC Direct Funding Request - NEAR Project Registry

NEAR Digital Collective HoM direct requests
1

Section 1 - DAO/Project Information

Project name: NEAR Project Registry

Date Established: November 2023

DAO’s Category: Ecosystem

Project’s Category: Community Led

Section 2. Previous Funding

Have you received funding for this project from any source?: No

Section 3. Twitter URLs

Twitter: https://x.com/TheblockchainOS?t=W4Hrh3zbjcHiQXJnIEoDWQ&s=09

Is Your DAO/Project Targeting a Specific Country? - We are targeting a global audience.

The language used will be focused in English.

Section 4. Applicant Information

POC - Cameron Dennis

Link to Governance Forum/near.social Profile: cameron.near

NEAR Wallet ID - cameron.near

Wallet ID that will be receiving funds - banyancollective.near

Country of Residence - United States

Twitter: https://twitter.com/Cameron_Dennis_
Telegram: @camerondennis

LinkedIn: Cameron Dennis - Banyan Collective | LinkedIn

Section 5. Team Members

  1. Yuen: Core Maintainer

    1. Onboard new maintainers via 1:1 calls explaining the curation process
    2. Be the primary point of contact for all of the database contributors
    3. Triage all inbound inquiries to the proper tag owner
    4. Suggest primary maintainers for initial categories

  2. Olaluwa Aina, Core Maintainer

    1. Manage tag standardization
    2. Ensuring quality control and that all projects are tagged properly
    3. Write and maintain docs and video tutorials

  3. Cameron Dennism, Core Maintainer

    1. General management & agenda setting
    2. Run weekly calls
    3. Distribute funds to contributors
    4. Be the secondary point of contact for all of the database contributors
    5. Work with the NEAR Foundation to standardize tags
    6. Champion the proposal and budget with the NDC

  4. Robert, Core Maintainer - Developer

    1. Design system of curators
    2. Provide engineering support where necessary

  5. Kent: Core Maintainer - Developer

    1. Develop and design database system and tools
    2. Provide engineering support where necessary

  6. Elliot, Maintainer - Development Support & Power User

    1. Developer support if needed
    2. Frontend implementations
    3. Composable design feedback

  7. Shot, Maintainer - Power User

    1. Advisory on how registry can be useful for Potlock
    2. Add new projects to the registry if they sign up through Potlock

Section 6. Experience

  1. Yuen, Core Maintainer: Contributor to NEAR Digital Collective and NEAR Malaysia

  2. Olaoluwa Aina: Founder of DiscoverBOS and Ex-Community Builder at Aurora

  3. Cameron Dennis, Core Maintainer: Founder of the Banyan Collective and Council in the NDC HOM

  4. Robert Yan, Lead Engineer: Head of Engineering at MetaWeb VC and Co-founder NEAR Catalog

  5. Kent, Engineer: Engineer at NEAR Vietnam and Co-founder NEAR Catalog

  6. Elliot Braem, Support Engineer: Maintainer at everything.dev and Council at BuildDAO

Section 7. DAO/Project Charter/White or Litepaper and Goals

This project registry is designed to serve as a frequently updated database of all of the projects built on NEAR. It can be thought of as a composable AwesomeNEAR that people can use to populate their project-specific ecosystem dashboards (ie: If Proximity wanted to only display DeFi projects, NF wanted to display all projects to previously received grants from them and their current status, Meteor wallet wants to display all apps with the “Consumer” tag in a promotional campaign to get their users using other NEAR apps, etc).

Slides

NEAR Project Registry Slides: NEAR Project Registry Slides - Google Slides)

What Problem Are You Aiming to Solve?

There is no coherent database registry that has a constantly updated information and status of all the projects on NEAR, so we are building a standardized and centralized community database for NEAR Projects with regularly updated projects status and information.

Section 8. Budget

2024 Budget: $97,000 to pay for work done from February 2024 - Dec 31st 2024.

Suggested Payment Schedule

  1. Q1 paid upfront to kick the project off and retroactively pay for work done in February - $16,900

  2. Q2 Paid After First Approved Report (estimated: April 9th) - $28,200

  • Milestone 1: Get the NEAR Foundation to review and accept internally standardized tags.

Formalize a maintenance system where contributors across ecosystem nodes ensure the database is up-to-date at the start of every month.

  • Milestone 2: Formalize Curator Onboarding form and maintance system so contributors across ecosystem nodes can ensure the database is up-to-date at the start of every month.

  • Milestone 3: Onboard and assign primary and secondary owners for each tag.

  1. Q3 Paid After Second Approved Report (estimated: July 8th) - $28,200

  • Milestone 1: Ship NEAR Project Registry widget that allows anyone to call the database.

  • Milestone 2: Translate NEAR Catalog (or similar UI) to English, Chinese, Spanish, Arabic, French, Bengali, Russian, Portuguese, Hindi, and Vietnamese.

  • Milestone 3: Ship Get two projects to pilot the project registry.

  1. Q4 Paid After Third Approved Report (estimated October 7th) - $28,200
    -To be determined after Q3 milestones are complete.

Banyan will not profit at all from these payments. All of the money will be allocated directly to contributors of this project and any left over funds will be sent back to the NDC Treasury at the end of the year in-case they don’t get spent.

What is the length of Commitment to Delivering Your Project?

  • Continuous and constantly updated

Will your team be working on this project full-time?

  • Part-time with an average of 10-20 hours a week commitment per person

Will your team be fully remunerated from this budget?

  • Yes

Section 9. Project/DAO longevity

Does your project/DAO require one-time or continuous funding?

  • Continuous funding

Will your DAO/Project device be a way of sustaining itself after this round of funding?

  • The project does not have any way to sustain itself as it aims to be a public good for the NEAR ecosystem.

What are the possible roadblocks to the success of your project/DAO?

  • Not getting funding to maintain the project registry.
3 Likes
2

This is a public good that the ecosystem has absolutely needed since AwesomeNEAR was sunset. Based team with a history of consistently delivering on NEAR. I fully support this initiative and its very reasonably priced funding request.

3

Amount requested has increased by approximately 30% since my initial reply. However, I continue to support this initiative.