[meta] solidity devs migration: essential

[extraymond]

Info

description:
For people migrating from eth-like ecosystem, the differences around building on laguna is mostly stemming from the contract environment we use, namely pallet-contracts in combination with solang. It's vital for developers to have at least stable and fixed environment and tooling to interact with the chain reliably. We'll start covering use cases for standard features that's essential.

expected results:

• working frontend to correctly deploy/read/write to the contract they use
• tools on ABI parsing/validation to make sure the contract in in good state to be submitted on chain
• deploy system libraries at fixed addresses that are not colliding with other accounts
• calling system libraries which allow them to integrate with runtime features
• cli tool for deploy/read/write the contract that supports encoding/decoding types using the ABI file
• self manageable contract with migration/updating working
• example tests and demos for solidity developers
• feature parity checks for features not supported by solang yet

estimated experience:

• able to use our cli to produce smart contract that is ABI compatible with ink
• able to deploy/read/write smart contract using the cli
• able to deploy/read/write smart contract using parity-contracts-ui

effected scope:

• runtime
• tests
• tooling
• frontend

todos:

• [feature] read/write/deploy contracts from its ABI file laguna-cli#1
• [feature] ABI validation conversion #30
• [feature] predeploy contract #16
• [testing] contract migration #31
• [testing] cover more cases for integration tests #32
• [docs] feature parity check for solidity on solang #33