For most DeFi objects, if they are associated with different MVR packages, it may imply potential risks.

We are pleased to announce the Move Registry (MVR), a package registry for promoting interop and code reuse between Sui apps! If you’re familiar with package registries like NPM or crates.io, you can probably guess how MVR can help you: - Give your Move package a human-readable name - Link your package’s source code (replacing the need to upload separately to each explorer) - Link arbitrary metadata to your package (e.g., your package’s website or MCP server) - Link your testnet and mainnet package ID's - Allow Move developers to depend on your package by name (instead of by ID) in Move.toml (and seamlessly switch between testnet and mainnet deps, as well as different versions) - Allow TypeScript developers to use your package name (instead of ID) in constructing PTBs and performing read queries - [soon] Look up your package metadata and source by name in explorers - [soon] MVR portal for browsing popular packages, see package analytics (transactions, active wallets, dependencies, composability, …) We’re particularly excited about the latter because surfacing verified usage data alongside the code is unique to MVR/Sui. Other package registries have code, download counts, dependency info, etc., but no connection to runtime package usage. This is really powerful stuff. If you're a Sui dev, we need your help in onboarding all popular Sui packages to MVR, making Sui packages open source by default, and enabling radical composability by eliminating the need to ask “what’s the package ID” ever again. Please take a look and consider registering your package! - Onboarding guide mystenlabs.notion.site/Move-… - Docs docs.suins.io/move-registry - Registry site moveregistry.com/