[hashcash] Re: stamp collisions

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Mon, 30 Aug 2004, Hubert Chan wrote:

Of course, your probabilities get reset at the beginning of the day, since the date is part of the stamp. (Although if you live to be over 100 years, you might run into problems, since it only has 2-digit years. ;-) (of course, by then, you would undoubtedly need to generate a larger bit-value stamp anyways)) If the stamp contained the time down to the second, along with the sender= extension, collisions would be pretty much impossible, although this is probably not needed. 
===========

would resolution to the second really help? i was under the impression (but i'm no expert on it) that certain inferior OSs give too much consideration to the time when generating a "random" number... if that's the case, then 2 stamps being independently minted for the same address and at the same second would still have a fairly high chance of being the same.


Another way to guarantee no collisions (in addition to the sender= extension) is to have a few bits in the "random" field be a sequential counter that gets incremented for every stamp generated. 
===========

that leaks too much information... such as how many emails one sends out in a given period... it might hint at BCC being used...


    ...atom

 _________________________________________
 PGP key - http://atom.smasher.org/pgp.txt
 762A 3B98 A3C3 96C9 C6B7 582A B88D 52E4 D9F5 7808
 -------------------------------------------------

        "The Army is the Indian's best friend."
                -- General George Armstron Custer, 1870
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.3.6 (FreeBSD)
Comment: What is this gibberish?
Comment: http://atom.smasher.org/links/#digital_signatures

iQEcBAEBCAAGBQJBM+K6AAoJEAx/d+cTpVciu7AH+wZsnPD6xKVQ9/88MnYf1qnB
zXuwh9zhLvDlldAU9kGKBj0jGdXDKOQwLu2gB+wT7dh5L22QpzphoxFFCV5ZXmXk
vb1g3rXn1wu/tPTjBBlpoQgKA1yjygUFXI62qqPkBL/kniY5c3PAJDMeT/p8koGq
qvUE3REJ+oiXkreX17kocEgE+yfw1e1AYRLB+mgiuJtjU44hmkznM1rWGuoX+0zt
EQgu2eVln6dwNvGUXAuNiILP5v2WJTpThvYHDv035Nnt3oIDAM8PFP6ljrkYQnLF
WV3byrthWwLEmepHV7T60P5mWMUoLSyAz8IHrKjCyEd6r8esH+kZlDGC5d/aADQ=
=SaKy
-----END PGP SIGNATURE-----

Other related posts: