Complete "Lesson 19: Exchange vs Self-Custody" first to unlock this lesson.Go to previous lesson

In this sixteen-minute beginner hands-on lab, learners practice wallet security using only fictional addresses, mock networks, invented messages, simulated tokens, and dummy recovery materials. They compare visually similar destination strings, verify network compatibility, calculate test-transfer fees, identify phishing through a weighted red-flag scorecard, assess limited versus unlimited token approvals, and calculate recovery transcription error probabilities. Learners also rehearse a recovery test on a fresh mock wallet, inspect signing permissions, review device hygiene, and apply a ten-item preflight checklist before hypothetical transfers. Six practical activities reinforce the distinction between technical controls and human mistakes. The outcome is a reproducible wallet safety procedure and journal documenting destination verification, network compatibility, transaction costs, permission exposure, recovery readiness, and suspicious-message responses. All inputs, probabilities, messages, transactions, accounts, and balances are fictional. No real wallets, private keys, recovery phrases, addresses, financial prices, or transactions are used.

Why Wallet Safety Begins With Human Verification

Digital wallet systems can use strong cryptographic signing while remaining vulnerable to human mistakes and social engineering. Attackers may not need to break the underlying blockchain. Instead, they can persuade someone to reveal a recovery secret, approve an unwanted contract permission, transfer funds to an impostor, or use an incompatible network. They often exploit urgency, fear, authority, financial rewards, and seemingly professional support messages. Effective wallet safety therefore combines technical protections with careful decision procedures. This lesson uses only fictional account information, invented warning messages, dummy recovery placeholders, and simulated tokens to rehearse those procedures without exposing real assets.

Learner practicing wallet safety with a simulated interface
Figure 1. A learner works through wallet safety exercises.
Social engineering threats targeting wallet users
Figure 2. Deceptive messages target the person, not the code.
Two nearly identical mock destination identifiers
Figure 3. Two lookalike destination cards with one subtle difference.

The previous custody lesson distinguished exchange accounts from self-custody. A custodial provider normally controls transaction-signing keys and may offer account recovery through authentication and support. A self-custody user controls signing authority and assumes responsibility for protecting keys, verifying transactions, and maintaining usable backups. Neither arrangement eliminates phishing, malware, financial loss, or operational mistakes. In a self-custody setting, an incorrect destination or harmful signing authorization may be difficult or impossible to reverse. The learner's first responsibility is to determine exactly what action is being requested before approving anything.

Key points

  • Strong cryptography does not protect against a person approving a dangerous action.
  • Attackers use urgency, fear, rewards and apparent authority.
  • Everything in this lab uses mock inputs: no real phrase, key, address or credential.
Six practical exercises
LabSkillMock input
1Address comparisonDEMO7F2K91XQ versus DEMO7F2K19XQ
2Network and test transferSample Coin on Network Alpha
3Phishing scorecardMessages A, B and C
4Token permissions100 SMP versus unlimited
5Recovery testdemo-1 to demo-12
6Preflight checklist150 SMP and 50 SMP transfers

Six practical exercises structure this lab: address comparison, network and test-transfer checks, phishing classification, token allowance review, dummy recovery testing, and a ten-item preflight checklist. Every address is deliberately fictitious, every website-like domain ends with .test, and every recovery placeholder is unusable as a genuine secret. The fictional asset is Sample Coin, abbreviated SMP. No real wallet application, exchange, address, key, recovery phrase, market price, or transaction is required. The objective is to demonstrate a repeatable verification workflow, not to practice transferring actual funds.

Lab One: Detect Lookalike Addresses and Clipboard Substitution

A destination comparison can fail when a person checks only the beginning and end of a long-looking identifier. For our fictional exercise, the legitimate mock destination is DEMO7F2K91XQ, while the lookalike destination is DEMO7F2K19XQ. Each string contains exactly twelve characters. Positions one through eight match, positions nine and ten differ, and positions eleven and twelve match. Specifically, the two adjacent characters 91 in the legitimate destination become 19 in the lookalike. Ten of the twelve positions therefore match, producing a positional similarity of ten divided by twelve, or approximately 83.3%.

Clipboard manipulation and address poisoning warning
Figure 4. Ten of twelve positions match; two differ.

Despite the high similarity, the strings are not equal and represent different fictional destinations. This exercise demonstrates why checking only a prefix or suffix is insufficient. An attacker might exploit address poisoning by placing lookalike identifiers in activity records or might use clipboard malware to substitute a destination after the user copies it. Copying and pasting reduces some transcription mistakes, but it does not prove that the clipboard contains the intended destination. A verification process should compare the complete string against a trusted source after pasting and before authorizing the transaction.

Digital asset networks with different destinations
Figure 5. An 83.3% match is still a different destination.

Key points

  • Mock strings DEMO7F2K91XQ and DEMO7F2K19XQ differ at positions 9 and 10 (91 became 19).
  • 10 of 12 positions match = 83.3%, yet they are different destinations.
  • Compare the whole string, verify after pasting, and beware clipboard swaps and address poisoning.
