Timeline for Problem with sending ERC20 token using [email protected]
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 29, 2018 at 1:16 | history | edited | Paul Razvan Berg | CC BY-SA 4.0 |
edited title
|
| Jul 28, 2018 at 21:48 | vote | accept | Paul Razvan Berg | ||
| Jul 28, 2018 at 21:37 | comment | added | Paul Razvan Berg | @smarx sorry I wanted to attach a link to this one. | |
| Jul 28, 2018 at 18:11 | answer | added | user19510 | timeline score: 2 | |
| Jul 28, 2018 at 18:10 | comment | added | user19510 |
Oh, actually, the transaction isn't being sent to a contract at all. The to address is ropsten.etherscan.io/address/…, which is not a contract. (There's no associated code.)
|
|
| Jul 28, 2018 at 18:09 | comment | added | user19510 |
Are you sure that's the right code for the contract? It doesn't appear to have a function called transfer.
|
|
| Jul 28, 2018 at 17:09 | comment | added | Paul Razvan Berg |
Just checked now, it's not 0, but a or 10 in decimal, just as it should. You can check out the tx and the contract yourself.
|
|
| Jul 28, 2018 at 16:57 | comment | added | Nulik | first thing I would do, is to get the block number, get the transaction input and decode it, check that the value transferred is not 0 | |
| Jul 28, 2018 at 16:55 | comment | added | Nulik | at what block was your transaction mined? | |
| Jul 28, 2018 at 16:38 | history | asked | Paul Razvan Berg | CC BY-SA 4.0 |