From ce9e54afdfb5ecfc704217252d2e4133ca47cec3 Mon Sep 17 00:00:00 2001 From: Alex Van de Sande Date: Fri, 18 May 2018 14:14:15 -0400 Subject: [PATCH] Automatically merged updates to draft EIP(s) 1078 Hi, I'm a bot! This change was automatically merged because: - It only modifies existing draft EIP(s) - The PR was approved or written by at least one author of each modified EIP - The build is passing --- EIPS/eip-1078.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/EIPS/eip-1078.md b/EIPS/eip-1078.md index 89488308..f0045666 100644 --- a/EIPS/eip-1078.md +++ b/EIPS/eip-1078.md @@ -36,7 +36,7 @@ The first step of the process is to request from the user the ENS name that poin If the user doesn’t have an identity, the app should provide the option to create one for them. Each app must have one or more domains they control which they can create immediate subdomains on demand. The app therefore will make these actions on the background: 1. Generate a private key which it will keep saved locally on the device or browser, the safest way possible. -2. Create (or set up) an identity contract which supports both ERC720 and ERC10XX +2. Create (or set up) an identity contract which supports both ERC720 and ERC1077 3. Register the private key created on step 1 as the *only* admin key of the contract (the app must not add any app-controlled key, except as recovery option - see 5) 4. Register the requested subdomain and transfer its ownership to the contract (while the app controls the main domain and may keep the option to reassign them at will, the ownership of the subdomain itself should belong to the identity, therefore allowing them to transfer it) 5. (Optionally) Register a recovery method on the contract, which allows the user to regain access to the contract in case the main key is lost.