Teaching Sui transactions in an education lesson

Teaching Sui transactions works best when students encounter the concepts in the same order as the action. Start with the object or asset they can identify, move through the transaction inputs and gas, and end with the wallet signature and confirmed digest.

A lesson in three passes

The first pass is vocabulary. Show that Sui organizes onchain state around objects with unique IDs, owners, versions, and transaction metadata. Contrast an address-owned object with a shared object without asking students to memorize every ownership variant. The official object-model documentation supports this distinction.

The second pass is composition. Use a token transfer to show inputs, recipient, and gas. Then show a small programmable transaction block example as a sequence of commands. Explain that a PTB can compose operations while the wallet still presents a transaction for the signer to inspect. Students should learn to ask which object is read, changed, or created.

The third pass is evidence. Have students label a review screen, a wallet prompt, a submitted digest, and a service readback. A quote is not a confirmation. A submitted transaction is not necessarily a verified activity record. A pending row is not an empty history.

Use a controlled exercise

Give each student a redacted fixture with a network, asset type, amount, and gas field. Ask them to answer:

1. Which value identifies the asset beyond its ticker?
2. Which account or object is expected to sign?
3. Which fee is being paid to the network?
4. Which screen would reveal the final transaction details?
5. What evidence would show that the service recorded the result?

Then give one negative fixture with a malformed coin type or missing amount. The expected response is a correction request, not a guessed value. Do not use a live wallet or real funds in a beginner exercise unless the course has a separate, documented safety process.

Introduce tools without hiding agency

An AI or MCP tool can return documentation, a public status, or a review checklist. The current participant kit exposes six read-only tools and a review-only action plan. It does not boot a wallet, quote, build, sign, send, activate a referral, or mint an NFT. Ask students to identify the tool’s source origin and asOf timestamp, then compare the result with the app documentation.

If the course covers Points, keep the arithmetic grounded in a confirmed record. The current Swap rule is one Point per $4 of verified volume. A $40 verified record corresponds to 10 Points; a prompt or simulation does not. If the course covers partners, explain that Trust derives from credited Partner Points at one fifth with fractional precision, while accrued revenue and payout state remain separate.

Assess explanation, not memorization

End with a short written explanation: “An object is __; gas is __; signing means __; confirmation is __; service verification is __.” Review whether the student keeps the stages distinct and names the source of each claim. This assessment still works if a provider label or wallet interface changes.

Link the class to the first Sui transaction guide and the simulation lesson. A good Sui lesson leaves students with a durable way to inspect a transaction and a clear understanding of which decision remains theirs.