MakerDAO Tool House Rock, 6 Apr 2023

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Tool House Rock #4 | Wonderverse

Description

Forum Link: https://forum.makerdao.com/t/tool-house-rock-4-wonderverse/20218

Description
Tool House Rock is a structured community call to give projects a way to showcase their tools and solutions to the growing MakerDAO Ecosystem. Tool House Rock will follow a consistent call agenda, focused on giving Ecosystem Actors a foundation for reviewing and assessing tools.

This Session's Guest: https://www.wonderverse.xyz/
Wonderverse is an interface software that coordinates workflow for decentralized teams. It is a proactive hub that can integrate with other source types and people could yield higher productivity and saved time for core unit facilitators. Within the software, one is able to:
* Prioritize and manage multiple projects.
* Interface with commonly used tools such as Discord and Notion.
* Configure token transactions with multiple wallets.
* Initiate and manage on-chain voting.
* Access web3 features such as token gating.
*Enable contributors to build and share a native web3 resume.

Disclaimer
This communication is provided for information purposes only. The views and opinions expressed in this meeting are those of people involved and do not reflect the official policy or position of MakerDAO or any of its contributors, Core Units, or affiliates. This communication makes no representations about the enduring accuracy of the information or its appropriateness for a given situation. This content is provided for informational purposes only and should not be relied upon as legal, business, investment, financial, or tax advice. You should consult your own advisers as to those matters. References to any digital assets and the use of finance-related terminology are for illustrative purposes only and do not constitute any recommendation for any action or an offer to provide investment, financial, or other advisory services.

MakerDAO Links:
https://makerendgame.com
https://mips.makerdao.com
https://forum.makerdao.com
https://chat.makerdao.com

A

Welcome everyone to episode number four of tool: House Rock um powered by the ecosystem cluster today we're we have this uh very interesting project uh called Wonder, verse and before we go or we dab deeper into it. um Just a quick reminder for those joining us for the first time or checking the the video.

A

So the the idea of two house rock is um is to give an overview of different tools uh and uh yeah potential solutions that either ecosystem actors or or subdials or metadatos or or any scope could use to potentially enhance their productivity, the rich their different categories actually, um but it is to give this quick overview and if someone wants to dive deeper, they can they can do it or engage, but it's just a way of bringing cool projects and give them some visibility.

A

So before we start the same disclaimers as as always, our views are our own, um so we are not representing the whole maker. There are a lot of possible inaccuracies as information changes very very fast, so we apologize for that. uh Try to check everything everything before uh making any an important decision and then yeah the classic, not Financial advice and not legal advice. So this is just for informational purposes.

A

Only um yeah, diving deeper on one diverse now so uh today, we're joined by Ed and Andros and I will give it to them very very soon, but before that these are the Scopes um that we have identified, that they might benefit the most from this application, uh so ecosystem infrastructure growth, um where we see the Improvement categories or collaboration, transparency, Innovation and governance, so without any more uh anymore. On radio, as study was saying uh earlier, I'll give it to Erin Andrews so that they can do a more Justice in in this introduction.

A

Thank you for being here guys.

B

Thanks for having us, oh do you want to do the yeah, of course, um yeah hi, everyone, I'm Andreas, um one of us. We essentially build coordination tooling for decentralized teams, so we help Dallas nft Projects gaming guilds.

B

um You know, T5 protocols, Etc manage some of their grants, their proposals and how that flows into operations like projects and tasks, and we help manage how you know value gets attributed and contributors get paid as well. So far, we've worked with over a thousand by three year olds like Bitcoin. Do idx, Bank, pastel mare, Circle Etc and have just under 60 000 contributors on the platform, so really excited to see how we could support the mega data ecosystem.

C

Hey everyone- and uh this is Ed- um the head of Partnerships at Wonder, verse, um just to plus one to everything that Andrew said, um I. Think um we'll we'll give you a presentation today um using the the format that uh that was suggested, um but also like we'll show you a live demo today. um What you'll see in the live demo is um a lot of a lot of the features were actually co-built and um co-created with Partners um I.

C

Think for us, like our philosophy, is just like working more closely with folks who use our product. So um a lot of our products are driven by Partners telling us like here's, the problem that they're facing, and we work very closely with them to scope out and build out those features to make sure that they're addressing real problems that um that particular partners are facing.

C

So um just wanted to to put that in mind um specifically because, as we go through the presentation and and there's like q, a um you know, there's I just wanted to be there in the back of your minds that there's a lot of room for collaboration um to co-build um on on the solution.

C

um So yeah just wanted to to throw that out there. um So I guess: I'll I'll share my screen now and go through the the presentation so.

C

um Can you see my screen yeah looking.

B

C