Address check
ItemString AString B
StringDEMO7F2K91XQDEMO7F2K19XQ
Positions 9 and 109119
Matching positions10 of 1210 of 12
Similarity83.3%83.3%
Positions that match (out of 12)
10
Match
2
Differ

For this lab, place both mock strings side by side, mark positions nine and ten, and record the exact mismatch. Do not convert either mock identifier into a real blockchain address or send anything to it. In a safe transfer workflow, confirm the intended recipient through a trustworthy channel, verify the full destination, check the chosen network, and consider a small test transfer before a larger amount. Even a successful test cannot guarantee that later authorization details remain unchanged, so every transaction requires its own final review.

Verifying wallet details on a hardware signing device
Figure 6. The address check as a table.

Lab Two: Verify Networks, Test Transfers and Fees

The fictional asset Sample Coin can move through two incompatible classroom networks, Network Alpha and Network Beta. Alpha charges a fee of 0.5 SMP per transfer, while Beta charges 0.1 SMP. However, the intended recipient accepts SMP only through Network Alpha. The lower fee on Beta is irrelevant if the recipient cannot access assets sent through that network. Wrong-network transfers may be unrecoverable, depending on actual systems and available recovery mechanisms. The essential verification question is whether the recipient, asset representation, destination and selected network are compatible before any transfer is authorized.

Small test transfer before a larger simulated transaction
Figure 7. Fictional Sample Coin on two networks with different fees.

Assume that the stated transfer amount includes the network fee, which is deducted before the recipient receives the tokens. A direct transfer of 100 SMP over Network Alpha costs 0.5 SMP, equal to 0.5% of the original amount, and delivers 99.5 SMP. Now consider a two-step plan. First, send a 1 SMP test transfer. After the 0.5 SMP Alpha fee, the recipient receives 0.5 SMP. Confirm that the mock transaction reaches the intended fictional destination on Network Alpha before preparing the remaining transfer. This confirmation is a verification checkpoint rather than a guarantee of future success.

Phishing message with suspicious urgency and false support
Figure 8. A direct 100 SMP transfer delivers 99.5 SMP.

Key points

  • Sample Coin: Network Alpha fee 0.5 SMP, Network Beta fee 0.1 SMP; the recipient accepts Alpha only.
  • Direct: send 100, fee 0.5 (0.5%), received 99.5. Test first: send 1 (receives 0.5), then 99 (receives 98.5).
  • Test first costs 1.0 SMP in fees versus 0.5 SMP: an extra 0.5 SMP, and it is not a guarantee.
Transfer plans on Network Alpha
PlanTransfersFeesReceived
Direct100 SMP0.5 SMP99.5 SMP
Test, then remainder1 SMP + 99 SMP0.5 + 0.5 = 1.0 SMP0.5 + 98.5 = 99 SMP
Extra cost of testing0.5 SMP0.5% of 100 SMP

Next send the remaining 99 SMP over Alpha, paying another 0.5 SMP fee. The recipient receives 98.5 SMP in the second transfer. Combined receipts equal 0.5 plus 98.5, or 99 SMP. Total network fees equal 1.0 SMP, which is 1.0% of the original 100 SMP. Compared with the direct-transfer fee of 0.5 SMP, the test-first plan costs an additional 0.5 SMP, or 0.5% of the original amount. This is an explicit trade-off between additional verification and higher transaction friction. The entire example is fictional and uses no real network or address.

Weighted phishing red-flag assessment
Figure 9. The test-first plan costs an extra 0.5 SMP.
Token approval review and revocation
Figure 10. Direct versus test-first transfer plans.

Lab Three: Recognize Phishing With a Weighted Scorecard

Phishing often depends on persuasion rather than sophisticated technical exploitation. We use a fictional six-factor scorecard to practice recognizing warning signs: urgency or threat receives two points, requesting a recovery phrase receives five, a domain mismatch receives three, a guaranteed reward or return receives three, an unknown sender receives one, and spelling errors receive one. Under the written classroom rule, a score of four or more means stop and do not act on the message. The weights and threshold are invented for education, not a validated model of real phishing probability. A message scoring below four can still be malicious.

Limited versus unlimited token spending permissions
Figure 11. Six red flags and their points.
Documenting a simulated wallet security incident
Figure 12. Four red flags to look for first.

Message A states: 'URGENT: verify your wallet within 24 hours at examp1e-wallet-support.test and enter your 12 words'. Assume the mock official domain for comparison is example-wallet.test. The phishing address differs, and the message combines urgency, a request for recovery information, and a mismatched domain. Its score is two plus five plus three, totaling ten. The correct response is to stop, avoid the link, never provide recovery information, and independently access the known official application through a trusted method. The .test addresses in this exercise are reserved fictional examples and are not services to visit.

Reviewing a wallet signing request before approval
Figure 13. Message A scores 10 points: stop.

Key points

  • Points: recovery phrase 5, domain mismatch 3, guaranteed reward 3, urgency 2, unknown sender 1, spelling errors 1.
  • Rule: 4 or more means stop. Message A = 10, Message B = 0, Message C = 4.
  • A score of 0 is not proof of safety: verify in the official app, never through a link.
