solved #66
Open
solved #66
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
🎉 Congrats on solving the 3rd Algorand Python Coding Challenge! I have labeled your PR approved, so you can now claim your certificate. You can claim your certificate of completion NFT here: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What was the bug?
The bug was smart contract deployment error. After evaluation the contract failed due to a transaction error highlighted by the client call. The deposit function was failing while sending an asset to a new address without the recepient address opting in to the asset. The address therfore needed to be funded for the transaction to pull through and deposit the asset to the recepients address.
How did you fix the bug?
I performed the run and debug prompt to highlight the errors and pinpoint the areas of interest.
With the help of the documentation from the challenge README file I finally cited the error coming from the ASA Vault smart contract script.
The command "algokit project deploy localnet"responsible for deploying the contract failed as the deposit asset application address was not opted in.
After keen research from the provided Algorand Python Documentation I understood that the optintoasset function was not complete and needed to submit the transaction that would opt in the application address. Funding the application address with the knowledge that: The amount of the asset to be transferred should be a zero amount transferred to the address and allocates that asset in the account's Asset map.
The optintoasset function as well as trhe deposit function needed to be modified in that: the inner transaction that handled zero asset transfer was missing which was handled by hardcoding the transaction. After which asserting that the application address is opted in before transferring the asset.
After simultaneously handling the two errors the contract complied successfully and deployed successfully. TheVault held the "Super Rare Oranges" as expected.
I ran the command "algokit explore" to view the transactions on Dappflow for a sharper verification, of course thanks to the Algorand Foundation for this intuitive approach.