Primary source — Tether's own announcement (official ticker is GEL₮, and they're calling it Georgia's "official stablecoin"):

https://tether.io/news/tether-and-the-government-of-georgia-to-launch-gelt-the-official-stablecoin-of-georgia/

The National Bank of Georgia has confirmed it (President Natia Turnava's statement), and per Georgian press on 27 May, Tether has already filed the issuance application under the March 2026 rules requiring 100% reserve backing.

Ok!! Yes I am currently full SSD I want to keep spinners for veracrypt for personal experiments.

No pi no, thinkcenters nano, elegant. I like it.

Btrfs

Ok good to know!!

Hum... Some AI-files specifically all hooks, the MCP's, the indexation for AI, this sort of stuff. Syncthing config files.

Architectual stuff mostly.

Snapshot at each boot
One per day
One per week
One per month
One per year

With auto-trim.

Works really well so far, no issue. With slightly custom-GRUB it pairs well.

But then again pure impro.

And I am not selling heavily modified laptops, I just mention to people this feature without making it like it's the product of the year/too ground-breaking.

But it is enjoyable. Harder to break things.

🚶 → 🏔️

Two years ago I was suicidal in Canada. Today I'm on a porch in Tbilisi starting the fight for the sovereign individual — alone, no one I know around, strange country, my own way. AI didn't fix the underlying thing. It just made the gap between intent and shipped artifact small enough that the building became the way through.

The thesis behind every layer: sovereignty = owning your substrate end-to-end so no third party mediates your money, identity, communication, learning, memory, ideology, or hardware.

My topbar clock rotates three glyphs every 15 seconds: 🌍 ¬ ∞ / ₿ ¬ ∞ / ⏳ ¬ ∞. Earth is not infinite. Bitcoin is not infinite (21M cap, hard-coded). Time on our hands is not infinite — which greatly gives it value.

VIRES IN NUMERIS. Decentralize or die trying.

@Hof / House of Freedom — Tbilisi 🇬🇪 ⚡ ₿

📜 Full essay (with all images, archived): naddr1qq0k...

🎯 THE ENDPOINT — Self-hosted AI joining the local mesh

My very last tech-goal.

A self-hosted LLM on some device I'd own and have at home, joining the private mesh as just another peer. Ollama + Open WebUI + SearXNG private search + Whisper dictation moving CPU → GPU. Once it lands, my daily AI workflow runs on MY silicon, indexes MY corpus, and never sends a token over the public internet.

The sovereign-compute debate (which my own arena produced) set a specific window — wait until 2027-2028 post-Blackwell. Specific window, debate-verdicted, not vibes.

But the real end goal isn't just "private LLM I query." It's an AI that becomes the permanent operator of the stack. Always-on, auth-gated through the same YubiKey + airlock perimeter as everything else, watching every node, managing every update, healing what it can catch before I see it. Self-updating. Self-maintaining. Self-healing. Not aspirationally — operationally.

What stays external — named consciously, not denied: food (biological), electricity (grid), public internet (only for crossing the mesh, not operating in it), and the country providing the substrate. Everything above that layer is mine.

☁️ CURRENT DEPENDENCIES

Here on Nostr, I think we will all agree on one thing.

There is no cloud. Just other people's computers.

As you noticed, everything is on my own stuff. However, I am for now heavily dependant on AIs I do not own or control = Claude API for the brain + a few inference calls to xAI/Gemini/DeepSeek for the debate arena. That's it.

Privacy on the AI layer specifically is a half-lost cause for now. The models live in someone else's datacenter. I send prompts that contain context about my life. I'm aware of this. The endpoint addresses it.

And honestly — AI has been my therapist for a stretch when I was on the move with no fixed support network. Privacy on that is straight out of the toilet, but it was that or nothing, and "that or nothing" is how a lot of survival actually works. Self-hosted endpoint solves it eventually. Until then, named openly.

🍷 THE FINE WINE THESIS

The doctrine I operate by:

▸ Acceleration = ignorance → capability → output compounding via AI. Closed-loop test: does it ship a tangible artifact? If yes → build. If self-referential → kill.

Most custom code rots in 5 years — abstractions move, dependencies break, the maintainer is gone. My stack inverts this because the artifacts I'm accumulating are NOT implementations. They are context that aligns AI to me.

43 SKILL.md files. ~50 memory files. 27 control-panel pages. ~30 architecture docs with debate verdicts. The CLAUDE.md constitution.

Today this corpus tells Claude how I want X done. When AI is 10× more capable in 2028, the same corpus will let it execute the methodology with zero supervision. A vanilla Claude in 2028 will be impressive in a vacuum. A 2028 Claude given my 2025-2026 corpus is an AI that operates AS me, not approximating-me.

The more powerful the AI, the easier — and the less I require of it. The artifact I ship today is leverage for next year's AI.

🍷 Fine wine.

🛡️ GUARDRAILS = SOVEREIGNTY + RESILIENCE

Guardrails aren't constraints ON the system — guardrails ARE the system's sovereignty and resilience. They guard the acceleration doctrine from drift. Without them, every AI session re-discovers (and re-fails) yesterday's lessons.

43 skills frozen in ~/.claude/skills/ — methodology that survives the conversation. A skill captures HOW I want X done so next month or next year doesn't re-derive it.

A multi-model debate arena — Grok attacks, Gemini defends, DeepSeek arbiters. Different model providers on purpose so they can't groupthink. Every load-bearing architectural decision in the stack has a verdict file behind it. I type /debate <topic> and the arena spins up, runs four sequential phases, returns a verdict.

Hooks catch failure classes — the substrate enforcing its own discipline. Honest disclosure: my hooks are still approximate. They misfire sometimes. I'm refining them constantly. Not entirely satisfying yet. But the trajectory is clear.

Multilingual forum intelligence skills crawl Zhihu/Weibo/RU/JP/EN forums, rank posts against my tagged theses using Bayesian weighting where contradiction is higher signal than confirmation. Information intake shaped by my priors, not by what an algorithm thinks I'll click.

This is the layer that separates "AI is making me faster" from "AI is making me coherent."

🛡️ HOW I CONTAIN THE AI — Airlock + Physical Key

Now the obvious question: if the AI has 240 tools and reads my disk, how do I keep it on a leash? Two answers, stacked — software on top, hardware underneath.

🛂 AIRLOCK CONTROL — the logical gate

The AI Airlock decides what Claude can read on my disk once any session is open. Four access modes (Full / Restricted / Paranoid / Off), explicit blocked-paths editor, kernel-level immutability on the constraint files (even root can't edit them without unlocking first), Deploy Mode toggle that gates mutating actions (audit-logged), one-click kill on remote AI access.

🔑 YUBIKEY — the physical root under the airlock

The Airlock is software. Software is mutable. The anchor is hardware.

In February 2026 I killed the password slot on my LUKS vault. The drive holding ~/Hub, Vaultwarden master, GPG/SSH keys, every API token — no longer accepts a passphrase. Not 2FA. Substitutive — the token IS the key. Pull the key out and the screen locks, vault closes. Hardware is the dead-man's switch.

The punchline: combining the multisig backbone with the YubiKey perimeter, the whole stack — generational wealth, digital infrastructure, AI cognitive layer — sits on two physical roots of trust: titanium plates spread across countries, and a 1.5cm aluminum stick on my keyring. The threat I'm defending against is duress-and-compromise, not loss. People who don't understand call it fragility. People who do call it the entire point.