Builder DAO

Background

Hey everyone!

My name is Jord. I’m an experienced developer who has been contributing to DAOs and DAO platforms full-time for close to three years.

I am excited to propose a three-month, part-time residency with Builder DAO!

Related Experience

My previous roles in DAOs were:

• DAO Masons: Co-founder. Governance Designer. fullstack developer
• DAOhaus: Senior frontend developer. Tooling & Integrations lead. Devrel.
• Raid Guild: Contributor. fullstack developer.

Past Builder Contributions

• Farcaster ‘Feed’ Integration V0.
  • DAO-specific feed built directly into the Builder App.
  • Research and collaboration with Farcaster folks to build a foundation for further integration.
  • https://github.com/ourzora/nouns-builder/actions/runs/5460129924
• Members List View (coming soon)
  • https://github.com/ourzora/nouns-builder/pull/300
• Product Ideation with Isaac and Neokry.
  • https://github.com/ourzora/nouns-builder/issues/286
  • https://github.com/ourzora/nouns-builder/issues/276
  • https://github.com/ourzora/nouns-builder/issues/275

Residency Scope

Part-time. 20+ hours per week.

Roadmap

I spent some time working with Zaak and Neokry on a roadmap of client-side features to build while Neokry begins development on protocol features.

Here are the items that we came up with.

Short/Mid Term:

• Email notifications. A service that allows the user to subscribe to DAO events or auctions. We plan to alert the user of the following events:
  • New auction
  • When the user is outbid
  • When you have won the auction + settlement reminder
  • New Proposal
  • Voting period open
  • One day before voting
  • Proposal result (Pass or fail)
  • Proposal requires execution
• Auction Chart. A chart that displays all of the final auction sale prices over time.
• Exploration around DAO Fiat payment services. The exact implementation of this is still in discovery, but either we build an integration with bridge.xyz or set up a flow with Utopia.
• Token Buyer TX type. Similar to or a version of Nouns Token Buyer. Application integration that allows a DAO to trade ETH for an ERC-20 token.
• DAO Context. These are smaller pragmatic features that add more content, richness, and context to DAOs, which will hopefully inspire more users to participate. Some of these features could include:
  • Rich Text information in the About section
  • Expanding social links.

Note: Some of the implementation details of these features may change based on technical constraints. Also, given the large scope of these features, and the limited time of the residency, it is possible that not all the features listed here will be completed within this residency term.

Long Term/Extras

• A simple static docs page that organizes all of the builder DAO content and affiliate projects, similar to nouns.center.
  • There’s also been discussion about creating a fully onchain DAO CMS that can be made available to all DAOs. Imagine being able to ratify documents through governance and having that data display either in the app or through static site templates.
• Unlocking the Metadata renderer. What else can the metadata renderer do? I want to make Builder DAOs more expressive and see how we can make changes to the client so that we can open up the design space for artists.

Overarching Goals:

In my previous draft, there was a heavier emphasis on sustainability for the DAO. However, this is still in the discovery stages, and I think it would be wise to implement based on the output of the various working groups who are tackling this challenge.

Additionally, I had also planned to integrate the client with new protocol developments. However, these new protocol features are still in development and will likely be a few months before they need integration into the application.

With that in mind, my goals for this term will be:

• Enhance the auction experience, both for DAOs and bidders. DAOs should be able to use the auction chart to gauge interest in their DAO. Bidders should be able to get the auction information when it is important (email notifications).
• DAO Expressivity and Character: I want to DAOs to be able to distinguish themselves and help attract new members. We can add new UI to enhance the character of each DAO and help orient members to where the DAO coordinates. Finally, I want to explore enriching the application experience by either opening up new patterns for creating art on the platform or giving DAOs the ability to store and ratify their content.
• Utility: Some features, while unsexy, are still very useful and should be implemented. This could come in the form of organizing Builder DAOs links into a static docs page, or building integrations to allow the DAO to make payments in fiat.

Additional Value Add

• Assist Neokry with some maintenance and bug fixes.
• Help with ideation and discovery for Builder DAO sustainability. I’d like to participate in some meetings and discovery sessions for potential features or updates that may help fund future development and DAO onboarding.
• Help with product ideation and development sessions. I currently attend most product sessions with Zaak and Neokry. I’m very happy to continue doing so.
• Perhaps some early discovery around devrel. I can tell Builder DAO is making efforts to attract developers to build on the protocol. I have some experience with Devrel and would be happy to help strategize.

Funding Request

• 6,500 USD/Month for 3 Months.
• Total of 19,500 USD.
• 10.54 ETH market price of 1,848.85. (Price at time of writing. Will recalculate when posting on-chain)

*The equivalent of ~$23k(12.44 ETH) (to absorb potential volatility in ETH from the time between submission and execution) would be sent to a multisig managed by trusted members of the community (Zaak, Neokry, and X). They would then convert $19.5k worth of ETH to USDC and create a Sablier stream.

Gnosis Safe to handle Jord’s transactions:

• 0xC280FB2E5E6033932aF286BDa4520BfE1251C68a

Signers:

• zaak.eth 0x77ac30452890E5210CB334f601a0A6E8F0A5201B
• Neokry.eth: 0x04bfb0034F24E424489F566f32D1f57647469f9E
• ccarella.eth: 0x3B60e31CFC48a9074CD5bEbb26C9EAa77650a43F