Skip to content
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

Airdropping an NFT with multiple serials in one TokenTransferList only sends the first serial #17409

Open
simzzz opened this issue Jan 16, 2025 · 0 comments · May be fixed by #17413
Open

Airdropping an NFT with multiple serials in one TokenTransferList only sends the first serial #17409

simzzz opened this issue Jan 16, 2025 · 0 comments · May be fixed by #17413
Assignees
Labels
Bug An error that causes the feature to behave differently than what was expected based on design.

Comments

@simzzz
Copy link

simzzz commented Jan 16, 2025

Description

When we try to send multiple serials of the same NFT in one transaction using a TokenTransferList with a nested array of NftTransfers, the first serial is sent correctly to the receiver, but all the subsequent ones are not.

The expected behavior is all of them to be sent successfully to the appropriate receiver, not just the first one.

Steps to reproduce

  1. Send multiple serials of the same NFT to different receivers using a TokenTranferList with multiple nested NftTransfer items.
  2. Observe the transfers in the transaction
  3. Check the owner of the serials other than the first one

Additional context

No response

Hedera network

No response

Version

0.57.3

Operating system

None

@simzzz simzzz added the Bug An error that causes the feature to behave differently than what was expected based on design. label Jan 16, 2025
@stoyanov-st stoyanov-st self-assigned this Jan 16, 2025
@stoyanov-st stoyanov-st moved this from Backlog to Sprint Backlog in Smart Contract Sprint Board Jan 16, 2025
@stoyanov-st stoyanov-st linked a pull request Jan 16, 2025 that will close this issue
2 tasks
@stoyanov-st stoyanov-st moved this from Sprint Backlog to In Review in Smart Contract Sprint Board Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug An error that causes the feature to behave differently than what was expected based on design.
Projects
Status: In Review
Development

Successfully merging a pull request may close this issue.

2 participants