You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, greet you and congratulate you for your good work in this network that I have just met as a developer. It looks very good.
I would like to convey a problem for me of lack of information. I am used to that in other networks the transfers of the native token are reflected in the function calls of the contracts. I have found that in this explorer this does not happen.
Below I transmit an example for its effective verification.
I see this as a serious problem for the support team. If you cannot validate in a clear way that a contract has sent the TFUEL it will be a matter of word against word. And this is blockchain. Somewhere that TFUEL transaction has to be reflected. Because my event can't be proof of payment, it could be misleading.
I have also made another example contract to test with the three ways of sending native token with solidity.
Finally I share an image of a call to a function that returns native token to the user. We can see that it is reflected in the input transfer the output of that token.
The text was updated successfully, but these errors were encountered:
Cainuriel
changed the title
TFUEL transactions by contracts do not appear on etherscan
TFUEL transactions by contracts do not appear on ledger explorer
Oct 27, 2022
First of all, greet you and congratulate you for your good work in this network that I have just met as a developer. It looks very good.
I would like to convey a problem for me of lack of information. I am used to that in other networks the transfers of the native token are reflected in the function calls of the contracts. I have found that in this explorer this does not happen.
Below I transmit an example for its effective verification.
I have created this contract to explain the problem. It is a contract that you can put in TFUEL and then withdraw it with a function. https://testnet-explorer.thetatoken.org/account/0x284a9b99d94f768c1fb5019f26996dce3d39f7f2#Contract
Here is an income of 10 TFUEL
https://testnet-explorer.thetatoken.org/tx/0xd3f516df650f30446a741a23e530bb946b277a0d78b8c7f5ade9335e1883e70f#Overview you can see the transfer
But when we call the withdrawal function, reclaimTFUEL, the withdrawal does not appear in value information.
It does appear in the log that I have created but it does not reflect that the contract has sent TFUEL to the user.
https://testnet-explorer.thetatoken.org/tx/0xc1ac47ab8be79ee7329524e765eacb2f8825c87cc52949ba5a50aa9226b01a26
I see this as a serious problem for the support team. If you cannot validate in a clear way that a contract has sent the TFUEL it will be a matter of word against word. And this is blockchain. Somewhere that TFUEL transaction has to be reflected. Because my event can't be proof of payment, it could be misleading.
I have also made another example contract to test with the three ways of sending native token with solidity.
https://testnet-explorer.thetatoken.org/account/0xad207884feff7ac4a0690a3fa81e834aebd31ad0#Contract
None of them reflect that transfer:
with transfer:
https://testnet-explorer.thetatoken.org/tx/0x78297c166c5df60ac9738ded387c5b6f97648fb5fa377f79968a0109c497168d
with useCall:
https://testnet-explorer.thetatoken.org/tx/0x8dbce5b1b5298636fa2eea94d73178d45e0a79bb316acfdcb8fedcf4ae62a3b7
with viaSend:
https://testnet-explorer.thetatoken.org/tx/0xc76840cdb114b2a15cadc202953ac764235c4c705573284ff8a6f3a4bb94ca31#Overview
Finally I share an image of a call to a function that returns native token to the user. We can see that it is reflected in the input transfer the output of that token.
The text was updated successfully, but these errors were encountered: