Write and update documentation for Account Recovery and ODIS #150
Conversation
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
added 20 commits
October 15, 2021 15:36
…se to existing docs
✅ Deploy Preview for celo-docs ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
codyborn
reviewed
Oct 28, 2021
codyborn
reviewed
Oct 28, 2021
docs/celo-codebase/protocol/odis/use-cases/phone-number-privacy.md
Outdated
Show resolved
Hide resolved
codyborn
reviewed
Oct 28, 2021
docs/celo-codebase/protocol/odis/use-cases/phone-number-privacy.md
Outdated
Show resolved
Hide resolved
codyborn
reviewed
Oct 28, 2021
| As of October 2021, ODIS operates with 7 signers and a threshold of 5 (i.e. $$m=7, k=5$$). | ||
| As a result, 5 of the 7 parties must cooperate in order to produce an output from the OPRF function, and as long as at least 3 are honest and secure, no unauthorized requests will be served. | ||
|
|
||
| <!-- TODO(victor): Once the new set is in production, information about the 7 operators should be included here --> |
codyborn
reviewed
Oct 28, 2021
codyborn
reviewed
Oct 28, 2021
codyborn
reviewed
Oct 28, 2021
codyborn
reviewed
Oct 28, 2021
codyborn
reviewed
Oct 28, 2021
codyborn
reviewed
Oct 28, 2021
docs/celo-codebase/protocol/odis/use-cases/phone-number-privacy.md
Outdated
Show resolved
Hide resolved
codyborn
approved these changes
Oct 28, 2021
…cs into victor/account-recovery-docs
Co-authored-by: Cody Born <codyborn@outlook.com>
nategraf
commented
Nov 23, 2021
| This context information is used to decide what rate limit and/or authentication should be applied to the request, and is combined into the result to ensure output is unique to the context. | ||
|
|
||
| As an example, a Domain for hashing an account password might specify an application username of "vitalik.eth" (context) and a cap of 10 password attempts (rate-limiting parameter). | ||
| These would be combined with the user's password (blinded input) in the POPRF, which acts as a one-way function, to form the final output. |
There was a problem hiding this comment.
Addressed in 3d86ab1
docs/celo-codebase/protocol/odis/use-cases/phone-number-privacy.md
Outdated
Show resolved
Hide resolved
added 7 commits
November 23, 2021 16:23
…cs into victor/account-recovery-docs
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In order to document the recent work on account recovery and ODIS, this PR includes new pages as well as updates to existing pages.
SUMMARY.mdfile which was used by GitBook but is no longer used.Related issues