From: Bryan Ford <baford@schirf.cs.utah.edu>
To: cypherpunks@toad.com
Message Hash: b45a45f465acec15050281c8273ad828a7d4848187e8b401ee0d07b5676d55e2
Message ID: <9402161725.AA05848@schirf.cs.utah.edu>
Reply To: <9402161539.AA13477@merde.dis.org>
UTC Datetime: 1994-02-16 17:30:15 UTC
Raw Date: Wed, 16 Feb 94 09:30:15 PST
From: Bryan Ford <baford@schirf.cs.utah.edu>
Date: Wed, 16 Feb 94 09:30:15 PST
To: cypherpunks@toad.com
Subject: Re: Magic Money and Remailers
In-Reply-To: <9402161539.AA13477@merde.dis.org>
Message-ID: <9402161725.AA05848@schirf.cs.utah.edu>
MIME-Version: 1.0
Content-Type: text/plain
In message <9402161539.AA13477@merde.dis.org> Pr0duct Cypher writes:
>Being an accountless system, Magic Money can be operated through a remailer.
>But Magic Money is an online system. Offline systems depend on the bank
>knowing who the customers are, and being able to punish them for double
>spending. How could an offline system be made immune to this attack?
Is it necessarily the bank's job to worry about this? Suppose the bank
simply honors the first request from "anyone" to re-mint a coin; after that
the bank only knows about the new coin. If Jack pays Jill with already-spent
money, Jill's attempt to deposit or re-mint the coin will fail, and it's
Jill's responsibility to find another way to collect the money. So if
she's smart, she'll make sure she can re-mint the money _before_ closing
the deal. It's much like checks or credit cards work today: a transaction
is not considered "complete" until it "clears".
Bryan
Return to February 1994
Return to “remailer@merde.dis.org (remailer bogus account)”