Add gossips extensions for the Staking Credentials framework #1054
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
This includes modifications to few BOLT4/BOLT7 data structures.
|
Sorry for the noise -- Aimed to open this pull request against my own BOLT repository, just fucked up the gamified interface of Github. For Staking Credentials, protocol aims to be documented in a serie of own BOLTs, one by component to favor cross-layers re-usability, good extensibility with the classic BOLTs and low-level of document to yield fine inter-operability. When I've have a version 0.1 ready for reviews, I'll udpate #1043 in consequence. Beyond, for now using some random BOLT ranges as we don't have a BOLT namespace opened for experimentation |
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 BOLT introduces 2 new types of gossips messages:
credentials_policycontract_policyThe idea with the new
contract_policy, it enables fine-grained risk-management per-type of contracts (e.g dual-funding, liquidity ads) but also a Contract Provider dynamically-accepting multiple credentials.TODO: cleanup the classic range of extensions.