Five Bitcoins with One Click

Gavin Andresen introduced freebitcoins.appspot.com on June 11, 2010, as his first Bitcoin programming project. He deliberately kept it simple: visitors entered an address, and the site sent them 5 BTC. Initially, it restricted repeat claims by the IP address of the internet connection; CAPTCHA was not yet enabled. Gavin funded the service with 1,100 BTC, enough for 220 full payouts.

His motivation was practical. A person who had read about Bitcoin could join and run the software, but without coins, they had nothing to send. Mining required time and luck, while buying was complicated in the early market. The faucet shortened the path from 'I'm interested' to 'I just received Bitcoin' to a few minutes.

Andresen didn't want to be the only donor. He provided an address where others could replenish the stock, and publicly displayed the status. The faucet thus became a shared distribution treasury of a small community. People who already had coins financed the experience of those who were just arriving.

Satoshi Nakamoto praised the project. He wrote that he himself had intended to create a similar service when it would be too difficult for ordinary users to obtain the full fifty-bitcoin block reward. His reaction shows that distribution was not a side marketing effort. The network needed people with wallets and balances just like running nodes.

Five bitcoins didn't have today's purchasing power or significance. The dose was large enough to experiment with and cheap enough for the programmer to send to strangers. The value of the faucet lay in the first touch with the wallet: the address ceased to be a string of characters and became a place where something actually arrived.

Gavin did not wait for a professional distribution service to appear. He built the site on whatever infrastructure he had at hand and publicly acknowledged that it was his first Bitcoin project. The faucet was thus both a gift and an open experiment. Every visitor was testing not only the transfer of five coins but also Gavin's code, the server's availability, and a new user's ability to create a valid address. When a security flaw was found in a debug mode that had been left enabled, the person who reported it received a reward, and Gavin fixed the service. Early Bitcoin did not grow on ready-made infrastructure; people built it while it was running and resolved bugs in plain sight of others.

Today's user can choose an exchange, exchange office, or Bitcoin ATM. In the summer of 2010, such services were just emerging and had low liquidity. Connecting a bank payment with a person willing to sell a few units was often more complicated than using the program itself. The faucet therefore didn't solve the price; it solved availability.

Each sent dose also created a small network opportunity. The recipient could return the coins, send them to a friend, use them in the first service, or just watch them in the program. The protocol already knew how to move value, but the social layer around it was empty. The giveaway helped populate it.

In this sense, the faucet was the opposite of an investment recommendation. It didn't promise profit and didn't encourage buying. It gave people units precisely so they wouldn't have to decide first how many dollars they were willing to risk. The experiment could begin without financial commitment, and only experience showed whether the novelty made sense.

The project also drew on the then-current method of distributing Bitcoin. New coins were obtained by miners, but not every newcomer wanted or was able to mine. Gavin Andresen changed part of his mining or purchased stock into a bridge between the first holders and a wider circle of users. It wasn't a new emission mechanism; all the distributed coins had already been created according to the network's rules.

The faucet thus revealed the paradox of an early currency. For it to have value, people must want and use it. To use it, they must first get it somewhere. The website didn't solve this circle forever, but at a crucial moment, it interrupted it with a gift. Each five bitcoins was an invitation that could be passed on.

The simple website quickly became a security test as well. One visitor discovered the enabled debug mode of Django. The error page could reveal sensitive application data and thus threaten the stock. Instead of quietly exploiting the bug, he reported it. Andresen fixed the setting and sent him 50 BTC as a reward.

The episode reminds us how personal early Bitcoin was. There was no established process for reporting vulnerabilities or a security team. There was the author, the user, the forum, and public reaction. The same openness that allowed for quick experiments exposed services to errors that could be catastrophic in a financial application.

Before long, some people were trying to get more than everyone else. They switched IP addresses and Bitcoin addresses to claim further payouts. Gavin gradually tightened the checks: at first, suspicious visitors had to solve a CAPTCHA; later, everyone did. The problem was not Bitcoin’s consensus. A site giving away something valuable was enough to make someone look for a way to take more.

Andresen described the changes publicly and without pretending the system was perfect. He needed to distinguish real newcomers from automated draining without turning the simple gate into a complicated registration. It was a small precursor to future services: the protocol could be permissionless, but the website over it had to deal with spam, scams, and operational security.

Voluntary replenishment also showed that the community stock wasn't bottomless. Each abused dose was missing someone who wanted to try Bitcoin for the first time. Protecting the faucet therefore wasn't about defending bank profits. It was an attempt to keep the open entry long enough to fulfill its distribution purpose.

By August 2010, Andresen was looking at different numbers from those in June. He wrote on the forum that the bitcoin price had risen from about half a US cent to six cents. That raised the value of the original payout from a few cents to thirty cents. It was still no fortune, but with thousands of visitors the supply of bitcoins available to give away was running down faster.

Gavin therefore announced that he would reduce each payout from 5 to 0.5 BTC. This was not a forecast of the future price. He was trying to make a limited supply last at a time when the market was finding its price and more people were becoming interested in Bitcoin. The faucet had to adapt to its own success.

From today's perspective, the story tempts us to multiply the distributed coins by the current exchange rate. Such a calculation, however, obscures its meaning. Andresen wasn't distributing known future wealth. He was distributing poorly liquid experimental units to increase the chance that the network would have users and eventually a market.

Some recipients lost the coins, others spent them, and others might have kept them. The faucet didn't keep a biography of each dose. Its success isn't measured by who made the most profit from the gift, but by how many people it removed the first barrier for. Getting Bitcoin stopped meaning mining, trading with a stranger, or studying an emerging exchange for a while.

The Bitcoin Faucet eventually belongs to history, just like the first wallets and the first purchases. It showed that new money needs not only cryptography but also distribution, patient explanation, and a willingness to bear the costs for someone else's experience. The website disappeared, but its basic question remained: how can a person understand an open monetary network until they send something through it themselves?

A modern perspective can easily turn the faucet into a ledger of squandered wealth. But such accounting confuses later value with the decisions made at the time. Gavin was not distributing rare collectibles with a guaranteed future value; he was paying with his own coins for the network to gain new users, transactions, and experience. Some of the gifts certainly ended up forgotten, some were sold, and some may have led someone to further experimentation. No blockchain will show which of these outcomes was the most important. It only shows that distribution was not a side issue. Without people who had something to send, a working protocol might have continued to resemble an empty square.