From 3d86ab1b34c17559a8f60fb8e0002cb39aa5aed8 Mon Sep 17 00:00:00 2001 From: Victor Graf Date: Tue, 23 Nov 2021 12:36:59 -0800 Subject: [PATCH] clarify the meaning of POPRF --- docs/celo-codebase/protocol/odis/domains/index.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/celo-codebase/protocol/odis/domains/index.md b/docs/celo-codebase/protocol/odis/domains/index.md index acbd8f68af..16d19ef44f 100644 --- a/docs/celo-codebase/protocol/odis/domains/index.md +++ b/docs/celo-codebase/protocol/odis/domains/index.md @@ -8,6 +8,7 @@ In order to support use cases such as password hardening, and future application A Domain instance is structured message sent to ODIS along with the secret blinded message. Unlike the blinded message, the Domain instance is visible to the ODIS service and allows the client to specify context information about their request. 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. +The Domain instance and blinded message are both passed to the ODIS partially oblivious pseudorandom function (POPRF), which is a new construction extending upon the [OPRF function](/celo-codebase/protocol/odis) used in the [phone number privacy service](/celo-codebase/protocol/odis/use-cases/phone-number-privacy). 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.