Update README with detailed peg-in confirmation process#1
Open
jsarenik wants to merge 1 commit intoaeonBTC:mainfrom
Open
Update README with detailed peg-in confirmation process#1jsarenik wants to merge 1 commit intoaeonBTC:mainfrom
jsarenik wants to merge 1 commit intoaeonBTC:mainfrom
Conversation
Clarified the description of the peg-in process, specifying the confirmation requirements for Bitcoin and Liquid. It explains where number 102 comes from. Tested back in 2024.
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
1 participant
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.
Clarified the description of the peg-in process, specifying the confirmation requirements for Bitcoin and Liquid. It explains where number 102 comes from.
Tested back in 2024.