Easy to use tx finalization #48
Closed
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
Collaborator
|
cc #32 |
ikripaka
force-pushed
the
feature/tx_finalization
branch
3 times, most recently
from
f37f63a to
ad385e0
Compare
KyrylR
force-pushed
the
feature/tx_finalization
branch
2 times, most recently
from
1e1a862 to
428a2ac
Compare
feat: * introduce SimplicityNetwork enum for simplifying parameters usage * introduce PartialPset to describe unfinalized type which doesn't have fees inserted * move fee rate fetcher to contracts sdk chore: * move fee from mandatory to optional parameter * add constants related to regtest * move fee outs creation to the finalization step
ikripaka
force-pushed
the
feature/tx_finalization
branch
from
428a2ac to
fbf5632
Compare
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.
No description provided.