Points per red flag
Red flagPoints
Asks for a recovery phrase5
Link domain does not match3
Guaranteed return or reward3
Urgency or threat2
Unknown sender1
Spelling errors1
Invented classroom rule. Four or more points means stop.
Phishing scorecard
MessageRed flagsScoreAction
AUrgency 2 + recovery phrase 5 + domain mismatch 310Stop
BNone counted0Verify in the official app
CGuaranteed reward 3 + unknown sender 14Stop

Message B states: 'You requested a withdrawal of 50 SMP at 10:05; if this was not you, open the official app yourself and review activity'. It scores zero under the specified categories, but zero does not establish authenticity or prove that the withdrawal occurred. The learner should still inspect activity independently inside the official application. Message C states: 'Support desk: send 1 SMP to unlock your 500 SMP reward'. Assign three points for the promised reward and one for the unknown sender, totaling four. The written rule therefore says stop. Never pay a supposed support representative to unlock an unexpected reward.

Dummy recovery materials stored securely
Figure 14. Message C scores 4 points: stop.
Suspected wallet compromise response
Figure 15. The phishing scorecard for three mock messages.

Lab Four: Inspect Token Approvals and Signing Prompts

Some token systems allow wallet owners to grant a contract permission to spend specified quantities of their tokens. Such approvals may remain active after the immediate interaction, depending on the contract and token design. A wallet can therefore face exposure even if it is not currently initiating a conventional transfer. Before approving a request, determine which token is involved, which contract receives authorization, whether the request is a one-time transfer or a continuing spending allowance, and what the maximum permitted amount is. An attractive interface or familiar-looking application is not proof that the underlying authorization is safe.

Our simulated wallet contains 1,000 SMP. A limited allowance of 100 SMP represents 100 divided by 1,000, or 10% of the balance. Under the exercise assumptions, that approval exposes at most 100 SMP through that particular allowance. An unlimited approval is modeled as permitting access to the entire current 1,000 SMP, representing 100% of the balance. These values describe potential permission exposure, not guaranteed losses. Actual contracts and balances may impose additional limits or behave differently, and future token deposits could change the amount exposed by an effectively unrestricted permission.

Testing restoration on an isolated fictional wallet
Figure 16. A limited 100 SMP approval exposes 10% of the balance.
Probability of transcription errors increasing across multiple items
Figure 17. An unlimited approval exposes 100% of the balance.

Key points

  • A limited 100 SMP approval on 1,000 SMP exposes 10%; an unlimited approval exposes 100%.
  • Read the contract, action, asset, allowance and consequences before signing.
  • Review and revoke approvals you no longer need; revoking may cost a fee.
Approval exposure
ApprovalAmount at riskShare of 1,000 SMP
Limited100 SMP10%
Unlimited1,000 SMP100%
Share of the balance exposed (%)
10%
Limited
100%
Unlimited

The learner should compare the two fictional permissions and identify the more tightly bounded authorization. Before signing, review the contract identity, function, asset, amount, allowance, network and expected consequence. If using a dedicated signing device, verify the information shown on the device itself rather than trusting only the computer screen. Periodically review and revoke allowances that are no longer required through verified procedures. Revocation may involve a separate transaction, may carry costs and may not undo prior transfers. This lab remains a mock permission analysis rather than a real contract interaction.

Lab Five: Dummy Recovery Phrase Transcription and Restore

Recovery materials can restore access only when they are accurate, complete and compatible with the wallet arrangement. For this lab, create a fictional sequence containing twelve placeholders named demo-1 through demo-12. These are ordinary exercise labels, not a valid cryptographic recovery phrase. Never replace them with actual recovery words. Assume each placeholder has an invented 1% probability of being copied incorrectly, independently of the other eleven placeholders. Therefore, each placeholder has a 99%, or 0.99, probability of being copied correctly. The probabilities are teaching assumptions, not measured rates of human transcription mistakes.

The probability that all twelve placeholders are copied correctly equals 0.99 multiplied by itself twelve times, or 0.99 raised to the twelfth power. This equals approximately 0.8863848717, or 88.64%. The probability of at least one transcription error is the complement: one minus 0.99 raised to the twelfth power, approximately 0.1136151283, or 11.36%. These calculations require the independence assumption. Real transcription errors may be correlated, and some wallet recovery procedures have additional validation mechanisms. The lesson is that a backup should be verified, not that these invented percentages describe real wallet reliability.

Ten-item wallet transfer preflight checklist
Figure 18. Chance of at least one copying error in twelve words: 11.36%.

Key points

  • Mock phrase: demo-1 to demo-12 only; never a real phrase.
  • All 12 correct = 0.99^12 = 88.64%; at least one error = 11.36% (invented 1% per word).
  • Verify the backup with a test restore on a fresh mock wallet.
Recovery transcription risk
StepCalculationResult
One word correct1 - 0.010.99
All 12 correct0.99 ^ 1288.64%
At least one error1 - 0.886411.36%
Invented 1% error per word; classroom mathematics.

