User — Your Character Sheet
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
Section titled “What this is”User contains Soul, On (Bao), Username and Entropy. CHO.Enter builds a record for tx.origin from a supplied owned LAU and sets On.Phi to that LAU. CHO stores the result in its delegate registry; it is not rebuilt from every LAU attribute on every read.
What you actually do with it
Section titled “What you actually do with it”Use LAU.Username(string) for the Username attribute and CHO.Enter to refresh/select the active delegate. Rename changes ERC-20 name/symbol instead. CHO’s User getters may react and update entropy; distinguish view getters from state-changing previews.
Use these calls here. Simulations preview the current state; each confirmed call is a separate transaction.
LAU.Username()Read
Open this function to load its call form.
CHO.GetUser()Simulate / call
Open this function to load its call form.
Identity limits
Section titled “Identity limits”Soul is the current session’s Saat(1), not an immutable wallet identifier: LAU.Void can replace Saat and On. A QING event carrying a Soul does not prove its transaction sender owned the LAU. Keep the wallet, LAU address, session identity and ownership evidence separate.
Where it connects
Section titled “Where it connects”User source, CHO, LAU and VOID.