From: snow <snow@smoke.suba.com>
To: “E. ALLEN SMITH” <EALLENSMITH@ocelot.Rutgers.EDU>
Message Hash: eb6d37746c2cb93d325373b87502e6433a3b0117ddcf5f7a6e1357629bb88528
Message ID: <Pine.LNX.3.93.960524230954.96A-100000@smoke.suba.com>
Reply To: <01I53GAYSQUC8Y4Z90@mbcl.rutgers.edu>
UTC Datetime: 1996-05-25 08:24:13 UTC
Raw Date: Sat, 25 May 1996 16:24:13 +0800
From: snow <snow@smoke.suba.com>
Date: Sat, 25 May 1996 16:24:13 +0800
To: "E. ALLEN SMITH" <EALLENSMITH@ocelot.Rutgers.EDU>
Subject: Re: Is Chaum's System Traceable or Untraceable?
In-Reply-To: <01I53GAYSQUC8Y4Z90@mbcl.rutgers.edu>
Message-ID: <Pine.LNX.3.93.960524230954.96A-100000@smoke.suba.com>
MIME-Version: 1.0
Content-Type: text/plain
On Fri, 24 May 1996, E. ALLEN SMITH wrote:
> From: IN%"iang@cs.berkeley.edu" 23-MAY-1996 13:56:31.71
>
> >Ah. I see I was misunderstood. The goal was not to make the shop anonymous,
> >but rather to be able to provide change to an anonymous payer.
>
> I had thought that the basic purpose of the fully anon system was just
> that - full anonymnity for payer and payee. Under your suggestion, the shop
> gives up this anonymnity under these circumstances in order to be able to make
> change. I'm not sure if I would call that a very good tradeoff...
Howzabout this: Figure out about how many coins of each denom. the
shop should have on hand, and every so often the shop goes online to even
out it's til. That way the shop maintains the capability to make change
for anything.
Alternative: Instead of the shop going online every <x> minutes,
set it up so that everytime the shop goes online it evens out the til so
that it really isn't know whether the shop went online to make change for
a specific customer, or just to even out the til.
Petro, Christopher C.
petro@suba.com <prefered for any non-list stuff>
snow@crash.suba.com
Return to May 1996
Return to “snow <snow@smoke.suba.com>”