Sui just tested AI wallets. The agent still doesn't hold the keys.
Seal MPC changes the job of an AI agent from custodian to proposer. That's a cleaner model, but it's still testnet code.
CryptoVibe Desk · sui · ai-agents · mpc
- →Mysten Labs reportedly launched a Seal MPC prototype on Sui testnet for AI agents that propose payments without holding private keys.
- →The real change is where control lives: key custody sits across servers, while spending rules run through Move contracts.
- →Watch whether Mysten confirms mainnet and audits before real funds move, because the June target is still unverified.
- MPC → Multi-party computation lets several servers approve a cryptographic action without any one server holding the full secret.
- private key → A private key is the secret that lets a wallet sign transactions and move funds.
- Move → Move is Sui's smart contract language, built to handle digital assets with strict ownership rules.
- testnet → A testnet is a live testing network where developers can try software before real funds are at risk.
Sui's AI wallet test is about custody. According to Crypto Briefing, Mysten Labs launched a Seal MPC prototype on Sui testnet. The prototype lets AI agents propose financial transactions without holding private keys.
That sounds small. It isn't. The bet is simple: agents should ask to spend, not own the secret that spends. Most agent-payment demos still put too much trust in the agent, the app, or a hosted wallet.
Seal MPC flips that model. The agent asks for a transaction. The key server network and Move policy decide whether it can happen.
At the contract level, that matters. Spending caps, approval thresholds, and counterparty rules can live on-chain in Move. Crypto Briefing says the system can express some rules in natural language. Those include daily caps and blocked counterparties.
Treat that part carefully for now. Natural language is a user interface, not the enforcement layer. The enforcement layer is the real story.
Move was built for digital asset rules, first at Meta's Diem project and then inside Sui. If a policy says an agent can spend only up to a daily cap, the contract should enforce that state. If a counterparty is blocked, the transaction should fail before signing becomes the issue.
This is a backpressure problem, not a chatbot problem. You don't want the agent to own the key and then hope prompts behave. You want the agent to hit a policy gate that can reject bad output. If you're building agent payments, your bag depends on where that gate sits.
Seal's earlier key server testnet reportedly went live on March 12, 2026. The MPC prototype builds on that server network. The broader Sui stack also includes Walrus for decentralized storage, encrypted messaging, and secure enclaves. The shape is clear: Mysten wants AI agents to use Sui rails without turning every agent into a hot wallet.
And that's the catch. This is still a testnet prototype. The brief has one Tier-2 source, and no official Mysten Labs post was present in the source cluster. Crypto Briefing also reported an anticipated mainnet launch around June 18, 2026.
As of June 20, 2026, that date has passed without confirmed go-live in the provided material. So the stance is narrow. Seal MPC is a better custody primitive than giving agents keys. It makes agents transaction proposers, not keyholders.
But until Mysten ships audits, mainnet confirmation, and stress-test results, the correct label is promising infrastructure. It is not production payment rails.
Mysten's choice to keep Seal MPC at prototype stage is the right constraint because agent payments need failed-policy tests before real funds move.
Before July 31, 2026, watch for Mysten to publish a mainnet confirmation plus audit notes, with a public contract address as the falsifiable signal.
Primary links and supporting reads used by the desk for this story.
Forward this.