Awesome, cool, okay, so yeah. So as uh Andrew also saying um you know where or wonder uh we're building coordination tools for uh for digital communities and teams um and yeah uh what problem is Wonder solving uh we're solving coordination problems within uh web3 teams, whereas web 2 is a very centralized dedicated teams working on solving the same problems and there's a lot of infrastructure in place and guide rails in place to make sure everyone's working on the same thing, progress is very tracked and very tied to compensation um in in process flows.

C

Web 3 there's there's a shift. It's more about decentralized teams of contributors that might have varying degrees of involvement like you could have someone who's like a core team member. You could have someone who's a core contributor and you can also have someone who's. A Community member contributes time to time, but they're, all they're, all driven by by Passion, for solving a specific problem or participating in a particular community and and so this web 2 to web3, there's a shift that creates new coordination challenges.

C

So how does how does Wonder solve this coordination problem? uh The first is through very nuanced role system, so it's based on detailed actions uh via Discord style roles. That can be token gated. So there's different ways to assign roles to to wonder. There's role-based invite links, there's token gating, nft gating, uh you can also import Discord rolls over, and you can also connect your guild XYZ on the right side. It showed examples of what that looks like this is an example of of roles.

C

You'll see that it's not it's not binary, it's not either you your super admin. You have access to everything or you have access to nothing. We have very like detailed action, specific roles that you can easily modify so and we'll get into that a little bit when we do the live demo.

C

um The second way we solve coordination problems is that we provide greater flexibility for metadows with pods. um So what pods are is essentially like a sub team um or or sub-gal Guild uh I. Guess in this case, metadals is the preferred terminology um where, um where the pods can have their own workspaces, their own documentation, they could also have like their own budgets, notices, safe, wallets permissions and privacy levels. So essentially like they are a separate, um uh separate entity in terms of operations but they're still connected to to the overall Mothership.

C

So in this case like uh in this workspace, like we have content, pods, Community, pods Etc, all with all, with its own set of permissioning privacy levels, memberships as well, and then that also uh that also leads into they have their own roles in Access systems, as well as as well as wallets and payment systems and again we'll go into that in the live demo.

C

The third way we solve coordination problems is, we have a seamless, end-to-end coordination flow, um so I think what Wonder does really well is that um from uh from creating uh governance like proposals and voting, it flows really well into and seamlessly into milestones and Sprint planning. um So you can create a proposal. You can vote on it uh when it's approved.

C

It turns into an internal task or project that you can assign people, or it could be a bounty that you can engage external community members and it also flows really well into payments, um whether it's like in-app or off platform, as well as flowing into building a reputation system uh for for contributors. So in this particular case, I just show an example of um of a grant where an approved Grant.

C

You can create a pod workspace so that there's that seamless flow between approving someone for granted and then creating a workspace to track progress for transparency and then some some public bounties that folks can work on as well as like spring planning uh with uh with Wonder uh the fourth.

C

The fourth way we um help solve coordination problems is that we also recognize that in web3 there's a lot of uh different uh tooling um and they may be solving uh specific problems, and there are some that are more commonly used than others and so I think Wonder does a really good job of integrating with uh commonly used tools I'm here just uh some examples of tools that we have Integrations with and, of course, like there's more to come.

C

There's like snapshot for for voting, Guild XYZ for relationships uh or our membership, uh we're we're integrated with Utopia Discord, coordinate, notion, GitHub, Auto, space, Etc and I.

C

Think our philosophy is that we will build um features to solve uh to solve specific problems, but we also recognize that um you know you you can, for example, you can do voting uh inside Wonder uh for um for proposals, but if your organization chooses to, we can also export that to snapshot, for example, um but uh we don't force the the user to uh to use Snapshot uh if, if they don't want to because we recognize like sometimes you just want a simple- you know uh yes or yes, or for or against a type of proposal, um but we are integrated with many different tools uh and, of course, like we're open to further Integrations in the future as well.

C

um So how do we? uh How do we improve existing uh processes? um So, um as Juan mentioned, there's like three three different areas uh to highlight: there's uh the governance. um So Wonder um supports, like nuanced roles, uh to help organize um holders, whether it's uh voter committees, delegates core units um or external experts, uh into specific roles, with specific uh things, uh permissions access um that that they can that they can execute on, as well as enabling maker holders participation.

C

um In in token gated, or will gated voting or proposals discussions and creating an audit Trail for transparent governance, um which ties into transparency um because, like we have a really good balance between transparency and private workflow, um we have the ability to make workspaces as well as pods, have public or private access.

C

um So you could. You could still have Wonder as a private workspace, but then you might have some pods that are public, um for example like if you want to run public bounties or if you want public votes, um but that are still gated. You can do that, um I think with transparent governance and voting um past Bounty submissions and payments, um because it's all integrated together um and you have that smooth end-to-end flow that really supports uh transparency for the organization um and finally, um with uh collaboration.

C

um Wonder enables a lot of Rich, customizations and flexibility in terms of roles in terms of like how work is set up as well as working uh between like organizations so I. Think. With this. With this flexibility, we can support different configurations of collaborations, which, uh which will address the different, the different needs of the meta Dows and the teams um and I think like because it's flexible it can also evolve over time.

C

So um if, if a metadat or sub-dial wants to configure work, a certain way, they're not they're, not stuck to it forever, because uh because Wonder enables customization and flexibility.

C

um Another other areas like include like impact, is just the ability to track progress um very easily um from end to end, so you can measure impact um and track it and then finally, the the collaboration or sorry Innovation is that uh with collaboration or shared workspaces, um we we support multiple organizations um having a shared workspace, as well as like shared notifications, um so um that can help metadows um explore Partnerships with um organizations um very easily and then ensure that everyone's aligned on responsibilities due dates, um but also like that.

C

Because of that that will increase collaboration with other other partners. We also have Community features um that will help surface ideas from the Greater Community that aligns on Mission and yeah.

C

We can talk a little bit more about that um and then just wanted to um uh just ensure that like uh to set our expectations or our understanding, um so what our understanding of um of end game and and how it relates to sort of like what we're working on is that um end game leans, happily into metadowns, um helping um like moving from a more um centralized like uh central body uh into uh different uh different metadals um that focus on specific specializations, um but that are still connected through, like the the central um Mothership, uh through uh uh tokenomics or infrastructure um or or people, um and then I think like from that.

C

uh By having like the the different metadats like The, Meta Dows will have its own um governance processes. It might have its own, like you know, token gating, uh for for governance or participation, um but it's essentially like different um uh diff, essentially different uh group or team that has its own, like treasury, has its own um uh roles and and access and there's a lot of flexibility and customization for each one, depending on what the what the needs are.

C

So that's the so that's our understanding that we're trying to ground uh with uh in our demo um so yeah just wanted to uh just wanted to repeat that. So yeah, so next we have a demo I'm, just gonna go over to to wonder: um yeah can can everyone? Can everyone see it just want to make sure like it's still sharing the the same window?

C

Yes, okay, cool! uh Maybe I'll increase the size a little bit too. Sorry I like to uh hopes.

C

Yeah, okay, cool, um okay, cool, um so this is a. uh This is a workspace for uh for maker Dow. um This is the the project home page, which kind of gives you like an overview of everything. uh So the way that um wonder is uh is structured. Is that there's like the workspace which is uh maker Dow, but then underneath that um there's uh the different pods or metadows?

C

um And then each each of these different levels has its own um access and permissioning that we'll get into, uh but I just wanted to, like sort of mention that at the very beginning- um and so here like I, have I I was not very creative I, just called it metadata one meta-dow two, but then I also had one that was just called Innovative products, because I just want to show a little bit more example, um but yeah so like this is the maker Dao um workspace, the pods and then the different um work items.

C

um So this is an aggregated view because we're at the the project home, but it also depends on like what permissions you have um and which will allow you to see certain things. uh So, for example, I see this logo design contest uh Bounty, because I actually have permissions uh into the Pod this is attached to.

C

But if you don't have um the proper permissions, you will not, uh you will not see it um and then here you also have like Milestones um proposals as well as members of the workspace and then collaboration workspaces that you have with other organizations um and then grants as well as documentation and we'll we'll go into all that um uh that that later, but um so I wanted to show one of the things.

C

uh What makes us um I think special in that like we provide a lot of like very nuanced permissioning, so I'm going into the maker Dao rules right now, um and so this would be roles for um the overall overall workspace, um so by default, there's um there's owner role, which gives access to like everything these are like your super admins um and then by default.

C

The second role is a core team role which gives access to more of like a subset of things, but again, as I mentioned in the slides before you can toggle on and off um specific actions. But you'll notice like these are very like specific actions that um uh that members can take um and then there's a contributor role which is really just uh participating in proposals, discussions and getting assigned work, but what what I wanted yeah, but what I wanted to highlight was actually uh the ability to create uh roles uh and specific roles.

C

So, for example, like I have a delegate role uh which um sorry I'm not extremely familiar with the exact um permission, so I kind of just took some creative freedom, um but I said, like a delegate, you know was able to review tasks um and so like because of this, then, um if you assign someone a delegate role, then they're able to review tasks like for the entire workspace you'll notice that you know, like you, can token gate um uh tokengate the role as well with um uh with nft or erc20 token.

C

You can also import your um your Discord roles as well um to to map your Discord role over to um uh to a Wonder role. So I also created roles for like facility, for example.

