Quadratic Funding Module and Dapp Application #268

chrisli30 · 2021-02-17T09:12:30Z

Added quardratic funding proposal
Finalized quadratic funding open grant proposal

Grant Application Checklist

The application-template.md has been copied, renamed ( "project_name.md") and updated.
A BTC or Ethereum (DAI) address for the payment of the milestones is provided inside the application.
The software of the project will be released under the Apache license version 2.0 as specified in the terms and conditions.
The total funding amount of the project is below USD $30k for initial grant applications and $100k for follow-up grants.
The initial PR contains only one commit (squash if needed before submitting your PR).
The grant will only be announced once we've successfully delivered the first milestone.

* Added quardratic funding proposal * Finalized quadratic funding open grant proposal

chrisli30 · 2021-02-17T09:19:56Z

Hi guys,

First time creating a proposal here! The funding amount of milestone one is a little bit over $30K. Of course I can break down the milestone but then the first deliver will hardly be in a feature-complete state. Could you take a look at it and let me know your thoughts?

Besides, @Noc2 and @Swader could you shed some light on the proposal?

Thanks!

Chris

Swader · 2021-02-17T09:45:19Z

I can take a look next week at the earliest, going OOO in 2 days and lots to handle before then. Thanks for the proposal and sorry I can't be more timely with it!

chrisli30 · 2021-02-17T21:40:52Z

I can take a look next week at the earliest, going OOO in 2 days and lots to handle before then. Thanks for the proposal and sorry I can't be more timely with it!

That sounds good, Bruno. Thanks!

semuelle · 2021-02-20T17:09:24Z

@chrisli30, the USD 30k limit applies to the total of the grant. You will have to apply through the General Grants program or limit this one to 30k. Follow-up grants in the Open Grants program are not bound to that limit.

Other than that, some (inofficial) suggestions:

could you add the finalize function to Deliverable 1 of Milestone 1? I know it's implied, just for completeness.
if pallet and UI are part of one grant, submit the designs with M1 so there is time to discuss and iterate.
I'm all for supporting studies and evaluations (M2 Deliverable 4), but I'm not sure the committee agrees with me there (@Noc2?). Either way, I personally would want to know in advance:
- how do you choose subjects (what is the target audience)? What is the target size?
- do you have specific questions you want answered or variables to measure?
- are you planning on making the results or your conclusion(s) public? Will this be part of M2?

chrisli30 · 2021-02-22T01:53:37Z

@semuelle, thanks for the input. Here's my response regarding your comments.

the USD 30k limit applies to the total of the grant.

My mistake. I thought it only applies to M1 and at the time of writing, 1 BTC was $30K, therefore I asked for 1 BTC for M1. I can squeeze in a simiple UI implementation(M2) to the program within $30K.

could you add the finalize function to Deliverable 1 of Milestone 1? I know it's implied, just for completeness.

Just to confirm. Do you mean that when the referendum is voted and passed, a finalize() function to make the funds available for withdrawal?

If pallet and UI are part of one grant, submit the designs with M1 so there is time to discuss and iterate.

Got it, I have been sketching the UI design and will add a wireframe.

how do you choose subjects (what is the target audience)? What is the target size? do you have specific questions you want answered or variables to measure? are you planning on making the results or your conclusion(s) public? Will this be part of M2?

I think those questions are to the reviewers of this PR? A staightforward use case would be similar to Gitcoin, in which the subjects are small open-source programs(for example, this project 😃 ) that would benefits the Polkadot ecosystem. You guys are already asking questions and measuring variables in this open grant program, so if the LR fulfills the same purpose, the measurements wouldn't be much different. I personally would like to see if the LR approach could work, that is to attract more dev talents as well as public attention for donation.

2. Adjusted BTC amount to make sure the total funding is within limit

semuelle · 2021-02-22T10:38:39Z

Hi @chrisli30,

Just to confirm. Do you mean that when the referendum is voted and passed, a finalize() function to make the funds available for withdrawal?

Yes, the diagram in your application mentions it.

Got it, I have been sketching the UI design and will add a wireframe.

Is that the extent of what you want to build in M2? Because that looks like quite a bit of work.

I think those questions are to the reviewers of this PR?

No, sorry, that was a bit confusing from me. What I meant to say was: to fund a study, I would like to know more details about the study. For example, how many people would you interview? What would be the questions/problems you are looking for? What are you going to do with the results?
However, since this is now one deliverable of many for 0.15 BTC, I wouldn't demand to know these things in advance.

Noc2

Sorry for the late reply here. I have an additional request: Could you change the denomination to USD. We recently updated this in the template. Once you deliver the milestone we would then pay you in DAI or BTC according to the current price. Therefore the payment in DAI is usually easier. Also do you already have any plans regarding Sybil resistance or anti collusion? You should probably also take a look at the following project, which we recently signed: https://github.com/w3f/General-Grants-Program/blob/master/grants/speculative/nuclei_governance_os_voting.md Regarding the UI, do you have any previous work, which you could share?

2. Fix the paragraph spacing of last commit

