Twitter Spaces
Through 2021Personal
Debated Bitcoin maximalists on Twitter, then on Spaces once it launched. After that it was mostly listening, with occasional debate.

I port Bitcoin’s public tools onto Litecoin. When I build AI, it answers only from sourced material, records what it couldn’t answer, and shuts off at a hard spending cap.
Foundation project board, $122k paid out from donations and matching as of Sep 2026. Chat capped at $5/day.
Review Litecoin Dev Kit, not independently audited.
On their own sites. Status matches the chronology.
The same few rules run through every project. Details for each are in the chronology below.
I port proven Bitcoin tools instead of reinventing them. Litecoin Dev Kit keeps the bdk_* API of Bitcoin Dev Kit, and the research kits fork Bitcoin Research Kit.
Models draft the code, ports, tests, and docs, which is why the work moves fast: the Dogecoin kit went from first scaffold to merged-mining parsing, Dogecoin economics, and its own branding in three days. Each port is checked against its upstream test suite, the Dev Kit has its own MWEB tests, golden tests pin expected output, and results are matched against Litecoin Core. When it’s unclear what to test, I ask subject-matter experts.
The model stays on material that was sourced. NKMAG.com was drafted that way, and Litecoin.com/chat answers only from Foundation content.
When the chat can’t answer from its content, the gap is recorded for editors. A hard spending cap stops it before costs run on. Source: Litecoin.com-Chat.
Prototypes are labeled as prototypes. Personal research is kept separate from Foundation contract work, and the LitecoinDevKit org is neither.
A full date marks a domain registration. A month, a year, or a span marks when that work started.
Through 2021Personal
Debated Bitcoin maximalists on Twitter, then on Spaces once it launched. After that it was mostly listening, with occasional debate.
2022Personal
Articles drafted from sourced material in OpenAI’s developer playground, as ChatGPT launched. Approach keeps that rule: the model stays on material that was sourced.
Feb 2023ArchivedPersonal research
Ordinals on Litecoin
Tried the port first, asked other devs, then opened a bounty to port Bitcoin Ordinals to Litecoin with 5 LTC. Litecoin community members raised it to 22 LTC. Anthony Guerrera (ynohtna92) landed the first port in about a week. Built the OrdLite explorer on it.
Mar 15, 2023ShippedFoundation contract
Webflow, The Giving Block
lite.space started as a reskin of opensats.org. The backend and multisig were set up with Litecoin Foundation directors. After the Foundation’s 501(c)(3) and the Litecoin.com domain, it moved to Litecoin.com/projects.
ArchivedPersonal
Transcription, embeddings, semantic search
Transcribed audio and video, summarized it, and made it searchable with timestamped results. It ran, then went unmaintained once the upkeep outweighed the use, and the source stays private.
Dec 2025ShippedFoundation contract
Hybrid search, query rewrite, semantic cache
Answers only from Foundation content. If the content doesn’t cover a question, it falls back to a clearly labeled web search and logs the gap for editors. It does not invent org facts.
Jul 1, 2026ResearchPersonal research
Litecoin Core, MWEB
Fork of Bitcoin Research Kit. Self-hostable from a Litecoin Core node. MWEB-aware.
Jul 15, 2026ResearchPersonal research
AuxPoW
Same method as the Litecoin kit. It reads merged-mined blocks (AuxPoW), where Dogecoin’s proof commits to another chain’s work.
The research kits are one method applied twice. Litecoin Dev Kit is the harder port: native MWEB on a thin alias of Bitcoin Dev Kit.
Aug 5, 2026PrototypeLitecoinDevKit org
bdk_* crates, UniFFI, Tauri
Thin alias port of Bitcoin Dev Kit, not independently audited. Crates keep bdk_* names and bitcoin:: paths; the bitcoin dependency is aliased to the Litecoin crate.
Oct 2026LitecoinDevKit org
Fork of Wizardsardine Liana for inheritance and loss protection. Not affiliated with Wizardsardine. A transparent vault is planned to recover with a Script timelock. MWEB recovery is planned as height-locked packages plus an heir backup: the same features, with different enforcement.