-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Create proposal for bison #2427
Conversation
There was a problem hiding this 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, @philoniare. This looks interesting, happy to support it.
@philoniare thanks for the proposal, this indeed is very interesting for me as well. I would, however, ask you to instead of forking Foundry making this proposal about contributing upstream directly to Foundry so that they support natively Polkadot. This way we ensure that current Solidity Developers don't have to go hunting for another tool, but rather use the development flow that they are familiar with today. At the same time, I would also encourage you to make sure Polkadot Asset Hub is a target usable within Foundry. The community has already approved the development of EVM on AH, and it will be very important to ensure the success of it that all the tools people are used to using on EVM land are compatible on AH as well. Foundry, particularly, is a very important tool. |
@SBalaguer Thank you for the insightful feedback. I agree that integrating Polkadot support directly into Foundry would be the ideal long-term goal. However, for this initial iteration, I believe that building an independent tool first would be more practical for a few reasons. The first issue is the complexity of adding Polkadot and JAM support into Foundry. Polkadot’s non-EVM PolkaVM environment introduces a different dependency tree, particularly with tools like Furthermore, I’d prefer to ensure the project’s success and stability first before pushing for upstream changes in Foundry. We want to showcase solid community support, proven use cases, and a stable toolset before proposing to merge into Foundry. This way, we can approach the Foundry community with a tested, working solution that has clear benefits and a demand from developers already using Polkadot and JAM protocols. I still believe there will be an opportunity to merge into Foundry at a later stage, but for now, focusing on delivering a standalone, optimized tool that fits the Polkadot ecosystem is a more achievable and valuable first step. Thanks again for your input, and I look forward to continuing the discussion as the project evolves. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the thorough answer @philoniare based on your previous work I'm also willing to approve.
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. |
Project Abstract
A streamlined developer tool for Solidity smart contract deployment and testing on Polkadot.
Grant level
Application Checklist
project_name.md
).@_______:matrix.org
(change the homeserver if you use a different one)