Sui devnet 会在一段时间后删除 Move 包和合约吗？

Question

我最近在 Sui 开发网络上部署了一个合约，一切运行正常. 我能够毫无问题地与合同进行互动. 但是，本周，我的Move包裹ID似乎消失了. 我再也无法在 Sui 开发网络资源管理器上找到它了. 我有已部署的 [合约]（suiexplorer.com/object/ 0x6b0903399d48974bb1a550925c5497a550925c5497a1d974f0bda070a07d93ad0632f20510eenetwork=devnet）的链接，该合约上周可以正常运行，但现在无法使用. 我很困惑在使用开发网络时是否需要每周重新部署合同.

以前，我成功使用了以下命令：

sui client call --function modify_threshold --module multisig --package $PACKAGE_ID --args 0x6beaaefd6387c5f91d3f0fa341390a7cf05c6a6f52efcc8ce6416b63253c3137 2 --gas-budget 10000000
echo $PACKAGE_ID (result: 0xa67043c277b23ec7b770ae049d18176aa7a8ed66b90a314117aeea10dd271b6c)

但是现在，我收到了错误消息：包对象不存在 ID 0xa67043c277b23ec7b770ae049d18176aa7a8ed66b90a314117aeea10dd271b6c

如果有任何关于这个问题的回复或想法，我将不胜感激.

此外，我想知道如何在本地更新我的 Sui 开发网络客户端. 我遇到了来自 SUI CLI 的以下警告： [警告] 客户端/服务器 API 版本不匹配，客户端 API 版本：1.9.0，服务器 API 版本：1.10.0

Jeremy · Answer

The issue youre experiencing seems to be two-fold: the disappearance of your package ID and the API version mismatch warning in your Sui devnet client. Package ID Disappearance: The disappearance of your package ID might be due to a network reset or other operational changes in the Sui devnet. According to the Sui DevNet Public Release, the Sui team prioritizes operational experience over stability in the early stages of the devnet. This means that there may be no backward compatibility and no Service Level Agreement (SLA) for network resets. Therefore, its possible that the package ID was reset or removed due to these operational changes. API Version Mismatch: The warning message youre seeing indicates a mismatch between the API versions of your Sui client and the server. This could be due to a recent update to the Sui server that your client has not yet been updated to accommodate. You can check the latest releases of the Sui server on their GitHub releases page. If theres a new release, you may need to update your Sui client to match the servers API version. To update your Sui devnet client locally, you can follow these steps: Check the latest release of the Sui server on their GitHub releases page. Download the latest release that matches your operating system. Replace the existing Sui binary in your local environment with the downloaded binary. Verify the update by checking the version of your Sui client using the command sui version. Please note that these are general suggestions and may not be applicable or feasible in the specific context of the Sui framework. For a more accurate and specific solution, it would be best to consult the Sui documentation or seek advice from the Sui community.

Steven · Answer

When interacting with Sui devnet, it is indeed expected to redeploy the Move smart contracts regularly. The Sui devnet undergoes a wipe approximately once per week, typically tied to significant updates. On the other hand, testnet wipes happen more infrequently and are usually announced. To update your installation, if you used cargo install, simply repeat the installation process. If you maintain your local repo, perform a git pull followed by cargo build -p sui. An alternative approach to minimize version mismatches is to use suibase, a third-party open-source project that maintains a local repo for each network (localnet, devnet, testnet, mainnet). By utilizing suibase, you can simply execute devnet update to install the latest available version corresponding to the Sui devnet. Keep in mind that developers may encounter warnings due to version mismatches, which are often visible to everyone, as the latest devnet branch version and server configurations are beyond our control. Despite this, Mysten Labs strives not to impede developers, and historically, minor version mismatches have not posed significant problems. If you have further questions or need assistance with a different approach, feel free to ask them here;

帖子

分享您的知识。

Sui devnet 会在一段时间后删除 Move 包和合约吗？

答案

你知道答案吗？

赚取你的 1000 Sui 份额