BIP 123: Clarify how used with non-Standards BIPs, and update list#477
Merged
luke-jr merged 1 commit intobitcoin:masterfrom Nov 30, 2016
Merged
BIP 123: Clarify how used with non-Standards BIPs, and update list#477luke-jr merged 1 commit intobitcoin:masterfrom
luke-jr merged 1 commit intobitcoin:masterfrom
Conversation
Contributor
|
@luke-jr I'd say Applications layer defines things like data structures and formatting. While a reference implementation is nice, it's up to application developers to implement it as they wish. On the other hand, the API/RPC layer defines calls that must be implemented either as a library or as a service. |
Member
Author
|
Ok, that sounds about right (but didn't match the layer assigned to stratum). Does this PR look good to merge then? |
Contributor
|
ACK |
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.
Also: It's unclear where to draw the lines for API/RPC. The previous draft had Stratum (which is being removed here since there sadly isn't a BIP yet) as Applications and GBT as API/RPC, when both protocols serve the same fundamental purpose.
Need to get this cleaned up to move forward on both it as well as BIP 2...
@CodeShark