2. Update the cost denomination to DAI instead of BTC

chrisli30 · 2021-02-23T05:07:31Z

@semuelle, regarding your comments Sebastian,

Yes, the diagram in your application mentions it.

The finalize() function is added to M1 delivery. Thanks for pointing it out.

Is that the extent of what you want to build in M2? Because that looks like quite a bit of work.

Yes, the schedule does seem a bit tight, but it's manageable. The goal is to build a MVP to show beta users what's this product is about. We probably need to cut corners, for example, using Google Forms for all the project submission instead of building fancy pages. Besides, this design doesn't include user profile & history component, which could be important to UX and should be considered in future plans.

No, sorry, that was a bit confusing from me. What I meant to say was: to fund a study, I would like to know more details about the study. For example, how many people would you interview? What would be the questions/problems you are looking for? What are you going to do with the results? However, since this is now one deliverable of many for 0.15 BTC, I wouldn't demand to know these things in advance.

Yeah, you are right. The details of the user study wasn't clear at all, but since we are trying to squeeze all work into this open grant I think it's better to take it out from M2. I've moved it to Future Plans and listed all your questions for reference.

chrisli30 · 2021-02-23T05:42:44Z

@Noc2 , no worries. Here are my updates with respect to your last comment.

Sorry for the late reply here. I have an additional request: Could you change the denomination to USD. We recently updated this in the template. Once you deliver the milestone we would then pay you in DAI or BTC according to the current price.
Therefore the payment in DAI is usually easier.

Sure, updated payment into DAI.

Also do you already have any plans regarding Sybil resistance or anti collusion? You should probably also take a look at the following project, which we recently signed: https://github.com/w3f/General-Grants-Program/blob/master/grants/speculative/nuclei_governance_os_voting.md

That's a great question! So far my best reference of Sybil resistence is Vitalik's post Minimal anti-collusion infrastructure. I don't know if you have read it, but in order to prevent Sybil attack, a relationship map of any two participating wallets need to be stored and examined. The map could be in a quite large size, but considering that the donation funds will not be withdrawn until after finalize(), we can save the map off-chain(using IPFS) and only examine it during finalization. In addition, such implementation requires wallet identity, so that is up for future experiments, whether we choose strict identity, or tolerate collusion to a certain degree. Since donating to open source community is a great thing, my guess is that probably 99% of participants have no trouble disclosing who they are.

Regarding Nuclei governance-os, it's a nice reference. However, I don't see the quadratic voting method in their delivery notes. I might need to go through their code commits and ask some questions.

Regarding the UI, do you have any previous work, which you could share?

Yep, I've added the link to design files to Update 2: UI Examples, but you can visit from here.

https://drive.google.com/drive/folders/1nZPg4PmWSBxbfHuMyuAlw8UVXSybjTHG?usp=sharing

chrisli30 · 2021-02-25T05:40:20Z

Hi @Noc2 , do you get time to take look at the changes this week?

Noc2

Thanks for the quick response. You also need to update the payment address at the top: “Payment Address: BTC, 141Y9sybQKH6rfCj6DhDeRFR9Ja7rAWKjw”. Are you planning to implement MACI? I mostly shared governance-os because they plan to use a commit reveal mechanism to deal with this, which might also be useful for you. Regarding sybil attack, it would be great if you could support the on-chain identity module of substrate, which is currently used for kusama as well as polkadot as part of this grant.

2. Added Sybil resistance to future plans

chrisli30 · 2021-02-26T05:37:40Z

Hi @Noc2 , no worries and those are good suggestions. My response is below.

Thanks for the quick response. You also need to update the payment address at the top: “Payment Address: BTC, 141Y9sybQKH6rfCj6DhDeRFR9Ja7rAWKjw”.

Oops, my mistake. I've updated the recipient address to ERC20 DAI.

Are you planning to implement MACI? I mostly shared governance-os because they plan to use a commit reveal mechanism to deal with this, which might also be useful for you.

I tend not to re-invent wheels, so it would be great if we can re-use the solution with which the governance-os project comes up. I'll keep my eyes on that project. Besides, MACI has been added to the future roadmap of this proposal, so yes if we feel it needed we will go ahead implement it.

Regarding sybil attack, it would be great if you could support the on-chain identity module of substrate, which is currently used for kusama as well as polkadot as part of this grant.

Yeah, I agree. I think being able to interact with identity module is essential. Our module should be able to filter participants based on their identity information. I've added that requirement to M1 delivery.

Thanks for the recommendations David. I look foward to collaborating with other teams building related blocks, so if you see any other connection please let us know 😃

Noc2

Thanks for the update. I’m happy to go ahead with it and will share the application with the rest of the team.

chrisli30 · 2021-02-26T22:52:56Z

@Noc2 That's awesome! Thanks for the feedback, and yeah let's see if others have questions too.

Swader · 2021-02-27T20:36:25Z

I have reviewed this and it sounds good to me.

semuelle · 2021-02-27T23:54:34Z

Hi @chrisli30, some more questions:

Gitcoin, as far as I know, applies quadrating funding to CLR rounds, where the resulting contributions are calculated and paid out for all participating projects at the same time after a fixed runtime. Buterin et al. use a monthly payment schedule as an example. How do you envision payouts being scheduled in your project?
What are projects and proposals in this context (see Milestone 1, Deliverable 1)? I assume a project is what is being funded and what is proposed for possible funding to the council by a developer. But what is a proposal then? Maybe you could integrate projects and proposals into the UML diagram you already provided?

chrisli30 · 2021-03-02T07:18:54Z

Hi @semuelle, thanks for your feedback. I gave some thoughts to your questions over the weekend and here're my answers.

Gitcoin, as far as I know, applies quadrating funding to CLR rounds, where the resulting contributions are calculated and paid out for all participating projects at the same time after a fixed runtime. Buterin et al. use a monthly payment schedule as an example. How do you envision payouts being scheduled in your project?

That's a great question. As you mentioned, there are two types of payment, lump sum and installments. Lump sum is a sum that paid in a single payment all at once, while installments are funds divided up and paid out over time.

Currently the payment type can be set in two ways,

When submitting a project, the creator is required to define a payment schedule. This is to make sure the funding of the project is thought through at the time of initiation.
After the contribution period ends but before finalizing, the CLR council can update the payment type with a Revision proposal. This gives the council an opportunity to adjust things unfit.

What are projects and proposals in this context (see Milestone 1, Deliverable 1)? I assume a project is what is being funded and what is proposed for possible funding to the council by a developer. But what is a proposal then? Maybe you could integrate projects and proposals into the UML diagram you already provided?

Similar to Polkadot, decisions or changes of CLR need to be voted upon. Since there are a variety of decisions, we need different types of proposal. In my current design, there are 3 types of proposal.

Governance, to change global configuration or member of council.
Regular, which is the most common type and includes below 3 sub-types,
1. Admission, to approve or deny a project's application.
2. Revision, to update project settings such as payment schedule before finalization.
3. Finalization, to finalize a project, making contribution available for withdrawn.
Appeal. Anybody can challenge a result by creating an appeal proposal within a certain period of time (48 hours). The proposal needs to be approved by the majority of the council in order to pass. This is to ensure that the platform is monitored and challenged by the public.

The governance is quite staight-forward compared to Polkadot's two-lane referendum implementation, but I think it will lay a working foundation for the CLR. @semuelle if you need to add anything please let me know. I also updated the UML chart to include the concepts of Project and Proposal. Now you can comment on the chart directly by clicking on Request Access.

chrisli30 · 2021-03-02T07:24:04Z

Oops, I updated the UML chart link but didn't know that the approvals would be dimissed by a new commit.

Sorry @BenWhiteJam and @Noc2 , but could you guys review again? 😅

semuelle · 2021-03-02T07:27:54Z

The updated diagram makes things a lot clearer. Thanks.

No more questions from me.

semuelle

lgtm

chrisli30 · 2021-03-02T09:14:34Z

Thank you guys! Your feedback is super helpful for sorting out the details. Time for us to work!

Noc2 · 2021-03-02T18:38:04Z

@chrisli30 Sorry, it seems I deleted the message on the wrong PR. Here is the message again:
"Congratulations! As part of the Open Grants Program, we want to help winning teams acknowledge their grants publicly. To that end, we’ve created a badge for projects that successfully delivered their first milestone. Please observe the foundation’s guidelines when making any announcements; in particular, don’t announce the grant publicly before you've completed at least the first milestone of the project.

At that point, we will be happy to collaborate on an announcement about the work you’re doing. Please get in touch with us at grantspr@web3.foundation in case you're interested (at least two weeks notice is preferred)."

chrisli30 · 2021-03-03T01:28:33Z

@Noc2 Thanks, that's awesome! Sure, let me propose it with an email from chris@forgelab.io.

alxs · 2021-04-15T07:56:05Z

Hey @chrisli30, I saw your comment on Medium. Could you create a PR and update the team's name and website, as well as add the repo or organisation on which the project will be located? Then we'll update the grants accepted list and the article.