C

Facilitator, might you know, be able to create tasks, basically anything related to tasks, um but then external consultant, you know, might not really have controls, because they're really there to participate in discussions um et cetera, et cetera um and then I wanted to show an example of token gating, so I created one where it was a maker holder and uh and so like. If I wanted to add a token gate. um I said these are some of the token Gates that I've created I created a maker holder.

C

So as long as you have at least one maker token, then you're considered a bigger toker, uh so yeah so I apply this maker holder to role okay. So that means that anybody who has at least um or who creates an account on wonder, connects your wallet if they have at least one maker, then uh they they can automatically get this uh get this role um so yeah. So that's an example of um the specific rules um and wallets I'll, just kind of flip over here to um like I created something called sample down.

C

um The reason why I'm flipping over is that I didn't connect, of course, um Guild over to the maker workspace. Our sample workspace because yeah um so I just want to show you like what what it looks like if I were to connect um a guild.

C

um So in this case like uh for sample Dow, which is a fake Dow that I created uh for contributor roll like. If you had this role on Guild, then you automatically get this uh get this role for for contributor for uh for sample doubt and then uh for stationary lovers.

C

um I have a stationary lovers role, because I love stationery um I connected my my Discord server, um where there's a station and Lover's role that I imported over and that connects to this uh wonder, wonder role.

C

um So so, if you, if you did that, then you don't have to um you just have to manage the the roles um once uh you set it up and then you can kind of like set it and forget it. You don't have to um you know manually uh like set up roles and whatnot.

C

um The next thing I just want to show you was um uh related to uh wallets, um so the workspace um can have its can have its own set of wallets um a noses, safe, wallets or metamask wallets. um But then the pods can also have their own um I didn't again.

C

I didn't set up a wallet for Baker Dow, but here's an example of sample Dow, uh where I could have like different wallets that I can use to pay out um different contributors or I can, like you know, pay out, bounties or I can use it to give out grants as well.

C

So you can connect to all these like different wallets for for the workspace, um but again like this could be at both the workspace level, but then also at the um at the Pod level, okay um and then from from uh sorry go back to uh maker. um So from from maker uh there's. Also um speaking of like um uh more Nuance like permissioning for documentation, um I know, there's a lot of documentations um and and processes in maker, and so like.

C

We have a documentation section where you can create different uh categories um and add links to documents.

C

um So we support linking to the documentation because we recognize that, like you, don't want documents in like two different places and then update in one place, but then forget to update in another, um and so instead, like we support linking. uh So you can just update it from from its source, um but I think the the benefit here is that you can also um you can also gate it so, for example, make your dial Frameworks and important documents, I added the Constitution and different Frameworks.

C

It's a Google doc link, but it's only accessible to uh to members as an example, um but then for um developer documentation uh for technical documentation. I made it public so that, like anybody, can can see it like if they were to go to this workspace or developer guides, because sometimes you might want public links, but then you might also want things that are only accessible to uh to to your own to your own members things.

C

um So this is. uh These are some things that are at the at the workspace level, but then I'm going to go into like specifically like a um what what it looks like in in a pod um and then also like explore some of the other things I wanted to cover.

C

um So this would be like, uh like sort of a line to uh the goals of moving to uh to more metadats and sub-dials.

C

uh One of one of the uh one of the goals is to be able to generate more like Innovative products and services, so I created a pod um that was, um that was public, um so the workspace previously was Private, um so you have to be a member to uh uh to like participate in things, but this is a public uh public pod uh for Innovative products, um so from here, um I want to quickly like show um settings so so from here like you'll notice, like there's a lot fewer roles, uh one of them I created Innovative uh products, facilitator uh not very creative, um but then over for this role like you can then uh toggle on and off certain permissions for the role or you can like token gate.

C

It Etc, but you'll notice that um this uh this Innovative products pod has its own set of role and permissioning. You can also configure a wallet for Innovative products. The idea is that um The Meta Dows would have its own um uh would have its own budgets or operating treasury so that they can operate very autonomously because, as long as you can have have access to and also manage your own goals as well as um as well as wallet, then you can. Then you can operate very autonomously.

C

um Oh uh yes, so got a question in the chat. uh What type of tokens are supposed uh for? The for the token gate? uh uh Yeah uh we support uh erc20 tokens. We support ERC, I, think 1155s.

C

Right right, yeah does that answer your your question.

C

A

Yeah, so just by recording processing if 721s are, are supported as well. We cannot hear very well they're in the back, but yeah.

B

Sorry yeah 721s are supported as well.

C

