A Telegram onboarding lesson for a Sui community

Telegram favors short, well-timed explanations, but a fast channel can make a wallet action look simpler than it is. A community lesson should give readers one stable reference message, one annotated example, and a place to ask questions without turning the chat into a sequence of unverified instructions.

Pin the vocabulary first

The pinned primer should define wallet, Sui network, asset identity, gas, quote, signature, and transaction digest. Keep each definition to one sentence, then link to the longer Sui introduction. Explain that a ticker is not a complete asset identity and that a wallet connection is separate from a signature.

Use a text example that readers can inspect on a phone:

Network: Sui mainnet
Input asset: [full type or verified label]
Output asset: [full type or verified label]
Quoted output: [value from the current screen]
Minimum received: [value from the current screen]
Gas and slippage: [values shown in the review]

Mark every value as an example unless it came from the reader’s current screen. Never paste a private key or ask a member to share a seed phrase.

Demonstrate the action in three messages

Message one names the task: “Find the asset identity and quote fields.” Message two walks through a redacted screen or a read-only response. Message three asks the member to repeat the checks in their own wallet. A moderator can use the same sequence for a stablecoin transfer or a swap review.

If the community uses the participant kit, keep the distinction visible. The six tools read public status, stage, history, Desk, or partner data, and the action tool creates a review-only route. It does not quote, build, sign, send, activate a referral, or mint an NFT. A tool result with an asOf timestamp is evidence of a read at that time, not a promise about a later quote.

Make the Q&A state-based

Answer questions by state rather than by guess:

• No wallet connected: explain how to choose the intended wallet; do not imply an authorization occurred.
• Quote visible: define output, minimum received, gas, route, and slippage; say that the quote can change.
• Wallet prompt visible: tell the member to inspect recipient, assets, amount, network, and gas.
• Pending: explain that confirmation is still missing.
• Confirmed: point to the digest and service readback.
• Unavailable: preserve the gap and give the next documented check.

For a referral question, explain that a link can be opened without creating an attributed wallet. For a Points question, direct the reader to the confirmed and verified record. The partner guide explains why Partner Points, Trust, accrued revenue, and payout status should remain separate.

Keep moderation honest

Moderators can pin corrections and record the date of a changed field. They should remove or correct invented prices, fixed gas amounts, unsupported provider availability, and claims that a plan earned Points. If a member posts a digest, ask them to use the official explorer or service readback rather than treating a screenshot as the ledger.

The strongest Telegram lesson is adaptable: the vocabulary stays stable, the example is clearly labelled, and the reader practices the review on their own screen. That keeps the community useful when routes, assets, or service status change.