When product = marketing, which promises lie, not dragging friends into a hole.
Prepaid referral trees neighbor promise pyramids
If income is promised “from the tail” and you must pay first — read economics skeptically. Friend pressure amplifies mistakes. Experimental limit only. Leaving the tree without guilt is fine.
Don’t connect the main wallet “so the referral counts”.
---
Why “referral” shows up exactly when you rush
“Referral trees: honestly about the user’s role” usually matters not on a calm Sunday night, but when the feed screams urgency. Hands outrun eyes. This block is intentionally slow: contour first, button second.
Frame in short: When product = marketing, which promises lie, not dragging friends into a hole. If someone sells that frame as guaranteed yield — different genre, not a manual.
Telegram is almost always nearby: channel, bot, Mini App, DM. Distribution is fast — clones too. Any step on “referral” starts with where the entry came from and which wallet is active.
A risk map for the “referral” scenario
Risks around “referral” mix technical and social. Technical: address, memo, network, spender, DNS. Social: “admin”, referral, urgent timer, comment screenshot. Different habits, one stop — Confirm.
Device risk: clipboard trojan, chat apk, screen share with seed in frame. If the hardware already feels foreign, “referral” can wait; clean key contour first.
Money ceiling: an amount you can lose on a UI mistake without shame. Without a ceiling every guide becomes theater.
A no-heroics walkthrough — “referral” focus
Reference entry → favorites → experimental wallet → read preview → dust → history check → size. Skipping dust “because the site looks familiar” is the costliest minute saved in “referral”.
At preview, say aloud: action type, spender/recipient, amount. If your tongue trips — too early. Cancel doesn’t make you “not degen”; it leaves you tomorrow.
Private log: link/bot, time, tx. Season memory lies. Logs don’t.
How the catalog helps (and doesn’t) with “referral”
TON Web Search next to “referral” helps find a storefront and compare lookalikes. Card statuses are snapshots. Don’t read the index as an audit. Matching a brand pin is mandatory when a brand exists.
Filters remove noise. They don’t remove signature responsibility. If a card is offline — don’t grab a comment “mirror”; only an official entry-change announce.
A week after reading about “referral”
One rule for seven days, tied to “referral”. Example: no favorite, no entry; no dust, no large tap; no global brand username hunt. Check the rule at night — yes/no.
Review: approvals, bookmarks, junk tokens, client update from an official source. Seed offline. Main and experimental contours split. Then “Referral trees: honestly about the user’s role” becomes daily life, not a quest.
How “referral” links to other ecosystem habits
Even when today’s focus is “Referral trees: honestly about the user’s role”, seed hygiene, username anti-phishing, wallet separation, and exchange memo care still matter. You don’t need to learn everything at once. You need to not break the base while handling the special case “referral”.
Leave TON Web Search as an entry map. Maps can be closed. Keys and limits cannot.
“referral” practice: three kill-switches
First kill-switch — source. If the entry for “Referral trees: honestly about the user’s role” didn’t come from the pin or your favorites, you’re already in a higher-risk zone. Second — wallet: experimental for new, main for known and verified. Third — size: dust before volume. Three switches close most everyday failure stories around “referral”.
Reminder frame: When product = marketing, which promises lie, not dragging friends into a hole. Don’t turn the frame into a “hurry” slogan. Refusing also counts as being on time.
FAQ without fluff (about referral)
**Do I need the main wallet?** Usually no. An experimental limit is enough to learn “referral”.
**What if friends are already in?** Their deposit doesn’t insure yours. Source checks stay yours.
**What if the catalog card is online?** That’s an entry-availability snapshot, not an audit. Next — pin and preview.
**What if I already signed something weird?** Don’t enter a seed into “recovery helpers”. New contour, clean device, move remainder.