Part 2: Development Environment Tools and How to Use MetaMask to Manage Keys
Last Week, Ontology announced the official deployment of a TestNet supporting EVM and opened the EVM compatible public beta to developers around the world. At the same time, the “Ontology Security Vulnerability and Threat Intelligence Bounty Programme” was officially launched in cooperation with SlowMist, a well-known code auditing agency. The top reward for reporting a vulnerability is $12,000 in ONG.
In order to encourage community developers to quickly and easily familiarize themselves with the Ontology EVM development environment, we specially prepared a “Handbook for Dummies”, which explains the essentials of Ontology EVM contract development.
In Part 1, we introduced the ChainID, RPC URL, browser address and other configuration information related to the Ontology EVM. Developers can configure MetaMask wallets to the Ontology network based on the above information. In this section, we introduce the tools for developing and deploying EVM contracts on Ontology, and how to use MetaMask plug-in wallets to manage Ethereum wallets.
2. Introduction to Development Environment Tools
Since the EVM contract is developed in the Solidity language, we have detailed how to build the Remix, Truffle and Hardhat development environment, and enter a series of work such as contract development, compilation, deployment, and debugging. In addition, developers can also directly reuse the existing Ethereum contract framework to develop and deploy EVM contracts on Ontology.
2.1 Remix Development Environment
Remix IDE is an open source Solidity contract integrated development environment that supports users in contract development, compilation, deployment, and debugging. Please see this link for the official English version of Remix IDE.
Below we use a Hello World contract example to show how to use Remix.
2.1.1 Install Development Environment
To use Remix for the first time, you need to find and add the ...
To keep reading, please go to the original article at:
OntologyNetwork - Medium