New in the Sovereign Starter path: the recovery step.

The path promises you can lose a laptop and still reason about recovery. That depends on a backup, and a backup is only a copy of a secret. Recovery is the procedure that turns it back into keys, on a new device, under stress, maybe done by someone other than you.

What the words don't carry:
• A BIP 39 passphrase. Every passphrase makes a valid wallet, so a typo at restore just shows an empty one.
• The wallet definition: script type, derivation path, whether it was one key in a multisig.
• Labels. Bitcoin Core's own guide: "Metadata cannot be retrieved from a blockchain rescan."

Monero's 25-word seed and the 16-word form aren't interchangeable, so write down which one you have.

The drill: restore on a clean device, compare the first receive address, write down anything you had to look up, then wipe it.

Never type real seed words into a website, chat or "validator" tool.

https://cryptodecentral.co.za/notes/seed-backup-is-not-recovery
Path: https://cryptodecentral.co.za/guides/sovereign-starter

#bitcoin #monero #selfcustody

A threat model is not a fear list.

It's one page: the secrets you protect (not the apps), the realistic adversaries, the one or two outcomes that would actually ruin you, and the costs you accept. Its real job is telling you what you can safely ignore.

It now opens the Keys module of Sovereign Starter.

https://cryptodecentral.co.za/notes/threat-model-one-page

Release radar, week of 19 Oct. Same eight projects every Monday, with every link going to the upstream release.

Shipped:
• Monero v0.18.5.4: bug-fix release with the new DNSSEC root trust anchor
• Autonomi Node v0.23.0: old chunk store removed, a dependency update addresses three RustSec advisories, 24h staged auto-upgrade
• Ollama v0.40.4 to v0.40.6: --ask decision models, Nemotron 3.5, a Windows orphan-process fix

No release: Core Lightning, LND, LDK, NIPs. Bitcoin Core 32.0 is still rc4.

https://cryptodecentral.co.za/notes/release-radar-2026-10-19

Local AI on a PS5
A jailbroken PlayStation 5 is now running llama.cpp as a native app that uses the GPU. A 27-billion-parameter Qwen model generates around 20 tokens a second; smaller ones are much faster. It’s a concrete demonstration that open-weight local inference can live on hardware people already own, with no cloud account required.

https://github.com/cobanov/PS5LM #opensourceAI

Monero FCMP++
Monero’s next privacy step is still moving. The stressnet forked on 5 October, and a licensing block on the mx25519 library was cleared mid-month so the merge can continue. Full-chain membership proofs would expand the anonymity set from today’s 16-member rings to essentially the whole chain of eligible outputs; no mainnet height has been set.

https://www.geekboots.com/story/monero-fcmp-release-date

More plain-language context: cryptodecentral.co.za

LayerTree
Lightning Labs published a design that lets thousands or millions of people share one Bitcoin output. Balances sit in an off-chain Merkle-sum tree; covenants keep the operator from taking funds, and any member can still leave alone in a single transaction whose size doesn’t grow with the group. It needs opcodes that have been proposed but aren’t active yet, so it’s research with a reference implementation rather than something you can run today.

https://layertree.tech/

Monero FCMP++ stressnet

Monero’s third beta stressnet for Full-Chain Membership Proofs (FCMP++) and the CARROT addressing changes has been running, aimed at moving the anonymity set from today’s fixed ring of 16 up to essentially the whole chain history. No mainnet date is set; it is still testing and audit work. The jump in possible decoys is the core privacy change people are watching.

https://www.getmonero.org/resources/roadmap/

Meta’s Muse Spark Open

Meta released the weights for Muse Spark Open, an 816-billion-parameter model (42 billion active) with a million-token context that is built for coding and longer agent tasks and can run on two Apple M5 Ultra Mac Studios. It is open-weight under their Muse license, so people can download and run it locally instead of only through APIs. Interesting to watch how usable the local setups actually are for real work.

https://research.meta.ai/blog/muse-spark-open

More local and open tooling coverage at cryptodecentral.co.za

LayerTree proposal

Lightning Labs put out a design where one Bitcoin output can hold balances for up to a million people, tracked off-chain in a Merkle-sum tree, with covenants so anyone can leave in a single transaction without timeouts or needing to stay online. It still needs opcodes that aren’t activated yet, so it’s a paper and reference code rather than something you can use today. Curious what the trade-offs look like once those opcodes land.

https://layertree.tech/

Sovereign Starter got a rebuild: 5 modules, 10 beginner steps, a quick check after each.

1. Keys – verify, then sign offline
2. Money – receive-only Lightning, default-private money
3. Nostr – relay lists and what they get wrong
4. Storage – encryption and immutable chunks
5. Local AI – where your data actually lives

No account, no cookies, no tracking. Four new notes land next week to fill the gaps.

https://cryptodecentral.co.za/guides/sovereign-starter

Running an agent in Docker is the starting line, not the boundary.

With Agent Zero, what actually decides what it can reach is the bridges you enable:
- where each model slot sends data (chat, utility, embedding, browser, vision)
- host file read/write (F3) and code execution (F4)
- Docker browser vs your own browser, and whose cookies
- every plugin and MCP server

List those and you've got your real boundary. Full map, checked against v2.14:
https://cryptodecentral.co.za/notes/agent-zero-container-is-not-the-boundary

#localAI