Refusing the Subscription Trap: A Year of V4V Lessons
The V4V revenue from sovgrid as of the most recent audit on 2026-05-04: zero sats received. That is not a typo. The Lightning address works, the QR code displays correctly, the test transactions clear from my own wallet, and the channel can receive payments. Readers have not tipped. This is the honest version of V4V at six months.
The article is not a how-to-make-money-with-V4V piece because that would require V4V to have made money first. The article is a what-I-have-learned piece, and the lessons are mostly about the architectural value of the channel versus the dollar volume of the payments.
Quick Take
- The architectural fact: the V4V channel exists and works, real and worth something independent of the dollar volume.
- The dollar volume at six months: 0 sats. Not failure, not success; the channel exists, the audience is not tipping yet.
- What V4V is good for, even at zero volume: the discipline of refusing subscription, the sovereign-payment signal to the audience, the technical readiness for the future state where readers do tip.
- What V4V is not good for: replacing a subscription business model. At six months and zero sats, V4V has not yet shown a revenue line.
- The lessons, six honest ones below: about audience, about discipline, about timeframes, about what V4V actually signals.
The architectural fact
The Lightning address cipherfox@sovgrid.org accepts payments. The QR code in the footer of every page on sovgrid.org displays a working Lightning invoice. The Alby ↗ Hub node has the channels open, the balance is real, and a tip would clear in under a second.
This is the architectural fact. It exists regardless of whether anyone has tipped. The fact is worth something for three reasons:
The fact is the signal that this site is not running on advertising. The audience sees the Lightning address and infers (correctly) that the operator is not selling them to advertisers. The inference is part of why the audience is the kind of audience that reads sovgrid in the first place.
The fact is the signal that the operator has the operational discipline to run a Lightning node. Running a node is real work. The audience that knows what Lightning is can read the signal and respect it.
The fact is the technical readiness for the future state. If, in a year, the audience does start tipping, the channel is ready. The work to make it ready is paid once; the readiness is permanent until I shut the node down.
The dollar volume at six months
Zero sats received.
This is the honest number. The temptation, when writing the V4V article, is to round up to “a handful” or to compute “the cumulative value of audience engagement is implicitly thousands of dollars.” Neither is the honest number. The honest number is zero, and the article has to start from the honest number.
The reasons V4V has not converted are not mysterious. The audience for sovgrid in 2026 is small in absolute terms (under a thousand visitors per month from the dashboard data). The fraction of that audience that has a Lightning wallet and is comfortable tipping is smaller. The fraction of that fraction that has actually tipped is zero.
This is fine. Six months is early. The channel exists; the audience is growing; the conversion will happen on its own timeline or it will not.
The mistake to avoid is treating the zero as a verdict on V4V as a model. It is not. It is a data point on this specific site at this specific time. Other sites with larger audiences (Citadel Dispatch, Stacker News, several Nostr-focused content sites) report V4V volumes in the tens to hundreds of euros per month. The mechanism is not broken; the specific audience-conversion at sovgrid scale is not yet there.
Six lessons
Lesson 1: V4V is a discipline, not a revenue model in the first year. The decision to refuse subscription pricing is a posture choice. The posture has value independent of the dollar conversion. The temptation to switch to subscription is real; the discipline of staying with V4V is the practice that builds the long-term audience-relationship the subscription model would have damaged.
Lesson 2: the audience that tips is the audience that has Lightning wallets. The sovgrid audience overlaps significantly with the Sovereign Engineering community, the Nostr operators, and the Bitcoin-adjacent technical readership. These groups have higher Lightning-wallet penetration than the general internet. The conversion rate is still low because tipping is a small-volume behavior even among the wallet-equipped audience.
Lesson 3: the V4V QR code is part of the brand, not just a payment surface. Visitors who do not tip still see the QR code. The code signals the site’s posture. Removing the code to reduce footer clutter would lose the signal even more than it would lose the (currently zero) tip volume.
Lesson 4: the timeframe for V4V to compound is longer than expected. Other operators who have published their V4V revenue over multi-year periods (Marty Bent, Matt Odell, Gigi) show curves that start near zero, stay near zero for the first year or two, and then begin to compound as the audience density and the wallet-equipped fraction both grow. Sovgrid is in year zero of this curve. The shape of the curve in years one and two is the actual test of the model.
Lesson 5: V4V tips are not the only Lightning revenue. The sovereign-AI consulting practice will accept Lightning for invoice payments at the customer’s option. The book pre-order page (when it opens) will accept Lightning. The MCP tool calls in Phase 3 will require Lightning via L402. The V4V tip volume is one column of the Lightning-revenue line; the other columns may not be zero.
Lesson 6: refusing subscription is a decision about who the customer is. A subscription model says “the operator’s revenue is more important than the buyer’s flexibility.” A per-call or V4V model says “the buyer’s flexibility is more important than the operator’s revenue smoothness.” The choice signals which side of the trade the operator is on. The signal matters even when (especially when) the immediate revenue is small.
The honest accounting: what V4V is not
V4V is not a substitute for an audience. The Lightning address on every page of sovgrid.org is real and functional, yet the cumulative total received as of May 2026 is zero sats across 12 months of operation. That is not a caveat buried in footnotes; it is the headline number. The reason the number is zero is not a broken payment rail but a small and still-forming audience. V4V scales with audience density, and in year one the density is not there yet.
V4V is not fast. In my case, the first year is a negative-return experiment in terms of direct revenue. The posture pays in audience signal, not in sats. The readers who understand the Lightning address are a specific subset; the conversion from “understands the signal” to “acts on it” takes longer than 12 months for most content sites of this scale, which is why the multi-year curves from operators like Citadel Dispatch and Stacker News are the correct reference frame, not the 6-month or 12-month snapshot.
V4V is not passive income. Running the Alby Hub node takes real operational hours. The Lightning Address visible site-wide required weeks of setup across DNS, Caddy, and channel management. The infrastructure exists because I chose to build it, not because V4V requires less maintenance than a Stripe subscription button. In practice, the operational overhead is comparable; the difference is that the sovereign-payment posture survives platform risk, which Stripe does not.
V4V does not work for audiences that lack Lightning wallets. The sovgrid readership skews toward technically sophisticated Nostr and Bitcoin-adjacent readers, which is a higher Lightning-wallet penetration than the general web. Even so, the fraction that has tipped is zero so far. For a publication targeting a mainstream audience, the caveat is sharper: the Lightning-conversion funnel is thinner than the trust-funnel for a Substack subscription, and pretending otherwise is not honest.
What the publication of this article changes
Writing this article is an explicit acknowledgment that V4V at sovgrid has not converted to revenue at six months. The acknowledgment is part of the engineering-honesty discipline; the alternative would be to write a triumphant V4V piece that the data does not support.
The publication of the article might also produce its own V4V volume: a reader who reads the lessons above might tip in solidarity with the posture, or might not. Either outcome is information. The article is not a tip-funnel; the article is a lessons piece. If readers tip, the data point shifts; if they do not, the lessons stand.
The follow-up article at the twelve-month mark will publish the cumulative V4V volume from this article’s publication date onward. That number is also information; it tells the next iteration of sovgrid which lessons were correct and which were rationalizations.
Where this fits
For the broader pricing-design argument, see How I Priced Sovereign AI Consulting and Why I Charge Per Tool Call, Not Per Subscription. For the year-one revenue context, see Year One on a DGX Spark: Real Revenue, Real Numbers, Real Lessons. For the Lightning operation, see The Operator’s Guide to Self-Hosted Lightning.
tip in sats, or do not
The QR code is in the footer. If the article was useful, a small tip is appreciated. If it was not, that is also information. The honest number to date is zero, and the next number is whatever the audience decides.