I made a number of improvements to the hashcash software to make it
into a more robust and better documented unix tool, including man page.

In doing this I changed the date format to be the simpler and more
human readable YYMMDD rather than 5 digit days since begining of unix
EPOC.

So the tokens now look like:

        020314:[EMAIL PROTECTED]:7a3ed56af63b7ef1

and the tool is more picky about returning error codes, it will only
return success if you really check every aspect (the resource string,
the number of bits of collision, and whether the token is double
spent).

See the man page

        http://www.cypherspace.org/hashcash/hashcash.html

for all new usage and database.

(It can also support an extended date format based on UTCTIME: of
YY[MM[DD[hh[mm[ss]]]]]'Z' where stuff in [] is optional for tokens
with long or short validity periods, but just creates the human YYMMDD
format by default).

        http://www.cypherspace.org/hashcash/

I made a lot of changes, so if anyone finds any bugs or portability
issues let me know.  The double spend database is not backwards-
compatible as I re-wrote it pretty much from scratch and changed the
format.

Adam

Reply via email to