在 Move VM 上发布移动模块时出现 “MODULE_ADDRESS_DOES_NOT_MATCH_SENDER” 错误时遇到问题

Question

大家好，我正在尝试将 Move VM 集成到我的自定义网络中，但在尝试将 Move 模块发布到 Move VM 时遇到了问题. 我读过 Move VM “与平台无关”，如果能就所涉及的初始步骤以及此过程是否涉及大量工作提供指导，我将不胜感激. 此外，我遇到了一个特定的问题. stdlib尝试发布 Move 模块时，我不断收到以下与 Move 依赖项相关的错误：

VMError {
  major_status: MODULE_ADDRESS_DOES_NOT_MATCH_SENDER,
  sub_status: None,
  message: None,
  exec_state: None,
  location: Undefined,
  indices: [(AddressIdentifier, 0)],
  offsets: []
}
Below is a snippet of my code:


fn build_and_publish_package(package_path: &str) {
  // Code for compiling the package and obtaining compiled units
  let instance = MoveVM::new(vec![]).unwrap();
  let myresolver = MyResolver::new();
  let mut new_session = instance.new_session(&myresolver);
  let sender_address = AccountAddress::ONE;
  let _ = new_session
    .publish_module_bundle(modules.clone(), sender_address, &mut UnmeteredGasMeter {})
    .unwrap();
}

stdlib在我的 Move.toml 文件中，0x1为其分配了地址. 重要的是，我没有在stdlib代码中的任何地方使用. 尽管如此，我还是经常遇到上面提到的错误. 有人能帮我了解可能出了什么问题或提供有效解决这个问题的见解吗？

Jackson · Answer

The problem youre facing is due to compiling the Move package in moving test mode, which includes a stdlib Move module with a different address assigned to it. When compiling the package, ensure that you are not including the stdlib Move module or any other modules with conflicting addresses. Compile the Move package without test mode to resolve the address mismatch issue. This should resolve the error youre encountering during module publishing. If you have any questions, you can ask them here;

Steven · Answer

The error message youre encountering, VMError { major_status: MODULE_ADDRESS_DOES_NOT_MATCH_SENDER, sub_status: None, message: None, exec_state: None, location: Undefined, indices: [(AddressIdentifier, 0)], offsets: [] } indicates that the address of the module youre trying to publish does not match the senders address. In the Move VM, the senders address is determined by the account that initiates the transaction. If the address of the module youre trying to publish does not match this senders address, you will encounter this error. In your code, youre setting the senders address to AccountAddress::ONE, which corresponds to the address 0x1. However, your Move.toml file assigns the stdlib address to 0x1. Even though youre not using the stdlib in your code, the Move VM still checks for this address when publishing a module. To resolve this issue, you can try changing the senders address to a different value that doesnt conflict with the stdlib address. For example: let sender_address = AccountAddress::new([2u8; AccountAddress::LENGTH]); This will assign the senders address to 0x2, which should not conflict with the stdlib address. As for the process of integrating Move VM into your custom network, it can be relatively straightforward or it can require a significant amount of effort, often referred to as lift. This largely depends on the complexity of your network and the specifics of your applications.

帖子

分享您的知识。

在 Move VM 上发布移动模块时出现 “MODULE_ADDRESS_DOES_NOT_MATCH_SENDER” 错误时遇到问题

答案

你知道答案吗？

赚取你的 1000 Sui 份额