Ethereum Transaction Revert Error: “The transaction is being reversed in the function of calling the book room”
As a developer that implements an intelligent contract using the Ethereum virtual machine (EVM), it is likely that you have encountered problems related to the reversals of transactions. In this article, we will immerse ourselves why an error occurred and how to solve it.
The problem
In your case, calling the Bookroom () function within its contract, the EVM meets a transaction reverse. This means that the execution of the smart contract code has stopped due to a validation failure or other error in the logic of the contract.
Error details
To solve problems of this problem, you can access the details of the transaction using the eth.gettransactionreceipt () from the EVM console. Here is an extract of its implementation script:
`JavaScript
Contract = new web3.eth.contract (
'0x' + [... yourcontractaddress],
[... yourcontractabi],
{Gas: 2000, args: [... yourags]}
);
In this example, theeth.gettransactionreceipt ()Call the transaction receipt associated with the last block in its block chain. From there, you can inspect the details of the transaction to identify the error.
Details of the transaction
When checking the transaction receipt, you must see an error message indicating the reason for reversing. In this case, the error can be seen something like this:
0x ... (transaction hash)
Error: Revert: "Book Room" function not found
Thefunctionin the error message indicates that the contract code tried to call a function called 'Bookroom ().
Solution
To solve this problem, you must ensure that the Bookroom () function is correctly defined within its contract. Here are some possible solutions:
- Update the ABI : Make sure the definition ofBookroom () function coincides with the one specified in its implementation script. If the name or parameters of the function have changed, update the ABI accordingly.
- Verify typographic errors : Verify that no typographic error has been lost when defining the
Bookroom () function. Use a code analyzer such as the built -in truffle link to capture possible errors.
- Verify the logic of the contract : Make sure the
Bookroom () function is correctly implemented and behaves as expected. If the problem persists, it further investigates the logic of the contract.
Example solution
To solve the problem, you can modify your implementation script to include a purification declaration:
JavaScript
Contract = new web3.eth.contract (
'0x' + [... yourcontractaddress],
[... yourcontractabi],
{Gas: 2000, args: [... yourags]}
);
Console.log ('Transaction:', Contract.transactionah);
This will generate the hash of the transaction associated with the last block. When inspecting this information, you can verify that theBookroom () function is defined correctly and calls the function as planned.
Following these steps and using the EVM console to inspect the details of the transaction, it must be able to identify and solve the problem that causes the error “the transaction is becoming the call function () function”.