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

EdgeSnap grant proposal #2209

Closed
wants to merge 3 commits into from
Closed

Conversation

ShankarWarang
Copy link

@ShankarWarang ShankarWarang commented Feb 7, 2024

Project Abstract

Please replace these instructions with a brief description of your project summarising key points (1-2 paragraphs).

If your application is a follow-up to a previous grant, please mention which one in the first line of the abstract and include a link to previous pull requests if applicable.

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.
  • Payment details have been provided (bank details via email or Polkadot (USDC & USDT) address in the application).
  • I am aware that, in order to receive a grant, I (and the entity I represent) have to successfully complete a KYC/KYB check.
  • 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: @shankarwarang:matrix.org (change the homeserver if you use a different one)

@github-actions github-actions bot added the admin-review This application requires a review from an admin. label Feb 7, 2024
Copy link
Contributor

github-actions bot commented Feb 7, 2024

CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅

@ShankarWarang
Copy link
Author

I have read and hereby sign the Contributor License Agreement.

Raj-RR1

This comment was marked as outdated.

@takahser takahser self-assigned this Feb 8, 2024
@takahser takahser self-requested a review February 8, 2024 06:21
Copy link
Collaborator

@takahser takahser left a comment

Choose a reason for hiding this comment

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

@ShankarWarang thanks for the submission of your proposal.
I have some initial inquiries:

Copy link
Member

@PieWol PieWol left a comment

Choose a reason for hiding this comment

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

I left some comments, please adjust the application accordingly.

applications/EdgeSnap.md Show resolved Hide resolved
applications/EdgeSnap.md Outdated Show resolved Hide resolved
applications/EdgeSnap.md Show resolved Hide resolved
@PieWol PieWol added the changes requested The team needs to clarify a few things first. label Feb 8, 2024
@PieWol PieWol self-assigned this Feb 8, 2024
Copy link
Member

@semuelle semuelle 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. Two comments:

@ShankarWarang
Copy link
Author

  1. Thanks for the feedback @takahser. We have updated the proposal as per the suggestion.
  2. Currently the Polkadot Snap by ChainSafe only supports Polkadot, Kusama and Westend. Also, EdgeSnap is not just about developing snap apps for substrate chains. We are building an App Store for Substrate Snaps. Also, the major proposition here is the whole service rather than just the product. We want to accelerate the snap-readiness in the Polkadot ecosystem dApps.
  3. Those repos that we've linked currently do not exist as of now and we will be storing the custom npm packages in them. At the moment, we are using the EdgeSnap repo as the mono repo.

@ShankarWarang
Copy link
Author

