Solved the problem #90
Open
Conversation
This file contains 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
solved the problem
|
Amazing job finding the answer 🔥 🎉Congrats on solving your first Algorand coding challenge! I have labeled your PR approved so you can now claim your certificate. You can claim your certificate of completion NFT here: https://goplausible.xyz/claim/r2747zdbzrvsfxs3zqx5mtmj389k8gwez5tm92m3dsrs8pbj65rn74j175dh1jacnnbrx1rcr1tdm6grsnx2spdnt78ce5tncje7p2r |
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.
solved the problem
Algorand Coding Challenge Submission
What was the bug?
The transaction wasn't signed. We had to sign it using the sender's private key before it could be sent.
How did you fix the bug?
All that I needed to do was add a line where I called signTxn() and sent in the sender's private key. It took me a while to figure out what the command was, but I ended up solving it by logging the sender object so I could see the structure of the data. Then I was stuck for a long time again because I tried to validate the transaction using the signed transaction object, so I ended up with a promise that never resolved. The docs were a little bit misleading in that regard, but maybe that is purposeful.
Console Screenshot: