Skip to content
Satnam SatoshiIn service of humanityFind your place ↗
Menu

LTC / The community wire

One Litecoin
family.
Room for everyone.

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.

A place at the table / No account required to read

Choose a small
first step.

Build

Find a documented testnet project. Inspect its network, code and current release.

Meet the builders →

Your next small step

Curiosity has a home.

Start with Litecoin

Seven short steps, from the first wallet question to your first contribution.

Take the first step ↗

The timechain calendar

Explore Litecoin’s rhythm with a halving orbit and a playful block-height lab.

Wind the block clock ↗

The open finance lab

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

The family
is building.

LitVM, Lester Labs, Dappit and the projects around the ecosystem conversation. Source-linked descriptions keep testnets and future plans visible.

Read the complete builders edition and speaker roster →

The workshop / LiteForge testnet

Lester Labs

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

Dappit

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

Lester’s Arcade

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

Lithium

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 shared family.
Different foundations.

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.

Three asset categories with different assumptionsNative Litecoin follows Litecoin network rules. A represented asset adds an issuer or bridge and another network. A testnet asset is for experiments. There are no conversion arrows because these are not interchangeable balances.ŁNATIVE LTCLitecoin network rulesKeys authorize spending⊕REPRESENTED ASSETIssuer or bridge assumptionsExact chain + contract matter◇TESTNET ASSETPractice and experimentationNot native mainnet LTC
Three categories, not three routes to the same guaranteed asset. A represented asset can add custody, redemption, contract and liquidity risks. A testnet token is not evidence of mainnet adoption.

Identify the thing you hold.

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 →

Keep current status visible.

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 ↗

Six questions for every milestone.

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

Which chain and asset?

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

What can someone use today?

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

Can the implementation be inspected?

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

Who can change or stop it?

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

What do the numbers measure?

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

How does someone leave?

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

A simpler name.
A separate privacy question.

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 public payment-name resolutionA fictional payment alias is looked up by a resolver, which returns a destination for a specific network. The sender verifies the destination before authorizing a payment. A public directory mapping can link the alias to on-chain activity; this diagram is not the AmericanFortress architecture.1 · ALIAS@exampleFictional name2 · RESOLVERLook up the recordWho controls it?3 · DESTINATIONExact asset + networkVerify before signing4 · PAYMENTSender authorizesNetwork processes itA convenient label does not automatically conceal a transaction.
Generic public-directory model. A diagram of concepts, not a live product or a map of every naming protocol. The fictional alias is not a payment instruction.
  1. Alias: a human-readable label. Confirm who owns the intended name through an independent trusted channel; familiar spelling is not proof of identity.
  2. Resolver: software or a service looks up a record. Ask who can update it, whether the result is authenticated and what happens if the service is unavailable.
  3. Destination: the wallet obtains or derives a destination for the exact asset and network. In a public-directory model, the mapping may itself expose the receiving address.
  4. Payment: the sender checks the operation and authorizes it privately. Name lookup is not authorization, settlement or a guarantee that the recipient is legitimate.

Generic model / Metadata questions

Who might see what?

  • Sender and recipient: each may retain invoices, names, amounts and timestamps. Either party can disclose their own records.
  • Resolver or infrastructure provider: depending on the design, it may observe lookups, account identifiers, IP addresses or timing. Encryption of transport alone does not answer the logging question.
  • Public observers: on a transparent chain, addresses and transaction data can support correlation. A public alias-to-address record can add an identity link.
  • Wallet and other services: telemetry, backups and third-party infrastructure can create additional metadata. Actual exposure depends on implementation and settings.

AmericanFortress / Attributed design

A name need not be a public address book.

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

Meet the wider
Litecoin family.

Litecoin Foundation

The organization’s mission, initiatives and original announcements.

Explore the source ↗

Look Into Litecoin

Independent education, books and opinion, with a disclosed pro-LTC perspective.

Explore the source ↗

LitVM / LiteForge

An application ecosystem with a dated testnet directory. A listing does not establish mainnet operation.

Explore the source ↗

LTC Media

Independent reading guides, original editorial and a dated record readers can check.

Explore the source ↗
Curated. Attributed. Dated.

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

From the builders.

Collected
Publication dates remain unchanged.

Selected October 5, 2026 / Original source dates below

A little context.
A longer view.

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

A privacy proposal, in its own words.

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.

What this source does—and does not—establish

This announcement does not establish a live integration, an independent audit or a privacy guarantee.

Read the original source ↗Build your Litecoin context →

MAKE MONEY USEFUL.

Product announcement / Litecoin Foundation

Source published

Payments are a user experience.

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.

What this source does—and does not—establish

Availability and merchant coverage were not independently tested. This is a May announcement, not a new feature report.

Read the original source ↗Understand wallet responsibilities →

EXPERIMENT. CHECK. REPEAT.

Testnet guide / LitVM

Source published

A testnet is a place to ask better questions.

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.

What this source does—and does not—establish

A testnet guide is not evidence of mainnet readiness. No wallet connection or software installation is needed to read it.

Read the original source ↗Explore open technology →

MEMORY IS A COMMON GOOD.

Learning archive / Litecoin Foundation

Source published

Keep the conversations that built the community.

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.

What this source does—and does not—establish

This is the organizer’s account of a past event. A statement made there does not establish a project’s present availability.

Read the original source ↗Read the Charlie Lee special →

Before something reaches this page

Worth sharing?
Show your work.

  1. Who said it?

    Check the source identity and link to the original. A requested account is a lead, not automatic authority.

  2. When did it happen?

    Keep the event, publication and collection dates separate. Old stories can teach without pretending to be new.

  3. What does it establish?

    Label releases, announcements and opinions. Follow material claims into code, official records or documentation.

  4. Why will it help?

    Add an understandable explanation, a useful learning path and a way to correct the record. Leave repetition and unsupported claims out.

Read our editorial commitments →

The founder’s 13-account reading list

Meet the conversation.

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.

The living archive

New chapters.
Old pages kept.

Each source check has a permanent record. The daily magazine, community notebook and project story each keep their own dates.