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

The open money school / Start here

A little learning.
A lot of possibility.

From “what is a blockchain?” to asking sharper questions about custody, privacy and open finance. Learn the words. Practise the decisions. Keep control of your pace.

Come as a newcomer, a Bitcoin reader or a future builder. Read freely. Take your time. You can finish the course without buying coins, connecting a wallet or creating an account.

ŁLEARN · TRY · VERIFY · SHARE

Three doors. One open table.

What brings you here?

Newcomer

Make it understandable.

Find out what a wallet does, who holds the keys and how to read a payment request. Start with fictional practice.

Take the seven steps ↓
Builder

Make something useful.

Explore LitVM’s documented LiteForge testnet, meet the projects and find a small contribution.

Open the testnet pathway ↗
Experienced reader

Follow the evidence.

Inspect Litecoin’s block rules, compare financial representations and challenge a source or method.

Explore the timechain ↗

Start at zero / Plain words first

Understand the system.
Then choose your tools.

Blockchain

A shared transaction history. Nodes check proposed blocks against network rules; proof of work helps the network choose a history. It is not a list of customer accounts maintained by one company.

Wallet

A tool for managing keys and preparing transactions. Your LTC is represented in the network’s records; it is not stored inside the app like a photograph.

Public address

A destination used to receive a payment on a particular network. Sharing it can reveal financial activity. An address alone does not normally authorize spending.

Private key

Secret information used to authorize spending. Someone who obtains it may be able to spend the associated funds. Keep it out of websites, chat and support messages.

Recovery phrase

Also called a seed phrase: a wallet’s recovery secret, often a sequence of words. Not every wallet uses this backup system. Follow the exact wallet’s recovery instructions privately.

Password or PIN

A lock on a particular app, device or account. It is not necessarily a backup of the underlying wallet. A recovery secret can bypass that local lock.

Wallet, transaction and shared ledgerA wallet manages keys locally, prepares an authorized transaction and broadcasts it. Network nodes check the rules. Miners can include it in a block. A recovery secret stays outside this flow.YOUR WALLETKeys stay privateTRANSACTIONNodes check the rulesBLOCK HISTORYMiners propose blocksA recovery secret is never part of a payment request.
A simplified map, not a promise of instant confirmation. A broadcast transaction may wait, conflict or fail to confirm.

Continue with the Litecoin Foundation learning center and your selected wallet’s official help documentation. These are external resources, not requirements to install a particular product.

Seven steps / Your pace

Your first week.
No starting balance required.

A “day” is a small chapter, not a deadline. Your checkmarks stay in this tab and reset when it closes or reloads. They are a personal reminder, not proof of competence.

0 of 7 steps marked complete.

STEP 01Understand what Litecoin is

Your aim: Explain native LTC, a wallet and a transaction in plain language.

Litecoin is an open-source network with rules that participating nodes check. LTC is its native unit. A wallet manages the keys used to authorize spending; an exchange account usually gives a service custody. Bitcoin and Litecoin have shared origins but different mining and timing rules.

  1. Read the network introduction and compare Bitcoin and Litecoin without ranking either as a guaranteed investment.
  2. Explain why a wallet controls keys rather than storing coins inside the app.
  3. Answer: is a company share or wrapped token the same thing as native LTC?

Try it: Correctly distinguish native LTC, a wallet and a third-party product.

Read the original learning or wallet guide ↗

STEP 02Choose a learning path and wallet

Your aim: Recognize custody choices before installing anything.

With self-custody, you are responsible for the keys and recovery process. With custodial services, the service controls access under its own terms. An official store listing should be reached from the publisher’s verified website; an advertisement or familiar-looking logo does not establish authenticity.

  1. Compare self-custody and a service holding keys for you; identify who can authorize and recover access.
  2. Open the wallet publisher's official website and follow its current store links.
  3. Review its supported network, backup method and support documentation. Installation is optional.

Try it: Identify the publisher and who controls recovery. No purchase required.

Read the original learning or wallet guide ↗

STEP 03Understand backup and recovery

Your aim: Keep secrets out of the learning platform.

A recovery secret can give someone control over a wallet. A screenshot or cloud copy can expose it to other accounts and devices. The correct backup method depends on the wallet. Use its current instructions privately; practising here never requires creating or revealing a real secret.

  1. Use a fictional recovery example in the practice lesson.
  2. Read the selected wallet's current backup instructions before creating a wallet.
  3. If choosing to create a real wallet, complete its backup privately. Never enter recovery words, private keys or backup images into our website, chat, a form or support message.

Try it: Explain recovery responsibilities using a fictional example; do not upload proof.

Read the original learning or wallet guide ↗

STEP 04Read a receive request

Your aim: Recognize the network, destination and amount.

A receive address tells a wallet where a transfer is intended to go on a particular network. A QR code is a convenient encoding, not a safety certificate. Native Litecoin, cbLTC on Base and a LitVM test token use different systems. Always identify the asset and network before treating a destination as compatible.

  1. Study a clearly labelled fictional Litecoin receive request.
  2. Explain why native Litecoin and represented LTC on another chain are not interchangeable destinations.
  3. Use the wallet publisher's receive guide if choosing a real-world transaction; verify details privately.

Try it: Identify which network a practice request belongs to.

Read the original learning or wallet guide ↗

STEP 05Understand a send and confirmation

Your aim: Know which checks happen before and after sending.

