Grant Application- Dogfooding the Proposal Inverter

  • Project Name: Proposal Inverter (Prime Flow)

  • Team Name:PrimeDAO

  • Payment Address:
    eth mainnet :0x954Ccb8E7828e29246740E29F02efba1de0467BE

- [Level]: :evergreen_tree:-Tree

Proposal Inverter Meta Proposal: PrimeDAO Proposal :robot: For Radicle Grant

*Meta proposal is a proposal where grant reviewers can see all the necessary information such as product reviews, user stories, team accountabilities and involvement scope of each party.

An indication of how your project relates to / integrates into Radicle

We are very excited to collaborate with the Radicle team as Proposal Inverter incorporates the Radicle Drip’s backend mechanism for funneling the funds within the Proposal Inverter. As stated in the Meta-proposal above;

“The proposal inverter inverts the DAO-proposal relationship. Such that, instead of having many proposals for a single DAO, we will have many DAOs for a single proposal. Through a fund funneling mechanism that continuously “drip” funds according to pre-negotiated contracts, the “inverted” proposal will be funded in a semi-automated manner.”

The Drip and Split mechanism have a perfect use case for creating this pre-negotiated fund funneling for allocating funds for proposal contributors as this action requires continuous drip of funds to the common pool then be splitted to different stakeholders. We believe the proposal inverter will be the main catalyst for drips adaption across the DAO space for running collaborative fundings and joint ventures. We are integrating drips into the emerging DAO to DAO ecosystem as a fundamental mechanism that can be further utilized by ecosystem participants.

As one can see the Proposal Inverter and Radicle Drips share common goals and aligned ethos. The “Introduction to Drips” article stated “…(Radicle) believe that sharing funds through Splits has the potential to become a new cultural norm in crypto and a fundamental building block for solving difficult problems like the funding of public goods and promoting more redistributive crypto economics.”, very aligned with what Proposal Inverter envisions to reduce collaborative effort between DAO to DAO relationships and by that it tried to nourish the public goods ecosystem. With this collaboration, we will provide a critical tool to the public goods ecosystem.

The original version of this table can be found in Meta-proposal above. ( Sorry for the image quality, the forum only allows me to have 1 photo.)

Future plans

In the short term our building partner, Token Engineering Commons will be accountable for the marketing, documentation, and communication side of the project. Along with those efforts, PrimeDAO’s pioneer position in the DAO to DAO ecosystem will help our team to integrate Proposal Inverter into this growing D2D ecosystem and make it heavily adopted. Through those efforts, Proposal Inverter would likely become a pivotal tool for DAO to DAO coordination. Regarding our future plans with the Radicle team and drips mechanism, as the community of builders behind the proposal inverter, by integrating drips backend and working around expanding the protocol’s architecture, it will also be a hub for pushing toward utilizing drips as a composable primitive for funding public goods, such as integrating quadratic funding, utilizing the sitting assets in the drip reserves for revenue generation, creating decision-making mechanisms around the that dripped funds, etc.

The development process of the PI will bring a wave of developers towards becoming familiar with the drips infrastructure. There will be a co-promotion process between Radicle and many other DAOs involved in this collaborative effort such as Gitcoin, PrimeDAO, TEC, and Longtail. The collectively joint marketing potential for this process is a very powerful force and will lead to some major disruption across the DAO space.

Contact

  • Contact Name: Mert Ozdal

  • Contact Email: mert@prime.xyz

  • Telegram: @mertozdal6

Team Code Repos

Team LinkedIn Profiles (if available)

Alp Ergin: https://www.linkedin.com/in/alp-ergin-401a9883/

Shawn Anderson: https://www.linkedin.com/in/shawnwanderson/

Mert Ozdal: https://www.linkedin.com/in/mert-ozdal-9a2789213/

Jeff Emmet (Advisory): https://www.linkedin.com/in/jeff-emmett-05268139/

2 Likes

Hey everyone,

Alp here. I wanted to underline that our goal is to arrange a monthly sync with the Radicle team and show/post our improvements before the next milestone, so that, the Radicle team and its community can transparently be involved in the building process of the Proposal Inverter and they will make sure to approve the next level of funding or request work improvement before doing so.
(That’s also embedded in the proposal inverter, a funder can exit anytime if the project doesn’t deliver as expected)

Also regarding the UX journey here is documentation that can provide some detail on the ongoing design;

Looking forward to your questions

1 Like

Hi Mert and Alp! On behalf of the Drips team, I wanted to say that we’re very excited to see your proposal – thank you for submitting it. I love the high-level vision for the Proposal Inverter, and I believe that if your vision is realized it has the potential to help solve DAO coordination challenges and streamline funding for many initiatives and projects that are hard to coordinate today.

