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

add frontier-pos-template #2391

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

add frontier-pos-template #2391

wants to merge 1 commit into from

Conversation

weimeme
Copy link

@weimeme weimeme commented Sep 10, 2024

Project Abstract

This is a development template based on Polkadot's NPOS consensus, compatible with EVM.
It aims to enable new developers or teams in the Polkadot ecosystem to quickly create EVM-compatible chains based on NPOS consensus.

reopen #2342

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 (Polkadot AssetHub (DOT, USDC & USDT) address in the application and bank details via email, if applicable).
  • I understand that an agreed upon percentage of each milestone will be paid in vested DOT, to the Polkadot address listed 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: @_______: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 Sep 10, 2024
Copy link
Contributor

CLA Assistant Lite bot: Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. Please submit the following text as a separate comment:


I have read and hereby sign the Contributor License Agreement.


You can retrigger this bot by commenting recheck in this Pull Request

@weimeme
Copy link
Author

weimeme commented Sep 10, 2024

I have read and hereby sign the Contributor License Agreement.

I have read and hereby sign the Contributor License Agreement.

@weimeme weimeme mentioned this pull request Sep 10, 2024
11 tasks
@weimeme weimeme force-pushed the master branch 2 times, most recently from f352611 to c79ce04 Compare September 11, 2024 09:32
@keeganquigley
Copy link
Contributor

Thanks for the application @weimeme and I'm happy to see that you have identified a common pain point for developers. My question is, how do you plan to fund & maintain this project after this grant? What are your plans for gaining traction with devs and marketing this product in a way that it can gain some real adoption?

@keeganquigley keeganquigley added the changes requested The team needs to clarify a few things first. label Sep 23, 2024
@weimeme
Copy link
Author

weimeme commented Sep 24, 2024

Thanks for the application @weimeme and I'm happy to see that you have identified a common pain point for developers. My question is, how do you plan to fund & maintain this project after this grant? What are your plans for gaining traction with devs and marketing this product in a way that it can gain some real adoption?

@keeganquigley Thank you very much for recognizing our ideas. In fact, committing to continuous maintenance without any financial return is a very difficult thing, unless it's a scam. However, we have currently found at least three cooperative teams. In the area of public chain development, we provide them with long-term technical support. Before their technology upgrades, what we must do is update this public template for testing. This is very necessary as it relates to our long-term cooperation with them and how many teams we can find for commercial cooperation in the future. Currently, the Dota community has also found us and hopes to use this template to create their own chain within a month. We will also receive their treasury rewards in such community development. SuperEX is a very professional and well-funded CEX team. They highly recognize the high TPS and high decentralization concept of the Polkadot chain (which is why they use Polkadot technology). It is very easy to obtain maintenance funds from them. For this template, multi-team cooperation is the driving force to ensure its continuous maintenance, and we have just solved this problem. Moreover, we will tend to apply for continuous maintenance funds for this template from these teams. The cost is not high, and they will be very willing to do so. Who would refuse to use the latest Polkadot technology, especially with Polkadot 2.0 coming soon?

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. changes requested The team needs to clarify a few things first.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants