- Chandra Station - Validator for Cosmos Chains
- Max / baktun - Akashlytics
- Gunjan Walecha - Open Registry
- Tom Beynon - Deploy Tools
- Tyler Frank aka TCF - AGE Network Partner
- Ethan Kravitz aka Ethos - AGE Network Partner
- Maddie - High school student, Web3 Hobbyist
- Colin Pollen - Akash Partnerships
- Adam - Akash CTO
- Boz Menzalji - Akash COO
- Eric Zietlow - Akash Developer Relations
- Kelsey Ruiz - Akash Comms & Content
- Adam Wozney - Akash Community
- Derek - Akash Engineering Lead
Mission Statement for Community Awards Board
- Chandra: Our focus is to make sure that people who deserve funding get it from $100 to $100,000.
- Max: Decisions should be made by the community.
- Gunjan: Agreed
- Tom: Get an eye on promising projects and developers coming up in the community.
- Tyler: Raise awareness and build the community
- Ethan: Increase the number of developers involved in the community.
- Adam: Agreed. Foster new projects.
- Boz: Mission statement should be narrow in focus on the projects that we are funding to contribute to the growth and adoption of the network. Examples include Akashlytics and Deploy UI tools.
- Derek: Agree
- Adam: Agree. Spurring innovation in the decentralized cloud across the Cosmos ecosystem
- Eric: Agree
Community Awards Board
Nominations for new CAB Members
- Colin Pollen - accepted, attended
- Chandra Station - accepted, attended
- Max / baktun - accepted, attended
- Gunjan Walecha - accepted, attended
- Tom Beynon - accepted, attended
- Ethan Kravitz aka Ethos - accepted, attended
- Maddie - accepted, attended
- Sara Sioux - accepted
Should we cap the number of board members?
- Boz: We should work on the process before expanding. We may want to have representatives from other communities such as Cosmos, Solana
Requirements for CAB Membership
- Attending meetings
- Voting on Project Proposals / Grant Applications
- Activity on the Forum
Funding for Developers
- Proposal was passed and 100,000 AKT was sent
- Chandra: We want the CAB to make decisions on 10k or more. We do not want to make developers wait to get started
- Ethan: We should require them to write a proposal to show they are committed to building.
- Kelsey: Agreed, we want them going through the different phases and showing some level of commitment.
- Derek: Does the Akash open source network want to compete with AWS and DigitalOcean?
- Colin: Note that our competitors offer $100 of credit to all developers with a GitHub account for free.
- Chandra: I feel the proposal was not meant for all developers.
- Ethan: I feel the same about the proposal.
- Eric: It seems to me that this fund is for improving the quality of the community rather than anyone off the street.
- Colin: Sounds like the consensus is to only give $100 to developers with a project proposal.
- Maddie: We don’t have a Testnet at this point. Getting 5 AKT would be enough to get them started.
- Ethan: Is there a cap on this? Colin: There could be 1000 new developers.
- Vote: 8 hands raised! Consensus
- Motion Passed
- Chandra/Tom/Maddie/Maxime: Everyone should review.
- Ethan: How do we determine the amount $1000 or $10000. If a project comes in that requests more funding.
- Gunjan: At this point we want to follow up with Jasdeep to present. We are already working full-time and part-time on this project.
Should people presenting their project be voting on their own proposal?
- Colin: No they should abstain.
- Gunjan: Agreed. (Note: Gunjan abstains from voting on OpenRegistry)
- Vote: Consensus is Yes
- Motion Passed
Should we vote to fund OpenRegistry?
- Yes Votes: 6
- No Votes: 0
- Abstain Votes: 1
- Motion Passed
Should we vote to fund Project Phoenix?
- Vote to give $1000 to Project Phoenix
- Yes Votes: 8 votes
- Motion Passed
Amendment to Proposal #9
Eventually, we came to an agreement. Initially small submissions ($100–$1000) will be internally managed by Akash, and funded through the Akash treasury. The next stage, larger funding submissions ($10,000+) will be managed through a committee, and funded through a multi-sig wallet managed by those committee members.
After Jack, and other validator(s) agreed to this, we approached the Akash team and they agreed as well. So in the next day or so, we plan to amend our proposal to reflect the new plan. This satisfies Jack’s desire for decentralized/ committee governance, ours for efficiency in phase 1/ small submission requests.
Moving forward, we are making a call to action for other Validators to get involved in this process. It was a pleasure to meet some of our Validator friends today, and we hope more of them reach out to get involved in the committee, or even just to say hello.
- Ethan: I would like the CAB to focus on larger awards. A Faucet should be built and funded by Akash not the CAB. I agree that we should make it a quick process to get $100 but not make it as simple as a Faucet. We want to know how much will go to the smaller grants. We should look at a breakdown of the funding to be spent by tier.
- Max: Maybe we can do partial payments. Will milestones be required for $10k or just $100k? Colin: up for discussion.
- Ethan: We agree but also think it should be in different wallets
- Gunjan: Agree larger amounts need votes
- Maddie: Agreed with Gunjan
CAB Meeting cadence and next meeting date.
##Weekly or monthly?
1.Maddie: Let’s meet more often than monthly to start.
Tabling these Agenda items for 2nd meeting:
- Vote on Amendment
- Break down of the funding by tier
- Faucet is recommended to Akash
- Vote on Mission Statement
- Vote on Closing Nominations