Rehearse recovery using a fresh, isolated mock wallet and the dummy placeholders only. Record the invented sequence, intentionally introduce and correct a practice transcription mistake if useful, and verify that the expected fictional wallet information is restored. Mark the backup tested only after the mock process succeeds. Real recovery phrases must never be typed into websites, photographed, uploaded into cloud notes, shared in support chats or copied into course submissions. In actual custody arrangements, compatible software, additional passphrases, configuration files or multiple keyholders may also be necessary, so a backup plan must account for all required components.

Wallet balance and transfer-size risk limits
Figure 19. Rehearse recovery on a fresh mock wallet.

Lab Six: The Ten-Item Preflight and Device Hygiene

Our hypothetical transaction policy requires a ten-item preflight checklist before sending more than 10% of a simulated wallet balance. Each completed check earns one point, and the required score is ten out of ten. The checklist verifies the correct network, complete destination comparison, successful test amount, checked amount and fee, independently opened official application, no suspicious link navigation, no recovery phrase entered, reviewed approvals, tested dummy backup and updated device. The policy is stricter for larger transfers but does not imply that smaller transfers are safe without checks. A failed or uncertain item should be resolved before proceeding.

For a fictional 1,000 SMP wallet, sending 150 SMP equals 150 divided by 1,000, or 15% of the balance. Because 15% exceeds the stated 10% threshold, all ten checks are mandatory before the simulated transfer. A separate 50 SMP transfer represents 5%, so the special ten-of-ten rule is not triggered, although core transaction safety remains necessary. The threshold is an invented educational rule, not a universal risk-management standard or proof that an approved transaction will succeed. As with the earlier risk-budget lesson, the goal is to define risk controls before an action rather than after an unwanted outcome.

Secure computing device maintenance
Figure 20. More than 10% of the balance needs all ten checks.

Key points

  • Ten checks: network, full address, test amount, amount and fee, official app, no link, no phrase typed, approvals reviewed, backup tested, device updated.
  • More than 10% of the balance needs 10 of 10: 150 of 1,000 SMP is 15%; 50 SMP is 5%.
  • Keep devices updated, avoid unknown software and check the hardware device screen.
Preflight rule
TransferShare of 1,000 SMPAbove 10%?Checks needed
150 SMP15%Yes10 of 10
50 SMP5%NoBasic checks
The ten checks
#Check
1Right network
2Full address compared
3Test amount sent and received
4Amount and fee checked
5Official app opened by me
6No link clicked
7No phrase typed
8Approvals reviewed
9Backup tested
10Device updated

Device hygiene supports these checks. Keep operating systems and wallet-related software updated, avoid unknown applications or extensions, and consider separating sensitive financial activity from everyday browsing. If using a hardware signing device, independently verify relevant details on its trusted display. Be cautious with unusual prompts and unexpected permissions even when the interface looks familiar. Updates, separate browser profiles and hardware devices can reduce some exposure but cannot eliminate phishing, compromised credentials, faulty decisions or all malware. The learner should document device status, checklist completion, hypothetical transfer amount and any reason for stopping.

Suspected Compromise, Journaling and Final Checkpoint

When compromise is suspected, stop interacting with the suspicious message, website, wallet interface or signing request. Do not provide recovery materials to anyone promising emergency assistance. Preserve relevant observations without copying secrets, and inspect account or wallet activity using independently verified methods from a trusted, clean environment. Depending on the situation, safe containment may involve reviewing and revoking permissions, securing remaining access, or evaluating whether assets can be moved safely using verified steps. Such actions can be complicated by malicious contracts, compromised devices, pending transactions or missing keys, so do not assume that one generic response will work in every case.

Learner organizing a complete wallet safety procedure
Figure 21. A four-line wallet safety checklist.
Learner completing the simulated wallet safety lab
Figure 22. Verify first, sign second.

Hands-On Lab: Verify, Score, Restore and Journal Mock Wallet Activity

Complete six exercises using fictional Sample Coin (SMP), Network Alpha, Network Beta, deliberately fake twelve-character destinations, reserved .test domains, mock phishing messages, fictional token permissions, and dummy recovery placeholders demo-1 through demo-12. Never use real addresses, private keys, seed phrases, wallet products, exchanges, websites, or actual transfers. Apply the specified fee convention: each network fee is deducted from the stated send amount. Treat all probabilities, phishing weights, thresholds and balances as invented teaching assumptions. For the final checklist, award one point per completed item and require ten out of ten before any simulated transfer exceeding 10% of the wallet balance. Record all calculations, verification steps, observations, status decisions and limitations in a dated mock execution journal.

  • Decision 1: A legitimate fictional destination is DEMO7F2K91XQ, while the suggested destination is DEMO7F2K19XQ. Both have twelve characters, and the learner notices that their beginnings and endings look similar. — Compare the complete identifiers, calculate their positional similarity, identify mismatched positions, and decide whether to proceed.
  • Decision 2: A fictional recipient accepts SMP only through Network Alpha. Alpha charges 0.5 SMP per transfer, Beta charges 0.1 SMP, and the learner intends to send 100 SMP with fees deducted from each stated amount. — Compare direct versus test-first transfers using Network Alpha, calculate recipient receipts and total fees, and explain why Network Beta is inappropriate.
  • Decision 3: The phishing scorecard assigns urgency 2 points, recovery phrase requests 5, domain mismatch 3, guaranteed rewards 3, unknown senders 1, and spelling errors 1. Scores of four or more require stopping. — Evaluate mock messages A, B and C, then explain why a zero-point message still requires checking through the independently opened official app.
  • Decision 4: A fictional wallet contains 1,000 SMP. One contract requests a limited allowance of 100 SMP, and another requests unrestricted token spending. Separately, twelve dummy recovery placeholders each have an invented independent 1% transcription-error probability. — Calculate the approval exposure percentages and the probability of an entirely correct dummy recovery transcription, then describe the safer verification procedure.
  • Decision 5: A simulated wallet holds 1,000 SMP and uses a ten-item preflight checklist. Every completed item earns one point, and the policy requires 10/10 before sending more than 10% of the balance. — Determine whether transfers of 150 SMP and 50 SMP trigger the full checklist, and outline what to journal after a suspected compromise.

