On 24 Dec 2001, at 9:40, Nomen Nescio wrote:
How simple can an ecash mint be?
For the simplest case there should be no accounts. All the mint does is
exchange coins for other coins. There are no customer lists, no records
of transactions (except as needed for double-spending detection).
How simple can an ecash mint be?
For the simplest case there should be no accounts. All the mint does is
exchange coins for other coins. There are no customer lists, no records
of transactions (except as needed for double-spending detection).
The very simplest mint is a pure ecoin changer.
Actually, I think to be practical you want something only
slightly more complex; 3x as much work, but 100x as useful.
Implemented in tamper-resistant hardware (a dedicated box or process
could substitute, but hardware is easier, and I have plenty):
stage 1:
* Some protocol for external
Tim writes:
This is a terribly important point. Implementing this atomic
transaction would be a major step. Having a Web site that does this
EVEN WITH PLAY TOKENS would be a useful step.
There used to be a little toy server run by Software Agents at
www.netbank.com. It exchanged
Ryan Lackey writes:
* Some protocol for external communication (direct sockets is easiest,
but message-based protocols are far better, and allow a front end
processor to handle communications details)
A message is simply a packet of data. Using a message-based protocol
says nothing about
I don't believe normal users should ever interact directly with the
mint; using the mint as a reissue server only in normal operation is a
key optimization -- especially when coupled with tamper-resistant mint
hardware. Easier to develop, easier to operate, easier to audit.
Users should
Ryan Lackey writes:
I don't believe normal users should ever interact directly with the
mint; using the mint as a reissue server only in normal operation is a
key optimization -- especially when coupled with tamper-resistant mint
hardware. Easier to develop, easier to operate, easier to
