1995-11-10 - Re: ecash speed

Header Data

From: Scott Brickner <sjb@universe.digex.net>
To: cypherpunks@toad.com
Message Hash: 1c303168a37332360b783e8d63c1bedeaed1a673ee08bd9466967ae223f36260
Message ID: <199511102145.QAA06533@universe.digex.net>
Reply To: <199511090508.VAA05884@jobe.shell.portal.com>
UTC Datetime: 1995-11-10 22:16:21 UTC
Raw Date: Sat, 11 Nov 1995 06:16:21 +0800

Raw message

From: Scott Brickner <sjb@universe.digex.net>
Date: Sat, 11 Nov 1995 06:16:21 +0800
To: cypherpunks@toad.com
Subject: Re: ecash speed
In-Reply-To: <199511090508.VAA05884@jobe.shell.portal.com>
Message-ID: <199511102145.QAA06533@universe.digex.net>
MIME-Version: 1.0
Content-Type: text/plain


Hal writes:
>This all has to happen whenever you click on a link in your browser.
>Even with fast CPU's I think the extra step of connecting to the bank,
>having it check against all coins, and getting approval will be
>considerable for each link traversal.

A system like Stephen Brands' should significantly improve the
situation.  There's no benefit in double-spending micropayments since
you'll be identified after the fact.  For small enough payments, you
can skip the on-line validation and handle them in batch-mode later.
It becomes a matter of risk management, then.

Thread

• Return to November 1995

• Return to “Hal <hfinney@shell.portal.com>”
• Return to ““Perry E. Metzger” <perry@piermont.com>”

• Return to “Scott Brickner <sjb@universe.digex.net>”

• 1995-11-09 (Thu, 9 Nov 1995 09:35:07 +0800) - ecash speed - Hal <hfinney@shell.portal.com>
  • 1995-11-09 (Thu, 9 Nov 1995 10:42:30 +0800) - Re: ecash speed - “Perry E. Metzger” <perry@piermont.com>
    • 1995-11-10 (Fri, 10 Nov 1995 10:17:22 +0800) - Re: ecash speed - Hal <hfinney@shell.portal.com>
      • 1995-11-09 (Thu, 9 Nov 1995 22:56:30 +0800) - Re: ecash speed - “Perry E. Metzger” <perry@piermont.com>
      • 1995-11-10 (Sat, 11 Nov 1995 06:16:21 +0800) - Re: ecash speed - Scott Brickner <sjb@universe.digex.net>