Answer key

Check your answers
DecisionAnswerHorizonReason
#1The strings differ at positions 9 and 10, where 91 becomes 19. Ten of twelve characters match, or approximately 83.3%, but the destinations are different. Stop, obtain the verified fictional destination, and compare the entire string again.Before the simulated transferTen matching positions divided by twelve gives approximately 83.3% similarity, while two mismatched positions establish that the identifiers are not equal.
#2A direct 100 SMP Alpha transfer delivers 99.5 SMP after a 0.5 SMP fee. A 1 SMP test delivers 0.5 SMP, and the subsequent 99 SMP transfer delivers 98.5 SMP. Combined receipts are 99 SMP, total fees are 1.0 SMP, and testing adds 0.5 SMP relative to the direct method. Network Beta is unsupported by the recipient.Before and after the fictional test transferThe two Alpha transfers each deduct a 0.5 SMP fee, making their combined fees 1.0 SMP versus 0.5 SMP for one direct transfer.
#3Message A scores 10 from urgency, phrase request and domain mismatch, so stop. Message B scores 0 but must be verified independently inside the official app. Message C scores 4 from a promised reward and unknown sender, so stop and do not send tokens.Immediately upon receiving a fictional security messageThe specified weights produce 2 + 5 + 3 = 10 for A, zero identified flags for B, and 3 + 1 = 4 for C.
#4The limited approval exposes 100 SMP or 10% of the balance; the unrestricted approval exposes the full modeled 1,000 SMP or 100%. The chance that all twelve placeholders are correct is approximately 88.64%, and the chance of at least one error is approximately 11.36%. Review approvals and test restoration using dummy materials on a fresh isolated mock wallet.Before fictional contract authorization and during mock backup verificationApproval percentages equal allowance divided by 1,000, while 0.99 raised to the twelfth power gives approximately 88.64% correct transcription.
#5A 150 SMP transfer represents 15% and requires all ten checks. A 50 SMP transfer represents 5% and does not trigger the special threshold, although basic checks remain necessary. For suspected compromise, stop suspicious interaction, use independently verified clean-device procedures, review permissions, document the timeline without secrets, and report through trusted channels.Before each mock transfer and immediately after suspicious activityTransfer percentages equal 150/1,000 = 15% and 50/1,000 = 5%, and only the former exceeds the written ten-percent threshold.

A useful incident journal records the date, suspicious message features, mock destination, chosen network, attempted authorization, observed status, affected permissions, and actions taken. It should also document any reports made through independently verified channels, without including a real private key, recovery phrase or usable address. The journal separates evidence from assumptions and notes whether the device, account, contract or recovery process remains trustworthy. Learners should retain the original observations rather than rewriting them to make the outcome appear predictable. The previous custody lesson provides the broader context: key control determines who has recovery responsibilities, while counterparty and operational risks can remain under either model.

Key points

  • If compromise is suspected: stop, use a clean device, review approvals, report through verified channels.
  • Record a dated incident journal without exposing secrets.
  • Verify 10 of 12, 83.3%, 1.0 versus 0.5 SMP, 10/0/4, 10% versus 100%, 11.36% and 15%.
Final worksheet answers
LabResult
Address10 of 12 match (83.3%), still different
Network1.0 SMP versus 0.5 SMP in fees
PhishingA = 10, B = 0 (verify), C = 4
Permissions10% versus 100%
Recovery11.36% chance of at least one error
Preflight15% needs 10 of 10

The final checkpoint combines all six exercises. Identify the two mismatched positions in the twelve-character destination strings and calculate 83.3% positional similarity. Verify that the Alpha network test-first plan delivers 99 SMP after 1.0 SMP total fees, compared with 99.5 SMP directly. Score mock phishing messages A, B and C as ten, zero and four, while independently reviewing B. Calculate 10% limited approval versus 100% unlimited approval, and 88.64% error-free dummy transcription versus 11.36% chance of at least one error. Finally, show that a 150 SMP transfer from a 1,000 SMP balance is 15% and requires all ten preflight checks. Save the completed fictional safety journal.

