Hello everybody! Posting here the brief answer I gave in the call that is currently ongoing.
1. As the domain allocator, how do you plan on building and maintaining a pipeline of grant requests for your domain?
Idea is to be reachable in the very short term. What I want from the grantee requesters is to be able to pitch first their idea in a few sentence, and then expand on the pain points (which are always there) and related solutions, alongside the value proposition. My job will then be to evaluate, if available, more in depth docs and get back to a second meeting with the requestors to go into details. If both meetings will be positive, it can be a first solid base to proceed.
I also plan to keep contacts with the projects that will be approved for the grants afterwards, to keep a tab on how the funds are used and if the team is doing what is actually supposed to do. This is to both have internal metrics and also a general feedback on our role as domain controllers.
2. What kind of rubrics will you set for your domain?
Value proposition: how do you plan to bring value to Arbitrum ecosystem
Pain points: what flaws do you see in your model, and how do you plan to address it
Financial planning: how do you plan to use efficiently the funds. This is not trivial, at all.
Timeline: do you have a clear timeline for your project, and how do you plan to respect it
Team: do you have the people with the right skill now that you are applying? What gaps do you currently have and if so how do you plan to fill them?
3. How will the selected rubrics help you make a decision when assessing requests?
Pain points is even more important than values. For example, it’s easy to say “my project aims to bring sticky liquidity”. It’s difficult to answer how you are going to deal with the current difficult environment, or what you are planning to do when the first batch of resources you allocated to this goal will end, just to refer to the previous point.
Another crucial point in the team: world is plenty of good ideas, and also plenty of money to realise these ideas. What lacks is people able to actually implement these. A team that is missing key players needs to first enforce the roaster, and then ask for grants in my view.
4. Is your schedule flexible enough to accommodate meetings with other domain allocators and the program manager to discuss program improvements and pain-points?
I work in crypto full time, and interface myself with people from different timezones everyday. Also, I really like working on weekends when days are slow. And when I am not at my laptop, i think a lot about the challenges that arise everyday. So, when is going to be the time to communicate with the rest of the team, not only I am going to be available, I am going also to be quite efficient in doing so.
5. How will the community be able to communicate with you to offer feedback on your performance?
Everyone can reach me out, through Twitter, Discord or Telegram. I have no issue not only in chatting with anybody, but also in setting up calls if someone wants to communicate something more complex. Even if I have a 1h call with a new person that doesn’t lead to specific results, I would have still connected to that person, enlarge the network, have new ideas and have a new point of view I didn’t had before on a specific topic. To me, this is a huge value added to this position, and not a burden.