-----BEGIN PGP SIGNED MESSAGE----- Hal saw through my laziness attempt: I thought it would be "easiest" for a cash accepting remailer to increment an account (marking bills as spent) and have users request more bills from the bank rather that filter requests through me. However, this does lead to a perpetually full bank account... But actually, a full service bank isn't required (although maybe that would be nice) - all that's really needed is for the remailer software to compare the included digicash versus a spent cash list and a valid cash list. The banking portion need only be one command for me to use: one that deposits newly created cash into the valid cash list. When a letter arrives, the digicash is checked, added to the spent cash list, and re-routed. For privacy, requests for digicash could come to me via anonymous remailers, along with the appropriate header to allow me to respond. This would render logs relating digicash and user useless, since I wouldn't know who is requesting digicash bills. On the other hand, somebody could store up several digicash bills by routing their request through the various remailers. But I'll accept that risk, hoping that nobody on this list would prepare a email attack (except for the unfortunate folks who can't seem to unsubscribe :-) JUST KIDDING!!) /-----------------------------------\ | Karl L. Barrus | | elee9sf@menudo.uh.edu | <- preferred address | barrus@tree.egr.uh.edu (NeXTMail) | \-----------------------------------/ -----BEGIN PGP SIGNATURE----- Version: 2.2 iQCVAgUBK6Ap24OA7OpLWtYzAQHZQAQAo2ofd6lPBx/7XMR3Jr+7G2atMzevNcj3 Wtdrjr1GQJ+15z9duu3vh3yyV4j0rswyJlqp3eJZPCcb1NgEeKVZ1pP54YjDRwL2 UOKcHD55g+SIckIYVE+VFo4s2Ha8CKgtRgHmRV6+MJgiheBBOaOQxjFqRMpru3pO fE9mYRkNUII= =NyB0 -----END PGP SIGNATURE-----
participants (1)
-
Karl Barrus