Initial proposal for verification API #2
Merged
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
ghost
assigned 
|
@maran you can assign @dacoinminster on merging pull requests. |
|
I am merging this pull request, there is nothing controversial in it as it's all optional API endpoints. |
ripper234
added a commit
that referenced
this pull request
Dec 30, 2013
Initial proposal for verification API
Closed
Merged
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.
As discussed my initial draft for a standardised verification API. If no one complaints I will try to setup an open-source web-service based on this draft. This should help us discover if the draft includes everything needed to make the comparison work between implementations.
I've added it as an appendix because I feel it does not belong in the spec itself but is rather an addition based on the spec.