Worked example at a glance

Wallet Safety Lab: Six Mock Exercises and One Preflight Rule
Destinations, networks and phishingApprovals, mock recovery and preflight
Lab environment: Fictional identifiers, .test domains, dummy recovery placeholders, simulated SMP onlyFictional wallet balance: 1,000 SMP
Legitimate mock address A: DEMO7F2K91XQLimited contract allowance: 100 SMP
Lookalike mock address B: DEMO7F2K19XQLimited approval exposure: 100 / 1,000 × 100 = 10%
Address length: 12 characters eachUnlimited allowance exposure: 1,000 SMP = 100% of the modeled balance
Mismatched positions: Positions 9 and 10: 91 versus 19Permission safety principle: Review contract identity, asset, action, allowance and consequences
Matching positions: 10 of 12Unused approvals: Review and revoke through verified mock workflows
Positional similarity: 10 / 12 × 100 = 83.333...% ≈ 83.3%Dummy recovery placeholders: demo-1 through demo-12; not a valid recovery phrase
Destination conclusion: Different strings mean different mock destinations despite high similarityInvented error probability per placeholder: 1%
Mock asset: Sample Coin (SMP)Probability one placeholder is correct: 1 - 0.01 = 0.99
Network Alpha transfer fee: 0.5 SMP per transferProbability all 12 are correct: 0.99^12 = 0.8863848717... ≈ 88.64%
Network Beta transfer fee: 0.1 SMP per transferProbability at least one error: (1 - 0.99^12) × 100 ≈ 11.36%
Recipient compatibility: Network Alpha onlyRecovery test: Restore dummy placeholders on a fresh isolated mock wallet and verify expected fictional details
Direct transfer amount: 100 SMPPreflight 1: Correct recipient-supported network
Direct Alpha fee: 0.5 SMP = 0.5% of 100 SMPPreflight 2: Entire destination string compared
Direct recipient receipt: 100 - 0.5 = 99.5 SMPPreflight 3: Test amount sent and arrival confirmed in simulation
First test amount: 1 SMPPreflight 4: Amount and network fee checked
First test recipient receipt: 1 - 0.5 = 0.5 SMPPreflight 5: Official application independently opened by learner
Second transfer amount: 99 SMPPreflight 6: No suspicious message link clicked
Second recipient receipt: 99 - 0.5 = 98.5 SMPPreflight 7: No real recovery phrase entered or shared
Total recipient receipt: 0.5 + 98.5 = 99 SMPPreflight 8: Relevant token approvals reviewed
Total two-transfer fees: 0.5 + 0.5 = 1.0 SMP = 1.0% of 100 SMPPreflight 9: Dummy backup successfully tested
Additional test cost: 1.0 - 0.5 = 0.5 SMP = 0.5% of 100 SMPPreflight 10: Practice device updated
Phishing: urgency or threat: 2 pointsScore calculation: 1 point per completed item; maximum 10
Phishing: recovery phrase request: 5 pointsLarge-transfer policy: More than 10% of wallet balance requires 10/10
Phishing: domain mismatch: 3 pointsMock large transfer: 150 / 1,000 × 100 = 15%
Phishing: guaranteed return or reward: 3 pointsLarge-transfer result: Full 10/10 preflight required
Phishing: unknown sender: 1 pointMock smaller transfer: 50 / 1,000 × 100 = 5%
Phishing: spelling errors: 1 pointSmaller-transfer result: Special 10/10 threshold not triggered; core checks still apply
Phishing threshold: Score >= 4: STOP and do not actDevice safety: Updates, trusted software, separate browser environment, device-screen verification
Mock official domain: example-wallet.test, for comparison only; never visit or treat as a real serviceSuspected compromise: Stop, isolate, verify on a clean device, review permissions, document and report
Message A: URGENT: verify your wallet within 24 hours at examp1e-wallet-support.test and enter your 12 wordsJournal fields: Date, exercise, mock inputs, checks, calculations, decision, status and lessons
Message A score: 2 urgency + 5 phrase request + 3 domain mismatch = 10; STOPActual credentials or transactions: Never permitted in this educational lab
Message B: You requested a withdrawal of 50 SMP at 10:05; if this was not you, open the official app yourself and review activity
Message B score: 0; still verify independently within the app
Message C: Support desk: send 1 SMP to unlock your 500 SMP reward
Message C score: 3 guaranteed reward + 1 unknown sender = 4; STOP
Scoring limitation: Invented teaching scorecard; low scores never establish authenticity
All wallet identifiers are deliberately invalid mock strings; all domains use the reserved .test suffix and must not be visited. Network Alpha, Network Beta and Sample Coin are fictional. The transaction calculations assume a fixed network fee deducted from each stated transfer amount. Phishing scores and transcription error probabilities are invented teaching assumptions, not measured security probabilities. The preflight 10/10 rule is an educational simulation rule and cannot guarantee safety. Never enter, store or disclose actual recovery phrases, private keys, account credentials or real wallet addresses in this lesson.

