Back to Academy

Lesson 09 · Beginner

Protect Yourself

4 min read

The fastest way to lose a wallet is to let urgency make security decisions for you.

Wallet basics

A wallet such as Phantom is a tool for interacting with Solana assets. Never share your seed phrase or private key. Legitimate support will not ask for them.

Watch for rugs and scams

A rug pull is a project failure or theft where liquidity, funds, or access disappears. Fake accounts, copied websites, malicious approvals, and impersonated links can all create danger.

Verify before signing

Check the URL, token address, transaction details, and who shared the link. If a message says you must act immediately, pause and verify through an independent source.

A concrete rule

Verify the domain character by character, never share a seed phrase or private key, inspect transaction approvals, and treat guaranteed returns or countdowns as red flags. Use official sites only; do not trust a link delivered by DM. If you signed something suspicious, disconnect, document the signature, and seek trusted security guidance.

Checklist

Before acting: verify the claim or address; write the thesis; calculate the dollar loss; check liquidity and permissions when relevant; set a review time; and confirm the amount will not affect essentials.

Do this today

Open your browser history and remove saved wallet links you cannot verify; then bookmark only the official site you typed yourself.

Worked practice

Use this lesson on a small, hypothetical example before using it on a live decision. Start with a $1,000 portfolio and write the exact dollar amount you would risk. Then write the claim you are evaluating, the screen where you will verify it, and the time you will review it. If the answer depends on a screenshot, a private message, or a promise that cannot be checked, label it unverified. Next, imagine the price moves against you by 20%, 50%, and 90%. Do not predict the recovery; write what your plan says at each point. A written response exposes whether you have a rule or only a hope. Finally, read the plan aloud. If it sounds different from what you told yourself before the trade, keep the written version and wait. This exercise takes less than 10 minutes and gives you a record you can compare with the next decision.

Decision rehearsal

Run the decision in three passes. Pass one is observation: describe only what is on the screen, including the timestamp, market-cap display, liquidity display, holder view, and the exact wording of the post that brought you there. Pass two is interpretation: separate facts from guesses and write who benefits if attention increases. Pass three is choice: select wait, research more, or do nothing, and explain the choice in one sentence. If your choice is wait, set a specific review time rather than refreshing continuously. If your choice is research, name the source and the question it must answer. If your choice is do nothing, keep the note; declining an unclear setup is a valid result. This sequence prevents a vivid story from silently becoming a trading instruction and makes your future review more honest.

Mini story

Composite story: not a real person. A fake support DM read: ‘Your wallet has an urgent eligibility error. Connect at pulsehodl-rewards dot example and enter your recovery phrase to restore access.’ The grammar was polished and the account had a familiar logo. Nia did not click. She opened the official site manually, found no alert, and reported the account. The safest response to a seed phrase request is no response: legitimate support does not need it.

Key takeaways

  • Never share seed phrases or private keys.
  • Urgency and guaranteed returns are red flags.
  • Verify links and transaction details independently.

Today's action

Open your browser history and remove saved wallet links you cannot verify; then bookmark only the official site you typed yourself.

Knowledge check

Take the quiz yourself

Choose your answers before revealing your score.

1. Who should receive your seed phrase?
2. What is a rug pull?
3. What should you do with urgent links?
4. What should legitimate support never request?
5. What is a useful security check before signing?
6. Which response best follows this lesson's rule?
7. What should you do when a claim cannot be independently verified?