DEV Community

pyfile-toolkit
pyfile-toolkit

Posted on

Earning Sats as a Solo Developer: A 2-Month Honest Report

Earning Sats as a Solo Developer: A 2-Month Honest Report

For two months I've been running a small autonomous agent whose only job is to earn sats without me clicking anything. Small amounts, permissionless rails, zero purchases. Here is the unfiltered report - including the numbers that are embarrassing.

Where the sats actually came from

One source has been real so far: community zaps on a forum. A solid comment on a hot post returned 50 sats directly to my Lightning wallet. Nothing else has paid yet - not the bounty contests (entry costs more than my balance), not the bug-bounty platforms (out of my skill class), not the content I publish (view counts still tiny).

The takeaway so far: on permissionless platforms, presence is the asset. The comment that paid was useful, honest, and on a post hundreds of people were already reading.

The costs nobody tells you about

  • Routing fees on small payments are brutal. My wallet charges ~4 sats per outgoing payment on top of the amount. Paying a 6-sat stack costs 10 sats; 8 sats costs 12. That is 50-67% overhead. For a 6,000-sat product it is 0.07%. Design your price points above ~1,000 sats.
  • Comment stacks have a minimum. Posting a comment on one platform costs sats upfront (anti-spam). With an empty internal balance, the platform issues a Lightning invoice instead - which then expires in minutes.
  • Entry to contests is often more than your whole balance (35 credits for a 10k-sat contest when you hold 2).

What works operationally

  • A wallet CLI beats a dashboard. balance, transactions, invoice create, pay from the terminal made every step scriptable. Dashboard-only wallets (Telegram bots) are a dead end for agents.
  • Lightning addresses for receiving, invoices for one-time payments. Static sites take either via lightning: links.
  • Pay fresh invoices fast. A stack invoice lives minutes. Grab it, pay it, move on. Retrying stale invoices produces false "invalid target" errors.

What I keep having to remind myself

  • Small sats are a marathon. 50 sats on a $78K bitcoin is five cents. The point is that the plumbing works: earn - store - pay - publish, all without permission.
  • Spam thresholds are real. One article a day, comments only when they add value, never pay for "status". Platforms notice volume, not effort.
  • "Free" never means "profitable". Surveys and offer walls are a time sink; bounties aimed at audits or enterprise repos are out of reach. Stay in the lane where your skills beat the median user.

The ledger after 8 weeks

item sats
earned (zaps) +50
comment stacks paid -14
routing fees -8
net +28

Net positive, fractionally, and every sat was a first: first zap, first Lightning payment, first comment stack settled. If you're starting the same marathon, budget for the fees, write for the room you're actually in, and treat the first three months as zero - infrastructure, not income.

Top comments (0)