What Is Sui Wallet? The Former Name for Slush

2026-08-24

Sui Wallet is the former Mysten product name; Mysten announced on 2025-04-24 that Sui Wallet and Stashed were combined under the Slush name. This neutral profile separates the documented system, its current naming, and the stated role of SUI.

This profile answers the identity and mechanism question first, then keeps the project name, its documented components, and its changing service state separate. The search phrases “sui wallet extension”; “sui wallet security”; “sui wallet setup” can describe a reader's lookup intent, but they do not prove a product feature, a current entitlement, or a financial conclusion. The article therefore uses source-scoped language and does not treat a ticker or a user-facing interface as a shortcut for the entire system.

What Is Sui Wallet and Slush

Sui Wallet and Slush should be read through the scope of their current primary materials. The accurate subject is therefore a custody and product-naming boundary: the historical product label, the current Slush product, and the broader category of wallets that support Sui are not identical things. That framing avoids a common error in project profiles: using one label for an organization, a protocol, an interface, an asset, and every service that may be associated with them. A careful description names the layer being discussed and does not assume that a statement about one layer automatically proves a statement about another.

Everything difficult about this subject is a naming problem, and the product history makes that concrete. Sui Wallet is a former Mysten product label, Slush is the current product, Sui is the network, and SUI is the network asset; four different subjects share three overlapping names. Material published before 2025-04-24 can be accurate about the extension it described and still misdescribe what a reader will install today. Keeping the label, the date and the layer attached to each statement is what allows old and new sources to be read side by side without merging them.

The rename has a date, and it was more than a rename. Mysten Labs published a post titled Sui Wallet and Stashed are Now Slush on 2025-04-24, describing a merger of the Sui Wallet extension with Stashed rather than a change of label alone; the post states that the change arrived as an ordinary update, that no reinstall or migration was needed, and that accounts, recovery phrases and wallet addresses were unchanged. Stashed Links became Slush Links and the zkLogin capability was folded in. The web application is at my.slush.app and the site's footer names Mysten Labs, Inc.

What Documentation Scope Helps Explain

At the mechanism level, a self-custody wallet is best understood as software managing authorization material for onchain activity, while assets and public records remain on the network rather than inside the application. The important point is not a promise about performance; it is the relationship the documents describe between components. Those components can have different update schedules, permissions, technical dependencies, and operational conditions. Explaining the relationship helps a reader see why a product label alone is not enough to determine what a particular record, feature, or asset actually represents.

The documented mechanism also needs a boundary around evidence. Public documentation usually has a publisher, a date, a product version, and a limited subject. It may be changed or superseded. A precise profile can say that a page describes a stated architecture, but it should not silently expand that page into a claim that every related application is live, every integration is current, or every future roadmap item has arrived. Those are distinct claims that need their own current source.

How the Components and Boundaries Differ

SUI belongs in the profile as a documented asset role, not as a verdict about ownership or value. SUI is the native network asset used for Sui network functions. It is not a token issued by the former Sui Wallet product or by Slush. A ticker is especially weak evidence when similarly named assets, multiple networks, receipt tokens, implementation contracts, or historical deployments exist. The release-day check should compare the project's current official identifier with the relevant official record, retain the network context, and avoid treating a copied symbol as definitive proof.

A useful way to read the asset section is to ask what it does in the documented system, what it does not establish, and which claims remain time-sensitive. A described coordination, access, security, or participation role does not automatically give every holder a product right, a governance result, a distribution right, or a service guarantee. The source may use conditional language, and a neutral profile should preserve that condition rather than replacing it with a stronger statement.

What SUI Does in the System

The project ecosystem should also be interpreted narrowly. A documentation hub can show components, code, environments, providers, or interface categories, but it is not automatically a permanent list of active partners or supported services. The word ecosystem is useful only when it points back to a defined source scope. It should not be used to imply that an organization controls every related application or that every named integration continues without interruption.

The current product and its terms should be attributed to Slush, while historical claims about Sui Wallet should retain their date and source scope. This distinction matters because product names and protocol names often persist while their interfaces, permissions, contracts, policies, and availability change. A profile that identifies both the current source and its exact claim gives readers a way to revisit the evidence later. A profile that turns a dated page into a permanent assertion gives a false sense of certainty.

The Sui Wallet and Slush Ecosystem and Documentation Scope

zkLogin is a Sui authentication primitive that can appear in application experiences; it should not be compressed into a claim that every wallet, account type, or recovery arrangement has the same properties. This is why network labels, contracts, mint records, or application URLs are release-day facts rather than evergreen prose. A neutral article can explain the categories involved without asking a reader to take an action. It should record the difference between an official identifier and an operational instruction, and it should not convert a verification principle into a deposit, claim, bridge, staking, or account-management tutorial.

What Is Sui Wallet? The Former Name for Slush documentation overview

There are technical limits as well as naming limits. Software has implementation assumptions; services depend on infrastructure; contracts can expose administrative controls; and offchain records can have different retention, privacy, and update properties from onchain records. An architecture description is not an audit, and an audit notice is not a blanket security guarantee. These distinctions matter more when a project involves data, identity, delegated execution, authorization material, or a changing token structure.

