demoing fetching the utxo with lwk and esplora #48
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
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.
This is a demo of including lwk_wollet in the webide to make it easier to use.
In particular is demoing the fetching of the txid of the UTXO of the address.
The generated wasm without optimizations went from 15.3MB to 17.2MB so about a 12% increase, I was expecting more but since many dependency are in common (bitcoin/elements)
(There is also room to save space in lwk if needed, like feature gating unused features...)
I didn't found in just the command to build with optimizations, maybe the percentual difference there is even less if some codepath is pruned.