Add decode_transaction_to_js to wasm bindings - #2105
Merged
Conversation
anyxem
force-pushed
the
feat/wasm-decode-tx-to-js
branch
from
August 27, 2026 22:09
dc1dabb to
bc86ff3
Compare
anyxem
force-pushed
the
feat/wasm-decode-tx-to-js
branch
from
August 27, 2026 23:06
bc86ff3 to
28ff46f
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Introduce decode_transaction_to_js function for decoding unsigned transactions
why not decode_unsigned_transaction_to_js?
to be consistent with exising
encode_transaction - decode_transaction_to_js
encode_partially_signed_transaction - decode_partially_signed_transaction_to_js
encode_signed_transaction - decode_signed_transaction_to_js