Skip to main content

BBS per Verifier Linkability
draft-kalos-bbs-per-verifier-linkability-00

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Vasilis Kalos , Greg M. Bernstein
Last updated 2024-10-20
Replaces draft-vasilis-bbs-per-verifier-linkability
Replaced by draft-irtf-cfrg-bbs-per-verifier-linkability
RFC stream (None)
Intended RFC status (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-irtf-cfrg-bbs-per-verifier-linkability
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

Abstract

The BBS Signatures scheme defined in [I-D.irtf-cfrg-bbs-signatures], describes a multi-message digital signature, that supports selectively disclosing the messages through unlinkable presentations, built using zero-knowledge proofs. Each BBS proof reveals no information other than the signed messages that the Prover chooses to disclose in that specific instance. As such, the Verifier (i.e., the recipient) of the BBS proof, may not be able to track those presentations over time. Although in many applications this is desirable, there are use cases that require the Verifier be able to track the BBS proofs they receive from the same Prover. Examples include monitoring the use of access credentials for abnormal activity, monetization etc.. This document presents the use of pseudonyms with BBS proofs. A pseudonym, is a value that will remain constant each time a Prover presents a BBS proof to the same Verifier, but will be different (and unlinkable), when the Prover interacts with a different Verifier. This provides a way for a recipient (Verifier) to track the presentations intended for them, while also hindering them from tracking the Prover's interactions with other Verifiers.

Authors

Vasilis Kalos
Greg M. Bernstein

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)