Problemas para publicar, mover el módulo a mover la máquina virtual con el error «MODULE_ADDRESS_DOES_NOT_MATCH_SENDER»

Question

Hola a todos, estoy intentando integrar Move VM en mi red personalizada y tengo problemas al intentar publicar un módulo Move en la Move VM. He leído que Move VM «no depende de ninguna plataforma» y agradecería recibir orientación sobre los pasos iniciales necesarios y sobre si este proceso implica un esfuerzo significativo. Además, me encuentro con un problema específico. Sigo recibiendo el siguiente error relacionado con la stdlibdependencia de Move cuando intento publicar un módulo de 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();
}

stdlibEn mi archivo Move.toml, 0x1se le asigna la dirección. Es importante destacar que no estoy usando stdlibninguna parte de mi código. A pesar de esto, me encuentro constantemente con el error mencionado anteriormente. ¿Podría alguien ayudarme a entender qué es lo que podría estar mal u ofrecerme información sobre cómo solucionar este problema de manera eficaz?

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.

Publicación

Comparte tu conocimiento.

Problemas para publicar, mover el módulo a mover la máquina virtual con el error «MODULE_ADDRESS_DOES_NOT_MATCH_SENDER»

Respuestas

Sabes la respuesta?

Gana tu parte de 1000 Sui