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

Meta Defender Proposal #1089

Merged
merged 3 commits into from
Aug 15, 2022
Merged

Meta Defender Proposal #1089

merged 3 commits into from
Aug 15, 2022

Conversation

327istesting
Copy link
Contributor

Project Abstract

Meta Defender is a leading provider of DeFi insurance, which provides a transparent, trustworthy, and convenient decentralized mechanism without intermediaries in insurance trading. Inspired by AMM pool, Meta Defender also has a pool in insurance trading. Also, the fee of insurance is driven by the market. Like most of the DeFi protocols, we run it a DAO system, which means, the whitelist of covered protocols(such as DeFi protocols or public chain security) is decided by all the token hodlers.

For which grant level are you applying?

  • 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, renamed ( project_name.md) and updated.
  • I have read and understood the FAQs, application guidelines and announcement guidelines.
  • A BTC, Ethereum (USDT/USDC/DAI) or Polkadot/Kusama (aUSD) address for the payment of the milestones is provided inside the application.
  • I have read and acknowledge the terms and conditions.
  • 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.
  • I prefer the discussion of this application to be in a private Element/Matrix channel. My username is: @_______

How Did You Hear About our grants program?

  • Social Media
  • Hackathon
  • Personal Recommendation
  • Substrate Builders Program
  • Investor/VC
  • Online Search
  • Other: _______

@CLAassistant
Copy link

CLAassistant commented Jul 27, 2022

CLA assistant check
All committers have signed the CLA.

Copy link
Collaborator

@Noc2 Noc2 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the application. Looks really interesting. However, this application seems to focus mostly on Acala/Karura, I therefore suggest to apply here: https://acala.network/ecosystem-program Especially, since we usually don’t support solidity smart contracts and mostly focus on ink! and substrate. Let me know, in case you want to develop an ink! version or pallet instead.

@Noc2 Noc2 added the changes requested The team needs to clarify a few things first. label Jul 27, 2022
@Noc2 Noc2 self-assigned this Jul 27, 2022
@327istesting
Copy link
Contributor Author

Thanks for the application. Looks really interesting. However, this application seems to focus mostly on Acala/Karura, I therefore suggest to apply here: https://acala.network/ecosystem-program Especially, since we usually don’t support solidity smart contracts and mostly focus on ink! and substrate. Let me know, in case you want to develop an ink! version or pallet instead.

@Noc2 Hi David, thanks for your prompt reply. After discussing with our team, we would like to change this proposal to mainly focus on the development of an ink! smart contract and to target the Polkadot ecosystem as a whole. I will update the application and let you know.

@327istesting
Copy link
Contributor Author

Hi @Noc2 , the revised version has been submitted. Thanks.

Copy link
Collaborator

@Noc2 Noc2 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks a lot for the update and sorry for the late response. I’m generally happy to go ahead with it, but could specify the deliverables of the milestone a little bit more detailed? For example, are you planning to implement “Buy Cover” and “Underwriting” as part of an ink! smart contract? Feel free to mention this as part of the specification. Also feel free to remove the part regarding the deployment on a parachain completely from the deliveries. The source code and a local testnet is fine for us and the deployment on a parachain might depend on other things that are out of your hands.

@327istesting
Copy link
Contributor Author

Hey @Noc2, sorry for the delay, I have updated the proposal accordingly, please let me know if any question.

@Noc2
Copy link
Collaborator

Noc2 commented Aug 15, 2022

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

@Noc2 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 Aug 15, 2022
@Noc2 Noc2 merged commit 3187675 into w3f:master Aug 15, 2022
@github-actions
Copy link
Contributor

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! 🚀

@keeganquigley
Copy link
Contributor

Hi @327istesting any chance you can give us an update on the progress of M1?

@327istesting
Copy link
Contributor Author

Hey @keeganquigley,

We managed to complete ink-contract and it looks good from contract-UI, however we stuck at ink-e2e testing. We encountered some issues and asked in stack exchange as well as directly to some devs in ink! developer team but unfortunately, we haven't received any reply. We still don't know whether it's because ink-e2e doesn't provide full support or we didn't deal with it in the right way. We are continuing working on it, otherwise I think we could provide a doc listing the steps of waterfall testing.

Also, we would like to move the second part of the first milestone (Manual of interaction between ink! and front-end) to second milestone because of the issue which is related to Weights V2 support in polkadot.js. It seems that it cannot be resolved in the near future, so we couldn't finish that part in the first milestone.

I will open a PR to reflect above issues after discussing with my team members. Cheers.

@327istesting
Copy link
Contributor Author

Hi @keeganquigley , the ink4 framework itself is unstable right now and we encountered some problems which seems cannot be fixed soon. The team is also committed to other jobs and won't have time to work on it in the near future, so we would like to terminate this one.

@Noc2 Noc2 mentioned this pull request Mar 27, 2023
@Noc2
Copy link
Collaborator

Noc2 commented Mar 27, 2023

@327istesting Thanks for the update. I just created the PR to terminate the grant: #1639. Feel free to reapply once you have the time to work on this.

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.

5 participants