{"action":"created","issue":{"url":"https://api.github.com/repos/bitshares/bsips/issues/80","repository_url":"https://api.github.com/repos/bitshares/bsips","labels_url":"https://api.github.com/repos/bitshares/bsips/issues/80/labels{/name}","comments_url":"https://api.github.com/repos/bitshares/bsips/issues/80/comments","events_url":"https://api.github.com/repos/bitshares/bsips/issues/80/events","html_url":"https://github.com/bitshares/bsips/issues/80","id":326660849,"node_id":"MDU6SXNzdWUzMjY2NjA4NDk=","number":80,"title":"New BSIP discussion: Require UIA owner permission to use UIA as backing collateral for an MPA?","user":{"login":"grctest","id":15861527,"node_id":"MDQ6VXNlcjE1ODYxNTI3","avatar_url":"https://avatars1.githubusercontent.com/u/15861527?v=4","gravatar_id":"","url":"https://api.github.com/users/grctest","html_url":"https://github.com/grctest","followers_url":"https://api.github.com/users/grctest/followers","following_url":"https://api.github.com/users/grctest/following{/other_user}","gists_url":"https://api.github.com/users/grctest/gists{/gist_id}","starred_url":"https://api.github.com/users/grctest/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/grctest/subscriptions","organizations_url":"https://api.github.com/users/grctest/orgs","repos_url":"https://api.github.com/users/grctest/repos","events_url":"https://api.github.com/users/grctest/events{/privacy}","received_events_url":"https://api.github.com/users/grctest/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":12,"created_at":"2018-05-25T20:52:16Z","updated_at":"2018-06-21T19:11:01Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"#### Should we require UIA owner permission to use UIA as backing collateral for an MPA?\r\n\r\nRecently, [issue #1537](https://github.com/bitshares/bitshares-ui/issues/1537) in the bitshares-ui Github repo highlighted the fact that despite the UI and documentation indicating that UIA cannot be used to back an MPA on the BTS DEX, the reality actually is that UIA are an allowed backing collateral asset type in the core code.\r\n\r\nThis BSIP is not arguing for/against UIA being used as an MPA's backing collateral, because this is already enforced by core (Abit has a testnet asset configured as such).\r\n\r\nThe purpose of this BSIP discussion is to whether or not you should require owner permissions/approval of the asset being assigned as backing collateral for a new MPA.\r\n\r\n##### Why I think we should require permission\r\n\r\n* Any assets locked away as MPA backing collateral cannot be reclaimed/recalled by the UIA owner (even by force). This has the consequence of being unable to reduce the supply to 0, potentially preventing asset settings from being changed or the asset from being fully shutdown.\r\n* By 'wrapping' an UIA in an MPA 'container' the MPA owner can effectively impose new asset settings over the existing UIA flags/permissions/settings to the potential detriment of the UIA owner.\r\n\r\n##### Why perhaps we shouldn't require such permissions\r\n\r\n* An asset owner may refuse (or be unable to) provide permission to use the asset as backing collateral, requiring an alternative asset for backing collateral.\r\n* The committee may be overwhelmed with requests to use committee owned assets as backing collateral, though that's subjective.\r\n* The committee would have a greater centralized control of backing collateral selection on the BTS DEX, however that could result in more private MPAs being created. The committee size could be increased too to offset risk.\r\n* Existing MPA with non-BTS backing collateral may make implementing such a permission requirement too complex? Perhaps existing MPA could be exempt?\r\n* What if the asset owner removed their approval at a later date? It'd have to be permanent approval unless supply was 0.\r\n* What happens if you have owner permissions of the backing asset & MPA, then transferred the backing asset ownership to another account?\r\n* Being able to avoid market fees and replace restrictive permission flags with an MPA is pretty cool.\r\n\r\n##### Exclusions:\r\n\r\n* The Bitshares core token should be excluded, as nobody has ownership permissions over it.\r\n\r\n----\r\n\r\nSo, what are your thoughts?\r\n\r\nNote: [This is a mirrored github post!](https://github.com/bitshares/bsips/issues/80)"},"comment":{"url":"https://api.github.com/repos/bitshares/bsips/issues/comments/399212057","html_url":"https://github.com/bitshares/bsips/issues/80#issuecomment-399212057","issue_url":"https://api.github.com/repos/bitshares/bsips/issues/80","id":399212057,"node_id":"MDEyOklzc3VlQ29tbWVudDM5OTIxMjA1Nw==","user":{"login":"happyconcepts","id":14145836,"node_id":"MDQ6VXNlcjE0MTQ1ODM2","avatar_url":"https://avatars2.githubusercontent.com/u/14145836?v=4","gravatar_id":"","url":"https://api.github.com/users/happyconcepts","html_url":"https://github.com/happyconcepts","followers_url":"https://api.github.com/users/happyconcepts/followers","following_url":"https://api.github.com/users/happyconcepts/following{/other_user}","gists_url":"https://api.github.com/users/happyconcepts/gists{/gist_id}","starred_url":"https://api.github.com/users/happyconcepts/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/happyconcepts/subscriptions","organizations_url":"https://api.github.com/users/happyconcepts/orgs","repos_url":"https://api.github.com/users/happyconcepts/repos","events_url":"https://api.github.com/users/happyconcepts/events{/privacy}","received_events_url":"https://api.github.com/users/happyconcepts/received_events","type":"User","site_admin":false},"created_at":"2018-06-21T19:11:01Z","updated_at":"2018-06-21T19:11:01Z","author_association":"NONE","body":"So bottom line if you're going to change it .... I don't think that this arbitrary and capricious approach via an undiscussed BSIP in order to enable one person's prediction market coin fantasy is the way to go.\r\n"}}
{"actor":{"display_login":"happyconcepts"}}