Sui Adds Move Clock Borrowing Without a Clock Input

Sui is adding `sui::clock::borrow(): &Clock`, allowing Move functions to access the transaction’s Clock without requiring it as an input or passing it through every caller. The Sui Clock borrow feature returns the same timestamp as an explicitly supplied Clock and records the Clock version as a read-only root in transaction effects. The change is scheduled for protocol version 141 with a Sui framework upgrade. Tests cover version pinning, fullnode replay and simulation, and reads in transactions that abort. The feature changes how Move applications access time; the article does not describe changes to SUI token economics.
Neutral
This is a Sui framework and developer-tooling change, not a tokenomics update or a major shift in network demand. It lets Move code access the transaction’s Clock without passing it as an input, while preserving version consistency and recording the implicit read in transaction effects. The upgrade is planned for protocol version 141. No immediate change to SUI supply, staking, fees, or transaction capacity is described, so a significant direct trading catalyst is unlikely. Short-term, traders may see little price response beyond any broader reaction to the protocol upgrade. Longer-term, simpler time access could make some Move application code easier to build and maintain, but any effect on SUI usage would depend on developer adoption and resulting application activity. As with other developer-focused upgrades, market impact would be more meaningful if followed by measurable growth in usage, fees, or ecosystem activity.