{"action":"opened","issue":{"url":"https://api.github.com/repos/eris-ltd/epm-go/issues/167","labels_url":"https://api.github.com/repos/eris-ltd/epm-go/issues/167/labels{/name}","comments_url":"https://api.github.com/repos/eris-ltd/epm-go/issues/167/comments","events_url":"https://api.github.com/repos/eris-ltd/epm-go/issues/167/events","html_url":"https://github.com/eris-ltd/epm-go/issues/167","id":71450981,"number":167,"title":"what is the benefit of not thelonious chains within epm?","user":{"login":"compleatang","id":590037,"avatar_url":"https://avatars.githubusercontent.com/u/590037?v=3","gravatar_id":"","url":"https://api.github.com/users/compleatang","html_url":"https://github.com/compleatang","followers_url":"https://api.github.com/users/compleatang/followers","following_url":"https://api.github.com/users/compleatang/following{/other_user}","gists_url":"https://api.github.com/users/compleatang/gists{/gist_id}","starred_url":"https://api.github.com/users/compleatang/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/compleatang/subscriptions","organizations_url":"https://api.github.com/users/compleatang/orgs","repos_url":"https://api.github.com/users/compleatang/repos","events_url":"https://api.github.com/users/compleatang/events{/privacy}","received_events_url":"https://api.github.com/users/compleatang/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/eris-ltd/epm-go/labels/ideas%20for%20review","name":"ideas for review","color":"eb6420"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-04-28T01:52:26Z","updated_at":"2015-04-28T01:52:26Z","closed_at":null,"body":"i am increasingly unconvinced of the benefits of having multiple chain types usable from this tool. \r\n\r\nepm's functionality can roughly be broken down into three major areas:\r\n\r\n1. dapp//project management (this includes refs and most of new)\r\n2. blockchain administration functionality (config, etc.) and operation functionality (checkout, run)\r\n3. smart contract package management\r\n\r\n`1` is only applicable to thelonious\r\n\r\n`2` is partially applicable to all three currently vetted types but the difficult parts of `2` are really only applicable to thelonious\r\n\r\n`3` should really only be done via rpc going forward as that will give us the most flexibility as to where a particular container is running (locally, remote, who cares). indeed as we break out the key signing function into a signing microservice/daemon, then we definitely should be using the rpc.\r\n\r\n## costs-benefits as i see them\r\n\r\ncosts:\r\n\r\n* this multibinary setup is going to be a bit complex to maintain, \r\n* setup currently feels significantly more sluggish than yesterday (before i rebased)\r\n\r\nbenefits:\r\n\r\n* universal command line interface ...? \r\n\r\nthe benefit is all well and good but if folks want eth or mint they can much more easily install those projects' tools and use them. i am not sure what value having those libs be integrated into epm gives our users. \r\n\r\nmaybe i'm wrong, but on balance I think that we need to focus this tool on being the best cli for thelonious because it seems to me its starting to get in our way.\r\n\r\n**N.B.**, this somewhat relates to #161 \r\n\r\n"}}