Timeline for why do i see input data in the transaction details when i didn't pass it as a data parameter
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 16, 2019 at 19:21 | comment | added | KwahuNashoba | Never really dug into the web3 code, but there is no reason to put it there from my point of view. It's more likely that it's using all the data (function and transaction params (the {} object) you provided to create a signed transaction in a way similar or exact as in the code I've linked in my answer. | |
| Apr 16, 2019 at 19:11 | comment | added | bbusdriver |
one more thing, you mentioned web3 packs... in the data field of transaction. Does that mean it is creating data object in the last parameter behind the scene although I did not explicitly added?
|
|
| Apr 16, 2019 at 19:00 | vote | accept | bbusdriver | ||
| Apr 16, 2019 at 18:59 | comment | added | KwahuNashoba | No, never tried it. There are also multiple versions of web3 out there that provide different handling of input data and transaction parameters, maybe some of them use that object...just guessing. | |
| Apr 16, 2019 at 18:56 | comment | added | bbusdriver |
Thanks for your answer. Have you ever used data object in the last parameter? I wonder if it can change the data I passed as name and age.
|
|
| Apr 16, 2019 at 18:22 | history | edited | KwahuNashoba | CC BY-SA 4.0 |
added 37 characters in body
|
| Apr 16, 2019 at 18:15 | history | answered | KwahuNashoba | CC BY-SA 4.0 |