Skip to content

Update README.md #5

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

Update README.md #5

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
34 changes: 27 additions & 7 deletions infrastructure/w3id/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ The metastate ecosystem has the only 1 type of identifiers, W3ID (did:w3id proto
### _Users & Groups_

Users and groups would have a persistent, unchanging identifier which is referred to as Web 3 Identifier
In case of a person, the W3ID is the life-long anchor which connects keys and the physical essence of a person. It is represented on the diagram below
In case of a person, the
(1-2 relations) personal W3ID and personal keys via eID certificate from PKI
(2-3 relations) personal W3ID and body characteristics, physical passport and friends.

Expand All @@ -22,12 +22,6 @@ eVault: An eVault would use its own unique W3ID, which is not shared with a user

W3 Envelope would use a W3ID, which is globally unique, and this W3ID would be used in the W3ID URI scheme to retrieve a envelope.

## Technical Requirements and Guarantees:

- The identity must be globally persistent, and unique.
- The identity must exist on a namespace with more range higher than 10^22
- The identity must support rotation of secrets and must only be loosely bound to keys
- The identity must be loosely tied to a passport in form of binding document

## W3ID URI Scheme

Expand All @@ -38,6 +32,32 @@ UUID range is 2^122 or 15 orders larger than expected amount of IDs (10^22) ther

### Example:


### W3ID URI format:

`w3id://<UUID in HEX>` (case insensitive, like any URI) formed by the rules of RFC4122. In particular, the number and positioning of the dashes in the string is mandatory!
UUID range is 2^122 or 15 orders larger than expected amount of IDs (10^22) therefore it fits the purpose perfectly.

### Example:


### W3ID URI format:

`w3id://<UUID in HEX>` (case insensitive, like any URI) formed by the rules of RFC4122. In particular, the number and positioning of the dashes in the string is mandatory!
UUID range is 2^122 or 15 orders larger than expected amount of IDs (10^22) therefore it fits the purpose perfectly.

### Example:


### W3ID URI format:

`w3id://<UUID in HEX>` (case insensitive, like any URI) formed by the rules of RFC4122. In particular, the number and positioning of the dashes in the string is mandatory!
UUID range is 2^122 or 15 orders larger than expected amount of IDs (10^22) therefore it fits the purpose perfectly.

### Example:



`w3id://e4d909c2-5d2f-4a7d-9473-b34b6c0f1a5a`
If a local ID is needed, it is added after “/”, also as UUID range e.g.:
`w3id://e4d909c2-5d2f-4a7d-9473-b34b6c0f1a5a/f2a6743e-8d5b-43bc-a9f0-1c7a3b9e90d7`
Expand Down