Skip to content

Unexpected Type Conversion in Move Call Arguments by nodejs #21282

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
apeming opened this issue Feb 19, 2025 · 2 comments
Open

Unexpected Type Conversion in Move Call Arguments by nodejs #21282

apeming opened this issue Feb 19, 2025 · 2 comments
Assignees

Comments

@apeming
Copy link

apeming commented Feb 19, 2025

Unexpected Type Conversion in Transaction Arguments

Steps to Reproduce Issue

  1. Execute the following Move call:
tx.moveCall({
    target: '0xAddress::interface::request_stake',
    arguments: [
        tx.object('0xValidator', { initialSharedVersion: version }),
        stakeCoin,
        tx.pure('address', '0x0'),  // Expected to be address type
        tx.object('0x5'),           // Expected to be SharedObject type
    ]
})

Expected Result

  • tx.pure('address', '0x') should resolve to an address type
  • tx.object('0x5') should be recognized as a SharedObject type

Actual Result

  • On-chain execution shows:
    • tx.pure('address', '0x') resolves to null type instead of address type
    • tx.object('0x5') is incorrectly interpreted as address type rather than SharedObject

System Information

  • SDK Version: @mysten/sui 1.21.2
Copy link
Contributor

Thank you for opening this issue, a team member will review it shortly. Until then, please do not interact with any users that claim to be from Sui support and do not click on any links!

@apeming
Copy link
Author

apeming commented Feb 19, 2025

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants