Michael Müller
Michael Müller
Can be reproduced like this: ```bash $ cargo contract new foo Created contract foo $ ls foo $ ln -s foo link_to_foo $ ls foo link_to_foo $ cargo +nightly contract...
As a shortcut for e.g. `--skip-confirm --skip-dry-run`.
The `DuplicateContract` error currently looks like this: ```bash $ cargo contract instantiate --suri //Alice --constructor new -x … Result ModuleError: Contracts::DuplicateContract: ["A contract with the same AccountId already exists."] ```...
With https://github.com/paritytech/cargo-contract/pull/999 we changed default behavior of `cargo-contract` to dry-run by default. There's a leftover though: `--suri` is still marked as required, but it is no longer. ``` cargo contract...
We are using a hardcoded `type Balance = u128` here: https://github.com/paritytech/cargo-contract/blob/d3fa8956ccd7b03fdc8cd4f477d9e85b65b12650/crates/cargo-contract/src/cmd/extrinsics/mod.rs#L94 ## ToDo For sub-commands that use this `type Balance` in any way: - [ ] Check if the chain...
We should improve the error message when the contract message/constructor expects arguments, but no `--args` were provided (or the wrong ones, or too few). Currently when trying to naively instantiate...
## Motivation For proper cross-contract communication between ink! and Solang-compiled Solidity contracts we need the ability to generate a Solidity interface for a contract. ## ToDo As part of this...
This has confused people during workshops: ``` cargo contract instantiate --manifest-path=flipper/Cargo.toml --suri //Alice --skip-confirm --args true --salt 1 error: invalid value '1' for '--salt ': Odd number of digits ```...
## Motivation For proper cross-contract communication between ink! and Solang-compiled Solidity contracts we need the ability to generate an ink! interface for a contract. ## ToDo As part of this...