Key terms

  • Social engineering: manipulating a person, rather than code, to gain access or action.
  • Lookalike address: a destination that closely resembles a trusted one.
  • Address poisoning: planting a similar-looking address so you copy the wrong one.
  • Network: the blockchain a transfer moves over; it must match the recipient.
  • Test transaction: a small transfer sent first to confirm the route.
  • Phishing: deceptive messages that trick you into acting or revealing secrets.
  • Token approval: permission for a contract to spend your tokens.
  • Allowance: the amount a contract may spend under an approval.
  • Recovery phrase: secret words that can regenerate wallet keys; never share them.
  • Test restore: rehearsing recovery on a fresh wallet with dummy data.
  • Preflight checklist: checks completed before sending a transfer.
  • Hardware wallet: a dedicated device that signs transactions on its own screen.
Multi Asset Trading Lab provides educational information only and does not constitute personalized investment, trading, financial, cybersecurity, legal, tax, custody, or operational security advice. Every instrument, domain, identifier, network, address-like string, wallet balance, message, permission, transaction, probability, risk score and outcome in this lesson is entirely fictional and exists only for simulation and classroom calculations. No real assets, exchanges, wallet products, recovery phrases, private keys, seed phrases, addresses, websites, or prices are used. The deliberately fake identifiers DEMO7F2K91XQ and DEMO7F2K19XQ are twelve-character classroom strings, not usable blockchain destinations. The example domains example-wallet.test and examp1e-wallet-support.test use the reserved .test suffix and are fictional labels; they must not be opened or treated as actual services. The placeholders demo-1 through demo-12 are not a genuine recovery phrase and must never be replaced with real recovery words in a training system. No learner should enter, upload, photograph, share, or transmit actual recovery phrases, private keys, signing credentials, account passwords, or real wallet addresses as part of any exercise. Cryptocurrency transfers and smart-contract signatures may be irreversible, and incorrect destinations, network choices, malicious permissions, malware, phishing, or compromised signing devices can result in substantial permanent losses. Copy-and-paste is not sufficient to establish recipient authenticity because clipboard manipulation, address poisoning and compromised interfaces can substitute misleading information. Comparing the full destination reduces some avoidable mistakes but does not guarantee that the trusted source itself is authentic. The mock address similarity calculation identifies exactly two mismatched positions among twelve, giving approximately 83.3% similarity; a high character-match percentage is not evidence that two destinations are interchangeable. Network Alpha, Network Beta and Sample Coin (SMP) are fictional. The Alpha fee of 0.5 SMP and Beta fee of 0.1 SMP are invented and do not describe any actual network. The classroom assumes that each fee is deducted from the stated amount sent, so a direct 100 SMP transfer delivers 99.5 SMP, while a 1 SMP test followed by 99 SMP delivers 0.5 SMP and 98.5 SMP respectively, totaling 99 SMP after 1.0 SMP of fees. The test-first approach incurs an additional 0.5 SMP cost relative to the direct approach. Real transfer fees, token quantities, fee currencies, minimum amounts and settlement mechanics can differ substantially. A successful test transfer can identify some errors but does not guarantee subsequent transaction safety or recovery. The phishing scorecard is an invented heuristic for educational practice and is not a validated security classifier or a probability model. Its point allocations are urgency or threat 2, recovery phrase request 5, domain mismatch 3, guaranteed reward or return 3, unknown sender 1, and spelling errors 1. The four-point stopping rule is a classroom threshold only. Mock messages A, B and C score 10, 0 and 4 respectively under the stipulated classification assumptions. A score of zero never proves authenticity, and a high score does not establish the identity of a sender; all sensitive events must be independently verified through trusted channels. No reward, support request, urgent message, or apparent account alert should be used as a reason to share recovery materials or make unverified payments. Token approval calculations assume a fictional wallet holding 1,000 SMP, where a limited 100 SMP allowance represents 10% of the balance and an unrestricted allowance is modeled as exposing the full 1,000 SMP or 100%. Actual allowance mechanics depend on contract logic, token balances, delegated authority, signature types, prior approvals, and possible future deposits. A limited approval can reduce potential exposure but does not guarantee that the approved contract is safe. Revoking permissions may require a separate transaction and may not reverse already completed transfers or remedy every type of compromise. Wallet signing requests must be evaluated for contract identity, destination, network, requested function, amount, allowance and other meaningful consequences. Dedicated signing devices and isolated browser profiles may reduce some risks but cannot prevent all malicious approvals, device compromise, supply-chain attacks, or user mistakes. The recovery transcription example uses twelve dummy placeholders and an invented independent one-percent error probability for each placeholder. The modeled probability that all twelve are transcribed correctly is 0.99^12, approximately 88.64%, and the probability of at least one transcription error is approximately 11.36%. These values are teaching assumptions, not measured human-error rates, real wallet restoration failure probabilities, or predictions of backup success. The independence assumption may not hold in practice, and genuine recovery systems can include checksums, additional credentials, passphrases, multiple keys or other requirements. Test restoration in this course must use dummy credentials and a fresh isolated mock wallet only. Real recovery secrets should never be exposed to training platforms, online forms, customer support agents, shared documents, screenshots or ordinary cloud notes. The ten-item preflight is an invented educational procedure. It awards one point for each of the following: correct network, complete address comparison, confirmed test transaction, checked amount and fee, independently opened official app, no suspicious link navigation, no recovery phrase entered, reviewed token permissions, tested mock backup and updated device. Its stated rule requires all ten items before a simulated transaction greater than ten percent of the 1,000 SMP balance. The 150 SMP example equals 15% and triggers the ten-of-ten requirement, whereas the 50 SMP example equals 5% and does not trigger that additional threshold. Neither completing ten checks nor making a smaller transfer guarantees safety, correctness, settlement or recoverability. Device security, software integrity, trusted application access, user authorization, legal control and operational circumstances may create risks beyond the listed checks. If compromise is suspected, stopping interaction with suspicious software or contacts and preserving observations can reduce additional exposure, but response actions depend on what has been compromised. Transferring remaining real assets or revoking permissions may expose a user to additional risks if the signing environment remains compromised or the proposed transaction is malicious. The course does not instruct learners to perform real emergency transfers. In a real incident, independently verified professional assistance and appropriate reporting channels may be necessary; never provide usable recovery secrets to anyone claiming that disclosure is required for rescue. The previous lessons' custody responsibilities and risk-budget rules remain conceptual planning frameworks, not guarantees against theft, mistaken transfers, counterparty failure or financial loss. Every exercise uses simulated money and mock information only. No real purchase, sale, wallet connection, contract approval, network transaction, exchange account, or financial commitment is required or encouraged. Nothing in this lesson recommends a particular wallet product, security provider, blockchain network, financial instrument, investment strategy or real transaction.
Lesson practice