Thanks for the application. Two comments:

  • Noted and made the changes accordingly.
  • Yes. However, we will be also including the solochains along with the parachains and relaychains (which are aligned with the Polkadot's vision, i.e. only those solochains which are available on Polkadot-JS/Apps). EdgeSnap is more of a service than just a project for the development of substrate snap apps and the brand new Substrate Snap Store. We started building on top of what ChainSafe built. ChainSafe is the core developing entity for bringing the Snap to Substrate in the first place. While we are aiming to become the accelerator for snap-readiness.

@PieWol
Copy link
Member

PieWol commented Feb 12, 2024

Hey @ShankarWarang , I want to follow up on this reply

  1. Currently the [Polkadot Snap by ChainSafe]
    (https://snaps.metamask.io/snap/npm/chainsafe/polkadot-snap/) only supports Polkadot, Kusama and Westend. Also, EdgeSnap is not just about developing snap apps for substrate chains. We are building an App Store for Substrate Snaps. Also, the major proposition here is the whole service rather than just the product. We want to accelerate the snap-readiness in the Polkadot ecosystem dApps.

The official metamask snap store is already such a store you envision with a lot of snaps available and a polished ux. What do you think will be the benefit of building another snap store? I suggest getting directly in touch with Chainsafe to see if you can simply work together on this project as it would be a pity to have two teams built on the same open source software with the same framework at the same time and most likely produce duplicates.

On another note: Having a milestone overly expensive to then argue that a non-paid service time will follow is nothing else but upfront payment. Please adjust your milestones so that you first deliver the service or software and upon delivery you will be paid. We can't hold anybody liable in case they completed all milestones and got paid but then don't (for any reason) deliver on further free promises that might have influenced the foundation to accept a grant in the first place.

If you really want to do something like this I would suggest to first write an application for the milestones you have, reduce the cost, and in case this project is a great success with lots of interest by ecosystem teams you can still apply for a maintenance grant. I think this makes it easier for all of us as there is no way to guess the maintenance and advisory workload that might occur in that timeframe.

Sadly the foundation doesn't fund market outreach, feedback collection, marketing or any community events that you are planning in the scope of this grant. Please see here: What activities/positions do you fund?

I'm looking forward to hearing back from you and hope that you will be able to reach out to Chainsafe.

@ShankarWarang
Copy link
Author

ShankarWarang commented Feb 12, 2024

@PieWol Thanks for the follow-up.

The official metamask snap store is not really what we envisioned. It only has two snaps from the whole substrate ecosystem! There could be entry barriers financially and reputation-wise. Building something substrate-native will massively benefit small/new parachains and solochains. The vercel preview (MVP) is for showcasing the functionalities. UI/UX improvements are part of the milestone 1.

ChainSafe proposed SubstrateSnap maintenance almost a year ago and it's partially delivered. Also, parachains/solochains support is not included in their grant.

Snap Store is just one component of the EdgeSnap along with the Interactive UI, combined with the service which includes the development of snap apps for all the substrate chains and periodic snap integrations on Polkadot/substrate ecosystem dApps.

We are happy to remove the mention of non-paid service (maintenance for 9 months) from the proposal to avoid the influence bias. The current milestones' costs are not influenced by the free 9-month maintenance period.

The per-chain integration costs here are substantially less than the industry average. The average total cost involved per chain for EdgeSnap considering all the milestones will be 1165.0485 USD and the average integration cost per chain (considering milestones 2 & 3) will be 728.1553 USD.

@semuelle
Copy link
Member

There could be entry barriers financially and reputation-wise.

IIRC, an audit is required for any snap to be listed in the Snap store.

ChainSafe proposed SubstrateSnap almost a year ago and it's not yet available. Also, parachains/solochains support is not included in their grant.

This grant was completed and the result was the initial version of https://github.com/ChainSafe/metamask-snap-polkadot.

Given the size of the undertaking and this grant and the relative novelty of the project, I would recommend that you apply with the Decentralized Futures Program instead.

@ShankarWarang
Copy link
Author

@semuelle

IIRC, an audit is required for any snap to be listed in the Snap store.

Thanks for highlighting that.

This grant was completed and the result was the initial version of https://github.com/ChainSafe/metamask-snap-polkadot.

I meant to imply that PolkadotApps/dotapps do not support the snap yet and the inclusion of parachains is not stated anywhere.

Given the size of the undertaking and this grant and the relative novelty of the project, I would recommend that you apply with the Decentralized Futures Program instead.

Does the Decentralized Futures Program process the applications on a rolling basis?

@PieWol
Copy link
Member

PieWol commented Feb 13, 2024

@ShankarWarang it's stated on the website of the decentralized futures program, that applications are open until june 2024. So you would have a good amount of time left to apply. It's also stated that applications are reviewed on a rolling basis, yes.

@PieWol PieWol removed the changes requested The team needs to clarify a few things first. label Feb 15, 2024
@keeganquigley
Copy link
Contributor

Thanks for your thorough answers @ShankarWarang and for the deep dive @PieWol I have to also concur that this would be a better fit for the DF program, since many of the deliverables cover parts of the development cycle we can't fund, and since the MVP has already been developed. For example, we can't fund feedback & analysis, weekly dev cohorts, etc. Let us know if this sounds good to you or if you'd rather refactor this application with a reduced scope/cost.

@ShankarWarang
Copy link
Author

Thanks for your thorough answers @ShankarWarang and for the deep dive @PieWol I have to also concur that this would be a better fit for the DF program, since many of the deliverables cover parts of the development cycle we can't fund, and since the MVP has already been developed. For example, we can't fund feedback & analysis, weekly dev cohorts, etc. Let us know if this sounds good to you or if you'd rather refactor this application with a reduced scope/cost.

Happy to apply for the DF program. Thanks again for the feedbacks @PieWol @semuelle @takahser @keeganquigley

@keeganquigley
Copy link
Contributor

Sounds good @ShankarWarang thanks for confirming with us. I will go ahead and close this, let us know if you have further questions.

@Polkadot-Forum
Copy link

This pull request has been mentioned on Polkadot Forum. There might be relevant details there:

https://forum.polkadot.network/t/edgesnap-substrate-snap-readiness-accelerator/6326/1

@ShankarWarang
Copy link
Author

We applied for the decentralised futures grant and also received a response from David Hawig. We replied to him using the edgeware.community custom domain email. As David might not have received any email from that domain before and as it also had embedded links, we suspect that email might have ended up in the spam box.
Can anyone please relay this to David if possible? @takahser @PieWol @semuelle @keeganquigley
Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
admin-review This application requires a review from an admin.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants