{"action":"created","issue":{"url":"https://api.github.com/repos/D-OZ/MIPs/issues/4","repository_url":"https://api.github.com/repos/D-OZ/MIPs","labels_url":"https://api.github.com/repos/D-OZ/MIPs/issues/4/labels{/name}","comments_url":"https://api.github.com/repos/D-OZ/MIPs/issues/4/comments","events_url":"https://api.github.com/repos/D-OZ/MIPs/issues/4/events","html_url":"https://github.com/D-OZ/MIPs/issues/4","id":335653644,"node_id":"MDU6SXNzdWUzMzU2NTM2NDQ=","number":4,"title":"Profile Recoverability","user":{"login":"ghiliweld","id":15185350,"node_id":"MDQ6VXNlcjE1MTg1MzUw","avatar_url":"https://avatars1.githubusercontent.com/u/15185350?v=4","gravatar_id":"","url":"https://api.github.com/users/ghiliweld","html_url":"https://github.com/ghiliweld","followers_url":"https://api.github.com/users/ghiliweld/followers","following_url":"https://api.github.com/users/ghiliweld/following{/other_user}","gists_url":"https://api.github.com/users/ghiliweld/gists{/gist_id}","starred_url":"https://api.github.com/users/ghiliweld/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ghiliweld/subscriptions","organizations_url":"https://api.github.com/users/ghiliweld/orgs","repos_url":"https://api.github.com/users/ghiliweld/repos","events_url":"https://api.github.com/users/ghiliweld/events{/privacy}","received_events_url":"https://api.github.com/users/ghiliweld/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-06-26T04:20:55Z","updated_at":"2018-07-07T15:15:17Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"Profile should be recoverable in the event of losing your private key or getting your wallet hacked."},"comment":{"url":"https://api.github.com/repos/D-OZ/MIPs/issues/comments/403222499","html_url":"https://github.com/D-OZ/MIPs/issues/4#issuecomment-403222499","issue_url":"https://api.github.com/repos/D-OZ/MIPs/issues/4","id":403222499,"node_id":"MDEyOklzc3VlQ29tbWVudDQwMzIyMjQ5OQ==","user":{"login":"moskalyk","id":8753589,"node_id":"MDQ6VXNlcjg3NTM1ODk=","avatar_url":"https://avatars0.githubusercontent.com/u/8753589?v=4","gravatar_id":"","url":"https://api.github.com/users/moskalyk","html_url":"https://github.com/moskalyk","followers_url":"https://api.github.com/users/moskalyk/followers","following_url":"https://api.github.com/users/moskalyk/following{/other_user}","gists_url":"https://api.github.com/users/moskalyk/gists{/gist_id}","starred_url":"https://api.github.com/users/moskalyk/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/moskalyk/subscriptions","organizations_url":"https://api.github.com/users/moskalyk/orgs","repos_url":"https://api.github.com/users/moskalyk/repos","events_url":"https://api.github.com/users/moskalyk/events{/privacy}","received_events_url":"https://api.github.com/users/moskalyk/received_events","type":"User","site_admin":false},"created_at":"2018-07-07T15:15:17Z","updated_at":"2018-07-07T15:15:17Z","author_association":"NONE","body":"Password recoverability 'typically' takes the form of using a group of 'trustees' with the use of a Shemir Secret (common amongst those implementations like uPort, NuCpyher, etc.)\r\n\r\n> Shamir’s secret sharing is an algorithm that divides a secret into shares. A secret can be recovered by combining certain numbers of shares.\r\n\r\nIn the mimo scenario, the private key would be the secret.\r\n\r\nIn traditional real identity based systems, this would represent a group of acquaintances or friends. In Mimo, given the decentralized / pseudo-anonymous nature, there might be a need for a staking mechanism (either economic or reputation based) to explore. \r\n\r\nConsiderations:\r\n* **Trustee**: Possible need for a participant within the mimo ecosystem called a \"Trustee\"\r\n* **Trustees as Followers or other Pseudo-Anon Profiles**: This may present the need within mimo to be able to choose a select few 'trusted' followers that opt into the ability to have a share of the secret provided.\r\n* **Staking model**: Additionally, a token staking model (if not Ether) as a economic reward based system. If not economic stake, then possible reputation based system attached to identities to prevent: collusion and password recover quick acting.\r\n**Reputation based system**: To create more 'at stake' in recovery / preventing collusion, a reputation within a community should be established.\r\n\r\nExample:\r\n_**Reputation**_\r\nMo loses his password. Mo has preset trustees he's chosen based on the trustees willingness stake their reputation at stake that they will act honestly, and incentived (amongst a group) to act quickly for a reward. This relationship to the account looking for password recovery help might be best anonymous, as a trustee would **act differently in knowing who they are providing help to** E.g: 1) profile with many followers might signal status (which is typically how the populist thinks) vs. 2) a new account with low followers. (which can be even more favourable to help those learning). Trustees are rewarded badges which have more reputation in password recovery / more likely to be chosen as a future trustee for others.\r\n\r\nConsiderations: The quantity of password recoveries might happen more often for newer accounts because of inexperienced holders. However, for the Mimo profile, there is less at stake given reputation (unless attached to a valuable ENS name) which may be less of an issue. Vs. matured profiles have more to lose, and if put in the wrong hands can act malicously and create a bad overall reputation of mimo profiles.. Need to unpack this and get back to you.\r\n\r\n**_Rewards_**\r\nAlternatively, this might better help the matured ecosystem, as those profiles with high followers / reputation would be willing to stake more to keep account, and choose highly 'reputable trustees' to protect account. This stake / claim would be to recover a password in the future. e.g. 10 MIMO tokens, and Trustees / Holders of the share are rewarded a staked sum to help in a backup. In the request for a back up, there is an incentive to provide the recovery quickly. \r\n\r\nConsideration: Some notifications / client / UI is a top need.\r\n\r\n**_Attacks_**\r\nWhile I'm not up to date on the complete picture of the mechanism design here, there is possible for **collusion for trustees** to find other trustees and collude to steal an account. Therefore, some counter stake, or governance around this might be needed for 'tattling' if a trustee finds out that another is sniffing for shares. From a reputation perspective, there is high incentive for profile owners to know they have a 'tattler' in their trustee group.\r\n\r\nOther Considerations: \r\n* Privacy features may be of use to prevent trustees from knowing other addresses of trustees, or, even knowing. \r\n* Might need to look into address / reveal scheme. Where a trustee does not know the address their hold a share of to prevent acting different given identity until after a password recovery notificaiton has been created."}}
{"actor":{"display_login":"moskalyk"}}