Ways to give. All optional. None require an account.
The value-for-value reasoning is on the value page;
this is the how. Direct channels go to me. Referrals go to products that
run this stack. Time and talent count too. The book is forthcoming.
// direct
Pay directly, no platform in between
01
Lightning Address
Pay-what-you-want over Bitcoin Lightning. A few sats say "this saved
me time." Every article also has its own zap button in the footer, so
you can pay the specific post that helped, from any Lightning wallet,
no Nostr account needed.
If your browser blocks the wallet link, scan this or use Copy above.
02
Nostr (comments + follow)
Zapping no longer needs Nostr: any Lightning wallet works, here or
from an article footer. Following works over Nostr or plain
RSS. What Nostr alone still does is comments,
which land on the relays, not on a platform.
Buying the book is the most direct way to pay for this work and the
one channel that doesn't exist yet. When the draft becomes a release,
this card flips to a Lightning pre-order with a per-format download.
Until then the signal that says "tell me when it lands" is a follow
on Nostr.
All four are products I use daily. Same price for you, small bonus for
me. No KYC on any of them. Inside articles, the same links are auto-marked
at their first and last mention with a Bitcoin-orange ₿Affiliate link. You support sovgrid at no extra cost to you. See /support. badge. The
disclosure block at the bottom of this page explains what the marker means.
01
Alby
The Lightning wallet I use daily for V4V tips and micro-transactions.
Frontier models (Claude, GPT, Gemini) over an OpenAI-compatible API,
topped up per query with Bitcoin Lightning, no account. The no-KYC
cloud fallback behind the local stack.
Why and how.
Not everything is sats. Two channels carry real weight.
Talent. Spotted an error, broke a setup guide, or have a
better fix, benchmark, or counter-take? Nostr for blog-article corrections
and discussion, GitHub Issues for the two public OSS repos (sovereign-mcp,
vps-healthcheck) where a reproducible bug or a PR is the right shape. Every
fix makes the next article better, and contributors get credited.
Time. A repost moves the project further than a small zap,
because it lives on discovery. Copy this line and paste it anywhere:
Self-hosted AI on a DGX Spark. No cloud, no tracking, CC BY-SA: https://sovgrid.org
A ₿Affiliate link. You support sovgrid at no extra cost to you. See /support. after a link means it is an affiliate link to a product I
actually run (Alby, BitBox02, Flokinet, ppq.ai). Same price for you, a small
commission for this site. A plain ↗
just marks an ordinary external link opening in a new tab, with no affiliate relationship.
No tracking pixels, no analytics on click. Plain HTTP redirect through the
vendor's own affiliate URL, with rel="sponsored" set. Hover or
keyboard-focus the ₿Affiliate link. You support sovgrid at no extra cost to you. See /support. after any affiliate link to see this note.
How links are marked on this site
Every link in the writing tells you where it goes before you click.
Each kind has its own cue. The live examples below are real links, so
you can see and test each cue right here:
Internal, stays on this site: green and underlined,
no marker. Example:
Start Here.
Learn term, a jargon word explained on this site:
body-coloured with a dotted underline and a small ⓘ, no new tab. It
links to a plain-language entry, less a link to chase than a "there is
a definition here" cue. Example:
OOM.
Browse them all under Learn.
External, leaves the site: body-coloured, underlined,
ends with a ↗ and opens in a new tab. Example:
the Bitcoin whitepaper.
Affiliate, a referral to a product I run: the link is
green and underlined, followed by a distinct Bitcoin-orange ₿ badge (no ↗). Example:
Flokinet₿Affiliate link. You support sovgrid at no extra cost to you. See /support..
Anchors and controls, in-page # jumps and
toggles like this expander: neutral, no marker. They are not navigation
to other content, so they deliberately do not look like internal links.
Example: jump to this section. Buttons and
call-to-action links keep their own button styling and carry no marker
either.