Lesson Checkpoint

Review what you learned and get feedback on your work.

0/20
01Why is comparing only the beginning and end of a destination string insufficient?
02Which network should be used in the fictional Sample Coin exercise?
03How should a fictional withdrawal notification with a phishing score of zero be handled?
04What is the main danger of granting an unlimited token approval?
05Which practices belong in the mock transaction verification workflow? Select all that apply.

Select all that apply

06Which actions reduce avoidable wallet security exposure? Select all that apply.

Select all that apply

07Which conclusion follows from the fictional address comparison?
Scenario

The strings DEMO7F2K91XQ and DEMO7F2K19XQ each have twelve characters, with ten matching positions and two mismatches.

08What is the correct interpretation of mock message C?
Scenario

An unknown sender offers to unlock a 500 SMP reward after receiving 1 SMP, and the scoring model assigns three points for guaranteed rewards and one for unknown senders.

09Which decision follows the written fictional preflight policy?
Scenario

A wallet contains 1,000 SMP, and the policy requires ten completed safety checks before any transfer exceeding 10% of the balance.

10Identify the incorrect statement in the fictional Network Alpha test-transfer calculation.
Network Alpha charges 0.5 SMP per transfer, deducted from the stated amount, and the learner sends a 1 SMP test followed by 99 SMP.

Select every line that contains an error

11Fill in the blanks

An attack that substitutes a destination through the operating system's copy-and-paste mechanism is commonly called clipboard .

12Fill in the blanks

Permission granted to a contract to spend a specified amount of tokens is called a token .

13Fill in the blanks

The safest exercise for checking recovery readiness without exposing genuine secrets uses a fresh wallet.

14Arrange the steps for the fictional address and Network Alpha test-transfer procedure.

Tap the steps in the correct order

    15Arrange the steps for the dummy recovery and large-transfer preflight exercise.

    Tap the steps in the correct order

      16Match each wallet safety concept to its meaning.
      Address poisoning
      Clipboard hijacking
      Network compatibility
      Test transfer
      Phishing
      Token allowance
      Unlimited approval
      Recovery test
      Preflight checklist
      Incident journal
      17Match each fictional wallet safety calculation to its correct result.
      Mock address length
      Differing address positions
      Matching address positions
      Address positional similarity
      Direct 100 SMP transfer fee
      Direct transfer recipient receipt
      Test transfer recipient receipt
      Second transfer recipient receipt
      Test-first total network fees
      Mock phishing message A score
      Mock phishing message B score
      Mock phishing message C score
      Limited token approval exposure
      Unlimited approval exposure
      Dummy transcription all-correct probability
      Dummy transcription any-error probability
      150 SMP transfer relative to wallet balance
      50 SMP transfer relative to wallet balance
      18The deliberately fake identifiers DEMO7F2K91XQ and DEMO7F2K19XQ have ten matching positions out of twelve. Calculate positional similarity as a percentage rounded to one decimal place.
      %
      19A fictional learner sends a 1 SMP test followed by 99 SMP on Network Alpha, which charges 0.5 SMP per transfer deducted from each stated send amount. Calculate total network fees.
      SMP
      20Twelve dummy recovery placeholders each have an invented independent 1% transcription-error probability. Calculate the chance of at least one error as a percentage, rounded to two decimal places.
      %
      Answered · 0/20