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 ↓The open money school / Start here
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.
Three doors. One open table.
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 ↓Explore LitVM’s documented LiteForge testnet, meet the projects and find a small contribution.
Open the testnet pathway ↗Inspect Litecoin’s block rules, compare financial representations and challenge a source or method.
Explore the timechain ↗Start at zero / Plain words first
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.
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.
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.
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.
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.
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.
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
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.
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.
Try it: Correctly distinguish native LTC, a wallet and a third-party product.
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.
Try it: Identify the publisher and who controls recovery. No purchase required.
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.
Try it: Explain recovery responsibilities using a fictional example; do not upload proof.
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.
Try it: Identify which network a practice request belongs to.
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.
Try it: Complete the simulated transaction checklist.
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.
Try it: Write one source-linked question about a project.
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.
Try it: One voluntary contribution or a saved personal learning plan.
Practise the pause / No real secrets
Choose an answer in your head, then open the explanation. No score, account, real address or recovery phrase is collected.
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.
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.
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.
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.
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.
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
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.
The existing Bitcoin lab offers fictional exercises in units, transaction change and multisignature thinking.
Open the practice lab ↗Use the October 15 project guide to find official documentation and a question you want answered.
Read the builders special ↗Improve an explanation, suggest a dated primary source or make a guest contribution plan.
Choose your first contribution ↗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 →