Builder

This proposal is also available as PDF on IPFS [here](https://ipfs.io/ipfs/Qmb6jCDUmoU1wo6ZapLcAUkxV6gkrsNYcqGgWFGkosMFoR).

# Summary

This proposal requests a **renewal of the Tech Pod Residency for a four-month term** to continue core development, technical maintenance, and community support for the Builder Protocol. Building on the successful handoff from the previous resident and the roadmap established during the first residency, the **returning team proposes to continue their efforts through agile development, active community engagement, and transparent reporting**. With proven feature delivery, this continuation ensures the protocol remains usable, competitive, and aligned with evolving DAO needs. **Compensation remains consistent with the first term**, and **deliverables will follow community-driven prioritisation** within a stable scope of work.

# Context

After filling the vacant role for the Tech Pod Residency on a short notice and introducing role sharing between a Product Owner (benedictvs.eth) and a Technology Lead in March, we turned the backlog into an actionable roadmap that could outlive us as residents. Our contributions have been instrumental in maintaining and improving the Builder Protocol as DAO-governed open-source software. Yet, ongoing upkeep and technical development is required for keeping Nouns Builder software functional, usable, and competitive. As proof of our work, we already delivered on agreed items:

- Ecosystem Tooling Report  
  - [https://ipfs.io/ipfs/QmdjXK9CNToUhEqb4fEcFRv8CGFJbS42CVCro94Mq6TTkE](https://ipfs.io/ipfs/QmdjXK9CNToUhEqb4fEcFRv8CGFJbS42CVCro94Mq6TTkE)  
  - [DAO Overview](https://docs.google.com/spreadsheets/d/11_1wKADjMkd9nZamNqoDQT-ZdaB09EMXYgMXzef5WWo/edit?usp=sharing)  
- Token delegation in the subgraph and on nouns.build ([Issue \#464](https://github.com/BuilderOSS/nouns-builder/issues/464))  
- Enhanced the escrow milestones proposal type with improved UX  
- Upgraded the Propdates feature twice (relevant to [Issue 181](https://github.com/BuilderOSS/nouns-builder/issues/181))  
- Ensured [Safe App Compatibility](https://github.com/BuilderOSS/nouns-builder/issues/472) with [additional UX enhancements](https://github.com/BuilderOSS/nouns-builder/issues/505)  
- Other noteworthy developments are:  
  - Full documentation audit and revision  
  - Farcaster notifications for Propdates  
  - Farcaster Mini App support  
  - A full changelog is available upon request

As we *involved the community to brainstorm needs and establish a roadmap*, initiatives deemed as high priority were pushed back by the community or changed in scope. For example, we addressed the issue of [Automated Auction Split](https://github.com/BuilderOSS/nouns-builder/issues/512), but the core user pain was identified to lie elsewhere ([\#513](https://github.com/BuilderOSS/nouns-builder/issues/513) & [\#594](https://github.com/BuilderOSS/nouns-builder/issues/594)). We significantly improved the documentation, while **improving the UX DAO creation, engagement, and proposal workflows** were assessed as less pressing by the community. Other aspects of the improvement of Nouns.build, only took shape as the community saw immediate needs addressed. For instance, the community is only now coming to terms with the scope for adding legacy support for Droposals.

A comprehensive overview of the required work is provided by the Github boards for the [Resident Cycle](https://github.com/orgs/BuilderOSS/projects/3) and the [Feature Roadmap](https://github.com/orgs/BuilderOSS/projects/2), which were established by the residents. For an exhaustive changelog, please consult [closed PRs on Github](https://github.com/BuilderOSS/nouns-builder/pulls?q=is%3Apr+is%3Aclosed+) or read up on the [Builder Buzz Newsletter](https://paragraph.com/@builder) editions 54 and following. With this track record, we want to continue providing the necessary support, technical expertise, and product vision for Nouns Builder to succeed.

# Proposal

This proposal consists of three main parts, which are elaborated on in the **Section Accountability** of this proposal. Namely, **communication and support**, **documentation and reporting**, as well as **technical development**.

## Documentation and Reporting

- Continue maintaining a prioritised roadmap [here](https://github.com/orgs/BuilderOSS/projects/2/views/1) and agile development sprint planning [here](https://github.com/orgs/BuilderOSS/projects/3/views/1)  
- Revise the Nouns Builder Ecosystem Tooling Report, which was compiled as v.1 [here](https://ipfs.io/ipfs/QmdjXK9CNToUhEqb4fEcFRv8CGFJbS42CVCro94Mq6TTkE)  
- Documentation of ecosystem tools, e.g. Droposals, the Builder Bot, and the Farcaster Mini App  
- Share monthly roadmap/features to be worked on

## Communication and Support

- Provide direct troubleshooting support for DAO members with the service level agreement outlined in the Section Status Updates.  
- Maintain weekly office hours and monitor **Discord** to proactively identify and resolve issues, as defined in the section Status Updates of this proposal  
- Attend **Ops Group** and **BuilderDAO** meetings to stay aligned with operational needs

## Technical Development

- Prioritisation of the backlog with the community and ongoing refinement of the roadmap for the residency, including the engagement of community resources through RFPs or call for proposals for applicable initiatives, such as design support and a template website  
- Continue agile development cycles according to the prioritised backlog for resolving existing and new issues

## North Star Alignment

This proposal supports Builder DAO’s mission to develop DAO infrastructure as a public good, ensuring ongoing accessibility, robustness, and user experience improvements for decentralised communities. Completing the current backlog and enhancing key features directly benefits the Builder Protocol ecosystem’s long-term viability.

## Accountability

### Timeline

The proposed timeline for the extension of the residency is 4 months, running from August 02, 2025 to December 02, 2025\. Payouts are tied to a steady delivery according to monthly milestones.

### Deliverables

As the technology residency follows a community-driven and agile development structure, only tentative deliverables can be provided. However, the roadmap in the first subsection has been established with great care and passed community feedback and **reflects certain priorities**. The second category of issues are of lower priority and/or smaller size, thus MAY shift in response to new community feedback or severe to medium bugs that need immediate addressing. The last category of deliverables “Discussion Topics” reflects the technology residents' determination to engage, shape, and structure ongoing community feedback. Issues from this last category MAY NOT translate into direct technology developments, but are important for community oversight of the technical development.

While specific deliverables may evolve in line with the agile development approach of the residency, the overall scope of work and the responsibilities covered by the residency retainer shall remain unchanged unless formally amended by mutual agreement.

#### Continuation of the Roadmap as Defined in the Community Product Session

| Month | Item | Description | Owners | Weeks | Status |
| :---- | :---- | :---- | :---- | :---- | :---- |
| JUL 2025 | [574](https://github.com/BuilderOSS/nouns-builder/issues/574) and [575](https://github.com/BuilderOSS/nouns-builder/issues/575) | NPM library including utils and hooks  | Tech Residents | 3 | Ongoing |
| JUL 2025 | [626](https://github.com/BuilderOSS/nouns-builder/issues/626) | Droposal legacy support on nouns.build UI | Tech Residents | 2 | Ongoing |
| AUG 2025 | [318](https://github.com/BuilderOSS/nouns-builder/issues/318) | Display "User votes", "User proposals", and voting history  in a new "Activity" tab on Profile page. | Tech Residents | 2 | Planned |
| AUG \- SEP 2025 | [463](https://github.com/BuilderOSS/nouns-builder/issues/463) | Stream payments via proposals, for example through Sablier or SuperFluid. | Tech Residents | 2 | Planned |
| TBD | [NounsSite](https://github.com/BuilderOSS/noun-site) | Template Website | Community | TBD | TBD |

#### Prioritised Issues in the Resident Cycle Backlog (🔗[Github](https://github.com/orgs/BuilderOSS/projects/3/views/1))

- \[Bug\] Discrepancy Between "Total Supply" and "Possible Votes" ([\#599](https://github.com/BuilderOSS/nouns-builder/issues/599))  
- \[Task\] Finalise Domain Transfer on Vercel and Migrate Docs Domain ([\#622](https://github.com/BuilderOSS/nouns-builder/issues/622))  
- \[Feature\] Enable ERC-20 Support for Escrow Proposals ([\#580](https://github.com/BuilderOSS/nouns-builder/issues/580))  
- \[Feature\] Onboarding Stage for First-Time Proposers ([\#405](https://github.com/BuilderOSS/nouns-builder/issues/405))  
- \[Feature\] Founder Split Settings and UI Enhancements ([\#513](https://github.com/BuilderOSS/nouns-builder/issues/513) & [\#594](https://github.com/BuilderOSS/nouns-builder/issues/594))

#### Actively Discussed Issues in the Community Requiring Specification

- Features shared by The Park DAO (🔗[Notion](https://criticus.notion.site/The-Park-Dao-22fe03c2c4518053816ff6074a3652d3))  
- Specifying and onboarding potential design support (🔗[Notion](https://criticus.notion.site/Design-Specification-Droposal-Minting-Page-for-Nouns-build-22fe03c2c45180c0acbdf69af6a5dbf5))  
- Specification, prioritisation, and delivery \[TBD\] of a [Flows](https://flows.wtf/) integration

#### Anticipated Issues and Roadmap

While we have crafted the above list of deliverables and roadmap with the utmost diligence and by involving the community, we are aware that priorities may change and that there are a plethora of issues in the backlog that need addressing. Therefore, we want to mention a number of issues we are aware of and have tentatively prioritised as alternatives and successors of the above scope, such as:

- [https://github.com/BuilderOSS/nouns-builder/issues/603](https://github.com/BuilderOSS/nouns-builder/issues/603) → Basename Support  
- DAO Links for Discord, websites, etc.  
  - [https://github.com/BuilderOSS/nouns-builder/issues/504](https://github.com/BuilderOSS/nouns-builder/issues/504)  
  - [https://github.com/BuilderOSS/nouns-builder/issues/244](https://github.com/BuilderOSS/nouns-builder/issues/244)  
- Additional proposal templates for Resume Auction, changing Artworks  
- User experience improvements for voting and DAO search  
- Revamping the proposal creation flow  
  - [https://github.com/BuilderOSS/nouns-builder/issues/404](https://github.com/BuilderOSS/nouns-builder/issues/404)  
  - [https://github.com/BuilderOSS/nouns-builder/issues/407](https://github.com/BuilderOSS/nouns-builder/issues/407)  
  - [https://github.com/BuilderOSS/nouns-builder/issues/236](https://github.com/BuilderOSS/nouns-builder/issues/236)

### Status Updates

As introduced during the first residency cycle of the proposers, the residents will update the community as follows:

1. In monthly delivery reports given as Propdates to the respective milestone  
2. During the bi-weekly DAO-wide community meeting  
3. As Tech Pod updates in every Builder Buzz Newsletter  
4. In regular posts to the /builder channel on Farcaster  
5. Through monthly community product sessions (justified by community attendance)  
    - Provision of dedicated [invite link](https://lu.ma/calendar/cal-EIrCoA7qn2i6kH5) for attendance and agenda  
    - A FigJam board (or similar)  
    - A set agenda for community members to prepare their attendance  
    - Revival of the [Github Discussions](https://github.com/BuilderOSS/nouns-builder/discussions)  
6. In regular, prompt, and structured responses in the community Discord server  
    - 48 hour response time on tickets raised  
    - Issues raised through tickets are prioritised  
7. Documentation and dissemination of outcomes of community product sessions  
8. Updated documentation, as done in the past (see PR [\#10](https://github.com/BuilderOSS/nouns-builder-docs/pull/10))  
9. Reports and roadmaps as specified above  
10. Availability for questions during weekly office hours and public channels

## Treasury Impact

### Compensation

In continuation of previous Protocol Technology Lead compensation, we are requesting a **monthly** retainer of **1.67 ETH and 8652.81 OP per month (\~12,500 USDC/ month on Jul 24, 2025\)** (adjusted pro-rata if necessary for limited duration). For the entire duration of the **4 months residency total compensation is 6.68 ETH and 34611.24 OP**, released monthly according to milestones. The compensation is split between the residents as follows:

- 60% to Resident Protocol Technology Lead  
- 40% to Resident Protocol Product Lead

### Impact

The treasury impact of this proposal is estimated to be 13.00%. The remaining funds will be covered separately, originating from OP grant funds.

# Transparency

## Disclosure

- Work under this proposal is **non-exclusive**  
- No personal financial interests outside the DAO scope are attached to the execution of this work

## Prior Funding

After the prior Resident Protocol Lead funding ended prematurely, Dan and Ben took over on a short notice to maintain continuity in the upkeep of the Nouns Builder protocol and platform. Their first term is coming to an end on August 02 and was funded with [Proposal 42](https://nouns.build/dao/base/0xe8af882f2f5c79580230710ac0e2344070099432/vote/42).

# Authors

- Resident Protocol Product Lead: **benedictvs.eth**  
- Resident Protocol Technology Lead: **dan13ram.eth**

## Tax Information

The proposers will provide necessary tax reporting information in accordance with DAO administrative requirements.

## About the Authors

### benedictvs.eth

Ben is a RaidGuild member and an expert on decentralised identity and Web3 infrastructure, who also reads for a PhD in DLT-based decentralised governance of small jurisdictions. As an entrepreneur, he successfully launched two Web3 consultancies in the past three years and received funding backed by the European Union on multiple occasions. His overarching objective is to bring DLT networks and society closer together.

### dan13ram.eth

Dan (Dhanwanthari) OneTree is a software developer focused on Web3 technologies, leading development at Smart Invoice and contributing to open-source projects. Passionate about blockchain, DAOs, and NFTs, he aims to drive positive change through technology.

0x292f94ac342636dec09ed7818e6fadf72b8fa1ba551fbc391589f3fc848e5ad6

Tech Pod Residency Renewal through December 2025 - updated