[Non-Constitutional] [RFC] Arbitrum D.A.O. (Domain Allocator Offerings) Grant Program - Season 3

Thanks for the feedback. Let me go point by point here

In the previous iterations, Questbook had a single management of both the PM and the platform, for a total of 10k/month. This was, likely, a way to optimize costs on their side, which now fell off with the decoupling of platform/role.
For the utility, as we have seen so far the biggest part is the public availability of information and the accountability part: while this depends mostly on how DAs engage with the grantees, we see that if milestones are properly reported as comment in questbook it becomes easier to effectively track the flow of information; same thing for analysing approved versus rejected proposals.
But I would like to leave the word to @Srijith-Questbook for a better analysis.

To be perfectly clear, the PM having less compensation compared to the DAs has been something dragged from the previous seasons. And it has been, up to some degree, an anomaly compared to most grant programs, both here and in other ecosystem, in which usually the PM has a more prominent compensation. That said, while I don’t have a specific answer for this (and i will contact you privately to clarify your point of view here), I am seeing several delegates suggesting different type of compensation, either in quantity or structure or both, which at this point could be worth exploring.

The $8K salary is from season 2, in which we mostly quantified the work as an 80 hours per month work at a comp of $100 per hour. This is also just a reference number: there has been a very different way to engage from the different DAs, likely also due to the very different nature of domains.
As stated in previous comments, we are likely scraping the bottom of the barrel on the DA side. The work is almost linear based on the amount of proposal inflow, the more proposals in, the higher the amount of work, and we can honestly expect the inflow to grow since this has been trued between season 1 and 2.

For this, first check my previous comment to blockworks; that said, totally fine in including this clause and adapt over time, knowing 1y is a long time and a lot of things can change.

I’ll contact you privately on this: discord archives after some time the discussions so not sure if everything that was discussed was still there; on that very specific case, and in general situations like this, I am currently working with entropy to mitigate the issue, and will post more in the report thread