From: smb@research.att.com
To: Mikolaj Habryn <dichro@tartarus.uwa.edu.au>
Message Hash: 3e4d0866487f5ce8126f2594d5246c2ec4d6dd9818637f57bd8e4fd5a5b9c510
Message ID: <9403261340.AA00242@toad.com>
Reply To: N/A
UTC Datetime: 1994-03-26 13:40:27 UTC
Raw Date: Sat, 26 Mar 94 05:40:27 PST
From: smb@research.att.com
Date: Sat, 26 Mar 94 05:40:27 PST
To: Mikolaj Habryn <dichro@tartarus.uwa.edu.au>
Subject: Re: Digital Cash
Message-ID: <9403261340.AA00242@toad.com>
MIME-Version: 1.0
Content-Type: text/plain
Just a thought on ways to deter all of this multiple spending
gunk - when you start off, have a centralized bank server.
While traffic is low, you can have each individual certificate
cleared with the bank server upon creation and execution.
As someone else noted, ``crypto is all economics''. In the New York
City subway system, the new fare card readers are all linked to a central
computer, specifically to prevent double spending. They could have
used smart cards and fancy crypto -- but this is cheaper, especially
because they have an excellent handle on the maximum load -- the number
of subway riders at rush hour. Fancy technology could get them into
an ``arms race'' with rip-off artists, who reverse-engineer cards,
crack algorithms, etc.
Digital cash -- which provide anonymity, as contrasted against
cryptographically-signed debit card transactions -- will become a
reality if and only if someone finds it more profitable than the
alternative, after deducting the costs for observer chips, licenses
for Chaum's patents, etc. Some people are willing to pay for privacy --
but are there enough of them to make it pay?
--Steve Bellovin
Return to March 1994
Return to “smb@research.att.com”
1994-03-26 (Sat, 26 Mar 94 05:40:27 PST) - Re: Digital Cash - smb@research.att.com