add frontier-pos-template #2342
Conversation
github-actions
bot
added
the
admin-review
|
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 |
I have read and hereby sign the Contributor License Agreement. |
|
|
||
| - **Team Name:** ChainSupport | ||
| - **Payment Details:** | ||
| - **Payment**: 0xcC1974d462B9F22F37D09c70F6023Ef9167EB3De (USDC) |
There was a problem hiding this comment.
We need a Polkadot and AssetHub address. Payments on Ethereum are not offered anymore.
| ## Development Status :open_book: | ||
|
|
||
| ### project | ||
| https://github.com/ChainSupport/frontier-pos-template |
There was a problem hiding this comment.
Can you elaborate what the status is?
| > Because our entire team of developers typically serves different public chain development teams, | ||
| > there is a requirement for a certain level of anonymity for our past GitHub accounts. If you need to know which specific projects we participated in, feel free to message me privately. |
There was a problem hiding this comment.
Can you please send us proof of your previous open source work to [email protected]?
| > It will drive community discussions on further optimizing the public chain development process, allowing the community to collaboratively enhance the development experience at the application layer. | ||
| > The work involved could easily cost much more than this $4,000. We simply hope that it doesn't waste too much money before being widely adopted. In short, this initiative is worth pursuing. | ||
|
|
||
| ### Milestone 1 Example — Basic functionality |
There was a problem hiding this comment.
This is template text, please adapt it to your project.
| | **0b.** | Documentation | We will provide a documentation tutorial for creating an EVM template based on NPOS consensus from scratch, for the community's reference. This will help future developers maintain the project and facilitate community code review. | | ||
| | **0c.** | Testing and Testing Guide | Core functions will be fully covered by comprehensive unit tests to ensure functionality and robustness. In the guide, we will describe how to run these tests. See the [delivery guidelines](https://grants.web3.foundation/docs/Support%20Docs/milestone-deliverables-guidelines#testing-guide) for details. | | ||
| | **0d.** | Docker | We will provide a Dockerfile(s) that can be used to test all the functionality delivered with this milestone. | | ||
| | 0e. | Article | We will publish an **article** that explains [...] (what was done/achieved as part of the grant). (Content, language, and medium should reflect your target audience described above.) | |
There was a problem hiding this comment.
This is template text, please adapt it to your project.
| | 1. | Client | An NPOS consensus and EVM-compatible client. | | ||
| | 2. | runtime | An NPOS consensus and EVM-compatible runtime. | | | ||
| | 3. | Substrate chain | An EVM-compatible chain with NPOS consensus. | | ||
| | 4. | Friendly code structure | A developer-friendly code structure, similar to the one found in https://github.com/substrate-developer-hub/substrate-node-template.git. | |
There was a problem hiding this comment.
This does not sound like a deliverable, but a feature of a deliverable. I suggest to remove it or make it part of one of the other deliverables.
There was a problem hiding this comment.
This does not sound like a deliverable, but a feature of a deliverable. I suggest to remove it or make it part of one of the other deliverables.
The deliverable is a fully functional solo chain with NPOS and EVM compatibility.
|
|
||
| - Are there any other projects similar to yours in the Substrate / Polkadot / Kusama ecosystem? If so, how is your project different? Please identify and assess any projects addressing the same need and explain how your project is distinct. Feel free to include applicable research data, statistics, or metrics. | ||
| https://github.com/substrate-developer-hub/substrate-node-template， No EVM compatibility and no NPOS. | ||
| https://github.com/substrate-developer-hub/frontier-node-template, No NPOS and the code structure is not developer-friendly. |
There was a problem hiding this comment.
Can you explain how you want to improve the code structure to make it more developer-friendly?
There was a problem hiding this comment.
Can you explain how you want to improve the code structure to make it more developer-friendly?
We hope that the code structure of this template, which is compatible with NPOS and EVM, can be similar to https://github.com/paritytech/polkadot-sdk/tree/master/templates/solochain. It should include Docker and some common scripts to assist in development. The testnet and mainnet should each have their own runtime and client, allowing any team to quickly launch their testnet and mainnet without having to write any code from scratch.
semuelle
added
the
changes requested
|
pinging @weimeme |
I apologize for the delayed response. We've been researching and coding recently. It turns out that creating such a template indeed requires a lot of effort and time from each development team, and it even necessitates highly experienced Substrate developers to accomplish it. I will review the application in the next few days and then update it. |
|
Hi @weimeme just a friendly ping for an update :) |
@semuelle @keeganquigley @Noc2 @PieWol We apologize for the delay in responding. We have been busy developing the client for this project and communicating with more potential teams to understand their difficulties and needs. Currently, four teams are seeking our support to use Polkadot and Ethereum technologies to create their own solo chains. They are also following the progress of Polkadot 2.0, but their Substrate developers lack the experience to implement a solo chain that is compatible with both NPOS and EVM in a short time. We believe that supporting them while open-sourcing this technology and related discussions is very meaningful and significant for the large-scale adoption of Substrate technology. Moreover, achieving full EVM compatibility requires more work. We found that in Blockscout, the transfer records of the balances module are still not displayed, which requires someone to try, identify, and solve the problems. We are very eager to receive initial support from W3F to explore this technology. At the same time, we are already promoting this technical solution to other teams, which will ensure continuous funding to maintain such a project in the future. I suggest we reopen this PR and discuss it further. |
|
The new grant application has been updated. |
|
This is the recent development work we did for SuperEx: https://github.com/weimeme/scs-chain. The client that is compatible with both NPOS and EVM still requires us to do a lot of detailed development work, which has taken us a lot of time. We do not want other teams with similar needs to repeat this work in the future, as it is meaningless and unreasonable. |
|
Thanks for the updates here. However, I'm unable to reopen the PR since the master was force-pushed. Could you create a new PR? |
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.
Grant level
Application Checklist
project_name.md).@_______:matrix.org(change the homeserver if you use a different one)