The Clover EVM should provide the same interface for balance transfer and query.
The balance transfer should run correctly and related balance updated.
Test cases can be viewed here: https://github.com/clover-network/clover-sdk/blob/main/tests/test-balance.ts
The Clover EVM can return correct genesis block.
Clover EVM can support query block by number or hash.
The returned block should contain transactions and correct transaction root.
The newly generated block should has valid timestamp and includes previous block as parent
Test cases can be viewed here: https://github.com/clover-network/clover-sdk/blob/main/tests/test-block.ts
The transaction receipt should contains correct bloom data
Test cases can be viewed here: https://github.com/clover-network/clover-sdk/blob/main/tests/test-bloom.ts
Smart contract can be correctly created by Clover EVM.
Smart contract creation can return transaction hash.
Test cases can be viewed here: https://github.com/clover-network/clover-sdk/blob/main/tests/test-contract.ts
Clover EVM should support the invoke of smart contract call.
The smart contract call should return expected result.
The smart contract call should fail in case of invalid parameters.
Test cases can be viewed here: https://github.com/clover-network/clover-sdk/blob/main/tests/test-contract-methods.ts
Clover EVM should support estimation of gas fee.
The gas limit should decrease on next block if gas unused.
The estimated gas should be correct for smart contract creation or method call.
Test cases can be viewed here: https://github.com/clover-network/clover-sdk/blob/main/tests/test-gas.ts
Clover EVM should support correct nonce query.
Clover EVM should return the revert reason in case of failure.
Clover EVM should return a valid transaction receipt for a successful or failed transaction.
Test cases can be viewed here: https://github.com/clover-network/clover-sdk/tree/main/tests
In order to test the full functionality of Clover EVM, we provide a script which can automatically deploy Uniswap on Clover for one-shot.
It can deploy Uniswap ERC20 token to Clover
It can deploy Uniswap V2 Factory smart contract to Clover
It can deploy WETH ERC20 token to Clover
It can deploy Uniswap V2 Router smart contract to Clover
It can deploy Multicall smart contract to Clover
Please find the cool script here: https://github.com/clover-network/clover-sdk/blob/main/tests/e2e-tests/test/test-uniswap.js
Clover EVM is based on Frontier, we find that the gas fee estimation under some cases may fail, such as nested smart contract call. Clover provides a binary search based solution to solve the problem. Please find the details here:
After the fix, Clover EVM can support all kinds of gas estimation correctly, please find the test case here: https://github.com/clover-network/clover-sdk/blob/main/tests/inner-contract-tests/test/test-inner-contract.js
Clover has a powerful dual-chain architecture, which will empower its users to build their decentralized apps and digital assets on one blockchain (Clover EVM powered) and take advantage of Polkadot chain on the other. Thus Clover account binding is very import, which make users able to do all the staffs under one unified account. Also the bound accounts can share the same balance, as well as the integration of the cool features on the dual-chain.
The related test cases can be found here: https://github.com/clover-network/clover-sdk/blob/main/tests/account-bind-tests/test-account-bind.js
In order to test the performance of Clover chain, test cases have been carried out both on EVM and Clover Parachain.
The EVM TPS tests can be found at: https://github.com/clover-network/clover-sdk/blob/main/tests/tps-tests/test-web3-tps.js
The Clover Parachain tests can be found at: https://github.com/clover-network/clover-sdk/blob/main/tests/tps-tests/test-polkadot-tps.js