deployment

Deployment is a term often used for military dispatch during mission. Soldiers may be part of the deployment to the Middle East

Deployment refers to the placement of people in various places, in particular to serve soldiers and other military personnel. Soldiers and equipment and generals may be included in the deployment. Deployment may be part of the mission of war and peace. In addition, non military organizations use this term. They may talk about placing workers in new offices. Looking at the word deployment, you can see that people are being sent somewhere in a particular task.

Deployer: The deployer is the Ethereum address and is responsible for the actual deployment of the Smart Contract. That is the only one that needs to be "hot" (accessible) during deployment. There is no need to balance Ethernet out of deployment, and even different addresses are not required for each deployment. Owner: The owner is the address that ultimately will be ownership owner of the smart contract. This can be multiple signatures wallet or DAO, but in most cases it will be a single owner. For a single owner account, you need to securely store the private key during deployment.

Deployment: All placement scripts need to be written in placement DSL with purescript. From the developer's point of view, this means that you can use all the effects you normally need, such as calling Web 3, reading from the file system, and calling up the network. Since each contract may have its own constructor that requires its own parameters, we standardized how this parameter is represented so that each parameter is validated against the required validation mechanism before deployment . At least this means that all types are correct, but it is also easy to add logic about the values ​​themselves, such as integer borders and string formats.

The arrangement is the same as Part 1. Enter a few ethers in the value field to preload the contract, enter the constructor parameters and click create. In this case, the mask requests acceptance / rejection of transaction (contract deployment). Click OK to wait for the transaction to complete. You can test the application by running npm start on the terminal and going to localhost: 8080 in your browser. Enter the amount and click the number. Metamask urges you to accept the transaction and the spinner starts. This is also an event as the first confirmation will arrive after 30 seconds. Because the balance has been changed, pollweb 3 will trigger the update of the balance.