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 spec is supposed to explain the way we authenticate parties on the network, using public keys system. That part has been clarified. Details about the cryptographic algorithms used to generate such keys has been added. The high-level description of a "component" managing such keys, renamed wallet management application (prior wallet service) has been updated.
However, the previous version also explain how a user would interact with the wallet service, from an implementation perspective. This is doesn't fit anymore, as the interaction between the user and the wallet doesn't relate to the "authentication" of a user and a party on the network. As a result, the wallet API ACs has been moved out of that spec, to a non-protocol spec.
Close #1575