feat(iota-framework/move-stdlib): Deprecated fixed_point32

[Dkwcs]

Description of change

• Deprecated fixed_point32
• Added uq32_32 to replace it
  Move fixed_point32 has been deprecated for a new uq32_32 module

Links to any relevant issues

Fixes #5137 .

Type of change

• Breaking change (fix or feature that would cause existing functionality to not work as expected)

How the change has been tested

Run in folder:
iota-framework/packages/move-stdlib/
iota-framework/packages/stardust/
iota-framework/packages/iota-framework/
iota move test

iota-framework-tests:
cargo test

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

4 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
apps-backend	⬜️ Ignored (Inspect)	Visit Preview		Feb 10, 2025 11:30am
apps-ui-kit	⬜️ Ignored (Inspect)	Visit Preview		Feb 10, 2025 11:30am
rebased-explorer	⬜️ Ignored (Inspect)	Visit Preview		Feb 10, 2025 11:30am
wallet-dashboard	⬜️ Ignored (Inspect)	Visit Preview		Feb 10, 2025 11:30am

[miker83z]

Check the CI error:
thread 'compatibility_tests::test_framework_compatibility' panicked at crates/iota-framework-snapshot/tests/compatibility_tests.rs:37:21: The current IOTA framework 0x000000000000000000000000000000000000000000000000000000000000107a is not compatible with version 1
It probably means that we use fixed_point32 there and we need to change it to uq32_32.

[valeriyr]

Check the CI error: thread 'compatibility_tests::test_framework_compatibility' panicked at crates/iota-framework-snapshot/tests/compatibility_tests.rs:37:21: The current IOTA framework 0x000000000000000000000000000000000000000000000000000000000000107a is not compatible with version 1 It probably means that we use fixed_point32 there and we need to change it to uq32_32.

@miker83z @Dkwcs Looks like it is because the royalties public function was changed which is not compatible.

[valeriyr]

The FixedPoint32 and UQ32_32 structures are compatible on the binary level but I think we still need to change the member type in the Irc27Metadata structure on the Rust side.

[valeriyr]

Since the Irc27Metadata structure became incompatible after changing the field type, I propose to leave the Stardust implementation as is. The main reason is that this is a deprecated type itself, and we will not create new instances of it.
Otherwise, we will have to put more effort into updating the type, such as creating a new version of the structure and public functions.