Hashcash and Bcc/envelope recipients

--t4apE7yKrX2dGgJC
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

I've built a Python script for Mutt that mints tokens based on the
addresses in the To: and Cc: fields, however, how does hashcash handle Bcc:
or envelope recipients? By putting a token for each recipient in the
header, the addresses of those recipients would be revealed, thus
defeating the whole point.

I've thought about minting a token with a resource of "bcc-recipients", and
placing that token in the headers, but then that reveals that there have
been Bcc: recipients added to the mail. I believe the whole point of Bcc:
is to be completely transparent, not revealing to anyone that they exist.

So, I'm guessing that it's probably best to just ignore Bcc: and envelope
recipients in general. I guess I could mint a token for the From: address
(is this what I should be doing anyway?), but then that begs the question
of why not just minting a token using the From: address only, and not worry
about the To: and Cc: addresses?

Am I missing something?

--
. o .   o . o   . . o   o . .   . o .
. . o   . o o   o . o   . o o   . . o
o o o   . o .   . o o   o o .   o o o

--t4apE7yKrX2dGgJC
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: http://tinyurl.com/aarongpg

iQEcBAEBCgAGBQJNimUBAAoJEM55Ebf8BAiPYqUIAJj7W+UqdzJnxictoHy302Rc
mdCdZABPGtm18YmilxjtRNdrmSjiL098AyKAV8h8xAyCKsxdMJwZtjkuyxzW6AkM
E6HEgFw0yo4tTqYGTTMyXD8NAZD2aew0MaX4aVCFCgj7Z4Sq0b1bHCc927nk9jkX
DUrvJLEf2ooTYDIVQ2f+Wj+X7YMfCGoKzb0QIIk1sGLispmbHVKsdhRmQFvSr8dY
sybyBXTVghrn7N4O6fL2HfBXRa5i7+e/wUturktlmFNROMhGvadAVwEPe+qGI1mW
XL+kua8CaPyQkZOE2rjzv9RimMbRJjTPgl9rTYQ9PbiF/ysJ+wQWW+k9prG/Ms8=
=R6zB
-----END PGP SIGNATURE-----

--t4apE7yKrX2dGgJC--