-
Notifications
You must be signed in to change notification settings - Fork 39
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #97 from mwufi/ft-ms-1
New Standard: Decentralized identifiers (DIDs) on Flow - Milestone 1
- Loading branch information
Showing
1 changed file
with
30 additions
and
0 deletions.
There are no files selected for viewing
30 changes: 30 additions & 0 deletions
30
submissions/issue-17/milestone-1/FlashyTigers/milestone-1.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,30 @@ | ||
# New Standard: Decentralized identifiers (DIDs) on Flow - Milestone 1 | ||
|
||
## Description | ||
|
||
This PR is for issue #17 (https://github.com/onflow/flip-fest/issues/17) | ||
|
||
|
||
## Submission Links & Documents | ||
|
||
[Flow DID Spec](https://eoverse.notion.site/Flow-ID-Spec-0a3bda315a574326b354b4c67b7b39a6) | ||
|
||
[Live Demo on netlify](https://flownames.netlify.app/godmode) | ||
1. Create a collection | ||
2. Register a name | ||
3. Lookup a name | ||
Please open the Devtools while these are happening (haven't implemented appropriate UI yet) | ||
|
||
[Github repo](https://github.com/flokilabs/fns) | ||
|
||
## Requirements Check | ||
|
||
- Have have you met the milestone requirements? YES | ||
- Have you included tests (if applicable)? YES | ||
- Have you met the contribution guidelines of the repos you have submitted code to (if applicable)? YES | ||
- If this is the last milestone: NO | ||
|
||
## Other Details | ||
|
||
- Is there anything specific you'd like the PoC to know or review for? NO | ||
- Are there other references, documentation, or relevant artificats to mention for this PR (ie. external links to justify design decisions, etc.)? NO |