The most useful thing to know about the extension is its identifier. The Chrome Web Store listing is published by Mysten Labs under extension ID opcgpfmipidbgpenhmajoajpbobppdil, shows a display name of Slush, and as of 2026-08-15 reported about 800,000 users and a last update on that same date. The older store address containing sui-wallet still resolves and redirects to the current canonical address, which is itself the clearest evidence that one listing was renamed rather than replaced. Official mobile builds for iOS and Android are linked from slush.app/download, and the official channels named in the site footer are Discord, X, Instagram, YouTube and support.slush.app; there is no official Telegram.

A Specific Design Boundary

The source boundary is also a reader-safety boundary, and for a browser extension the boundary is an identifier rather than an address. The Chrome Web Store listing is published by Mysten Labs under the extension ID opcgpfmipidbgpenhmajoajpbobppdil and shows a display name of Slush; the older store address containing sui-wallet still resolves and redirects to it, which is itself the evidence that one listing was renamed rather than replaced. A lookalike can copy the name, the icon and the screenshots, but it cannot occupy that ID. The web application is best reached by typing my.slush.app rather than by following a link.

Credential loss, phishing, misleading links, malicious application prompts, irreversible onchain effects, and changing product terms remain risks even where software offers safety features. These risks do not mean that the documented design is invalid; they mean that a short profile should not overstate what it establishes. The proper conclusion is conditional: documentation supports the mechanism it actually describes, subject to implementation, governance, source freshness, and the surrounding technical and legal context. Readers need more current evidence for claims about access, performance, holdings, allocations, audit coverage, or regional treatment.

Risks and Limitations

Risk also arises when distinct terms are merged. A network is not automatically a wallet, a proof is not automatically raw data, a receipt is not automatically the protocol asset, and a public identifier is not automatically the only valid deployment. Keeping these distinctions visible makes it easier to notice false equivalence, unsupported entitlement claims, and time-sensitive statements. It also makes the article useful without turning it into a comparison, endorsement, or operational guide.

Neutral verification begins with the official project domain and its documentation hierarchy. Check the exact name used by the publisher, the stated role of SUI, and the scope of any current technical or legal notice. If an official page provides a contract address or equivalent identifier, compare the date, network, and label with the corresponding official block explorer record. Do not infer a relationship from a matching ticker, a copied address, or a page whose scope is unrelated to the claim being made.

Two limits are worth stating precisely. First, the security page describes non-custodial key handling, an open-source community-maintained phishing blocklist, hardware-wallet integration and scam detection, but it discloses no specific counterfeit extension or phishing site; this article therefore names none, because inventing an example would be worse than describing the check. The practical rule is that the official entry points listed above are the complete set, and anything outside that set should not be installed. Second, the scope is narrower than the word wallet suggests, because Slush supports Sui only and is not a multi-chain wallet.

How to Verify Sui Wallet and Slush Information

Nearly every checkable fact above sits on one of three pages. The Chrome Web Store listing, for the extension ID, the publisher name, the display name, the reported user count and the last update date; the download links for the official mobile builds; and the channel list in the site footer, including the statement that there is no official Telegram. The rename post and its date belong in the same pass. This second pass matters because an accurate description of self-custody can stay true for years while a store listing, a download page and a support address all move.

Sui Wallet and Slush can therefore be introduced as a documented system with distinct layers rather than as a single undifferentiated product. SUI should be described only through its sourced role, and every more specific claim should retain its network, contract, interface, or product context. This explains the project without treating documentation as an offer, a guarantee, or an instruction.

The identifier check is the one step that appearance cannot fake. The store listing can be opened and the extension ID compared character by character with opcgpfmipidbgpenhmajoajpbobppdil, with the publisher confirmed as Mysten Labs; a lookalike listing can copy the name, the icon and the screenshots, but it cannot occupy the same identifier. The same principle applies to the web application, which is best reached by typing my.slush.app rather than by following a link, and to support, which is best reached from the address in the site footer rather than from an unsolicited message.

Conclusion

The core interpretive rule is separation. A project label is not every product layer. A token symbol is not every contract or network. A current interface is not a timeless availability statement. A technical description is not a security certification. Once those distinctions are made explicit, the reader can compare sources more carefully and avoid projecting a claim from one category into another.

For a release-ready version, keep the mechanism, asset role, and document boundary in separate sentences. Do not add claims about supply, allocations, audits, governance, partners, legal status, performance, or access unless a fresh official source covers the precise claim. If a statement is conditional or forward-looking in the source, preserve that wording. This approach is deliberately conservative because it is more accurate for systems whose product, network, and token details can change.

In summary, the responsible question is not merely what is Sui Wallet and Slush, but what exact layer a source describes, what SUI is documented to do, and which facts still need release-day verification. That approach leaves room for readers to investigate official records while keeping the article educational, neutral, and free of financial conclusions or product-operation instructions.