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

ink! 4.0 #1343

Closed
cmichi opened this issue Jul 28, 2022 · 8 comments
Closed

ink! 4.0 #1343

cmichi opened this issue Jul 28, 2022 · 8 comments
Labels
A-eDSL Concerning the Rust eDSL as a total. A-repo Task or issue concerning the GitHub repository.

Comments

@cmichi
Copy link
Collaborator

cmichi commented Jul 28, 2022

The Vision

With the next major release of ink! we strive to:

  • implement all remaining breaking changes from our endeavor of reducing contract sizes (how the storage API works).
  • Introduce a new metadata format to account for some of our current shortcomings (e.g. versioning).
  • make ink! closer to the idiomatic way of Rust (by reverting transactions on Err returns from constructors).
  • create tooling for testing cross-contract calls and testing against a custom runtime.
  • improve the developer experience by bundling all ink! crates into one ink entrance crate.
  • allow different contracts to reference and use the same event types.

We moved this point to 4.1:

  • include first support for XCM and XCM testing.

The Plan

We're already in the middle of this. See the linked view.

Open Questions

If you want to help us out and contribute to this issue, in this section you can find open questions and tasks where we would appreciate any input.

Currently we don't have open questions.


Here you can find the board with specific sub-tasks to this milestone:
https://github.com/orgs/paritytech/projects/29/views/6

@forgetso
Copy link
Contributor

forgetso commented Aug 3, 2022

Hi, can't wait to see cross contract testing. Where has the board for ink v4 gone? This link 404s https://github.com/orgs/paritytech/projects/30/views/2

@cmichi
Copy link
Collaborator Author

cmichi commented Aug 4, 2022

@forgetso It should all be on here: https://github.com/paritytech/ink/projects/8, the other one was an experiment which only existed for a short amount of time. I'm surprised that you even noticed it!

@cmichi
Copy link
Collaborator Author

cmichi commented Aug 5, 2022

Ah I get it now, the link to the board was in the GitHub description of this issue, I've updated it.

Hi, can't wait to see cross contract testing.

Yes, me too! How are you doing it right now? redspot + scripting?

@kvinwang
Copy link
Contributor

kvinwang commented Aug 8, 2022

Would the pallet-contracts running ink! 4.0 contracts can also run ink! 3.0 contracts?

@forgetso
Copy link
Contributor

Thanks for the link!

Yes, me too! How are you doing it right now? redspot + scripting?

We are not currently testing cross contract calls although we would have used redspot, yes.

@ascjones ascjones mentioned this issue Nov 7, 2022
8 tasks
@stillonearth
Copy link

stillonearth commented Nov 8, 2022

So cross-contact calls testing is scheduled for 4.0? Should one wait for it (if it's fairly close) or go with redspot?

@HCastano
Copy link
Contributor

@stillonearth yes it's already working (albeit with some rough edges). For example, take a look at the contracts in lang-err-integration-tests for some examples on how to use it

@HCastano HCastano added A-eDSL Concerning the Rust eDSL as a total. A-repo Task or issue concerning the GitHub repository. labels Dec 11, 2022
@HCastano
Copy link
Contributor

Closed via #1653 :shipit:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-eDSL Concerning the Rust eDSL as a total. A-repo Task or issue concerning the GitHub repository.
Projects
None yet
Development

No branches or pull requests

5 participants