Cool um yeah, so just wanted to also um so after the the role wanted to show um uh show bounties. um So bounties are uh things that um you might. You might get multiple submissions for so difference between a task and a bounty is Task is something that you assign one person um you could either make it like. First come first serve uh it because, especially if you're working with poor teams, um you don't really care who works on it. um Do you just care that someone works on it?

C

So first come first serve or you can apply an application layer so that uh either uh only folks there's multiple configurations, but some configurations are only certain roles can apply for this uh to take on these tasks, or only certain roles uh can just automatically take the task. Bounties are more open-ended where multiple submissions can be made. So things like you, know, logo design contests for this new Innovative product number, one again, not very creatively named, but you can have different folks submit um uh submissions for uh for these bounties.

C

You can, you know, request you can request edit. You can leave comments and then, like you, can you can also approve and then like make payments. uh You can also like change the um the uh the yeah sorry, my brain's blinking, the the number um for for the Bounty as well. So if you so that enables you to uh support contests and competitions.

C

um If, if you want to use variable bounties and then you can pay like through through your notes to save wallet or metamask, um so we can support uh bounties. That way.

C

um Another thing that um that also wanted to uh to cover was uh was grants um so even within um within a Meta Meta dowel like if you wanted to offer uh grants like you, can create a grant system um so put up a put up with Grant, uh fill out the the details of the purpose description requirements, um and then you can set a a budget to give out grants to folks and then from here like when, when you do approve grants, it will just.

C

You can also create uh additional pods to track progress of those grants, um so it it supports a lot of transparency and seamless flow and operations.

C

uh Oh, um do you want us to answer the questions now in the chat, or do you want to uh or do you want us to answer it at the at the end.

A

It's up to you guys if you feel that it's on topic for twitch you're describing feel free to to go more in depth right now or or if you think that some section that you will present is coming, you can also take them later. Yeah.

C

Maybe we'll maybe we'll answer it after just yeah just so that we can answer all the questions at the same time. So uh but I'll go back to the chat after yeah um yeah, so I think one last thing I wanted to um uh to cover. Is that uh like recognizing that um uh that there that there are, uh there is also an emphasis on on governance and uh proposals?

C

um So so you can create proposals. uh Sorry, actually we'll just go to the purple section. uh You can create proposals, um whether at the overall project level or the workspace level, so you can make you can create proposals at the maker maker, workspace level or you can make uh or you can create proposals at the Pod level.

C

um So I think that supports also like the the idea that meta Dows can, you know, run its own governance um governance process, so here just uh two examples that I just pulled from um recent uh proposals um if I click into it uh yeah if I click into it. You know you'll see like this is this is the proposal um you can vote. You know for or against um uh the uh the proposal.

C

uh You'll also see like the number of uh the votes, uh but you won't see like the like who actually voted for for what um this was done intentionally, so that um there is an undue influence. um If someone votes for one way or another, uh you could participate in discussions.

C

And the discussions are then, of course, like tied to the proposals.

C

um You can also like add tags uh due dates uh for um for the proposals, and if the proposals are approved, um then they are recorded um under under uh actually I'll, just I guess: I'll just approve it um under approved um approved proposals, and uh it will also you also see it under um tasks uh board, because it could be a project or um or task that you that you assigned somebody um we also support.

C

Oh, we also support snapshot, um exporting uh votes to snapshot so again, I didn't set up Snapshot for the the test uh space for maker, um so I'll just go to like sample now, uh but yeah so like these are all the uh proposals I created for sample Dow on wonder, but then I exported some to uh to snapshot um so that you might want to do like voting first um on on wonder and then, if the vote calls for it, you can also export it to snapshot.

C

So so, in this case, like you know so, sample Dow should attend. Nmp NYC uh it'll export it to your snapshot space and then it will just leverage whatever voting system, that you've decided on um previously, like inside your your snapshot, um yeah.

B

Filter reads: existing Snapchat proposals that are open all those just so you.

C

Know people can see what they can vote, cool um I, think the only thing I, maybe sorry, I'll just do it really quickly, but just two more things um that I'll cover um is a collaboration workspaces, because I think this helps with um uh you know, having like quicker um uh or or enabling uh quicker collaborations and Innovations uh with the different metapods, is the idea of like a shared workspace um between two organizations, so in this case Wonder, verse and maker Dow.

C

uh We created um this like shared workspace, um where, like both teams can have access to it. You can invite you know more members to it, and then you can also like create tasks um that you can assign to people uh even like uh outside of your own organization, so like in this case, like I, could maybe assign something uh to someone from um so from maker, um and then, if you connect, um if you connect to your uh Discord or telegram integration here, um you can.

C

You can then get notifications for for the for the different tasks, um so yeah so like. If you want to connect your Discord, if you want to connect your telegram, then you'll also get like pings like uh this. um So anytime, like proposals are created or or someone's assigned something someone's uh completed, something you'll get a notification uh to a specific channel that you specify or you'll, also get like a DM.