A transaction authorizes a transfer under the network’s rules. A fee is separate from the amount received, and a broadcast transaction is not the same as a confirmed one. Blocks record transactions; the appropriate confirmation policy depends on the recipient and context. Litecoin transfers do not have a general chargeback mechanism.

  1. Use a fictional amount to inspect destination, network, fee and confirmation status.
  2. Explain that the sender must verify details before authorizing, and that a wallet provider cannot simply reverse a confirmed transfer.
  3. If independently choosing real practice, begin with a small affordable test and follow current official instructions; the course never initiates transfers.

Try it: Complete the simulated transaction checklist.

Read the original learning or wallet guide ↗

STEP 06Explore privacy, builders and representations

Your aim: Ask a better product question.

Privacy depends on the actual implementation and how it is used. Native MWEB, wallet features and application-layer systems should be examined separately. A project on testnet is for experimentation; a wrapped asset adds issuer or bridge assumptions beyond those of native LTC.

  1. Read the introductory privacy explanation and distinguish native MWEB from application-layer features.
  2. Choose a documented demo or project and identify its release stage, network and maintainer.
  3. Explain that a testnet asset, bridge representation and native LTC have different assumptions.

Try it: Write one source-linked question about a project.

Read the original learning or wallet guide ↗

STEP 07Make your first contribution

Your aim: Help the next learner.

An open community needs more than developers and asset owners. Clear documentation, translation, reproducible bug reports and sourced corrections help everyone. A useful contribution names the page or project, explains the issue and provides a public reference where possible.

  1. Choose one useful action: improve a glossary entry, report a broken link, suggest a sourced correction or explain a term.
  2. Optionally subscribe through a tested consent flow when available; sign-in alone does not subscribe anyone.
  3. Share the public lesson link with a willing friend. No address-book import or automatic invitations.

Try it: One voluntary contribution or a saved personal learning plan.

Read the original learning or wallet guide ↗

Practise the pause / No real secrets

Spot the trap.
Explain the next move.

Choose an answer in your head, then open the explanation. No score, account, real address or recovery phrase is collected.

SCENARIO 1A “support agent” asks for your recovery words to fix a missing balance.

Stop the conversation. Do not send words, private keys or backup images. Reach the wallet publisher through its independently verified documentation. A familiar avatar or urgent message is not identity verification.

SCENARIO 2A wallet has a strong PIN. Does that mean you can recover it if the phone is lost?

Not necessarily. The PIN protects local access; recovery depends on that wallet’s backup method. Learn the documented recovery process before relying on the wallet. Practise only with a separate disposable wallet following official instructions, never by entering real secrets here.

SCENARIO 3A QR code says “Litecoin,” but the sender says the asset is on another network.

Pause. A logo and QR code do not establish network compatibility. Identify the exact asset and chain using official documentation and the recipient’s independently confirmed instructions. Native LTC and represented LTC can require different destinations and tools.

SCENARIO 4You see a tiny payment from an unfamiliar address in your history. Can you copy that address for your next payment?

Do not use transaction history as proof of the intended recipient. Attackers can seed look-alike entries. Obtain the destination through a trusted channel and compare the complete destination in the signing interface.

SCENARIO 5A dapp asks for an unlimited token approval or an unreadable signature.

Stop until you understand the network, contract, operation and authority granted. A signature can create permissions even without an immediate transfer. Token approvals are an EVM application concept, not an ordinary native Litecoin payment. Disconnecting a site does not necessarily revoke existing approvals.

SCENARIO 6Someone promises guaranteed yield and says the offer closes in five minutes.

Treat the guarantee and urgency as reasons to investigate, not reasons to hurry. Identify custody, liquidation, contract, oracle, issuer and exit risks. Choosing not to participate is a complete decision.

Sources: Bitcoin.org wallet security · Ethereum.org security and approval guidance. EVM advice applies to compatible applications; it should not be confused with native Litecoin transaction rules.

Build judgment / Beyond the first week

Four levels.
Keep your curiosity.

01 · Foundations

Explain before installing.

  • Describe a blockchain, wallet, address and recovery secret.
  • Name who controls spending and recovery for your chosen custody model.
  • Recognize that a seed phrase, PIN and optional wallet passphrase are different concepts.
Work through the seven steps →
02 · Everyday practice

Read the whole payment.

  • Identify asset, network, destination, amount and fee in fictional examples.
  • Distinguish broadcast, confirmation and recipient acceptance policies.
  • Keep a private backup and an independently verified support route; never submit backup proof.
Open the fictional Bitcoin lab →
03 · Advanced safety

Question every permission.

  • Map device loss, phishing, physical access and recovery dependencies.
  • Understand hardware-wallet display checks, watch-only privacy and multisignature recovery complexity before adopting them.
  • Prepare a private inheritance and recovery plan; complexity can also cause loss.
Practise the safety scenarios →
04 · Research & building

Verify the assumptions.

  • Compare native LTC, a wrapped asset, a test token and a lending position.
  • Inspect exact chain and contract, oracle, permissions, liquidity and exit conditions.
  • Use isolated testnet experiments and public reproducible bug reports, without exposing credentials.
Explore the finance learning lab →

Learning is an ongoing practice, not a safety certificate. MWEB and other privacy tools have implementation and usage limits; hardware devices, multisignature and smart contracts each add their own assumptions. Ask what can fail and how recovery works before committing funds.

Turn a lesson into a contribution.

Try a small experiment.

The existing Bitcoin lab offers fictional exercises in units, transaction change and multisignature thinking.

Open the practice lab ↗

AI-prepared learning school · Foundational safety sources checked October 22, 2026; the seven-step source record is dated October 15. Independent curriculum review remains pending. Continue at the Litecoin Foundation learning center ↗ · Follow the publication →