Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Maki application #1144

Merged
merged 2 commits into from
Sep 9, 2022
Merged

Maki application #1144

merged 2 commits into from
Sep 9, 2022

Conversation

CrommVardek
Copy link
Contributor

Project Abstract

This application is a response from the anti-collusion infrastructure RFP

Maki aims to be a simple MACI implementation for the Polkadot eco-system, similar to the existing one on Ethereum (MACI)

Grant level

  • Level 1: Up to $10,000, 2 approvals
  • Level 2: Up to $30,000, 3 approvals
  • Level 3: Unlimited, 5 approvals (for >$100k: Web3 Foundation Council approval)

Application Checklist

  • The application template has been copied and aptly renamed (project_name.md).
  • I have read the application guidelines.
  • A BTC, Ethereum (USDT/USDC/DAI) or Polkadot/Kusama (aUSD) address for the payment of the milestones is provided inside the application.
  • The software delivered for this grant will be released under an open-source license specified in the application.
  • The initial PR contains only one commit (squash and force-push if needed).
  • The grant will only be announced once the first milestone has been accepted (see the announcement guidelines).
  • I prefer the discussion of this application to take place in a private Element/Matrix channel. My username is: @_______:matrix.org (change the homeserver if you use a different one)

@CLAassistant
Copy link

CLAassistant commented Aug 24, 2022

CLA assistant check
All committers have signed the CLA.

@alxs alxs self-assigned this Aug 25, 2022
@alxs
Copy link
Contributor

alxs commented Aug 25, 2022

Thanks for applying again @CrommVardek! Are you aware of this previous application for this RFP? The team didn't go ahead with the project in the end, but you might want to have a look at their proposal. In particular, they list a more detailed interface. How would this functionality be provided in your case? Feel free to add details to your application.

Also could you just clarify in the deliverables which language you'll use for each of them? I.e. TS for the prover vs ink! for the verifier etc.

@CrommVardek
Copy link
Contributor Author

Hi @alxs , thanks for your comment.

I wasn't aware of that application for the same RFP, I'll read their proposal and the detailed interface (which is indeed more detailled than mine).

I'll add more details in the Project Details section and clarify the languages used in the deliverables.

@CrommVardek
Copy link
Contributor Author

Hi @alxs , just for information, I'll complete my application by the end of this week. Sorry for the idle time on this.

@alxs
Copy link
Contributor

alxs commented Sep 6, 2022

Sounds good, no worries and thanks for the update.

@CrommVardek
Copy link
Contributor Author

Hi @alxs , I've added details of the interface and interactions of Maki.
Just to add, the main difference between the pallet_maci and maki is reusability, with the latter, for each new vote round, a new contract must be deployed. Old one cannot be reused.
This is a choice, to facilitate maintainability of Maki's usage I think it's better - when a new version of Maki is released - to just use the latest one rather than having the dilemma to choose between continue using an old one or deploy a new one.

@alxs
Copy link
Contributor

alxs commented Sep 9, 2022

Thanks a lot for the additional details - looks really good to me, I'm happy to approve it and I will share it with the rest of the committee.

@alxs alxs added the ready for review The project is ready to be reviewed by the committee members. label Sep 9, 2022
@Noc2 Noc2 merged commit 0c5ca99 into w3f:master Sep 9, 2022
@github-actions
Copy link
Contributor

github-actions bot commented Sep 9, 2022

Congratulations and welcome to the Web3 Foundation Grants Program! Please refer to our Milestone Delivery repository for instructions on how to submit milestones and invoices, our FAQ for frequently asked questions and the support section of our README for more ways to find answers to your questions.

Before you start, take a moment to read through our announcement guidelines for all communications related to the grant or make them known to the right person in your organisation. In particular, please don't announce the grant publicly before at least the first milestone of your project has been approved. At that point or shortly before, you can get in touch with us at [email protected] and we'll be happy to collaborate on an announcement about the work you’re doing.

Lastly, please remember to let us know in case you run into any delays or deviate from the deliverables in your application. You can either leave a comment here or directly request to amend your application via PR. We wish you luck with your project! 🚀

@CrommVardek
Copy link
Contributor Author

Thanks for trusting me again :)

@CrommVardek
Copy link
Contributor Author

Hello,

I'm just writting this comment to say that I'm still working on the 1st milestone, slower than I wish. But the project is not dead.

However at this pace, I don't expect to be able to deliver the 1st milestone before the start of the next year. Just so you know.

Best,

@semuelle
Copy link
Member

Thanks for the update. Feel free to submit an amendment with updated timeline to take the pressure off, or if you think it might take longer than that.

@keeganquigley
Copy link
Contributor

Hi @CrommVardek just checking in. If you still think there will be significant delays I would recommend filing an amendment to update the timeline. Thanks!

@keeganquigley
Copy link
Contributor

Hi @CrommVardek just checking to see if you can give us an update on M1, as I believe we are approaching on 6 months. Thanks!

@CrommVardek
Copy link
Contributor Author

Hi @keeganquigley , sure, the M1 is almost done, there is still the doc that needs to be completed and the step 4 that has to be finalized as well. I cannot give you a strict deadline for me to finish the M1, but soon :)

@keeganquigley
Copy link
Contributor

Thanks for the update @CrommVardek if you think it might take longer than 2 weeks please submit an amendment to extend the timeline.

@CrommVardek CrommVardek mentioned this pull request May 3, 2023
@CrommVardek
Copy link
Contributor Author

Sorry for the late reply, rather than just adding a month, I added 3 months on the the application for the first milestone in PR #1717

@rhysbalevicius rhysbalevicius mentioned this pull request Sep 4, 2023
10 tasks
@keeganquigley
Copy link
Contributor

Hi @CrommVardek how is the first milestone coming along?

@CrommVardek
Copy link
Contributor Author

Hi @keeganquigley , it was terminated : #1830

@keeganquigley
Copy link
Contributor

ah thanks @CrommVardek I had not seen that amendment, I will mark it as such.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready for review The project is ready to be reviewed by the committee members.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants