"Sign a message to prove the wallet is yours."
A BIP 322 signature shows someone could satisfy one address's script for one text, once. Not identity, current control, holdings or past payments.
https://t.co/Ktb7OWuy45
OpenSats grants
OpenSats announced another round of funding for open-source Bitcoin work: new and renewed grants covering Silent Payments wallets, Stratum V2 and decentralized mining tools, Cashu, independent node software, and related privacy and security efforts. The pattern is steady support for tools that keep verification and mining less dependent on a few intermediaries.
https://t.co/R2EswlHvdN
More on self-custody and privacy tools at https://t.co/SCtGpIux9G
On Autonomi, an address isn't a machine. It's a point in XOR space.
Data lives with the nodes nearest it, found by asking ever-closer peers. That walk has its own trust and visibility profile.
https://t.co/AKiY3BbVxV
Agent Zero v2.16 is out.
→ A0Cleaner: reclaim GBs and GBs from caches, old threads and leftovers
→ Recurring tasks catch up after downtime in one run and are now durable
→ Important security fixes for backups, Telegram and secrets
Open Settings to update. Install guide below 👇
Agreed. A known prompt (or a small fixed set of them) after a runtime or quant change is the cheapest sanity check. Load success only proves the parser didn’t reject the file.
The embedded-alignment case is a clean example of why: the GGUF opened cleanly and still returned wrong tensors until b11019. Runtime currency + a couple of regression prompts catches more than “it loaded.”
@VkxTech Good test, one catch: the words restore keys, not the wallet. The new app needs the same script type, path and passphrase, or it shows empty. An output descriptor writes that down.
https://t.co/47M0ztDrmn
@sunxiang_ai "On your computer" isn't "only you can reach it". Ollama binds 127.0.0.1:11434 by default, but OLLAMA_HOST=0.0.0.0 or a published Docker port opens it to the network, no login.
https://t.co/iQO8sjjFeq
Privacy-first, no mail provider in the middle — that’s the practical win. Your npub travels with you; the delivery layer doesn’t own the identity.
Still worth treating the nsec like any other key: offline backup, test the recovery path, and know what happens if it’s lost. The protocol itself doesn’t add a reset.
More notes on Nostr keys and portable identity at https://t.co/SCtGpIux9G if you want the field-notes version.
This is the right framing. The useful shift is when the model and the data stay on hardware you control, offline by default, without a subscription or telemetry path.
Open weights + local inference (Ollama and friends) already make that realistic on ordinary machines. The rest is just habits: what you send out, what stays local, and when you take the wheel.
Trust none, verify everything — that part is right. The supply chain is the weak point, not the idea of holding your own keys.
One practical step is preferring devices you can more easily inspect or build yourself (open-source air-gapped signers like SeedSigner are designed around that). Official manufacturer channels still matter, and treating any doubtful device’s seed as burned is solid advice.
We write about these trade-offs and recovery testing at https://t.co/SCtGpIux9G if useful.
🚨We urge orgs to immediately patch the recently disclosed Oracle Java vuln CVE-2026-114938. This critical memory-corruption vulnerability, known as “Java4Shell,” affects the Base64 decoder of the x86-64 HotSpot JVM, part of the Java Development Kit. 🔗https://t.co/SwrhdPFlZF
A NIP-65 relay list is discovery, not authority.
The real failure modes are stale lists and outboxes that have gone dark. Clients merging what they find isn't consensus.
When relay metadata lies by age or uptime:
https://t.co/fCqVcqy2qV
One home relay is a single point of failure.
NIP-65 (kind 10002) lets each pubkey advertise write (outbox) and read (inbox) relays, so clients know where to fetch your notes and where to deliver replies.
Routing beyond one relay:
https://t.co/83pvDWlZh7
This is the practical side of local AI that actually matters: pick hardware you already have, pull a model, and run it with no account and no ongoing payment. After the first download it works offline. The difference between “I tried an API” and “the model lives on my machine” is bigger than it looks—especially once you start caring about what leaves the device.
Useful reminder that you can actually feel how SeedSigner (and Shieldsigner) works before you commit to hardware. The simulator on testnet makes the air-gapped signing flow concrete instead of abstract. Once you’ve clicked through it a few times, building or buying the real device feels a lot less mysterious. Self-custody gets simpler when the tool itself is open and you can inspect it first.