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

Sikh Bitcoin · Beginner · Lesson 10 of 21

Scams, urgency and trusted routes

Recognize a bad request before the technology becomes a distraction.

About 10 minutes with practice. You only need something to take notes with. No real wallet details or payments are part of this lesson.

Course contents · Lesson 10 of 21
  1. Bitcoin without jargon
  2. Keys, custody and keeping control
  3. Payments for humans, including Lightning
  4. Money, prices and units
  5. Follow a payment from request to receipt
  6. Addresses, networks and QR codes
  7. Confirmations and patience
  8. Fees buy scarce block space
  9. Backups before dependence
  10. Scams, urgency and trusted routes
  11. Privacy is a practice
  12. Custody is a relationship
  13. Reading a Lightning invoice
  14. Exchanges and access to bitcoin
  15. Volatility and practical planning
  16. A fair invoice for creative work
  17. Donations with accountable purpose
  18. Proof of work and honest energy questions
  19. Bitcoin and Litecoin: related ideas, separate networks
  20. Read Bitcoin news with a source trail
  21. Capstone: welcome a newcomer safely

What you will learn

  • Identify secret-exposure and payment-pressure patterns.
  • Choose an independent route for verification.

The request matters more than the costume

A message can use a familiar logo, a friendly name or a convincing screenshot. Judge what it asks you to do. Revealing recovery information, approving an unexplained transaction or paying to unlock an invented reward are requests that deserve a stop. A polished page is not a security assessment, and an AI-written explanation is not independent evidence.

Urgency removes time to compare

A fictional message says your community grant expires in five minutes unless you synchronize your wallet. The deadline tries to make deliberation feel like failure. Close that route and return to a known community page or previously verified contact. Do not use contact details supplied by the suspicious message to verify the same message; that creates a circular check.

Get help without making the exposure worse

Describe the request and the domain, but omit secrets and sensitive account information. If you have already interacted, avoid following another unsolicited recovery helper. A responsible incident response first establishes what was disclosed or signed. This lesson does not ask you to send funds or perform emergency wallet operations. The community must never require proof of wealth, a deposit or a wallet secret to grant access to learning or a meal.

Practice on paper

Write a reply to a supposed moderator asking for your seed to verify membership. Then describe a route that does not depend on that message.

Reveal the worked answer

A suitable response is: “I will not share recovery information.” Independently open the verified community site and use its established support route. You do not need to keep negotiating with the suspicious account.

Check your understanding

Choose an answer in your head or on paper, then reveal the explanation. Retry whenever you like. Answers are not submitted or scored; completion marks are your own learning notes.

1. Does a direct message from a familiar display name prove identity?

  • Yes
  • No
Reveal answer 1

No. Accounts, names and images can be copied or compromised.

2. Should an expiring offer override a missing explanation?

  • Yes
  • No
Reveal answer 2

No. A deadline is not evidence that a request is legitimate.

Take this with you

Pause, verify independently and never turn politeness into secret disclosure.

Your learning, at your pace

Read every lesson freely. Optional progress tracking needs JavaScript and browser storage; it does not require an account or wallet.