[hashcash] Re: new format tweak coming...

On Fri, Mar 12, 2004 at 10:09:00AM -0500, Eric S. Johansson wrote:
> I'm just trying to clarify that if there is no extension the format 
> would look something like:
> 
> version:date:resource::random
> 
> correct?

yes.

> >the suprising things or gotchas are that (a) the resource can contain
> >':' char.  The rule is: the version and date are : separated from the
> >left, the random and extension are : separated from the right, and the
> >bit in the middle is the resource name.
> 
> but can't extensions contain colon characters?  Something like:
> 
> 0:20040303:esj@xxxxxxxxxxxxxxxx:keyurl=http://key.troublemaker.com/public/esj:random

yes that would be convenient.  Let me think about that see if there is
a convenient way to allow this and keep things simple to avoid per
extension encoding.

> In fact, the more I think about this, the more I think it's a great
> idea because now I can take things I was going to include as extra
> headers and actually embed them in the stamp.  For example get out
> of jail information would be one such tidbit.  

Yes I was thinking of you ;-)

> Also broadcasting current postage rates might another good use of
> these extensions.

I think that could be a separate header as it's not per recipient,
it's per sender.  And sender things are not authenticated.

So I'm also thinking eg:

[X-Hashcash-Sender: extension]

with same format for extension.  Then the postage rate would go there.

Mechanically at programming level I am thinking the hashcash
executable will look for "hashcash-camram" executable if there is an
extension camram=foo=var,za=2,by=asdf and invoke it with 

hashcash-camram stamp foo=var za=2 by=asdf etc.

And the unauth part:

hashcash-sender-camram bar=taz

for 

X-Hashcash-Sender: bar=taz

details to be filled but the aim is to have a convenient scriptable /
plugable interface to me.

Adam

Other related posts: