Erarim Etherken API Internal Deal is Back Despite Switzer
As a developer, we are checking the Athensken API to collect information on the transactions of the Blockchan. However, despite a simple exchange demand, we found a single internal deal for a simple exchange request.
Transaction details
සැක සහිත ගනුදෙනුව පහත පරිදි වේ: 0x33E0DAB83A831A81A81A81A891A4C691A3491A491A3491ADB6A35AD30C11111111111111111111113 This transaction appears to be a simple transfer of GALA tokens from the sender's wallet (address0x33e0dab83aa27ba8b2a08b3c69d61a34911a4adb6e7a35dd30cf11383f43fcc3) to the recipient's wallet (0xfed5e3ee3bf6ffcaac38ceebef89f6ecfa98bc94).
Release
After reviewing transaction information on Merken then, we saw that one internal transaction was actually listed,1. At first glance, it seems to be reconstructed, however, this internal deal is not really connected to simple exchange request.
The response of API
According to the Ethenken API documentation, internal transaction for certain types of transactions:
- 1 change of ether
- 0x0000000000000000000000000000000000000000000000000000
(ගෑස් ඒකකය)
- 0x0000000000000000000000000000000000000000000000000000000000000000000
In this case, the internal deal will be returned because of ‘1 ether.’ The documentation is clearly stated that the documentation can return an internal transaction for simple exchange demands, which led to our opening confusion.
conclusion
APSon API internal transaction should be given to a simple exchange request, and it seems to be misrepresented in transaction details. This problem highlights the importance of carefully reviewing the back on the back of different types of transactions and highlighting the underlying logic. As developers, we must ensure that our Testing and Inquiry API is correctly reflecting the desired behavior of the API.
Example code
For a snippet of ilones (erections) showing a simple exchange request is an example code code code code code code:
`Stronger
Pragma Strengthening ^ 0.8.0;
Contract ampltransfer {
Active exchange (address recipient) common {
// Make the transfer logic here …
// … …
}
}
`
This contract includes a function of exchange, and allows us to imitate a simple transfer between two purses.
I hope this letter helps us to explain any confusion of the Return behavior of the Etherkan API for internal deals.