-
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
Update openbrush-follow-up-2.md #1237
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 update. Could @xgreenx and @TtomaS7 confirm here that they are fine with these changes? They are the two contributors of the initial PR, see https://github.com/w3f/Grants-Program/blob/master/applications/openbrush-follow-up-2.md.
hello! |
And I confirm!=) |
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.
Perfect. Thanks. I will mark the amendment as ready for review and approve it myself.
Project Abstract
This is an update of an already approved grant.
Supercolony as you know it will cease to exist in a few weeks.
The sleeping partner that Markian started Supercolony with no longer shares the vision and mission of our company. Mainly because of a different values mindset. The best option is to separate at this point.
and we would like to continue infrastructure development and enhancing Polkadot with a new identity now - 727.ventures.
Many developers are asking for the feature to test cross-contract calls in unit tests because it is hard to mock it each time and makes the testing much harder, forcing people to write integration tests with Redspot, Swanky, and Typechain-Polkadot.
We want to prioritize this task and deliver the trait refactoring in ink! later(Initially, we plan to implement an advanced testing framework in milestone eight it is why we can swap those tasks). Because it is a hot topic and after discussion in the issue and element channel, it is clear how it should be implemented=)
The scope of work is the same and also related to the ink! repository. Because it requires modification of the off-chain environment.
Grant level
#921