In terms of more specific feedback on your proposal, it’s clear that your team has done a lot of great work around the mechanism design and other theoretical aspects of the project.

In addition to that, it would be great to see more high-level detail around the problems that PI is aiming to solve for everyday users (both on the DAO side and the contributor side) and then some rough sketches of what that would look like in action. This might include:

  • User stories and use cases
  • UX wireframes
  • Technical requirements

The first versions of these can just be drafts, but they would be super helpful in building excitement and consensus among stakeholders around what PI will do. The CoolLabs case study is a great start towards this and if you can add some wireframes and user stories I believe that the proposal will be in a good place and it will really help communicate the uniqueness and power of your vision.

The second piece of feedback I have is that your timeline looks pretty ambitious to me in terms of getting all of this built out and deployed by the end of July. As part of your initial scoping work and work on wireframes and user stories, I would strongly suggest that you think about the smallest MVP build you could initially do, and then aim to deploy that first, with successive builds coming in later stages over time. Because I think getting the full version of what you envision deployed by the end of July will be really tough, but getting a MVP deployed by that time is probably reasonable and then looking to expand on that in later phases based on feedback of stakeholders, adoption, funding, etc.

Finally, in terms of the monthly meeting, we’re happy to do it so let’s look to schedule that for sure!

1 Like

Thanks a ton for this awesome feedback @andrewd
This kind of deep analysis from a core member is invaluable!

Just want to say that I second what @andrewd has noted. Getting those three items (user stories/use cases, UX wireframes, and tech requirements) will help a lot. This is the initial investment of time/effort I’d expect from grants, especially larger ones.

I’ll address each of these below:

User stories/use cases + Wireframes

User stories: There is a single example (Alice, Bob, Rachel and Bartu). I think it would beneficial if you really create a fully fleshed out list of possible user stories and use cases (i.e. not just Alice, but others too). Categorize these and speak to how your solution will solve each of their unique problems.

UX wireframes: There are some hints of how things work with diagrams. But, for example, how might the MVP look? How might this look if integrated with Radicle Drips? Painting a picture of short, medium, and long-term look/feel would be great here. As @andrewd said: just some simple drafts are fine here

In your planning doc, you have the milestones below. This seems to point to the ideas above. It seems really close, but could be fleshed out more (using some of the ideas above). Especially before we jump in from milestone 4-onward :slight_smile:

Technical requirements

There is a lot of theoretical work (like here). Do you have some more details on how this will be technically implemented?

I’m actually not the best the review the really weedy specifics (presumably that’s why we want this audited). This is less a sticking point for me, but might help folks like @andrewd get involved in a deeper manner.

Overall, I’m really excited about PI. I think we just want to flesh this out a bit more.

Thanks!

Hi everyone,

This is Ruben I am working together with Bartu on the UX/UI design for the Proposal Inverter. First of all, thank you for your constructive feedforward and we wanted to say that we agree with your concerns. We have just completed creating User Personas and now will be working on further creating some user stories (based on the previously shared cool labs case), linking these with scenarios/use cases, and providing some draft wireframes for the Radicle community.

We think we will have these new drafts for you by the end of next week!

Once again thanks @andrewd @bordumb.

1 Like

@Ruben

Awesome to hear!
And thanks a bunch for the quick response.

Please feel free to just respond here with any useful links, images, text, or other materials once those pieces are ready.

Looking forward to it! :slight_smile:

2 Likes

Hey @bordumb @andrewd ,

As promised we created an extra user story (the contributor)/ scenario and made a wireframe draft for the proposal owner user flow.

Contributor User story/Scenario

Wireframes Proposal Owner flow (drafts) in miro

Please keep in mind that these are drafts and we would love to receive comments and feedforward so we can design better. Looking forward to hearing from you all!

Have a great weekend.

2 Likes

Hi @Ruben

Thanks a bunch for sharing these. These are great and the wireframe definitely helps illustrate what you’re looking to build.

I will start the vote for Milestone 1 ASAP. Keep in mind that the scheduling will be as follows:

  • Milestone 1: if passed, 20% of funds will be dispersed immediately (4,000 USDC). One completed/approved, the remaining 80% will be dispersed upon approval (16,000 USDC)
  • Milestone 2: will only start once Milestone 1 is fully completed. The voting funding process will follow a similar schedule as Milestone 1.
  • Milestone 3: will only start once Milestone 2 is fully completed. The voting funding process will follow a similar schedule as Milestone 1.
  • Milestone 4: will only start once Milestone 3 is fully completed. The voting funding process will follow a similar schedule as Milestone 1.

Let me know if you have any questions in the meantime.

1 Like