C

Mentioning like hey like these are, um like people requested to join your workspace or, like oh yeah, like this vote was or sorry proposal was approved. um So, like you, also get updates that it has been, uh has been approved um and then I guess. The only other thing um that I'll really briefly touch on is uh we we also uh oops uh the wonderbot.

C

uh So so we we created um a wonderbot which uh helps you, um which helps supports the um uh the tasks of um of uh community members or of of um the members of the workspace. uh Sorry I'm having like a brain fog.

C

um So uh if you wanted to uh create like let's say, um if you're working on like SEO strategy, for example, you can just ask the wonderbot to um you know like create um SEO strategy, and then it would Auto generate um tasks to fit within a milestone um that um you know that you can, of course like choose to accept or or like modify. uh But the idea is that um we're also trying to lean more heavily into uh into AI um so that we can uh more easily like support the.

C

If efficiency of oh sorry, efficiency of um of work, um so yeah.

C

D

C

An example, if you want to create like a design Sprint for the marketing team, this will then generate a list of uh list of tasks that you can accept or you can or you can modify. um We are. We are trying to lean more heavily into into this, because we we think that this can um support more efficient uh work.

C

Cool I think uh yeah I, think that covers everything.

B

um Yeah, we'll just try to cover some of the questions.

A

uh Super cool, yeah, I, don't know the team. If you want to jump on them, our team actually left. Okay, he left the question. So, let's see here check clear the recording um but yeah I can read them out loud. If you want um so the first one is: how do you handle when people leave or switch admin controls.

B

Yeah so when, when you say, when people leave, you mean when they leave the workspace or when you mean um I I, think basically, what we do is that, like other admins are able to just like you know, edit the rows, and um you know they can change up the sort of membership levels of.

C

B

Sort of like I, don't know contributor. Basically, um so that's how we would handle I think when someone leaves the team or stops being an administrator, um oh yeah, so for reputation.

B

um There are two different things: um I don't know if you've actually minted anything for me through those times um yeah for completed tasks and um bounties, you can actually mint um your sort of complete Tartan Bounty as an nft. So in that sense you can take away your completed work with you um and then also I, guess like for local reputation. We do have this idea of like a leaderboard, um you know of a CJ song like the number of complete tasks.

B

This is you know why a little bit for fun and engagement where you see like you, know all time, who's completed the most things or you know um done the most bounties and things like that. um But you know for contributors and Community. This might be an interesting, interesting way to engage um and then when Milestones Escape creep, yeah so I think basically how we handled that we advise teams to do. It is basically like when things don't come, get completed in a particular Milestone.

B

um You can just like sort of roll that into um roll the sort of um roll the toss out and keep completed into the next roadmap piece or like the next Sprint or whatever um that that you would.

B

You would be setting up and then any other Integrations that we're excited about um yeah, we're actually hoping to sort of we're working with this organization called inverter Network, and so you know, they'll be helping us Implement, some of drips functionalities, so like streaming payments so that you know contributors can get paid um per time period as well or get streamed their payments.

B

um So that's pretty exciting and then Peyton asked. Can you use Wonder to issue tokens as well? um Yes, yeah! uh So we have this idea of a payments ledger. So once you've connected your sort of notice, you can actually just choose to pay everyone, for example, on polygon, uh and you can actually just like batch pay, um and this basically creates a uh you know, batch payment transaction on the Queue of your nurses. So you can like distribute your tokens whatever it might be uh and then Frank is asking.

B

Can you please go over how one of us reduces bias in Grant distribution which can lead to unequal distribution of resources?

B

um How does your tooling monitor grants that are awarded and failed to use funds effectively or recipients fails to deliver on promises?

B

um I think on the first point, um yeah I'm curious as to as to how y'all do you know Cloud description, but um the idea is that, at least from the sort of organizations that we've worked with there's normally a committee that basically votes um on proposals on like sort of Grant applications and I think the way that we can help.

B

Is you know, for example, you can create a proposal on who to vote with uh who to vote for, uh for example, like you know, you can vote for a grant application here, um which can then you know enable your community, or whatever Community or committee, to actually like vote on which Grant application should go through um and then, in terms of you know, monitor grants that are well. Do you have something to show hard workspace, yeah.

C

B

D

Again over here so.

C

uh It's sampled out, see I, think one of these I I believe um oh yeah, okay, so this yeah so then so then like this is one of the um sorry like it's not filled out very much because it's just an example, but um so this would be like a grant uh application that was approved. um The idea was, like I, think, build on the ecosystem and then I said yeah portfolio pages on sampled out um and then here, like I, already created a workspace.

C

