Get on the update. So, we implemented to clawback mechanisms or rather a clawback mechanism that is applicable now on the cloud and then other flow mechanism that will be applicable when we actually know who the service providers that are going to be elected to the car as well. So, there will be sort of these two clawback mechanisms both using different mechanics, but catering for two different facets that I will explain shortly. So, the first clause of mechanism is that the Dow through the Zodiac governance module that we implemented in the safe, the safe multisig will be actually been through an on chain vote to retrieve the funds from the multi SIG itself. This is something similar to the step multi SIG the quest book multi SIG for that grant program. So this is sort of the standard I think we have set in the arbitrage Dow that there's actually not a lot of other ecosystems, sort of enabling the community to actually return the funds from a multi SIG. So, that is the first clawback mechanism that we've implemented on the safe multi SIG for the ARDC via the Zodiac governance module. The second one is another clawback mechanism. Once the elections are finalized once we know who the service providers contributors that will form part of the ARDC through those through the DAO advocate will be we will be used utilizing Keji to pay out the funding and the fees for those funding for those applicable service providers. Part of Hedgy is that you have this grant manager role and then that grants manager role we will actually be putting the arbitration that won by arbitration now I mean, naturally, our token holders and this will enable token holders through an on chain vote to terminate the stream for all the service providers and the power to get should there be a breach. So payouts will happen on a monthly basis to service providers and the Dow advocates will give time for the 16 day on chain vote to pass should during that month something occur, a breach of an agreement take place so that I will have ample time to actually submit an on chain proposal and also affect that project proposal should there be a breach of the agreement on disclose conflicts of interest, for example, whatever it may be, so that is the second check and balance we've implemented even on chain with the help of Lindsay. Thanks a lot for that. That will be applicable though we don't have implemented beforehand because we don't know what the service providers are. And we need to know the analysis of the electric service provider for that to be implemented. So that's the second update in relation to the clawback. The third update, which is I think the most important is that the proposal is now entirely at the entry of both externally after what seems to be years of my lifespan, but it's finally there. So that's another sort of minor update. Another update in the proposal is that my retroactive payments was set at 16k ARB, it is now set at 16k USD payable and ARB because I think I you know, the payments reflected the efforts mouth from the firm other companies contributors that you know, contributed to this particular proposal and checks and balances etc. I don't like the look at page two, okay, in light of the current through product five for the work done on this, so it's amended to reflect the work done and the hours contributed from from our firm side. So it's now 16k payable in ARB as opposed to 16k R which will be like two to 2k USD. So that's, so that's a minor update. And I think one last thing is sort of interest from election, a question that I'm getting very frequently. Now we're seeing I think I've seen an episode for the risk research and security will have an average of three interested parties. For security interest, there are around five or six interested parties actually, for research as of today, that around three, four, and four, discuss whether another three, four, or other interested parties that would want to apply, shouldn't be on a footpath. Something that's also beneficial is that I'm actually getting words of a lot of people that are interested in also joining up and submitting your drilling publication, as opposed to single applicant will potentially have joint applicants as well, which could be very interesting. And also something very interesting as well is the payment methods that they are just searching for example I spoke to two security firms. And they have nothing short of getting paid by by task as opposed to getting paid via retainer model and there potentially won't be work. So that's something that delegates would have to consider prior to voting on the service provider. I think, you know, applicants are being very cautious on or rather very diligent on the payment models. They will put in the application should be on chain podcast. So an interesting model whereby, for example, these two security firms basically discuss Listen, we want to get paid when we actually do work. So potentially in the application, they will be doing this sort of model, whereby payments are only affected once work is actually affected from it, which is again, very interesting. I think more beneficial for the Dow and that's something that delegates will have to scrutinize sort of which service provider is waiting for the Dow and we get more bang for our buck as an instance. So I think those are the the updates I had from my end is very short and sweet. It's merely an update will want to update you guys on what's currently going on. So yeah, I think similar to the procurement one short and sweet from an update perspective, and if you guys have any questions, feel free to take the floor even feel that potential the application process election process, because there is no way that we can optimize on that as well. I don't think there will be any qualms or optimizations on the election side because the election does start I think three days actually three days after the onset of both parties.
We'll also be having another update. I think I spoke with syncope, actually a few minutes ago. Another update on the 17th of January at 4pm UTC. On both proposals. So this proposal research collective and the other proposal being the procurement one, which by the time it will, it will be on Thursday as well. So yeah, I think those are the updates from my end. Do you guys have any questions and queries and feedback even even though we're on chain I mean, always open to feedback. And we can even iterate and optimize on this particular endeavor if the on chain vote path is throughout the tenure of the DC as well. So you have any questions or queries feel free to voice them all yours.
What is the timeframe for? Like if we wanted to run? Oh, for example, one of the things we really wanted to do is Tao personas, and we were gonna run a grant for that. And we'd love to run it through the procurement committee, right, like that's what I'm here for. Right? So when would it be ready for us to run something through like what's the expected date?
So for the procurement I will say is a separate proposal than than the research collective because this call is research collective base, but I thought I can also address sort of my acronyms. Noise we have, I think we have we have we need an acronym database because there's LTIP SPI PIR DCI deputy even I'm getting confused at this point
because there's a double double P or a single P. Okay, and awkward. But I can also address the procurement one while we're here. So the procurement committee the on chain proposal will hopefully be up by the week I think decayed. I'll work with JK to put that on chain propped up by end the week so that there's a 16 day period, though or something that we've been considering. And while we're here maybe we can get we can get through that. That's a very good point that experts will be the first thing on their to do list. Something that we've been discussing and that hopefully next week, it will be affected is since the snapshot pass with a substantial margin to be more I would say efficient. We can initiate sort of the election process for the procurement committee members while the entree vote is live. I think if if I have seen for example, only a 60% in favor on the procurement committees. I would be hesitant to do this. But given that there was I think 99.28% in favor. I think it's safe to say that we can potentially potentially and I'm still getting feedback from different delegates and third parties on this initiate the election process for the procurement committee members in tandem in parallel with the on chain vote as well. So that's one on chain both parties, the procurement committee members will be appointed and we can basically hit the ground running on the procurement side because I know even from a subsidy fund perspective, from a security service perspective, because that's the only framework that we have in place at the moment. You know, people are eager to get this going and especially usual, you know, that could potentially be another vertical that that was the procurement from a hypothetical. And so yeah, I think for efficiency sake, it's something where it's maybe one thing to have the on chain vote and the election process run in parallel. I think there's no harm in doing that. If the on chain vote doesn't pass and the elections are concluded, the elected members just don't get on the committee. There's no harm done, apart from you know, just submitting an application and then getting elected because the Shambo didn't pass, but I'm pretty confident I think that that will be an issue. So what do you think about that job running them in parallel? Maybe
happy even way? Really, I'm just looking for the like, what's the date that like I should because there's a couple of things like you don't like in that persona saying it's like, Should we wait and run it through so you know, like everything in our you know, first milestone we were making a lot of calls right like President discretion there. And then was like the point of our proposal, but you know, we want to start using these tools testing them. And before sort of just kind of like looking at like, Should we wait for this or is it going to be like a month before we can run it through that we could have the work done by them? Right?
I think sort of, I would say a ballpark estimate would be that if we run them in parallel, you know, by end of month or first week, February, the procurement committee will be in full effect and you can actually run this by the procurement committee by end of month first week, February. If we decide to do so. Later this week or early next sort of the announcement for the election process late this week or the next so we could be looking at that ballpark sort of timeframe there but yeah, I do like the fact that you know, I want to see all these different committees and diverse etc. be interoperable with each other, you know, the procurement committee needs expertise or research on a particular vertical solid three policies that need from the ARDC. You know, grant programs need a particular expertise or research done on a particular area of solid Z or the Z. So I think we need to actually or we have to more rather because the tools are there actually use these tools that we have and I'd love to see some interoperability between the groups, for sure. Yeah.
Awesome. Thanks.
So I'll wait another three minutes, maybe 10 or 20. And if anyone doesn't have any questions, we can. We can switch off for today. I guess. A hobby LTIP voter coming, Alex, because since we're here and there are a few delegates, maybe even have the time to discuss that as well.
Nothing, nothing major to put on that end. We're still pushing things forward. And I believe we work with Clifton on getting the word out for getting more applicants in something we heard from a lot of delegates was that they wanted to have they wanted to give everyone an access or the opportunity to apply. And I think over time, more and more delegates and different people in the community realize like this was a good way for them to show their value to that doubt. So we're planning to get more delegates. I think the proposal is pretty much kind of locked in at least for a snapshot and then we'll take it over to tally.
Perfect. Yes.
Just wanted to kind of plug in the session that I'm holding tomorrow. Anybody who's received a grant from arbitrage is actually eligible for a profile for karma and I spent the holidays kind of filling in as much information as possible. And so I'll be holding a session on tomorrow to discuss the onboarding for reviewers as well as grantees onto karma. But then also speak about how we can lead towards a pathway to actual impact evaluation, as the ones that we're running right now are, of course in regards to perception, and whether or not it was a irresponsible to fund but I think as a community, especially with a working group like this, it would really help kind of, you know, create the foundations for an aligned impact evaluation framework. So I just posted it on the QAT. So I hope that as many of you can join.
That's a good question. Is that added to the arbitrary bow calendar themes because I don't know if I've seen it. Yeah,
I've asked for it to be added. So I'm hoping that it will be managed today.
It is now.
Perfect. I don't know if it's called because this is, I think, a herd that that will also have to overcome I think for the procurement committee elections. For the city. I think there are a lot of interests but how do we actually do better rather have a more effective approach towards attracting contributors even from other ecosystems? To apply for these particular rules? Can we roles can we use job boards for example, I don't know this data may be rather link have an arbitrary Gao African job board, for example, for all these roles, like a repository for available roles within the ecosystem. So it's not scattered like it's on the photo more links to a forum post but a central repository or of Available Roles or other opportunities within the Dow. Makes it more harmonized I think.
Sorry, Was that directed to me or is that an open question?
I think in general, but yeah, if you have a response, because it's something I've been thinking about because for dydx, who had the sorts of benefits of using the green house job boards, and that's and so a threat like a lot of applicants, but for the Dow, it seems to always be within the Dow itself, but it's difficult to attract those applicants sort of the other extreme use to the ecosystem, which is something that through job boards can be done and that we've managed to do and the idea of sort of addressing contributors from other ecosystems. So it's not always restricted to the same pool of people applying for the roles. I don't know if there's sort of a more dispersed or decentralized way to affect this. Yep. And
yeah, so I don't think it's in terms of the approach. We can have a job board we can have, you know, contributor pathways. I think that the biggest kind of the issues from the people that I've talked to, who are like highly skilled and want to get into web three are curious about the work that I'm doing is that there needs to be an exact structure of exactly what their expectations are and what the outcome from that activity is. I think that like, you know, there's a lot of like gray areas, and it's like everybody can participate. But people also want to know whether or not it's valuable to their time, but whether or not they can actually add value to it and like meet their intrinsic kind of goals like professional goals or contributions. And so I think that the first thing even with the research group could also be like, how do we create like actual scopes of work? And specializations in which those types of people can actually participate?
Yeah, I've actually also been thinking about you know, coupling all these endeavors with a bounty board. For example, so that even though the particular group has this scope of work that they're carrying out, if they have ancillary thoughts, which, for example, are low priority, and they're not tackling at the moment, they can put them up on this bounty board and potential contributors, if they affect the thought, in a satisfactory manner can actually get rewarded for affecting that policy as well. So it's something but the implementation thereof will be tricky, because you know, there is a multi SIG and we'll have to link it to the the bound report and the quality assurance of the task, whether the task is satisfactory or not, and that there is some subjectivity in there as well. So I think it's a matter of do we execute on the idea, sort of because bounty bounty boards have been prone to a bit of subjectivity and poeticism in the past, it's, it's a criticism that they get frequently actually. So how do we eliminate sort of the these conflicts of interests, which bounty boards when administered by a central party, fall Pivotal, so yeah, it's something that I've been thinking about hence the question.
So I think we can get there today, if there aren't any more questions. Thanks a lot for joining guys. I won't set up another ARDC or procurement call, or procurement committee call this week, because next week on the 17th on the community, I think governance will I'll be giving an update on both so there will be that opportunity to actually update on both proposals and, you know, the state the current state of both proposals, and hopefully an update also on the procurement committee elections of late this week early next we announced the elections to be done in parallel with the on chain vote. Thanks a lot for joining and thanks for taking the time guys appreciate it.
Labs proposals gonna be up as soon as foundation approves it. So do you see that pop up? We'd love some, some people commenting and supporting sooner than later.
Perfect. Finally, let's hope there isn't another one day delay job. I've been waiting on this. Hey,
you know, one day five one days it's the same.
Thanks a lot. Thanks a lot for your time. Good, everyone. All right. I want