1996-05-21 - Re: The Crisis with Remailers

Header Data

From: bryce@digicash.com
To: Matts Kallioniemi <matts@pi.se>
Message Hash: fff1a228b3add233ced9819c0cf4498afa7262442efa34c8363bf4190d5badee
Message ID: <199605211544.RAA04042@digicash.com>
Reply To: <2.2.32.19960521135644.00354324@mail.pi.se>
UTC Datetime: 1996-05-21 21:15:45 UTC
Raw Date: Wed, 22 May 1996 05:15:45 +0800

Raw message

From: bryce@digicash.com
Date: Wed, 22 May 1996 05:15:45 +0800
To: Matts Kallioniemi <matts@pi.se>
Subject: Re: The Crisis with Remailers
In-Reply-To: <2.2.32.19960521135644.00354324@mail.pi.se>
Message-ID: <199605211544.RAA04042@digicash.com>
MIME-Version: 1.0
Content-Type: text/plain



-----BEGIN PGP SIGNED MESSAGE-----

 Matts Kallionieme <matts@pi.se>:
 (> > == Bryce <bryce@digicash.com>)
>
> >Actually it can sometimes get more complicated than that, and 
> >there are some details about how the forthcoming ecashlib 
> >handles this to be found at "http://www.digicash.com/api".
> 
> Will the api make it possible to create coins of arbitrary value? Is
> the mint software (and the bank accountants) capable of doing
> floating point arithmetic?


Matts, you don't want to do floating point for money, because
floating point doesn't give you good control of precision.  If
you want to know how it _is_ done, RTFAPI ("read the fantastic
API.")  Scan for "EC_Coinage".


Keep in mind that only Ecash(tm) Mints can create Ecash(tm) 
coins and choose what values the coins have.


I'm glad you are asking these questions.  Perhaps this will be
the start of the Ecash(tm) API FAQ.


Regards,

Bryce

(I'm getting tired of typing "(tm)".  I'm going to make a macro
that appends "(tm)" to every instance of "Ecash" as I type 
it...)

- -----BEGIN GOODTIMES VIRUS INNOCULATION-----
Copy me into your .sig for added protection!
- ----- END  GOODTIMES VIRUS INNOCULATION-----



-----BEGIN PGP SIGNATURE-----
Version: 2.6.2i
Comment: Auto-signed under Unix with 'BAP' Easy-PGP v1.1b2

iQB1AwUBMaHk8UjbHy8sKZitAQFWcwMAsIK/HDloWq9LslPcQd3R0h6tOx1sH6I0
Ngc8jkSBsDPVL28I0tvimHLfMInq9EEPoOvwUjFQ8cmKTeVJVSRyYDCyQVTSbfWa
2gA8mjBTcCw5QrEYQAP74Dg0Os+iSwB5
=K79Z
-----END PGP SIGNATURE-----





Thread