um So uh these are the sample Dow grants um they're. That grantees can then create like Milestones, that uh uh that could be made uh public um and then uh like. You could then show progress.

C

um Whether if you want to build it publicly um or you I mean you could keep it private, but then um the uh the sample down this case um who is giving out the grants, can then still see the progress of um of the grantee um and track it and then I think with uh with future Integrations like with inverter Network, for example.

C

um Then you could. You could then give out grants um on a streamed basis, uh rather than like either like upfront or or at the or at the end um that that's tied to Milestones right now. um Right now, it is uh like a manual um approval or manual send of of that uh Grant, but uh with future Integrations like it would be tied to like, uh pending, like approved uh Milestones, um that that the group have accomplished.

A

Nice super cool I see that Pros has his hand up. I, don't know poster if that's by Design or you actually hit it yeah.

D

It was uh intentional um wanted to go on and kind of, just make sure I'm I'm understanding the the product Suite correctly, because to me this seems like a really neat way for for Dallas to kind of uh interface via their operations, um but I'm curious if I'm viewing it to too limited right um and one way I thought to to maybe ask about that is with the roles themselves.

D

I saw you could import them from Discord, but is there anything that ties the roles to like uh on-chain wallets, for instance, or is it all kind of uh off chain or or centralized or whatever you want to call it.

B

um Yeah, so in the in the roles, so you can basically uh date them by tokens. um So I don't know if that's what you meant so Guild is an option, but you can also obviously token get by the number of you know. Bitcoin that someone holds or you know it could be. You know an nft that they're holding to so I I. Think that's it that that's what you mean. That's kind of the on-chain way where, if I have this many tokens in my wallet, um then you know I can access a particular role.

A

The token checked, like let's say: I, we have like a I, don't know a Channel or some working group for M care holders and you need at least I, don't know 100 mkr in that sense. uh What if I sold um the the tokens and how often would you check to to make sure that I'm still holding them.

B

A

B

A that's a great point, I think for us on the way we did it was like it will basically notify you if someone um stops having the token, um but obviously you know they might still have a core role. That's not really tied just to the on-chain wallet. If you see one well, I mean um so we don't automatically remove roles.

A

B

You don't really do we do not. We do not automatically remove a role when like um uh when someone like uh basically sort of like gets rid of that token, but we let you know.

C

But we don't automatically remove it.

A

Okay, so you would always need like human intervention at some point, foreign.

B

Yeah I think for for that it was. It was more the fact that some people, you know it might be like a requirement, at least with the rules that we worked with, like a requirement for them to sort of build trust in the beginning, and then once that becomes um once that trust is built then like, if even if someone doesn't have the requisite token requirement.

B

There's still, you know a core contributor, for example, um so there's still that contributing work, so it makes sense for them to for the roles just to be automatically removed, um but yeah.

A

Nice and um I was going to say is the opposite. Also true: if someone gets the tokens with the kind of like the super admins, get this notification or is it uh or would they get the role automatically.

B

um So for that, if the admins super admins have set up like oh, you can get the core contributor role. If you get, if you meet this token requirement, then they can request that um they can request that. Look at that role.

A

A

um I don't know if there are any questions. I'm not seeing any in the in the chat frankly want to to open the mic to yeah.

E

So thank thanks for uh answering that question with regards to how to handle grants and monitor if the recipient is putting in the work, so I think there's. Definitely a lot of development and transparency uh being inclusive right. An efficient process that needs to have happened in Dow governance. I was wondering uh with regards to privacy.

E

Obviously this is a centralized database right. This is not. This is not living on ipfs.

E

um So how are you you know? What's the infrastructure to promote user privacy, security and like data ownership, uh since that's what uh the reason why I joined web3 uh was mostly because of data ownership yeah, you know kind of fostering the collaboration, innovation of of web3.

B

Yeah so I think for us um the the purse that we've taken is that, like all, uh let me just see if I can go on something that you created. um Let me just.

B

Yeah, so we also have a mission control by the way where you see everything that you've completed um but I'm just trying to turn something into that's just this one um yeah. So our idea is that, like for completed work, you can basically like mint a task, um something that you've completed and has been improved, and the idea is that you can then put these things on chain So.

B

That, obviously, like you know, most of the data is, as you said, like um sort of on in a database, but I can then sort of uh mint a task um sort of on polygon um and this the fact that I complete something always lives on chain. So you can take the data away with you, that's kind of like our idea of you know providing some ownership over over the data that you have. You might not want to, like.

B

You know, put everything that you've completed on chain, but for specific parts of work that you want. You're proud of. um You can take that away with you. That's kind of the idea.

A

Nice yeah: this is super cool um guys. If someone wants to try this out, uh what's the what's the right way, can they do it uh or online permission, let's say or do they need to get like early Alpha access or something.

