We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
If we make a transaction with type CALL without payload and to an address that there is no smart contract the engine accepts the transaction.
Example:
https://testnet.aergoscan.io/transaction/CQPK53ftHwgEC8bRBce3vPHvnEZgBJquFXBe3Cv16Vo7/
Notice that the destination account is not a contract and the payload is empty.
If the transaction is a CALL or QUERY then the engine should make these 2 verifications:
default
The text was updated successfully, but these errors were encountered:
Here we have a similar case:
https://testnet.aergoscan.io/transaction/6CggiP7zHNCaxJLgTaxUJA3pyj9AJnhtxZfBQiKHgWyG/
Where the payload is valid but the recipient does not exist (is not a contract)
Strangely the transaction is marked as "success"
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
If we make a transaction with type CALL without payload and to an address that there is no smart contract the engine accepts the transaction.
Example:
https://testnet.aergoscan.io/transaction/CQPK53ftHwgEC8bRBce3vPHvnEZgBJquFXBe3Cv16Vo7/
Notice that the destination account is not a contract and the payload is empty.
If the transaction is a CALL or QUERY then the engine should make these 2 verifications:
The transaction must have a valid payload(empty payload calls thedefault
function)The text was updated successfully, but these errors were encountered: