SEI — New Player Onboarding

Evidence scope: The behavior below is from the pinned Solidity source. A source-file hash does not establish deployed bytecode equivalence. Check the selected deployment and caller before sending a transaction.

What this is

SEI uses CHAN.Yan(tx.origin) to find the origin’s YUE. A wallet can have no registered YUE before onboarding and at most one entry in that registry at a time. CHAN’s transfer operation can move that association to another origin.

What you actually do with it

• Start(lau, name, symbol) returns both (YUE, LAU) addresses. On the first call it enters the supplied owned LAU through CHO, creates a YUE, gives CHAN ownership, and registers the YUE for tx.origin.
• When a YUE already exists, Start uses Chi() and renames the existing YUE. The supplied LAU argument is not used to switch the active character in this branch. Use CHO.Enter for that separate change.
• Chi() is a caller-sensitive view returning the registered YUE and CHO’s currently active LAU for tx.origin. It reverts NotStarted if no YUE is registered.

Use these calls here. Simulations preview the current state; each confirmed call is a separate transaction.

SEI

0x3dC54d46e030C42979f33C9992348a990acb6067

SEI.Start(address LauToken, string YueName, string YueSymbol)Simulate / call

Open this function to load its call form.

SEI.Chi()Read

Open this function to load its call form.

Requirements & gating

First-time Start reaches CHO’s LAU ownership check. Repeated Start still depends on SEI being authorized to rename the existing YUE. It also calls SEI’s _mintToCap, so describing the transaction as having no token-side effects would be inaccurate.

Where it connects

SEI source, CHAN, and CHOA. CHOA.Play reads an existing pair; it does not create the YUE. Creating another LAU does not by itself create another YUE for the same origin.