Draft Hyperledger Use Case: After-the-fact mandate changes
Deventer, M.O. (Oskar) van <oskar.vandeventer@...>
Dear friends of the Hyperledger RequirementsWG,
Here is a first draft of the use case on “After-the-fact mandate changes”. https://docs.google.com/document/d/1psJc9UWuteSzOqIG0VLIdzdlxFb9kq-Csw-dxcjPzEo/edit
Please read, review and comment on the draft use case.
Best regards,
Oskar
|
|||||||||||||||||
|
|||||||||||||||||
Deventer, M.O. (Oskar) van <oskar.vandeventer@...>
Dear friends of the Hyperledger RequirementsWG,
There were some questions about mutability of the blockchain at the Requirements WG call of Monday 16 June, triggered by the draft “After-the-fact mandate changes” (https://docs.google.com/document/d/1psJc9UWuteSzOqIG0VLIdzdlxFb9kq-Csw-dxcjPzEo/edit). It was concluded that mutability was not needed of even desirable, as the signing over of an authorization/mandate should not require any rewriting or erasing of the past.
Hence, we added a fourth requirement: “The solution to requirements 1 and 2 shall not require mutability of the blockchain”.
Please let me know if you have any further comments or suggestions to the document. Thank you!
Best regards,
Oskar
From: hyperledger-requirements-wg-bounces@... [mailto:hyperledger-requirements-wg-bounces@...]
On Behalf Of Deventer, M.O. (Oskar) van
Sent: Friday, 09 June, 2017 09:40 To: hyperledger-requirements-wg@... Subject: [Hyperledger-Requirements-WG] Draft Hyperledger Use Case: After-the-fact mandate changes
Dear friends of the Hyperledger RequirementsWG,
Here is a first draft of the use case on “After-the-fact mandate changes”. https://docs.google.com/document/d/1psJc9UWuteSzOqIG0VLIdzdlxFb9kq-Csw-dxcjPzEo/edit
Please read, review and comment on the draft use case.
Best regards,
Oskar
|
|||||||||||||||||
|