Installation problems in Ethereum in Remix: Guide for the repair of errors of “installation transaction non -pinging”
As a developer who uses a Remix, he probably found errors when he installed contracts in the Ethereum Network. One of the general questions that arises is the “transaction is not payable” that can occur when a Remix -based compilation device is used. In this article, we examine the causes of this error and offer step -by -step solutions to correct it.
What is the error of “non -payable installation transaction”?
The error “The installation transaction is not paid” occurs when the Remix tries to install a contract that does not have enough ether balance (eth) in the metamask wallet. This can happen if you have installed a contract with an unpaid feature or if your contract wishes to apply an approach to my payment.
** The reasons for “the installation transaction is not paid”
Here are some general reasons for this error:
- Functions that do not pay : contracts that do not pay for their own installation, such as the characteristics that do not return anything (0x) or take arguments, the remix may think that the transaction is not paid.
- Payment controls : The use of a payment contract can also make this mistake, since Remix does not know how much ether can charge for the installation.
- Incorrect balance of the metamask wallet : If the metamask wallet does not have enough ETH to cover the installation costs, the Remix will show the error of “no payments”.
Symptoms
If the error “the installation transaction is not paid” will experience the remix:
- The error message appears when clicking on the installation
- Your contract is installed correctly but the transaction has failed
- Receive an error message like
0x ...
Paso of the passage solutions to correct the error of “installation not paid”
To solve the “installation transaction that should not be paid”, follow these steps:
1. Update Remix and Metamk’s wallet
Be sure to run the latest version of Remix (4.2.10 or posterior) and that MetamSk wallet is updated.
2. Verify the installation syntax of your contract
Check the contract installation syntax to ensure that you comply with the typical format for the installation of contracts in Ethereum. Find functions that do not pay, payment approaches to incorrect sheet or arguments for the contract code.
3. Verify the Metamask Wallet Balance
Make sure the metamash wallet has a sufficient ether balance to cover the installation costs. You can verify this by reviewing the balance of your wallet in the Remix.
`JavaScript
Console.log (Metamask.balance ());
If you are not sure in your wallet balance, try to update the Remix or wait for a short period to update your balance.
4.
You can install contracts directly from Remix using the "Web3.Eth 部署 Contract" function, which allows you to determine the contract syntax more accurately.
JavaScript
Const web3 = required ("web3");
Const implement = new web3.eth.deploymentContract ();
// Replace the contract address and ABI with real contractual data
Implement.DPLOY (Contractaddress, ABI);
5. Execute the remix in purification mode
If you install contracts in Remix, you can execute the application mode application to see more detailed error messages.
JavaScript
Remix Run-DeBug Installation Agreement
If the "Web3.eth 部署 contract" does not work or does not return an error message such as "0x ...", try to execute the remix in purification mode:
Bash
Remix Run-DeBug Installation Agreement
`
With these steps, you must be able to resolve the “unpaid” error in Remix and successfully install the contract. If the question is still, give me more details of your project or contract code and I will do everything possible to help you.