1996-01-22 - double-spending ecash

Header Data

From: “Patiwat Panurach (akira rising)” <pati@ipied.tu.ac.th>
To: ecash@digicash.com
Message Hash: bae386208158baa25725359563b71baa6c728d0fc0920c2a25ea517759685946
Message ID: <Pine.SUN.3.91.960122193424.25584C-100000@ipied>
Reply To: <9601112011.AA25213@toad.com>
UTC Datetime: 1996-01-22 12:35:08 UTC
Raw Date: Mon, 22 Jan 96 04:35:08 PST

Raw message

From: "Patiwat Panurach  (akira rising)" <pati@ipied.tu.ac.th>
Date: Mon, 22 Jan 96 04:35:08 PST
To: ecash@digicash.com
Subject: double-spending ecash
In-Reply-To: <9601112011.AA25213@toad.com>
Message-ID: <Pine.SUN.3.91.960122193424.25584C-100000@ipied>
MIME-Version: 1.0
Content-Type: text/plain


	Double spending using ecash isn't possible, but why so?  Is it 
because of the verification protocol?  Or is it an implication of the 
isueing intricacies?
	And how about tracing, is it merely unfeasable that ecash 
spending can be traced, or is it mathamatically impossible to trace?
	Any explanations or pointers would be extremely helpful.  

-------------------------------------------------------------------------------
Patiwat Panurach      	     Whatever you can do, or dream you can, begin it.
eMAIL: pati@ipied.tu.ac.th      Boldness has genius, power and magic in it.
m/18 junior Fac of Economics		-Johann W.Von Goethe
-------------------------------------------------------------------------------








Thread