Timeline for Invalid Address Error when interacting with a smart contract with metamask
Current License: CC BY-SA 3.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 29, 2022 at 12:06 | answer | added | Gleichmut | timeline score: 0 | |
| Sep 19, 2019 at 8:47 | answer | added | Ytsen de Boer | timeline score: 1 | |
| Jul 23, 2019 at 0:13 | answer | added | Joodi | timeline score: 0 | |
| May 7, 2019 at 23:18 | answer | added | Сергей Демидов | timeline score: 1 | |
| Jan 16, 2019 at 17:03 | answer | added | Jesbus | timeline score: 5 | |
| Nov 24, 2018 at 3:11 | answer | added | J Technology | timeline score: 1 | |
| Nov 29, 2017 at 20:44 | answer | added | Jorge M. Londoño P. | timeline score: 16 | |
| Sep 27, 2017 at 14:52 | answer | added | gorik | timeline score: -2 | |
| Aug 5, 2017 at 8:55 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jul 8, 2017 at 19:48 | comment | added | Victor Baranov |
Try to set default account and send transaction in callback from web3.eth.getAccounts(function(err, accounts) {...}. Maybe, it'll help.
|
|
| Jul 6, 2017 at 9:33 | comment | added | Gawey |
I have a similar problem and doesn't exist a lot information about the invalid address errors. The only what i found is the web3.eth.accounts "solution", but this doens't work for me, cause metamask put the correct account with injected web3. Maybe somethign like this can help you, if you found the answer write here again ^^
|
|
| Jul 6, 2017 at 6:59 | answer | added | Rohan Khanna | timeline score: 8 | |
| Jul 6, 2017 at 0:05 | answer | added | DanF | timeline score: 5 | |
| Jul 5, 2017 at 23:52 | history | asked | gpanterov | CC BY-SA 3.0 |