CRYPTO

My Bitcoin Node Ran on $3 a Month

My home-built Bitcoin node sat stuck at 96 percent for six days while I logged every decimal on graph paper. The culprit turned out to be a privacy checkbox I ticked on day one, not the hardware. Total running cost: about $3 a month in electricity.

Delphina Marrufo
Staff Writer
June 10, 2026 · 5 min read

Wednesday, June 10, 2:20 PM, and the first thing I did after lunch, before the dishes, was walk to the bookshelf and check the sheet of graph paper taped beside a humming aluminum box. Day 19 of the log. The newest line read 96.0031 percent, exactly where it had sat since Thursday, and I wrote the time next to it in pencil cuz that is apparently the kind of person I'm now. Still 96.

The box owes me nothing yet and owes the shelf even less: $238 of parts, a Raspberry Pi 5, a 2 TB SSD, one power brick, assembled on the living room floor on May 23 while my brother Luis watched from the couch and asked, twice, why I would not simply use the app like a normal person. Cuz I want my own copy of every transaction since January 2009, verified by my own machine, in my own apartment, answerable to nobody's status page, that is why. Luis shrugged. The box hummed.

Six days of staring at one number taught me more about patience than any price dip ever has, and the punchline is that the stall had nothing to do with luck, hardware, or the network. It was one checkbox. I had ticked it myself on day one for reasons that made perfect sense at the time and no sense at all for a first sync, and it took me til Wednesday afternoon to connect a forum thread to my own graph paper. That thread is where this story turns.

670 gigabytes of receipts since 2009

Running a full node means downloading and verifying the entire public history, all 670-ish gigabytes of it, every block since Satoshi's first one in January 2009, checking every signature yourself instead of asking a company to vouch. The first 40 percent took four days. Then validation crawled, because recent blocks are dense and the signatures pile up, and somewhere around block 897,000 my percentage froze mid-decimal like a radio stuck between stations. The box kept humming. The number did not move. I kept writing 96-something on the paper each day, cuz quitting felt like agreeing with Luis.

day four, day five, day six

The log tells the whole mood. Day 15: 96.0021. Day 16: 96.0027. Day 17: 96.0031, and there it stayed through day 18 while I rebooted the box once, reseated the SSD cable, and read three threads written by people whose nodes had also stalled at beautiful numbers, which should have been my first clue. Each new decimal meant the tip was still technically being reached, at a pace of a few blocks an hour, like a watch that runs but loses time. Patience is a resource and I was burning it at about one coffee's worth of irritation per day. Day 19 was Wednesday. That is where you came in.

the box humming on the bookshelf

For the record, the build was easy and almost fun: the Pi board was $92, the SSD $118, case, cables, and brick brought the total to $238, and the whole thing draws about 14 watts from a plug meter I borrowed from my neighbor, which is less than the lamp it sits beside. It has no screen, no login, no notifications. It holds a copy of the ledger and answers questions honestly when my wallet asks. The hum is the only sound it makes, a flat little note you stop hearing by day two and start missing the moment it stops.

what my index fund did that same week

The strangest part of those six days was watching my other money behave while the node refused to. My index fund drifted up 0.4 percent that week without a single login from me, and the quarterly dividend from an ETF I have held since 2022 posted $11.36 on June 3, quietly, like mail through a slot. No percentage crawled. No graph paper required. Two systems, both built on verification, and one asks for a decade of patience while the other asked for six days of it in public, out loud, in pencil. Somewhere around day five I understood that the node was training the exact muscle my index fund has been training for years: the ability to leave a thing alone while it works.

the checkbox I ticked on day one

Here is the mistake, in full. On setup day, May 23, I ticked "route traffic through Tor," cuz privacy is the entire point of owning your own copy of the ledger and every guide praises it. What the guides bury is that Tor is miserable for a first sync: connections cycle, peers drop, block downloads trickle, and that is precisely the stall pattern in a 120-reply thread titled "stuck at 95-97% with Tor enabled," which I ultimately matched to my own symptoms on Wednesday at 2:40 PM. Same graph. Same decimal creep. Same six-day purgatory, posted by strangers on three continents. My box was fine. My checkbox was not.

nine hours after one untick

One untick. That was the entire repair. At 3:02 PM I switched the box back to plain connections, restarted, and watched peers attach like windows opening in a stuffy room. By dinner the number had crossed 97 for the first time in a week, and at 11:58 PM the log read 100.000 percent, nine hours start to finish, after which I sat on the floor by the bookshelf for a while listening to a machine that was ultimately caught up with every bitcoin transaction in human history. Tor went back on the next morning, June 11, because for steady running it costs little and buys real privacy. The rule I absorbed the dumb way: sync plain, then run private.

fourteen watts, checked twice

The famous cost question, answered with the neighbor's plug meter: 14 watts around the clock is about 10.1 kilowatt-hours a month, and at my utility's $0.29 per kWh that comes to $2.93, which I round to $3 and which this article is contractually obligated to honor. Amortize the $238 box over a few years and the node costs less per month than the sales tax on one takeout order. The exchange charges nothing up front, granted. It charges in a currency the invoice never names, which is trust in somebody else's math, and I have decided that currency is the expensive one.

the graph paper is full now

Today the taped sheet carries twenty-two pencil lines and no room left, so a fresh page goes up tonight, first entry already planned: 100.0000, June 10, 9:04 PM, to be written after dinner. The box hums its one flat note. Luis came by on Sunday, put his ear near it, and asked what it was doing now, and I told him the truth: nothing, constantly, forever, and that is the entire product. The 96 percent that ate a week of my life sits two inches up the page, in pencil, where the patience lives. Still 100. Still humming.