{"action":"opened","issue":{"url":"https://api.github.com/repos/aionnetwork/AVM/issues/144","repository_url":"https://api.github.com/repos/aionnetwork/AVM","labels_url":"https://api.github.com/repos/aionnetwork/AVM/issues/144/labels{/name}","comments_url":"https://api.github.com/repos/aionnetwork/AVM/issues/144/comments","events_url":"https://api.github.com/repos/aionnetwork/AVM/issues/144/events","html_url":"https://github.com/aionnetwork/AVM/issues/144","id":387514320,"node_id":"MDU6SXNzdWUzODc1MTQzMjA=","number":144,"title":"[CLOSED] Split AvmImpl into its high-level uses","user":{"login":"aionbot","id":45608482,"node_id":"MDQ6VXNlcjQ1NjA4NDgy","avatar_url":"https://avatars1.githubusercontent.com/u/45608482?v=4","gravatar_id":"","url":"https://api.github.com/users/aionbot","html_url":"https://github.com/aionbot","followers_url":"https://api.github.com/users/aionbot/followers","following_url":"https://api.github.com/users/aionbot/following{/other_user}","gists_url":"https://api.github.com/users/aionbot/gists{/gist_id}","starred_url":"https://api.github.com/users/aionbot/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/aionbot/subscriptions","organizations_url":"https://api.github.com/users/aionbot/orgs","repos_url":"https://api.github.com/users/aionbot/repos","events_url":"https://api.github.com/users/aionbot/events{/privacy}","received_events_url":"https://api.github.com/users/aionbot/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-12-04T22:47:47Z","updated_at":"2018-12-04T22:47:47Z","closed_at":null,"author_association":"COLLABORATOR","body":"**Issue created by [jeff-aion](https://github.com/jeff-aion)** (on Tuesday Jul 17, 2018 at 19:34 GMT)\n\nThe `AvmImpl` currently has to many, largely unrelated, responsibilities.  The most obvious split being:\r\n\r\n- transforming bytecode, for deployment\r\n- executing transactions\r\n\r\nThese should be more directly split since the use-cases, while part of the same system, do not overlap.\r\n\r\nIt might also be worth reversing the relationship between `AvmImpl` and `NodeEnvironment` (making the latter into a real factory of the former) as part of this, but only if it makes things easier (as that is arguably a completely different change).\n"}}
{"actor":{"display_login":"aionbot"}}