It's worth mentioning that hashcash has never been widely deployed for email spam prevention, and never will be. (As far as I'm aware its widest success was getting a modest reduction in scores in the default SpamAssassin ruleset at one point, which -- AFAIK -- was eventually rolled back because, while people are attracted to the philosophy of hashcash, nobody actually uses it.)<p>Why?<p>1) The supermajority of spam is sent through systems which can be operated by an attacker but which are not actually owned by them. This includes, most prominently, botted-up residential PCs. Prior to wide availability of always-on high speed Internet it included email servers which were insufficiently locked-down. Hashcash does not meaningfully affected the economics of botnets.<p>2) The most successful anti-spam measure in history makes direct use of a consequence of #1: since mail servers do not move in nature that much, and legitimate mail systems do not frequently mix outgoing spam and outgoing ham, you can make IP-based reputational systems. If a residential IP starts sending email in large amounts, assume spam. If a novel IP starts sending email, treat as suspiciously smelling ham until they've demonstrated sufficient history, but flip the spam bit if/when they get aggressive. If a new MSA springs up, ensure their industry veterans at the helm understand the importance of their anti-abuse team, and tell them explicitly that their IPs are dead if they don't.<p>This worked fantastically well. It's the primary anti-spam measure which protects your inbox. (No. I know you think Bayesian filters are. They're more expensive to operate at scale, are virtually unusable by the common-denominator email user, and don't solve any problem better than IP reputation does.)<p>3) Hashcash never caught on in part because the people who care most about spam also care most about sending billions of emails. "We make it economically unattractive to send billions of emails" is a non-starter for them. You can guess who I'm talking about by taking a look at any user database and observing what percentage of email addresses in it terminate with the top, oh, five domain names. (Interestingly, email is a P2P protocol at the server level which is best described as "All peers are equal, in that they will be equally squashed beneath the boots of our governing oligopoly if they misbehave.")<p>Note that none of hashcash's problems are solved by "And now it can be stored for later."<p>Source: My first engineering job was as an anti-spam researcher.
<i>In order to send an email, the sender first has to solve a math problem. Legitimate activities suffer an indiscernible delay, but illegitimate activities that require massive volume are hobbled.</i><p>Illegitimate activities are often carried out in a parasitic manner using infected and hijacked equipment for which the spammer and attacker don't have to pay. This will do little to hinder those tactics.
<i>How valuable would stored Hashcash be?</i><p>It depends on the rules of the system. If the system arbitrarily limits the creation of hashcash to 2.5 per minute and limits the total in circulation to 21 M then it could be worth a lot (although with high volatility). Without such limits each unit of hashcash would be worth almost nothing, but the overall system might be more efficient and thus worth more.<p>Also, if the system limits itself to 7 transactions per second it may not be useful for anti-spam or bandwidth accounting.
How is that not bitcoin?<p>I've long been a fan of a "bounty" system -- you attach digital coins to a message, with the recipient specifying how many coins must be attached (maybe higher for voice, lower for email, mid level for SMS). If the message was unwanted (not merely spam, but even just a stupid request), the recipient collects the coins; otherwise, the sender gets them back.<p>This nicely aligns incentives. If the recipient takes coins improperly, you stop sending him mail.
I'm not sure how stored hashcash makes sense for preventing spam and DDoS. Won't services pop up that mine away, accumulate successful computation tokens, then sell them cheaply to spammers and flooders? Or spammers and flooders can simply leave their computer running a week in advance of planned attacks, and acquire a bunch of tokens all on their own.<p>We already see this kind of thing in CAPTCHA farms.
Your post advocates a<p>(X) technical ( ) legislative (X) market-based ( ) vigilante<p>approach to fighting spam. Your idea will not work. Here is why it won't work. (One or more of the following may apply to your particular idea, and it may have other flaws which used to vary from state to state before a bad federal law was passed.)<p>( ) Spammers can easily use it to harvest email addresses<p>(X) Mailing lists and other legitimate email uses would be affected<p>( ) No one will be able to find the guy or collect the money<p>( ) It is defenseless against brute force attacks<p>( ) It will stop spam for two weeks and then we'll be stuck with it<p>( ) Users of email will not put up with it<p>( ) Microsoft will not put up with it<p>( ) The police will not put up with it<p>( ) Requires too much cooperation from spammers<p>(X) Requires immediate total cooperation from everybody at once<p>(X) Many email users cannot afford to lose business or alienate potential employers<p>( ) Spammers don't care about invalid addresses in their lists<p>( ) Anyone could anonymously destroy anyone else's career or business<p>Specifically, your plan fails to account for<p>( ) Laws expressly prohibiting it<p>( ) Lack of centrally controlling authority for email<p>( ) Open relays in foreign countries<p>( ) Ease of searching tiny alphanumeric address space of all email addresses<p>(X) Asshats<p>( ) Jurisdictional problems<p>(X) Unpopularity of weird new taxes<p>(X) Public reluctance to accept weird new forms of money<p>(X) Huge existing software investment in SMTP<p>( ) Susceptibility of protocols other than SMTP to attack<p>(X) Willingness of users to install OS patches received by email<p>(X) Armies of worm riddled broadband-connected Windows boxes<p>(X) Eternal arms race involved in all filtering approaches<p>(X) Extreme profitability of spam<p>( ) Joe jobs and/or identity theft<p>( ) Technically illiterate politicians<p>( ) Extreme stupidity on the part of people who do business with spammers<p>( ) Dishonesty on the part of spammers themselves<p>( ) Bandwidth costs that are unaffected by client filtering<p>(X) Outlook<p>and the following philosophical objections may also apply:<p>(X) Ideas similar to yours are easy to come up with, yet none have ever
been shown practical<p>( ) Any scheme based on opt-out is unacceptable<p>( ) SMTP headers should not be the subject of legislation<p>( ) Blacklists suck<p>( ) Whitelists suck<p>( ) We should be able to talk about Viagra without being censored<p>( ) Countermeasures should not involve wire fraud or credit card fraud<p>( ) Countermeasures should not involve sabotage of public networks<p>( ) Countermeasures must work if phased in gradually<p>(X) Sending email should be free<p>( ) Why should we have to trust you and your servers?<p>( ) Incompatiblity with open source or open source licenses<p>( ) Feel-good measures do nothing to solve the problem<p>( ) Temporary/one-time email addresses are cumbersome<p>( ) I don't want the government reading my email<p>(X) Killing them that way is not slow and painful enough<p>Furthermore, this is what I think about you:<p>(X) Sorry dude, but I don't think it would work.<p>( ) This is a stupid idea, and you're a stupid person for suggesting it.<p>( ) Nice try, assh0le! I'm going to find out where you live and burn your
house down!
Instead of hash cash, could you charge 10 dogecoin?<p>We abstract out the computational requirements into a sub-penny but not insignificant payment.<p>Then again, how much would spammers be willing to pay?