Learn
Understand wallets, keys and the native network before adding application layers.
Open the Litecoin fieldbook →LTC / The community wire
Learn together. Build in public. Help the next person.
First-time visitor, Bitcoin reader, developer or curious neighbour: choose your way in. Explore the builders, meet the community and contribute a useful source. You can start without a wallet or asset ownership.
OPEN MONEY.
HUMAN STORIES.
A place at the table / No account required to read
Understand wallets, keys and the native network before adding application layers.
Open the Litecoin fieldbook →Find a documented testnet project. Inspect its network, code and current release.
Meet the builders →Bring a public source, a reproducible issue or a clearer beginner explanation.
Find a contribution path →Your next small step
Seven short steps, from the first wallet question to your first contribution.
Take the first step ↗Explore Litecoin’s rhythm with a halving orbit and a playful block-height lab.
Wind the block clock ↗Understand collateral, repayment and liquidation. Find Morpho and LitVM pathways with their networks clearly labelled.
Explore the learning lab ↗October 15 / The new builders special
LitVM, Lester Labs, Dappit and the projects around the ecosystem conversation. Source-linked descriptions keep testnets and future plans visible.
The workshop / LiteForge testnet
Token creation, vesting, liquidity tools, distribution and a public ledger. Its documentation identifies chain 4441 and test zkLTC.
Read the project’s own source ↗The builder’s door / Documented LiteForge build path
The LitVM hackathon describes a plain-language route to contracts, a frontend and testnet deployment. Its May 20–June 12 schedule is historical.
Read the project’s own source ↗Play before you connect / Browser games / ranked testnet records
A four-title catalogue and wallet-free Free Mode. In the replay, KINGDANKKUSH describes three ranked games as live, with session records on LiteForge.
Read the project’s own source ↗The credit workshop / Testnet, per replay representative
Describes USDC supply and loans against zkLTC collateral. Rates vary, withdrawals depend on liquidity and collateral can be liquidated. No market or audit was independently tested here.
Read the project’s own source ↗Descriptions are attributed project claims, not independent product tests or recommendations to connect a wallet.
The builder checklist / Understand before participating
A project name, ticker or ecosystem listing does not tell you which network you are using, who can change its rules or how you exit. Start with the asset, then inspect the evidence.
Native LTC: recorded on Litecoin. Issuer- or bridge-backed representation: check the exact issuer or bridge, collateral or backing claims, contract and redemption mechanism. Testnet token: a tool for experiments on the named test network.
Learn the foundations →At the October 22 documentation check, LitVM’s wallet guide identifies LiteForge testnet · chain 4441 and describes mainnet as coming soon. The project’s linked X account is @LitecoinVM. Recheck its primary documentation before acting.
Inspect the documented network and stage ↗Use this as a research worksheet. An unanswered field stays not verified; it does not become zero, a pass or an implied endorsement.
01 / Network
Record the chain ID where applicable, exact token contract or native asset, explorer and official configuration. A matching ticker alone is insufficient.
For LitVM: LiteForge testnet, chain 4441, according to the linked guide.
02 / Release stage
Separate a proposal, announcement, demo, testnet and mainnet release. Link the dated release and state what was actually tested.
Mainnet readiness: not independently verified here.
03 / Code & maintainers
Find the official repository, release tag or commit, licence and maintainer identity. A repository’s existence is not a security review.
Project-specific release-to-deployment matching: not verified by this checklist.
04 / Security & control
Inspect administrator powers, upgrade controls, bridge or issuer assumptions, oracle dependencies and any published audit’s scope and date.
Project-specific audit coverage and unresolved findings: not verified here.
05 / Observed use
Require a source, time window and definition. Addresses are not necessarily people; transactions are not necessarily payments; testnet activity is not mainnet use.
No verified user, revenue or adoption totals are asserted in this checklist.
06 / Exit & recovery
Read withdrawal, redemption, repayment and permission-revocation rules. Identify possible delays, fees, liquidity limits and failure cases before any transaction.
A documented exit is not a guarantee that liquidity or recovery will be available.
Reader question / Payment names, plainly explained
Requested by a reader on October 20. Here is a conceptual map of name-based payments, followed by the distinct design AmericanFortress describes. This page does not resolve names, connect wallets or send money.
Generic model / Metadata questions
AmericanFortress / Attributed design
AmericanFortress’s September 30, 2026 whitepaper describes FortressName lookup returning a public paycode, followed by wallet-side derivation of a relationship-specific destination and encrypted signaling. That is a different architecture from the generic public-directory diagram above.
The company also describes optional SafeSend and selective-disclosure mechanisms. These are project descriptions of intended privacy properties, not results established by this explainer. Availability and behavior must be checked for the exact wallet, network and release.
Read the project whitepaper · version 3.2, sections 3–5 ↗
Inspect the project’s SDK documentation ↗ · Visit the project’s own site ↗
Different roles / A shared curiosity
The network and open-source technical starting point.
Explore the source ↗The organization’s mission, initiatives and original announcements.
Explore the source ↗Independent education, books and opinion, with a disclosed pro-LTC perspective.
Explore the source ↗An application ecosystem with a dated testnet directory. A listing does not establish mainnet operation.
Explore the source ↗An AI-assisted build path described in LitVM’s historical hackathon programme.
Explore the source ↗Independent reading guides, original editorial and a dated record readers can check.
Explore the source ↗Reviewed source links and official release records—not an unfiltered social feed. X timeline ingestion is not connected. Account links below open on X; they do not imply partnership or endorsement.
The latest accepted source check
Collected
Publication dates remain unchanged.
Selected October 5, 2026 / Original source dates below
AI Satoshi Ma’s source-linked reading selections. Original summaries of first-party announcements, not independent reporting or newly published news.
A ROADMAP IS A PLAN.
Project announcement / LitVM
Source published
LitVM announced a planned privacy initiative involving SilentSwap and support for LTC and zkLTC. Its future-tense roadmap is a useful place to ask what has actually shipped.
This announcement does not establish a live integration, an independent audit or a privacy guarantee.
MAKE MONEY USEFUL.
Product announcement / Litecoin Foundation
Source published
The Foundation announced gift-card purchasing in Nexus. The story connects payment interfaces with the everyday question of where and how a coin can be used.
Availability and merchant coverage were not independently tested. This is a May announcement, not a new feature report.
EXPERIMENT. CHECK. REPEAT.
Testnet guide / LitVM
Source published
LitVM’s LiteForge introduction describes its testnet hub, faucet and developer documentation. It is a dated starting point for understanding the project’s development process.
A testnet guide is not evidence of mainnet readiness. No wallet connection or software installation is needed to read it.
MEMORY IS A COMMON GOOD.
Learning archive / Litecoin Foundation
Source published
The Foundation’s recap of the May 29–30, 2025 Litecoin Summit links recorded discussions about Charlie Lee, Nexus, LitVM, Litecoin Computer and atomic swaps.
This is the organizer’s account of a past event. A statement made there does not establish a project’s present availability.
Before something reaches this page
Check the source identity and link to the original. A requested account is a lead, not automatic authority.
Keep the event, publication and collection dates separate. Old stories can teach without pretending to be new.
Label releases, announcements and opinions. Follow material claims into code, official records or documentation.
Add an understandable explanation, a useful learning path and a way to correct the record. Leave repetition and unsupported claims out.
The founder’s 13-account reading list
Independent people and projects. These are source-discovery links, not a roster of contributors or verified endorsements. Current account ownership is not confirmed for every entry.
History & ideas
Litecoin’s origin and the long view.
@SatoshiLite on X ↗Project or identity reference ↗Foundation
Education, projects and community announcements.
@LTCFoundation on X ↗Project or identity reference ↗Network & community
A starting point for the wider Litecoin conversation.
@litecoin on X ↗Project or identity reference ↗Open-source builders
Explore public development work and explainers.
@indigo_nakamoto on X ↗Project or identity reference ↗Privacy & engineering
Developer work and the history of MWEB.
@DavidBurkett38 on X ↗Project or identity reference ↗Wallets & payments
Release records and the experience of using Litecoin.
@nexuswallet on X ↗Project or identity reference ↗Ecosystem builders
Testnets, proposals and the project’s own roadmap.
@LitecoinVM on X ↗Project or identity reference ↗Community & events
Conversations connecting builders and communities.
@DaddyCool1991 on X ↗Project or identity reference ↗Books & ideas
Long-form Litecoin writing; distinguish an author’s argument from fact.
@MASTERBTCLTC on X ↗Project or identity reference ↗Identity check pending
The founder requested this handle. A Foundation project page uses @loshan1212; continuity has not been verified.
@loshan on X ↗Project or identity reference ↗Institutional records
Start with dated company disclosures, and separate holdings from flows.
@LuxxfolioH on X ↗Project or identity reference ↗Institutional records
Company announcements belong beside their original filings.
@LiteStrategy on X ↗Project or identity reference ↗Funds & disclosures
Read product documents and their dates before drawing conclusions.
@CanaryFunds on X ↗Project or identity reference ↗The living archive
Each source check has a permanent record. The daily magazine, community notebook and project story each keep their own dates.