Page Comparison

...

Minutes

Anti-trust policy reviewed.

...

Vipin Bharathan - 5 years blockchain. Software industry. Work on systems toward privacy-preserving.

Marvin Berstecher - 

Richard Esplin - products - evernym. Upstream projects like Hyperledger. Bring into actual code to deploy.

...

Comments on the Hyperledger Identity white paper. 

Drummond - current presentations on Sovrin, etc. 

Sovrin - by December 4, 2019 will submit the data protection revisions to the SVF. Finished 2nd generation in March. Tackled everything except GDPR compliance (DPR compliance). A number of our stewards and customers pointed out GDPR is one set of compliance regulations. Some potential Sovrin customers are governments. Provenances of BC and Ontario, for example. Transaction endorser agreement. Transaction author is anyone who wants to write to the Sovrin Network. Working with BC.gov to close on addressing issues. How does SSI, which is ultimately backed by blockchain immutable ledgers, GDPR rights of data subjects (right of erasure). In systems like Sovrin, there is very little on the ledger. Widely acknowledged even a DID, if it identifies an individual (even pseudonymous) is subject to GDPR. Eight documents involved. Contract - transaction author agreement. Sovrin as a legal representative of the stewards as a whole. There will be a web page, there currently is a diagram. 

Image Added

Three roles GDPR sets out. GDPR did not anticipate SSI where the ultimate data controller is the individual. Individuals and Things will eventually be able to write to the ledger. Two policy paths, the only path today is permission write access. Driving toward public write access. Now, need to go through Transaction Endorser > Steward > you submit a proper transaction that is validated and it goes on the ledger. In public, transaction authors write directly to the ledger via the Stewards, with a fee (no commitment to Sovrin tokens or dates - only future possibility).