Thank you to everyone here for engaging in a dialogue, we are grateful for your feedback.
The lion’s share of the projects that need funding are open source and public goods, and cannot have a private investment component; the returns needs to accrue to ATOM holders.
Replying to @Sumit_Redhu, @JD-Lorax, @jacobgadikian:
We are viewing this as a public service activity, not a seed investing activity; that said, we do have several team members with backgrounds in investing & setting-up investment team processes, which does position us to establish a public funding function competently based on our direct experience.
The DAO set-up does not allow for any beneficial ownership, and, since the stated purpose in the proposal (ie, the vision) “is to create a grant program to support small/med size projects for open source software, public goods, and ecosystem initiatives that add value for ATOM holders”, there is no possibility or intention of taking any equity interest in anything.
Replying to @Cosmic_Validator, @alijnmerchant21:
We agree with you that experience, team design, and workflows all matter tremendously to establish a successful grant-making function.
Five members of the team bring investment experience, including investment lead at Chorus One, team members at Delphi Digital, team members at Cosmostation, and the head a top ranked VC in APAC region, plus myself.
My personal track record (since people are asking about qualifications): I’ve been making seed investments for 20 years, I had 1200+ seed deals per year come across my desk and did ~85 pre-seed and seed deals in 2022. Over the last decade I’ve invested in more then 50+ Y-Combinator deals thru my partnership with Liquid2 Ventures, and, my track record as a seed investor on AngelList where I’ve done 100+ seed deals is top 5-10%’ile over last 8 years. I’ve been involved in several investment clubs and funded dozens of projects on behalf of Stanford University during the five years that I served as Executive Director of a cross-disciplinary research program there. I’ve also built three software companies. I’d be happy review my seed investing and professional track-record with a few community members if that would be helpful towards creating trust, pls schedule a time via Calendy.
As for rationale for how we built the team, here is the thought process: Cosmos validators, investors, & community members w/ deep Cosmos knowledge; low drama people who ship; good reputations & track-records; a group that is neutral to ICF; committed to a vision of funding public goods to create value for ATOM holders; available to spend time on this activity.
Replying to @yoda, ala.Tusz.am, @jacobgadikian:
We agree with you that funding experiments/prototypes is needed, that is the right idea for a program like this.
With respect to the question of ‘breadth of mandate’, this is an interesting topic. On the one hand, a successful program like Y-Combinator (since people are using it as a reference) is totally open to ideas across all of technology globally – and it is this openness to finding the next brilliant entrepreneur with a blue sky idea that is a big part of its success. I see Y-Combinator’s other success elements as a blend of strong positive brand, high volume of applications, efficient process for entrepreneurs, excellent mentorship, and team-based workflows to sift through and rank 1000s of proposals every year.
The idea of ‘depth vs breadth’ is relevant to the discussion of mandate for a grant program. For a typical software project, you want to see ‘depth’ of team & execution capability around a specific project plan. However, for a grant program, you actually want to see a team & workflow to handle ‘breadth’ of proposals. That is the comparative advantage of such a program in the first place: achieving horizontal breadth & exploration of ideas to find teams and initiatives that can bring new value into the Cosmos community!
Also, we need to create a culture where we try lots of ideas with willingness to accept at least 1/2 of them will fail, and, to get out of this mindset of over-deliberating on every small item and instead get into an action-orientation around the precise workflow that we know can lead to catalyzing positive initiatives within our ecosystem.
Although constraining a grant-program pipeline building mandate seems value-limiting for the reasons pointed out above, we could certainly do so if that is the wisdom and feedback of the community.
A question for community members: if we were going to constrain the grant-making mandate under this proposal to a more narrow purpose, how would you recommend we do so? In addition to the vision statement already provided, would pre-specifying a few program themes, such as building on top of ICS, governance/tooling, etc. be sufficient?
Can you please share your feedback on this topic? We are open-minded to adapting our proposal based on community feedback, but so far the feedback isn’t specific enough to actually be useful in narrowing the focus of the grant-making activity.
If you’d like to discuss and brainstorm with us via a Zoom call feel free to book us over next few days via Calendy. That can be a faster way to discuss complex topics and brainstorm together.