Bringing Builder Coining to Market and Protocol Maintenance through February 2025

Summary

We are seeking to renew our residency for three months (Dec 2025-Feb 2026) to continue maintaining and improving the Builder Protocol as DAO-governed public-good infrastructure. We have been consistently delivering since March 2025 and look forward to bringing Builder Coining to market. We are committed to the roadmap shared below and continue our support for delivering revenue opportunities. This proposal funds continued technical development, documentation, and community support, with the launch of Builder Coining as the next major primary milestone. We will ensure accountability through monthly reporting, office hours, and structured governance updates as consistently provided during our prior terms.

Context

The previous Tech Pod Residency, funded under Prop #45, has been successfully concluded, with all deliverables addressed or updated. Our contributions have continued to be instrumental in maintaining and improving the Builder Protocol as DAO-governed open-source software. We have also grown close to the community and enjoy working with all of you and want to continue providing the necessary support, technical expertise, and product vision for Nouns Builder to succeed.

A comprehensive overview of priorities work items is provided by the Github boards for the Resident Cycle and the Feature Roadmap, by the residents. For an exhaustive changelog, please consult closed PRs on Github or read up on the Builder Buzz Newsletter editions 57 and following. From the previous proposal, we have delivered on agreed items and advanced the status of planned work as follows.

• All issues listed under “Prioritised Issues in the Resident Cycle Backlog” of the previous proposal were completed
• Defined community roadmap was delivered as promised
  • Streams proposal type (#463) remains open, pending community vote on Sablier revenue share agreement
  • Droposal support (#626) was deprioritised in favour of Coining, which will deliver the frontend for legacy support
• Beyond Prop #45, we also co-hosted the Builder x Gnars Hacker House @ Devconnect (Prop #51), which yielded warm leads for revenue generation opportunities, such as Web3 funding and the Polygon Agglayer ecosystem (Katana)

Proposal

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

Documentation and Reporting

• Continue maintaining a prioritised roadmap here and agile development sprint planning here
• Release the Builder Coining Design Document on version 1.0 after updating v.0.1 here
• 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 3 months, running from December 2025 through February 2026. Payouts are tied to a steady delivery according to monthly milestones.

Deliverables

We continue to follow a community-driven and agile development structure, focused on protocol maintenance and feature development. Accordingly, tentative deliverables are provided below, which MAY shift in response to new community feedback or severe to medium bugs that need immediate addressing. Highest priority is the launch of the Builder Coining update. Please follow and engage with status updates on the Builder Coining initiative here.

We are determined to deliver on revenue generating initiatives, which currently include integrating Sablier streams, advancing our conversation with Katana, and supporting high-profile DAOs to onboard to the Builder Protocol.

• The Tech Pod continues to provide technical support to the Community Resident for the targeted onboarding of existing DAOs, interested in migrating to Builder. This includes, but is not limited to:
  • Satori’s ongoing engagement with Choo Choo Dev
  • PublicNouns, where early conversations were held with Sky
  • Onboarding of ATX DAO, which would request the implementation of the dynamic auction mechanism and has tentatively shared openness to explore joint funding opportunities
• We continue our conversation with Katana, as their team signalled openness to make Builder the first SocialFi application on their chain.

Continuation of the Roadmap as Defined in the Community Product Session

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:

• Integration of Farcaster usernames on the platform and enhancements to the Farcaster mini app
• UX refinements in the DAO deploy flow and custom proposal templates

Smart Contract Updates

Should the opportunity arise that an external stakeholders would support funding a smart contract audit for custom features they are requesting, requested smart contract updates will be prioritised accordingly. The full list of requested smart contract changes is found here.

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 for attendance and agenda
   • A FigJam board (or similar)
   • A set agenda for community members to prepare their attendance
   • Revival of the Github 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)
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 3.38 ETH and 8608.24 OP (payable in ETH) per month (~12,500 USDC/ month on Dec 16, 2025) (adjusted pro-rata if necessary for limited duration). For the entire duration of the 3 months residency total compensation is 10.14 ETH and 25561.29 OP (payable in ETH), 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 26.89%. 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

Dan and Ben took over the role of Tech Residents at the end of March 2025 (Prop #42). Their second term came to an end on December 02 2025 and was funded with Prop #45.

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.