Check out the new USENIX Web site. next up previous
Next: Adversaries and attacks Up: Model and System Architecture Previous: Security design goals

Parties and roles

We will use the following terminology for the parties involved in VarietyCash. In a typical transaction there would be three parties involved: the payer, the payee, and the bank or e-money server. However, we would like to be more specific than that: In turn, a coin-holder may play the following roles:Further, we make the following distinction amongst participants:The idea here is that a participant may wish to be able to ``play the game,'' i.e., accept and use coins as a form of payment, without going through the more elaborate process that enables the purchase or redemption of e-money. Note that parties and roles are not mutually exclusive.

In VarietyCash all the participants have distinct identities, as well as public keys. The issuer has a database listing the identities of all participants, and, for each one, its public key. This information is entered at the time of registration. In all transactions directly involving the issuer, there is thus no need for an external certification authority; however, the design leaves an option for such a case.

We assume in this extended abstract a unique issuer, thus dispensing with the presentation of a more elaborate clearing system.


next up previous
Next: Adversaries and attacks Up: Model and System Architecture Previous: Security design goals
Juan A. Garay
7/20/1998