{"action":"opened","issue":{"url":"https://api.github.com/repos/ethereum/go-ethereum/issues/17961","repository_url":"https://api.github.com/repos/ethereum/go-ethereum","labels_url":"https://api.github.com/repos/ethereum/go-ethereum/issues/17961/labels{/name}","comments_url":"https://api.github.com/repos/ethereum/go-ethereum/issues/17961/comments","events_url":"https://api.github.com/repos/ethereum/go-ethereum/issues/17961/events","html_url":"https://github.com/ethereum/go-ethereum/issues/17961","id":372914835,"node_id":"MDU6SXNzdWUzNzI5MTQ4MzU=","number":17961,"title":"Feature Request: Estimate multiple transactions with one call in same context","user":{"login":"arthurlataks","id":1751652,"node_id":"MDQ6VXNlcjE3NTE2NTI=","avatar_url":"https://avatars2.githubusercontent.com/u/1751652?v=4","gravatar_id":"","url":"https://api.github.com/users/arthurlataks","html_url":"https://github.com/arthurlataks","followers_url":"https://api.github.com/users/arthurlataks/followers","following_url":"https://api.github.com/users/arthurlataks/following{/other_user}","gists_url":"https://api.github.com/users/arthurlataks/gists{/gist_id}","starred_url":"https://api.github.com/users/arthurlataks/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/arthurlataks/subscriptions","organizations_url":"https://api.github.com/users/arthurlataks/orgs","repos_url":"https://api.github.com/users/arthurlataks/repos","events_url":"https://api.github.com/users/arthurlataks/events{/privacy}","received_events_url":"https://api.github.com/users/arthurlataks/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-10-23T10:00:42Z","updated_at":"2018-10-23T10:00:42Z","closed_at":null,"author_association":"NONE","body":"Hello,\r\n\r\ncurrently there is a way to estimate single transaction gas cost, which works good. But in some cases (for example ERC20 tokens, approve scenario) there is a need to estimate multiple transactions in the same context (aka without `approve` TX discarded) otherwise what happens - `buy` TX is being estimated only until that part where it is impossible to continue without approved allowance, and then in irl case allowance is set and code is continues executing (below above mentioned point) thus spending more gas than was estimated and then it runs out of gas :|\r\n\r\n#### System information\r\n\r\nGeth version: `Version: 1.8.12-stable`\r\nOS & Version: `Linux (4.9.93-linuxkit-aufs)`\r\n"}}
{"actor":{"display_login":"arthurlataks"}}