mutator set update must be possible

⚓ Neptune    📅 2025-04-03    👤 marco    👁️ 1379      

marco

Warning

This post was published 508 days ago. The infomation described in this article may have changed.

mutator set update must be possible， I meet this error when I finished a compose task。

Cannot apply transaction to current mutator set when I recive PeerMessage::Transaction form peers

how the fix?

🏷️ mutator set compose

aszepieniec    2025-04-04 👍 👎

There are two reasons why a mutator set update might be impossible.

  1. Some removal record’s authentication paths are invalid. (Very malicious.)
  2. The removal record was already applied. This is the double-spend protection kicking in. It could be malicious but it could be benign.

Is there anything particular you are doing to provoke this error?

1