On Sat, Sep 14, 2013 at 4:49 PM, David D <da...@7tele.com> wrote: > Great points all around. Your suggestions for identification and punishment > are delightful.
someone mentioned a bitcoin assassination pool: names to addresses, addresses to kill bid, according to harm perpetuated. if your spec includes a NULL suite, it also carries mortal risk ;) . . . unfortunately this is likely to result in a final burn of NIST curves and SHA1 preimage capability which until this year had remained closely guarded secret. the subsequent overtake of the bitcoin network would be used to finance the death of all cypherpunks and malcontents instead, before then destroying the network itself. have we carried this thread sufficiently off the rails? vengeance lust sated? </wild_tangents> the only practical value of such a list (read as - not crazy mob witch hunt frenzy): apply defense in depth, and pair cleared individual work product with a scrutinizer not so encumbered. call it peer review across trust boundaries. it is mandatory! unfortunately the budgets, skill, and other resources available outside of five eyes and their industry partners are significantly smaller... _______________________________________________ cryptography mailing list cryptography@randombit.net http://lists.randombit.net/mailman/listinfo/cryptography
