Sebastian Miasojed
Sebastian Miasojed
> WIll this also be a tagged github release? Correct me if I'm wrong, but all the changes we need for ink5 are in the 1.9.0 release. So, we could...
@cmichi @ascjones, please advise if we need two releases: one aligned with polkadot-release 1.9.0 (fully compatible with ink 5.0.0 and we publish crates), and a second one with this commit,...
I think it would make sense to add to the release notes information about compatibility between `Ink`, `rustc`, `pallet_contracts`, and `cargo-contract`. WDYT?
> * cargo-contract: `>=4.0.0-rc.3` I think cargo-contract: >=4.0.0-rc.3, >=5.0.0
My mistake, it should be >=4.0.0-rc.3, >=4.0.0 I remember that in semantic versioning, pre-release version ranges like `>=4.0.0-rc.3` do not match stable release versions like `4.0.0`. I think that to...
> Could you describe the criteria to decide which contracts are `public` and which ones are `internal`? Internal contracts for CI should be created solely for testing purposes and should...
bot bench substrate-pallet --pallet=pallet_contracts
bot bench substrate-pallet --pallet=pallet_contracts
bot cancel 5-a1be7227-1f82-4a82-9891-dfc753222de3
@athei I assumed that `chain_extension` calls the API over the `Ext` trait, so read-only protection in the `Ext` implementation is good enough, please comment Another option is to extend `Ext`...