B

uh Actually I mean I'll, I'll sort of you can create. You can sign up today and create a workspace normally. How we work with you know more dedicated Partners is, you know, will help you set everything up um and go through like um an onboarding process, but yeah for sort of testing. You can, you know, go to app.1 device.xyz now and actually um create a test workspace or.

C

They could even use the password space. We've been like yeah.

B

You can also use one today.

C

I can paste like the invite links uh here and then you could yeah. You could just join it um like everything that I put in there. Of course, you could just delete it um or you can modify it so I could just paste the invite links uh there, so you can kind of go through the the process or experience of like if you were to also invite other people to your workspace. What that what that would look like and then even from there, you can then create your own workspace too.

A

um I think we have one last question but yeah Peyton saying to ask a red team question: why should Dallas Wonder rather than just adding custom plugins to the Discord for the features they need.

B

I think what we've realized with this score is just because of a the you know the fact that it's a messaging app mainly that a lot of things get lost and it becomes quite chaotic um and I think what we provide is basically a dedicated space that you know links with different um sort of existing tools. Like snapshot GitHub, you know, Etc. That just makes it more focused on coordination and collaboration, um but yeah I'd say mainly. That was that was the. That would be the why we serve a better purpose there, but yeah.

C

Yeah everything you said and um and also like I I, think sometimes like when you're doing uh like discussions versus like doing deep work, um I I think you're you're, like your mindset, is a little bit different, like you want to sort of like exit the space where I usually do discussions uh separately from from where you do uh deeper work um and I.

C

Think like with the I I I, don't know if the question around like custom plugins to like address like specific, um like features or like you know, like different functions of work um but uh yeah like I, think also with um our our Discord uh notification integration and like Discord um uh threads. uh So like you can also turn um uh discussions over here into Discord threads.

C

um That kind of bridges um that Gap but um I think we just made a conscious decision to have work here as opposed to like living it on the Discord so yeah. Oh thanks.

A

Nice yeah and um in terms of, uh if someone's watching this later on on YouTube or or whatever platform, and they want to reach out to ask any questions. What's the best way of reaching out.

B

um Yeah I I I, don't know what prefer for, um but we can. We can give our telegram.

C

Yeah yeah, like yeah, maybe I'll, just like put it here.

C

D

C

Oh sorry, what is it? Okay, yeah? So those are our TG, um but also like I'll just paste. The uh the admin invite link over here. I trust, you all, um but also this is just the test workspace.

C

um So if, if you do sign up uh through this link that I just pasted in the uh in the zoom chat, uh you'll be an owner of the workspace and then from there like uh you can. You know also get access to like the different pods I created and and play around with that. um I.

C

Do want to mention just reminder that, like the permissions on the workspace level is different from the permissions of the Pod levels, um but because because I, because I pasted the owner or the admin role access, you will be able to like get go into these pods, um but you'll still need to be a member of them like if you want to contribute or add discussions and whatnot to them. Yeah.

A

So you might have sent them privately to someone because I'm not seeing it.

C

Oh sorry, I sent it to okay. Yes, okay, sorry, my bad! Let me let me paste it there. Everyone, okay, I, set it to do.

C

There you go sorry about that.

A

Perfect, so that doesn't take them telegram handles right.

C

Yeah, those are our telegram handles.

A

Perfect, so it's at Jack, Alpha underscore XYZ and the other one is at andros418.

A

um Perfect uh yeah any any closing comments guys before we. We close this call.

C

uh No I I guess just from our side like yeah, we would be uh really excited to to work with uh maker, Dao and I I think our philosophies are very aligned in terms of like how we designed this whole work structure um as well as endgame uh in that, like we do believe in. You know, like organizations leveraging um meta dowels um to have very specialized like governance and processes and and roles and permissions and workflow um to support the overall organization.

C

So um yeah like when I read endgame, like I thought it was uh totally aligned philosophically to like how we've been designing things so yeah. We would love uh we'd love to work with. um uh You know, maker Dao, whether it's like, um like one or two teams or or or more I, think the way that we've been that we've built. This is that it's very modular. So it's not that the entire organization needs to move over, even though, like I mean obviously that's great but um like I, think typically like how we work is.

C

We can also like offer one or two teams and then grow from there too, so um yeah. But thank you for the opportunity to uh to present today.

A

Yeah, just a minor clarification uh after end game, uh and if this vote passes, it would be more with like the subtitles or metados or the ecosystem actors, and not with the with the core directly um right, yeah yeah, but but yeah. That was the last thing: uh yeah uh Ed Andros. Thank you very much for for coming this. uh This has been great um yeah thanks for for the presentation at the time.

B

The time everyone cheers thank you.