Here’s an article:
Metamascus: False transaction mined, but execution failed
Wen, I tried to schedule smartly on remix.etherum use metamask on ully. The error message indicated a false transaction that is mined, and I will investigate.
Problem
After reviewing my transactions, I noticed that false transaction instead of really being, but execution. This resulted in the contraction not distributed as expected, and any damping to do it is a handsome error message. The error message pointed to a problem that is carried out by a transaction, it is a true resolant by Blockchain for the Velid transaction.
Error Message
Here is the detained error message that I have joined:
False transaction mined but execution
This indicates that Metamascus has discovered that a false transaction is mined on the polygon network, but it is not executors.
What went wrong
After further investigation, I discovered that the problem was specifically, Kodlja and the performer script was not properly configured, lying to an invalid transaction.
Solution*
To solve this problem, I follow Maganges:
- Properly implemented with contraction
: I updated my counteraact code to ensure that it is compatible with remix.etereum and the application ID.
- Updated implementing script : I changed the script for implementation in the correct ABI -uTxhash` field.
Result
With these changes, my smart contract section is deployed on a remix.etr using a metamic on the polygon network. A false transaction that is mined what is a grid and can continue the execution of contraction.
Conclusion*
In this article, I demonstrated that it is easy to arrange the smart contraction of remix.etherum wth targets on a false transaction that is mined but not exec. By correcting the configuration and update of the script, I should have solved the problem and successfully implement.
Recent Comments