On January 19, 2019, the pseudonymous Bitcoin user hodlonaut started what became known as the Lightning Torch: a relay built around a 100,000-satoshi payment sent through Bitcoin’s Lightning Network. The public instructions were simple. The first recipient would add 10,000 satoshis, choose another person considered trustworthy, and forward 110,000 satoshis. Each new holder would repeat the process.

The surviving launch post establishes the date, starting amount and intended rule. A later CoinGecko quarterly report preserved screenshots showing hodlonaut announcing that the first recipient, the account @fartface2000, had received 100,000 satoshis and was preparing to forward 110,000. That makes the event a documented payment experiment, not merely an announced idea.

A relay built on payment channels

One bitcoin equals 100 million satoshis, so the opening payment was 0.001 BTC and the required increment was 0.0001 BTC. The experiment used Lightning rather than recording every relay transfer as a separate Bitcoin base-layer transaction.

The Lightning Network paper by Joseph Poon and Thaddeus Dryja described a system of off-chain payment channels whose latest balances could ultimately be enforced through transactions broadcast to Bitcoin. Routed payments were designed to cross a network of channels without requiring every intermediary to be trusted. The torch added a deliberately social layer: each current holder had to trust the next person to continue the relay instead of keeping the funds.

That tension was the point. Lightning’s payment construction aimed to reduce the need to trust routing intermediaries, but this particular game depended on human cooperation between successive holders. The “trust chain” therefore tested both payment routing and community coordination.

Why the small payment mattered

The amount was modest, but the demonstration addressed an important question facing Bitcoin in early 2019: could Lightning support usable, low-value payments outside developer test cases? A successful handoff required a recipient able to receive through Lightning and a route with sufficient liquidity for the growing invoice. Each additional 10,000 satoshis made the next transfer slightly more demanding.

The experiment was not a benchmark. It had no control group, standardized wallet setup, published fee schedule or independent record of every routing attempt on January 19. A completed hop showed that one payment found a route under the conditions faced by those users. It did not establish network-wide capacity, reliability, decentralization, privacy or consumer readiness.

Nor was the relay a protocol upgrade or a company launch. No rule change occurred on Bitcoin on January 19, 2019. Its significance was practical and cultural: users turned an experimental payment layer into a public, repeatable demonstration whose failure condition was easy to understand.

Market scale and calculation

Kraken’s exchange report for January 19 listed BTC at $3,702, up 2.50% for its daily measurement, with $31.5 million in BTC trading volume on Kraken. Using that venue-specific reference price, 100,000 satoshis equaled about $3.70 and each 10,000-satoshi increment equaled about $0.37.

Those dollar figures are calculations, not execution prices for the torch. Bitcoin traded continuously across venues, Kraken’s report does not create a universal market close, and the payment’s exact dollar value would have varied with the timestamp and pricing source. There is also no evidence that the torch caused the day’s BTC move.

Later context, kept separate

The relay’s eventual reach was unknowable on January 19. On February 5, 2019, CoinDesk reported that it had reached 139 participants in at least 37 countries. CoinGecko’s later first-quarter review recorded a much longer sequence. Those later observations confirm that the initial handoff became consequential, but they should not be read back into what participants could verify when the experiment began.

Primary sourceHodlonaut’s January 19, 2019 Lightning Torch launch post

The complete source packet and revision history are retained with the newsroom record.

Automated desk disclosure

Automated systems may have assisted with source organization and drafting. Coinburn is accountable for the published text and maintains a revision record.

Financial-risk note

This article provides news and analysis, not investment, legal or tax advice. Digital assets are volatile and may result in total loss.