An issue where a BitString overflow error occurs while sending a jetton transfer with a 42 length string via tonconnectUI.
Bounty Context
Why it's Important?
The issue is disabling developers from sending jetton transfers with a 42 length string via tonconnectUI. This limitation hinders the functionality of the platform, potentially reducing its practicability and appeal to end-users who wish to carry out such transactions within the specified string length.
Problem showcase
The user tries to execute a jetton transfer with a 42-length string as the forwardPayload via tonconnectUI, but the operation fails with a BitString overflow error. However, the same operation completes successfully when performed via the Wallet bot, indicating a probable issue within the tonconnectUI.
Potential Solution
A plausible solution must be developed and implemented to fix the BitString overflow issue while implementing a jetton transfer with a 42-length string via tonconnectUI. The solution must ensure the successful completion of the transaction without any errors and should behave consistently with the Wallet bot. Furthermore, underlying code or package dependencies may need to be examined, debugged and possibly updated to fix this bug.
Defenition of Done
Replicate the BitString overflow error and identify the root cause, Develop a fix for the identified problem, Successfully test a jetton transfer with a 42-length string on tonconnectUI, Ensure the tonconnectUI behavior is consistent with that of the Wallet bot, Integration and compatibility with existing system and components, Submission of final deliverable with appropriate documentation
References
No specific references are available currently. Reference material and similar solutions to the problem may be found when researching the BitString overflow issue.
Summary
An issue where a BitString overflow error occurs while sending a jetton transfer with a 42 length string via tonconnectUI.
Bounty Context
Why it's Important? The issue is disabling developers from sending jetton transfers with a 42 length string via tonconnectUI. This limitation hinders the functionality of the platform, potentially reducing its practicability and appeal to end-users who wish to carry out such transactions within the specified string length.
Problem showcase The user tries to execute a jetton transfer with a 42-length string as the forwardPayload via tonconnectUI, but the operation fails with a BitString overflow error. However, the same operation completes successfully when performed via the Wallet bot, indicating a probable issue within the tonconnectUI.
Potential Solution A plausible solution must be developed and implemented to fix the BitString overflow issue while implementing a jetton transfer with a 42-length string via tonconnectUI. The solution must ensure the successful completion of the transaction without any errors and should behave consistently with the Wallet bot. Furthermore, underlying code or package dependencies may need to be examined, debugged and possibly updated to fix this bug.
Defenition of Done
Replicate the BitString overflow error and identify the root cause, Develop a fix for the identified problem, Successfully test a jetton transfer with a 42-length string on tonconnectUI, Ensure the tonconnectUI behavior is consistent with that of the Wallet bot, Integration and compatibility with existing system and components, Submission of final deliverable with appropriate documentation
References
No specific references are available currently. Reference material and similar solutions to the problem may be found when researching the BitString overflow issue.
REWARD
🪄 Created with the help of TON Bounties Creator Bot.