Same as [Self::instantiate_with_code], but intended to be dispatched only
by an EVM transaction through the EVM compatibility layer.
Parameters
value: The balance to transfer from the origin to the newly created contract.
weight_limit: The gas limit used to derive the transaction weight for transaction
payment
eth_gas_limit: The Ethereum gas limit governing the resource usage of the execution
code: The contract code to deploy in raw bytes.
data: The input data to pass to the contract constructor.
transaction_encoded: The RLP encoding of the signed Ethereum transaction,
represented as [crate::evm::TransactionSigned], provided by the Ethereum wallet. This
is used for building the Ethereum transaction root.
effective_gas_price: the price of a unit of gas
encoded len: the byte code size of the eth_transact extrinsic
Calling this dispatchable ensures that the origin's nonce is bumped only once,
via the CheckNonce transaction extension. In contrast, [Self::instantiate_with_code]
also bumps the nonce after contract instantiation, since it may be invoked multiple
times within a batch call transaction.
Same as [
Self::instantiate_with_code], but intended to be dispatched only by an EVM transaction through the EVM compatibility layer.Parameters
value: The balance to transfer from theoriginto the newly created contract.weight_limit: The gas limit used to derive the transaction weight for transaction paymenteth_gas_limit: The Ethereum gas limit governing the resource usage of the executioncode: The contract code to deploy in raw bytes.data: The input data to pass to the contract constructor.transaction_encoded: The RLP encoding of the signed Ethereum transaction, represented as [crate::evm::TransactionSigned], provided by the Ethereum wallet. This is used for building the Ethereum transaction root.eth_transactextrinsicCalling this dispatchable ensures that the origin's nonce is bumped only once, via the
CheckNoncetransaction extension. In contrast, [Self::instantiate_with_code] also bumps the nonce after contract instantiation, since it may be invoked multiple times within a batch call transaction.