* resource viewer * changed milestone 3 * quadratic-funding (w3f#227) * quadratic-funding * add license, unit test and a standalone minimalistic frontend to spec * add SEOR code-less smart contract platform application (w3f#205) * add SEOR code-less smart contract platform application * update deliverable & add future plans * add multi-chain support in Milestone 2 & 3's deliverable * formart the subtitles of 'Project Details' segment * Polkastarter Grant Application (w3f#204) * Make Polkastarter Grant Application * Added screenshots * Added testing guides Co-authored-by: Tiago Martins <tiagom87@gmail.com> * Added curve market maker (w3f#225) * Added Zondax maintenance+recovery extensions+support (w3f#234) * Create polkakeeper.md (w3f#200) * Create polkakeeper.md * Update polkakeeper.md * Update polkakeeper.md * Update polkakeeper.md * Update polkakeeper.md * Update polkakeeper.md * Update polkakeeper.md * Update polkakeeper.md * Update polkakeeper.md * Update polkakeeper.md * Update polkakeeper.md * Update polkakeeper.md * Update polkakeeper.md * Update polkakeeper.md * Update polkakeeper.md Added UI User stories, and more detail on the milestones * Update polkakeeper.md * Update polkakeeper.md * Update polkakeeper.md * Update polkakeeper.md * Update polkakeeper.md * Update polkakeeper.md Co-authored-by: Caspar Oostendorp <caspar@oostvoort.com> * Readmefixing (w3f#241) * upgrade readme * fix icons * smaller icons * correct icons * Update README.md Updated Evaluators * Update welcome.yml (w3f#242) * Update welcome.yml Update Welcome message * Update welcome.yml updated * Create proposal of stone index on substrate * Updated the BTC payment address * draft of pallet design * Added more details of public functions * Added back the mandatory deliverables * Added desc for public exposed methods * Adjusted the budget * Revised the deliverables 1. Merge the token module into indexed basket management module 2. Made it more clear for DEX integration 3. Update the sequence of deliverables * Create AlgoCash.md * Update AlgoCash.md * Update AlgoCash.md * Update AlgoCash.md * Update AlgoCash.md * Update AlgoCash.md Update the approach of further 500,000 share token distribution * Update AlgoCash.md Add contract specification * Update AlgoCash.md * Update README.md (w3f#250) As discussed on Element, David, I've added Edgeware Grants and Bounties under the other grant programs header. * Update welcome.yml fix html </b> * Create php-scale-lib.md * Payment change * Upgradeability * Add missing milestone title * Reduce scope by removing milestone 2 Milestone 2 was deemed too uncertain to be part of the initial grant. Depending on the results of the first milestone, we will consider submitting another proposal with more concrete steps. * Update pull_request_template.md * Denominating in usd (w3f#253) * Update application-template.md denominating in USD * Update README.md * Create starry_network.md * Rename starry_network.md to Starry_Network.md * Update Starry_Network.md * update Ecosystem Fit * update overview * update architecture * remove ecosystem fit and add additional Information * update overview * Update Starry_Network.md * add nft dao architecture image and reduce price * Added user story about NFT DAO, update demo link * reduce from 12000 DAI to 10000 DAI * Update pull_request_template.md (w3f#261) * Update kylin_network.md (w3f#259) Update the original contract based on grant evaluation comments. [Here](w3f/Grant-Milestone-Delivery#98) Co-authored-by: wannam2049 <71331352+wannam2049@users.noreply.github.com> * Unified TOC and language with general grants (w3f#264) * Update sensio_network.md Second milestone of senseo will no longer be delivered * Remove forum link (w3f#269) * NewOmega Application (w3f#243) * Add newomega application newomega: Fix alignment newomega: More details newomega: Improve formatting * newomega: Include github link to solidity contracts in deliverables * newomega: Update deliverables to reflect file rename * newomega: Update deliverableremove third milestone, tweak price * newomega: more precision in milestone 2 definition * dotmog application * Create bright_treasury.md * Update currency to DAI, add DoD * Update README.md Updated Committee * Update .gitignore (w3f#279) Co-authored-by: Aleixo Sánchez <15819210+alxs@users.noreply.github.com> * Delete .DS_Store * StandardProtocol application (w3f#244) * Add Standard Protocol Application * Update Standard_Protocol.md * Update Standard_Protocol.md * Update Standard_Protocol.md * Update Standard_Protocol.md * Update Standard_Protocol.md * Update Standard_Protocol.md * Update Standard_Protocol.md * Update Standard_Protocol.md * Update Standard_Protocol.md * Create application-template.md (w3f#276) * Create application-template.md - Some clarifications and highlighting based on past issues, - mention licensing, - more emojis ✊, - ask for - short and long term plans, - community & contributors, - status of project before grant, - previous grant applications, - work done. * Apply suggestions from code review Co-authored-by: Aleixo Sánchez <15819210+alxs@users.noreply.github.com> * Update applications/application-template.md Co-authored-by: Aleixo Sánchez <15819210+alxs@users.noreply.github.com> Co-authored-by: David Hawig <davidhawig@gmail.com> Co-authored-by: Aleixo Sánchez <15819210+alxs@users.noreply.github.com> * Ask for follow-up grant info (w3f#280) * Update README.md * fix headings (w3f#285) * SkyePass application (w3f#212) * add application for skyepass * update porposal * update: identity solution spec * updates on milestone desc * update milestone descp * update milestones * update total cost * update milestone spec * delete status col * Polkadot UI Web Identicon + Angular Identicon (w3f#252) * Submission of the project grant template * Adding repositories for Angular and Web Identicon projects * Deliverable + future plans update * Grant Amount Update * Create ZeroPool.md (w3f#208) * add ZeroPool.md * remove the last milestone * fix typo * Update ZeroPool.md * Quadratic Funding Module and Dapp Application (w3f#268) * Quadratic Funding Module and Dapp Application (#2) * Added quardratic funding proposal * Finalized quadratic funding open grant proposal * Added web app wireframe link and description to project details * 1. Added finalize function to M1 delivery 2. Adjusted BTC amount to make sure the total funding is within limit * 1. Move user study out of M2 to future plans due to tightness 2. Fix the paragraph spacing of last commit * 1. Added UI examples to team's experience section 2. Update the cost denomination to DAI instead of BTC * 1. Changed BTC address to ERC20 DAI address 2. Added Sybil resistance to future plans * Added identity module interaction requirement to M1 delivery * Added project and proposal concepts to UML chart * Webb Mixer (w3f#216) * Create MIXER.md * Update MIXER.md * Update MIXER.md * Update MIXER.md * Update MIXER.md * Update MIXER.md * Update README.md (w3f#288) * Update README.md * Update application-template.md (w3f#289) - target audience - limitations - `the project` -> `your project` * Action to automatically label by approvals remaining (w3f#291) * Github action to label based on approvals (missing) * Revert "Github action to label based on approvals (missing)" This reverts commit f6a6b70. * Github action to label based on approvals * Create Gluon_decentralized_hardware_crypto_wallet_services.md (w3f#182) * Create Gluon_decentralized_hardware_crypto_wallet_services.md * Merge branch 'master' of https://github.com/tearust/Open-Grants-Program * update btc to dot * add light node to communicate with DOT. adjust cost based on BTC price change * update based on discussion. using schnorr and social recovery pellet * update milestones * add prerequisites to Schnorr threshold sign * update using Schnorrkel algorithm * update to USD * Update google_sheet_update.yml * EverlastingCash Web3 Grant Application (w3f#277) * Create EverlastingCash.md ELC - An algorithmic stablecoin with reserves * Update EverlastingCash.md * Update EverlastingCash.md * Update EverlastingCash.md * Update EverlastingCash.md * Update Linkedin Co-authored-by: steven <39795608+steven858@users.noreply.github.com> * approval labeler rewrite (w3f#292) * Github action to label based on approvals (missing) * Revert "Github action to label based on approvals (missing)" This reverts commit f6a6b70. * Github action to label based on approvals * approval labeler rewrite * substrate identity directory (w3f#255) * substrate identity directory * substrate identity directory * added 0a to 0d deliveries to milestone 1 * price changed Co-authored-by: dark64 <darem966@gmail.com> * A comma (w3f#298) * Update README as in General Grants repo (w3f#303) * Update README as in General Grants repo * Update README.md Co-authored-by: Aleixo Sánchez <15819210+alxs@users.noreply.github.com> Co-authored-by: David Hawig <davidhawig@gmail.com> * Update README.md Fixing links * Update README.md fix rfp link * Update README.md fix milestone-deliverables-guidelines link * Update README.md Update tech stack/accepted links * Fix broken links (w3f#307) * Update MAP-Bridge.md Termination, see [comment](w3f/Grant-Milestone-Delivery#89 (comment)) * Update MAP-Bridge.md Added payment address again, just in case * Update clover_network.md (w3f#310) * Update shadows-network.md (w3f#309) * Update README.md * Update README.md * Update README.md * Open Grants Program application for project Delmonicos (w3f#283) * Update delmonicos.md + Application update after questions from Noc2 * Update to address demand from gautamdhameja * Changed repo url Repo moved to the newly created Delmonicos organisation * Update polkadex.md * Add Treasureland Grant (w3f#218) * Create Treasureland.md * Update Treasureland.md * Update Treasureland.md * Update Treasureland.md * Update Treasureland.md * Update Treasureland.md * Update Treasureland.md * Update Treasureland.md * Update Treasureland.md * ChainJS Grant application (w3f#228) * Create chainjs.md Adding template for grant proposal * Update chainjs.md Adding ChainJS for Polkadot draft proposal * Update chainjs.md Corrected title * Update chainjs.md formatting * Update chainjs.md added ecosystem fit section * Update chainjs.md * Update chainjs.md Removed instructions * Update chainjs.md removed instructions * Update chainjs.md Added more narrative to future plans * Update chainjs.md * Update chainjs.md Added Kusama support into the grant application, and added more description of the difference between ChainJS and Polkadot.js * Update chainjs.md Updated pricing * Update chainjs.md Lowering price * PolkaJ Android Support proposal (w3f#301) * PolkaJ Android Support proposal * Update BTC to DAI * Adjust price based on feedback * Remove undelivered milestone (w3f#318) * xtoken - XCM Implementation for Fungible Assets (w3f#316) * xtoken * update description * update * update payment denomination, and milestone 1 deliverables * file name change, milestone cost updated Co-authored-by: Bryan Chen <xlchen1291@gmail.com> * stable-asset.md (w3f#286) * stable-asset.md * Update stable-asset.md * Update stable-asset.md * Update stable-asset.md Co-authored-by: Shengda Ding <dingshengda@gmail.com> * move the application file into its proper folder (w3f#320) * discount based on hackathon participation (w3f#325) * Update EVANESCO Legal Structure (w3f#326) * pallet-maci (Minimal Anti Collusion Infrastructure) (w3f#232) * Create pallet_maci.md * Update pallet_maci.md * Update pallet_maci.md * Update pallet_maci.md * discount Apron Network for ParityAsia hackathon award (w3f#323) * changed the bitcoin address (w3f#330) * discount deeper network due to hackathon participation (w3f#324) * Create XPredictMarket.md (w3f#313) * update the gsheet workflow * re-estimate the price of milestone (w3f#331) * Update Apron_Network.md Remove SDK from milestone and reduce the price * Update Apron_Network.md Reduce the price * Bit.Country Milestone 2 (w3f#305) * Create bit_country_m2.md initial draft for m2. * Update bit_country_m2.md Finalised the tasks in the milestone. * Update bit_country_m2.md minor milestone text update * Update bit_country_m2.md update team member * Update bit_country_m2.md update image. * Update bit_country_m2.md Change the amount to be USD as required. * Update bit_country_m2.md Add bootstrap tasks for launching testnet. * Update grant application. (#1) Restructure and update wording to improve clarity of deliverables. Add summary and considerations sections. * Tech stack and changing NFT native to support NFT Tech stack and changing NFT native to support NFT * update Duration update Duration * fix typo Co-authored-by: Shannon Christie <20452861+shannon-christie@users.noreply.github.com> * removed "Adopt storage", reduced costs (w3f#339) * Create vera_defi.md (w3f#281) * Create vera_defi.md Initial grant application * Update grant application * Replace https with http to fix images link. * Add more details to the milestone * Update vera_defi.md Update bio * Update vera_defi.md * Clarification on NFT Lending * Update vera_defi.md NFT Token development clarification * Update vera_defi.md Fix style * Update vera_defi.md Fix style * Update vera_defi.md Update scope to focus on AssetManager. Use existing NFT implementation instead of building our own. * Update vera_defi.md Update cost Co-authored-by: arbach <dev@dev.com> Co-authored-by: Denis <denislam@users.noreply.github.com> * Create Parallel.md (w3f#329) * Auto-merge action (w3f#349) * NFT Collectibles Wallet (w3f#341) * NFT Collectibles Wallet * updating project scope and adjusting cost * updating estimated duration * reordering milestone numbers Co-authored-by: Michael Huntington <2466745+MikeHuntington@users.noreply.github.com> * Clean & fix actions (w3f#359) * Delete label_approval_count.yml * Update auto_merge.yml (w3f#360) * remove m2 (w3f#355) * Update README.md * cosmetic fixes * Subspace (w3f#357) * first draft * second draft * minor edits * finial revisions * Rename subspace.md to spartan_poc_consensus_module.md * adjust license and cost * adjust license and cost * no parallel funding from multiple sources * Update dorahacks-quadratic-funding.md * Update README + other minor changes (w3f#367) * Add more info to README * Track team provenance + minor updates to template * Update PR template * Update dorahacks-quadratic-funding.md (w3f#370) We completed frontend integration with HackerLink. However due to tight schedules we didn't create a demo page based on the substrate-frontend-template (task #2 of Milestone-2). Another reason why we didn't create the simple page is that HackerLink has a complete infrastructure for user registration, project upload / display, etc. The HackerLink code base is not open source. We would like to provide a complete demo of how quadratic funding grant is functioning on a parachain or potentially on Polkadot / Kusama relaychains in the future. Therefore we would like to still submit a milestone. Given that our frontend is not open source and we are only providing a demonstration site that uses our milestone-1 code to provide a service for quadratic funding grant, we are reducing the price to 0 accordingly. * Delete application-template-cn.md (w3f#372) Co-authored-by: borispovod <boris@wings.ai> Co-authored-by: Jiannan Zhang <jn.zhang610@gmail.com> Co-authored-by: AKACoder <30492526+AKACoder@users.noreply.github.com> Co-authored-by: Polkastarter <72085336+polkastarter@users.noreply.github.com> Co-authored-by: Tiago Martins <tiagom87@gmail.com> Co-authored-by: mikolajsobolewski <51751942+mikolajsobolewski@users.noreply.github.com> Co-authored-by: Juan Leni <juan.leni@zondax.ch> Co-authored-by: RAMPDEFITEAM <70554959+RAMPDEFITEAM@users.noreply.github.com> Co-authored-by: Caspar Oostendorp <caspar@oostvoort.com> Co-authored-by: semuelle <sebastian@web3.foundation> Co-authored-by: David Hawig <davidhawig@gmail.com> Co-authored-by: calvinzhou-rockx <55546839+calvinzhou-rockx@users.noreply.github.com> Co-authored-by: Dohkooo <77781754+Dohkooo@users.noreply.github.com> Co-authored-by: Junte <59536049+Madtodist@users.noreply.github.com> Co-authored-by: gmajor <63032554+gmajor-encrypt@users.noreply.github.com> Co-authored-by: Hugo Peixoto <hugo.peixoto@gmail.com> Co-authored-by: Fuling <mon.samuel@qq.com> Co-authored-by: Aleixo Sánchez <aleixosk@gmail.com> Co-authored-by: kylin <70003847+kylin-dev@users.noreply.github.com> Co-authored-by: wannam2049 <71331352+wannam2049@users.noreply.github.com> Co-authored-by: celrisen <78207373+celrisen@users.noreply.github.com> Co-authored-by: darkfriend77 <darkfriend77@users.noreply.github.com> Co-authored-by: Agnieszka Olszewska <agnieszka.olszewska@brightinventions.pl> Co-authored-by: Kasia Łukasiewicz <katarzyna.bulska@gmail.com> Co-authored-by: Aleixo Sánchez <15819210+alxs@users.noreply.github.com> Co-authored-by: Hyungsuk Kang <hskang9@gmail.com> Co-authored-by: Song Zhou <zs@ziorix.com> Co-authored-by: Mor GUEYE <74042620+morgueye4@users.noreply.github.com> Co-authored-by: Igor Gulamov <igor.gulamov@gmail.com> Co-authored-by: Drew Stone <drewstone329@gmail.com> Co-authored-by: Kevin Zhang <kevin.zhang.canada@gmail.com> Co-authored-by: steve <39795608+steve1588@users.noreply.github.com> Co-authored-by: steven <39795608+steven858@users.noreply.github.com> Co-authored-by: Ana Milić-Štrkalj <48686305+anamst@users.noreply.github.com> Co-authored-by: dark64 <darem966@gmail.com> Co-authored-by: Lumena <78696551+lumena-tech@users.noreply.github.com> Co-authored-by: dego-team <69787970+dego-team@users.noreply.github.com> Co-authored-by: Marc Blinder <marc@api.market> Co-authored-by: Nathan Schwermann <schwiz@gmail.com> Co-authored-by: Bette <42193328+bette7@users.noreply.github.com> Co-authored-by: Bryan Chen <xlchen1291@gmail.com> Co-authored-by: Frank Yin <ukby.1234@gmail.com> Co-authored-by: Shengda Ding <dingshengda@gmail.com> Co-authored-by: Marcin <marcin@web3.foundation> Co-authored-by: eva-networks <evanesco.networks@hotmail.com> Co-authored-by: Filip Pajic <42151917+pajicf@users.noreply.github.com> Co-authored-by: Sota Watanabe <w.souta.s.life@gmail.com> Co-authored-by: XPredictMarket <80562134+XPredictMarket@users.noreply.github.com> Co-authored-by: Toney <74755044+Apron2050@users.noreply.github.com> Co-authored-by: Ray Lu <ray@codemeit.com> Co-authored-by: Shannon Christie <20452861+shannon-christie@users.noreply.github.com> Co-authored-by: arbach <aarbache@gmail.com> Co-authored-by: arbach <dev@dev.com> Co-authored-by: Denis <denislam@users.noreply.github.com> Co-authored-by: yubo-ruan <40745291+yubo-ruan@users.noreply.github.com> Co-authored-by: Michael (GP) <79423936+GamePowerDev@users.noreply.github.com> Co-authored-by: Michael Huntington <2466745+MikeHuntington@users.noreply.github.com> Co-authored-by: J Wagstaff <7297707+rg3l3dr@users.noreply.github.com>

chrisli30 · 2021-04-19T01:41:52Z

@alxs, thanks for pointing it out. 👍 I have submitted a PR #377 to address the change. Please take a look to see if the changes are fine.

semuelle · 2021-09-16T14:14:00Z

Hi @chrisli30, are you still working on the second milestone? According to the roadmap, this was projected for July.

chrisli30 · 2021-09-16T16:53:27Z

Hi @chrisli30, are you still working on the second milestone? According to the roadmap, this was projected for July.

@semuelle , yes we actually completed the work in July. Thanks for following up. We'll write a report and submit the result in 2 days!

alxs · 2021-10-05T20:08:44Z

@chrisli30 friendly reminder.

chrisli30 · 2021-10-06T18:31:06Z

@chrisli30 friendly reminder.

@alxs and @semuelle, sorry for the delay in submitting M2, but here is it!

https://github.com/w3f/Grant-Milestone-Delivery/pulls

We'd love to hear your feedback on it.

alxs · 2021-10-07T08:33:20Z

Thanks @chrisli30, we'll get back to you as soon as we can.

Quadratic Funding Module and Dapp Application (#2)

9da2b2e

* Added quardratic funding proposal * Finalized quadratic funding open grant proposal

chrisli30 added 2 commits February 22, 2021 00:44

Added web app wireframe link and description to project details

4000a8a

1. Added finalize function to M1 delivery

dc86c22

2. Adjusted BTC amount to make sure the total funding is within limit

Noc2 self-assigned this Feb 22, 2021

Noc2 requested changes Feb 22, 2021

View reviewed changes

Noc2 added the changes requested The team needs to clarify a few things first. label Feb 22, 2021

chrisli30 added 2 commits February 22, 2021 20:11

1. Move user study out of M2 to future plans due to tightness

d881efb

2. Fix the paragraph spacing of last commit

1. Added UI examples to team's experience section

59f7a6c

2. Update the cost denomination to DAI instead of BTC

Noc2 requested changes Feb 25, 2021

View reviewed changes

chrisli30 added 2 commits February 25, 2021 20:55

1. Changed BTC address to ERC20 DAI address

aa86451

2. Added Sybil resistance to future plans

Added identity module interaction requirement to M1 delivery

990d011

Noc2 previously approved these changes Feb 26, 2021

View reviewed changes

Noc2 added ready for review The project is ready to be reviewed by the committee members. and removed changes requested The team needs to clarify a few things first. labels Feb 26, 2021

BenWhiteJam previously approved these changes Mar 1, 2021

View reviewed changes

Added project and proposal concepts to UML chart

5506096

chrisli30 dismissed BenWhiteJam’s stale review via 5506096 March 2, 2021 07:09

chrisli30 dismissed Noc2’s stale review via 5506096 March 2, 2021 07:09

semuelle approved these changes Mar 2, 2021

View reviewed changes

semuelle requested review from BenWhiteJam and Noc2 March 2, 2021 07:29

Noc2 approved these changes Mar 2, 2021

View reviewed changes

BenWhiteJam approved these changes Mar 2, 2021

View reviewed changes

Noc2 merged commit d55a437 into w3f:master Mar 2, 2021

w3f deleted a comment from github-actions bot Mar 2, 2021

chrisli30 mentioned this pull request Oct 6, 2021

Quadratic Funding M2 Delivery from OAK Network w3f/Grant-Milestone-Delivery#284

Merged

5 tasks

alxs mentioned this pull request Oct 9, 2021

Updated applications/quadratic-funding to adjust the M2 cost to 0 DAI #635

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Quadratic Funding Module and Dapp Application #268

Quadratic Funding Module and Dapp Application #268

chrisli30 commented Feb 17, 2021 •

edited

Loading

chrisli30 commented Feb 17, 2021 •

edited

Loading

Swader commented Feb 17, 2021

chrisli30 commented Feb 17, 2021

semuelle commented Feb 20, 2021

chrisli30 commented Feb 22, 2021 •

edited

Loading

semuelle commented Feb 22, 2021

Noc2 left a comment

chrisli30 commented Feb 23, 2021

chrisli30 commented Feb 23, 2021 •

edited

Loading

chrisli30 commented Feb 25, 2021

Noc2 left a comment

chrisli30 commented Feb 26, 2021 •

edited

Loading

Noc2 left a comment

chrisli30 commented Feb 26, 2021

Swader commented Feb 27, 2021

semuelle commented Feb 27, 2021

chrisli30 commented Mar 2, 2021 •

edited

Loading

chrisli30 commented Mar 2, 2021

semuelle commented Mar 2, 2021

semuelle left a comment

chrisli30 commented Mar 2, 2021

Noc2 commented Mar 2, 2021

chrisli30 commented Mar 3, 2021

alxs commented Apr 15, 2021

chrisli30 commented Apr 19, 2021

semuelle commented Sep 16, 2021

chrisli30 commented Sep 16, 2021

alxs commented Oct 5, 2021

chrisli30 commented Oct 6, 2021

alxs commented Oct 7, 2021

Quadratic Funding Module and Dapp Application #268

Quadratic Funding Module and Dapp Application #268

Conversation

chrisli30 commented Feb 17, 2021 • edited Loading

Grant Application Checklist

chrisli30 commented Feb 17, 2021 • edited Loading

Swader commented Feb 17, 2021

chrisli30 commented Feb 17, 2021

semuelle commented Feb 20, 2021

chrisli30 commented Feb 22, 2021 • edited Loading

semuelle commented Feb 22, 2021

Noc2 left a comment

Choose a reason for hiding this comment

chrisli30 commented Feb 23, 2021

chrisli30 commented Feb 23, 2021 • edited Loading

chrisli30 commented Feb 25, 2021

Noc2 left a comment

Choose a reason for hiding this comment

chrisli30 commented Feb 26, 2021 • edited Loading

Noc2 left a comment

Choose a reason for hiding this comment

chrisli30 commented Feb 26, 2021

Swader commented Feb 27, 2021

semuelle commented Feb 27, 2021

chrisli30 commented Mar 2, 2021 • edited Loading

chrisli30 commented Mar 2, 2021

semuelle commented Mar 2, 2021

semuelle left a comment

Choose a reason for hiding this comment

chrisli30 commented Mar 2, 2021

Noc2 commented Mar 2, 2021

chrisli30 commented Mar 3, 2021

alxs commented Apr 15, 2021

chrisli30 commented Apr 19, 2021

semuelle commented Sep 16, 2021

chrisli30 commented Sep 16, 2021

alxs commented Oct 5, 2021

chrisli30 commented Oct 6, 2021

alxs commented Oct 7, 2021

chrisli30 commented Feb 17, 2021 •

edited

Loading

chrisli30 commented Feb 17, 2021 •

edited

Loading

chrisli30 commented Feb 22, 2021 •

edited

Loading

chrisli30 commented Feb 23, 2021 •

edited

Loading

chrisli30 commented Feb 26, 2021 •

edited

Loading

chrisli30 commented Mar 2, 2021 •

edited

Loading