[Task Tracker (VM-Language)]: Stardust Move models audit

[miker83z]

The audit is not comprehensive. It is composed of two parts:

• Positive scenarios, in which the intended behavior of the PRBs is implemented
• Negative scenario, in which extreme cases that should return an error are tested

The PTB examples will be put under crates/iota-sdk/examples/stardust/.

Negative scenarios implementation might imply to change the iota-framework/stardust/tests

Test the PTB first locally with iota-test-validator, an then use the alphanet. The mnemonics used for PTBs should be taken from the test_outputs in crates/iota-genesis-builder/src/stardust/test_outputs/.

Tasks

Preview Give feedback

1. [Task (VM-Language)]: Test the positive scenarios for migrating an Alias Output #1325
   vm-language +1
   
2. [Task (VM-Language)]: Test the positive scenarios for migrating an NFT Output #1326
   vm-language +1
   
3. [Task (VM-Language)]: Test the positive scenarios for migrating an Basic Output #1327
   vm-language +1
   
4. [Task (VM-Language)]: Test the positive scenarios for migrating an Output where the owner is another Output (special address unlock condition) #1328
   vm-language +1
   
5. [Task (VM-Language)]: Test the positive scenarios for using an Alias object #1333
   vm-language +1
   
6. [Task (VM-Language)]: Test the positive scenarios for using an NFT object #1334
   vm-language +1
   
7. [Task (VM-Language)]: Test the positive scenarios for migrating a Foundry Output #1526
   vm-language +1
   
8. [Task (VM-Language)]: Test positive scenarios for self sponsoring a Shimmer asset claim #1658
   vm-language +1