Timeline for Out of gas when calling contract method - Browser Solidity & Metamask
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 8, 2017 at 9:03 | history | bounty ended | Juan Ignacio Pérez Sacristán | ||
| Feb 8, 2017 at 8:58 | comment | added | Juan Ignacio Pérez Sacristán | Thanks Matthew. A bug with metamask is my hypothesis too. | |
| Feb 8, 2017 at 8:57 | vote | accept | Juan Ignacio Pérez Sacristán | ||
| Feb 7, 2017 at 20:25 | comment | added | Matthew Schmidt | Or not!? See my latest edit. | |
| Feb 7, 2017 at 20:24 | history | edited | Matthew Schmidt | CC BY-SA 3.0 |
A solution?
|
| Feb 7, 2017 at 20:06 | comment | added | Matthew Schmidt | I still can't think of it being anything but not having quite enough gas, since the transactions are identical otherwise. What client sent it shouldn't matter, as it's miners that execute it. | |
| Feb 7, 2017 at 17:17 | comment | added | Juan Ignacio Pérez Sacristán | gas sent by metamask: 33787 on testnet.etherscan.io/tx/… 58787 on testnet.etherscan.io/tx/… and testnet.etherscan.io/tx/… while geth is sending 1000000 but spending just 23263 => testnet.etherscan.io/tx/… | |
| Feb 7, 2017 at 14:49 | comment | added | Matthew Schmidt | Looking closely, it seems that metamask sends exactly enough gas, whereas geth sends extra gas. I'm not sure why it would break if it has just enough--there's a small number of obscure possibilities. (I don't think it's a refund issue, since there's no storage deletion or selfdestructs.) | |
| Feb 7, 2017 at 0:30 | comment | added | Juan Ignacio Pérez Sacristán | Unfortunately, it doesn't work this way either: testnet.etherscan.io/tx/… In this case, destination address is testnet.etherscan.io/address/… having several previous txs and a not null balance. This same tx using geth node works ok from a geth node => testnet.etherscan.io/tx/… | |
| Feb 6, 2017 at 19:04 | history | answered | Matthew Schmidt | CC BY-SA 3.0 |