- DG-BSC - mailman.kantarainitiative.org

FYI
by John Wunderlich 30 Sep '16

30 Sep '16

https://medium.com/@bsuichies/why-blockchain-must-die-in-2016-e992774c03b4#… This is the posting that contains a"Do you even need a blockchain" flowchart that fits into discussions of scope etc. Sincerely, John Wunderlich @PrivacyCDN <https://twitter.com/PrivacyCDN> Call: +1 (647) 669-4749 eMail: john(a)wunderlich.ca -- This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.

4 3

ONC/NIST blockchain papers
by Scott Shorter 29 Sep '16

29 Sep '16

Hi all, As mentioned on the call, here’s the link to the submissions to the NIST/ONC healthcare blockchain challenge: https://oncprojectracking.healthit.gov/wiki/display/TechLabI/Blockchain+Cha… Enjoy! - Scott Scott Shorter - Vice President, Security sshorter(a)kimbleassociates.com<mailto:sshorter@kimbleassociates.com>

2 1

Notes from BSC telecon Thursday, September 29
by Eve Maler 29 Sep '16

29 Sep '16

http://kantarainitiative.org/confluence/display/BSC/2016-09+%28September+20… Agenda: - Report <http://kantarainitiative.org/confluence/display/BSC/Report+from+the+Blockch…> writing Attending: Eve, Thorsten, Andrew, Scott S, Kathleen, Matisse We did a lot of report writing work, directly in the report. *AI:* Eve: Ask Scott D if he will take an action to write the "Legal Contracts" section of the report, providing a definition, a short discussion of strengths and weakness of the current way of doing things, and pointers to the other technology and technique sections as appropriate for starters. Bringing in the ethics perspective would also be awesome. *AI:* Eve: Ask Thomas if he will take an action to write the "IPFS" section along the lines just above. *AI:* Eve: Ask John W if he will take an action to write the "Consent Receipts" section along the lines just above, and either write or find a designee for the "User-Submitted Terms" section. Others took AIs to fill in other similar report sections on the call; see the report for those. Everyone please review the report for the latest! *Eve Maler*ForgeRock Office of the CTO | VP Innovation & Emerging Technology Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl *ForgeRock Summits and UnSummits* are coming to <http://summits.forgerock.com/> *London and Paris!*

1 0

Sovrin
by Thorsten H. Niebuhr [WedaCon GmbH] 29 Sep '16

29 Sep '16

Definitly worth a look: https://www.sovrin.org/ Thorsten

1 0

Fwd: Trying to explain BSC to HL7 Security and Privacy WGs
by Eve Maler 29 Sep '16

29 Sep '16

For posterity, please find below Kathleen's "matrix" table and 3D diagram that we'd been discussing in the last couple of weeks. *Eve Maler*ForgeRock Office of the CTO | VP Innovation & Emerging Technology Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl *ForgeRock Summits and UnSummits* are coming to <http://summits.forgerock.com/> *London and Paris!* ---------- Forwarded message ---------- From: Kathleen Connor <kathleen_connor(a)comcast.net> Date: Tue, Sep 20, 2016 at 5:21 AM Subject: RE: Trying to explain BSC to HL7 Security and Privacy WGs To: Eve Maler <eve.maler(a)forgerock.com>, Thomas Hardjono <hardjono(a)mit.edu>, john(a)wunderlich.ca, james.g.hzard(a)gmail.com Cc: Kathleen Connor <kathleen_connor(a)comcast.net> Hi Maybe a picture works better than words in this case. Visually, what I’m wishing for is something like this graph against which BSC protocols/schemes could be plotted. I.e., could any of you plot Stellar and Ethereum, or other types, on this graph? If not, what needs to change. It’s somewhat difficult to clearly delineate economic and governance paradigms, so maybe that’s the first step. Public/Private may be easier. -K *From:* Kathleen Connor [mailto:kathleen_connor@comcast.net] *Sent:* Tuesday, September 20, 2016 12:54 AM *To:* 'Eve Maler'; 'Thomas Hardjono'; john(a)wunderlich.ca; ' james.g.hzard(a)gmail.com' *Cc:* 'Kathleen Connor' *Subject:* Trying to explain BSC to HL7 Security and Privacy WGs Hi – I’m at HL7 cochairing Security and Financial Management WGs – and BSC is a “hot topic”. During the last couple of BSC calls, we’ve talked about the different governance/control/risk vectors related to the several BSC protocols. I just wish I had enough of an overarching view that I could convey this to those interested, large scale communities who are interested in deploying for healthcare. I have a few breadcrumbs, but know I’ve heard more from our DG. Seems to me that if there were such a multi-axel grid for others to quickly gauge where a particular BSC player/community/protocol lived in relation to the rest, that it would be a “goodness” that we could contribute as a DG. So, it’s too late for me to get enough done by tomorrow’s presentation other than hand waving over a matrix – and I’m going to miss all of this week’s calls, but wanted to know if this sort of approach [raw] makes sense to the this group, and if so, to the larger group as a “cheat sheet” contribution, if only to gather our own thoughts on the BSC taxonomy. E.g. Purpose, how do I best explain the difference between MedRec and the Alice/Bob Research use cases. Or Ethereum and Stellar for preservation of Governance Principles? If this has already been done – please let me know. Scott seemed to be way ahead of us on the ethics/governance front. Is there a simple way to make this clear to ourselves and others? If not, could we put this on the work list as a possible taxonomy for the BSC use cases? Below are just guesses on columns and entries for discussion purposes. -K BSC Protocol Public / Private De/Centralized Consensus/Dictator Data Owner Control Data Subject Control Community Economic PRO Community Economic CON Risk Mitigation Comments Pure Public D Anarchy Ethereum Public Vetted D Ranked voters Stellar Private Vetted D Vetted Voters

2 1

FYI: Blockchain art exhibit in NYC
by John Wunderlich 27 Sep '16

27 Sep '16

http://www.petzel.com/exhibitions/2016-09-08_simon-denny/ Sincerely, John Wunderlich @PrivacyCDN <https://twitter.com/PrivacyCDN> Call: +1 (647) 669-4749 eMail: john(a)wunderlich.ca -- This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.

3 2

A definition for "Digital Identity"
by Andrew Hughes 27 Sep '16

27 Sep '16

Hi folks - I'd like to test out a variation on the typical definition of 'identity'. If it gets traction in this group, it could possibly be a way to express the "requirements" that this digital identity thing has of the blockchain and smart contracts capabilities (which is one way to view the mandate of the DG). You will probably notice a mash-up and blending of several different well-known concepts and definitions to try and adopt those aspects of the other representations (user-centric, VRM, OpenNotice/Consent/Information Sharing, myData, privacy principles, self-sovereign and many more) *tl;dr* *By describing digital identity in terms of information records that may contain 'identity' information, we can talk about actors and services that use the information assets rather than a more abstract notion of identity as a right or embodied characteristic of an entity. NB: Other works can deal with credentials and authentication - this is not that - this is about the information itself.* So: I'd appreciate your observations and comments directly or to the list. I'm not really looking for word-smithing advice but rather: is the following a reasonable working definition? A secondary thought is: given the capabilities and features of blockchains and smart contracts, do the descriptions of 'self-sovereign' and 'administrative' identity information (records) lead to obvious and useful explorations of requirements? I await the deluge of critical thought and advice ;-) andrew. =============== Digital Identity: - The identifiers, credentials and the credentials’ authenticators that an Entity uses to claim that they are the Subject of a Digital Identity Information Record. - The Digital Identity Information Records in any storage location. There are many schools of thought about what a digital identity represents and the uses for digital identities. Each has a different taxonomy to describe the different types and characteristics of those identities. The school of thought related to the personal data ecosystem, personal data stores, and self-sovereign identity (see Searls, Windley, Blakley, Cameron, et al) uses at least two major categories, paraphrased and expanded below: Administrative identity information: labels used to keep track of entities, their information records and the services they use. These labels are controlled by the issuer. A common example today are email addresses used as login identifiers. Self-sovereign identity information: information about the entity that is controlled by the entity and released on the authority of that entity. Self-sovereign identity information may include identifiers or attributes. Self-sovereign identity information can be used to assert facts about the self without subservience to a central authority. *Digital Identity Information Record:* - The information records containing information about an Entity that can be used to attempt to identify or distinguish the Entity from other Entities in a population - The Digital Identity may or may not enable unique distinguishment of an Entity in a population - Can contain personal information, personally identifiable information, identity attribute information. - The record may also contain, secondarily, non-personal or non-identity information. It is uncommon to see ‘pure’ Digital Identity Information Records because the records contain information related to the purposes of the record holder. The main point being that the record has a direct association to the Entity. - Can also contain information about relationships and bindings =============== *Andrew Hughes *CISM CISSP Independent Consultant *In Turn Information Management Consulting* o +1 650.209.7542 m +1 250.888.9474 1249 Palmer Road, Victoria, BC V8P 2H8 AndrewHughes3000(a)gmail.com ca.linkedin.com/pub/andrew-hughes/a/58/682/ *Identity Management | IT Governance | Information Security *

1 0

Notes from BSC telecon Tuesday, September 27
by Eve Maler 27 Sep '16

27 Sep '16

http://kantarainitiative.org/confluence/display/BSC/2016-09+%28September+20… Agenda: - Report <http://kantarainitiative.org/confluence/display/BSC/Report+from+the+Blockch…> writing Attending: Eve, Thomas, Thorsten, Andrew, John W, Jim H, Matisse We have a LOT of new information sources, including some comparative material, to help us complete our thematic introduction in the report. (One new source shared on the call: Stellar info <https://www.stellar.org/developers/guides/concepts/scp.html>.) Is it meaningful to achieve "transactional empowerment" use cases if you are some way down the path of decentralization, or must you reach 100% decentralization? Andrew suggests that where perfect decentralization can't be achieved, transparency and accountability can shore up the necessarily centralized parts of the system. Having "an authority" (vs. "your peers") detect a transgression requires traditional controls. But, speaking of roles here, depending on what sort of blockchain technology *and* governance model *and* blockchain contents are involved, are they really "your peers"? There seem to be a lot of ways that the node miners' interests may not be strictly aligned with yours. Matisse believes the main value of choosing blockchain for "transactional empowerment" would be smart contracts – being able to withdraw your consent from a contract and, say, get your money back from a smart vending machine. Jim notes that smart contracts are really a different technology from blockchain – based on blockchain technology but a specific application that requires "contract semantics" at the nodes. Regarding economic efficiencies, a big attraction of Bitcoin use cases has been to make transactions more efficient by removing intermediaries. However, the world has been finding that technical inefficiencies (performance challenges) have arisen. Specific use cases: currency (a la Bitcoin), certification (a la notary services), smart contracts (a la vending machine, land registry, drone control)... Jim has made the case that smart contracts need to connect to the legal world through both format and semantics. A transactional system presumably must take into account the "business/legal" environment in some fashion, even if just implicitly (say, by referencing certain jurisdictional laws, terms, and concepts). So either a smart contract is a non-contract (the way a contract with a killer would be – though perhaps with consequences less dire!) or it is a true contract precisely by taking into account its surrounding business/legal environment through a standardized format and semantics. It had better be possible for a true "smart contract" to have parties who have the proper rights and responsibilities. AIs: - Jim: Share his draft Kantara blog post on the list - Eve: Take the latest notes and try and squeeze them into the report for review on Thursday - All: Please review all the resources shared on the list and in the notes before Thursday *Eve Maler*ForgeRock Office of the CTO | VP Innovation & Emerging Technology Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl *ForgeRock Summits and UnSummits* are coming to <http://summits.forgerock.com/> *London and Paris!*

1 0

Fwd: link to some blockchain papers
by Eve Maler 26 Sep '16

26 Sep '16

Matisse has kindly assembled the following materials to help us with our efforts to analyze and document the tensions/themes. Please see below. Separately, John W sent me the following link, which contains some comparative analysis: https://docs.google.com/presentation/d/11WwKRK8RrGokPvrm3APshHY_DlyYOKz_ipc… I suspect the best way for us to make progress is for those with keen analytical and writing skills to do some homework *before* the next meeting, perhaps with a glass of wine handy. :-) *Eve Maler*ForgeRock Office of the CTO | VP Innovation & Emerging Technology Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl *ForgeRock Summits and UnSummits* are coming to <http://summits.forgerock.com/> *London and Paris!* ---------- Forwarded message ---------- From: mat perugini <mat.perugini(a)gmail.com> Date: Mon, Sep 26, 2016 at 1:11 AM Subject: link to some blockchain papers To: Eve Maler <eve.maler(a)forgerock.com> Dear Eve, here is the paper list you have been asking for. The historical part covers from 1982 to 2009. The ethereum blog expalins in a very linear way the issue of concurring blockchains. Paper: Smart Contract a Preliminary evaluation, exposes the state of my reasarch at the end of 2015. Even though there are things I have reconsidered (and that will be better explained in my fnal essay), it exposes some of the main concepts I am working on. Kind regards Matisse ************************** history •David Chaum, Blind signatures for untraceable payments, 1982 *http://www.hit.bme.hu/~buttyan/courses/BMEVIHIM219/2009/Chaum.BlindSigForPayment.1982.PDF <http://www.hit.bme.hu/%7Ebuttyan/courses/BMEVIHIM219/2009/Chaum.BlindSigFor…>* •David Chaum, Online Cash Cecks, 1989 *https://w2.eff.org/Privacy/Digital_money/?f=online_cash_chaum.paper.txt <https://w2.eff.org/Privacy/Digital_money/?f=online_cash_chaum.paper.txt>* •Timothy C. May, The Crypto Anarchist Manifesto, 1988, *http://www.activism.net/cypherpunk/crypto-anarchy.html <http://www.activism.net/cypherpunk/crypto-anarchy.html>* •Nick Szabo, Contracts with Bearers, 1998, *http://szabo.best.vwh.net/bearer_contracts.html <http://szabo.best.vwh.net/bearer_contracts.html>*: •Wei Dai, B-money 1998, *http://www.weidai.com/bmoney.txt <http://www.weidai.com/bmoney.txt>** <http://www.weidai.com/bmoney.txt>* •Satoshi Nakamoto, Bitcoin: A Peer-to-Peer Electronic Cash System, 2008, http://bitcoin.org/bitcoin.pdf ethereum blog on public and private blockchains - https://blog.ethereum.org/2015/08/07/on-public-and-private-blockchains/ my papers on SSRN - http://papers.ssrn.com/sol3/results.cfm

1 0

FYI; Blockchain as HosPjan 2.0
by John Wunderlich 23 Sep '16

23 Sep '16

http://bb9.berlinbiennale.de/blockchain-as-gosplan-2-0/ Thanks, John 4giv spellin errurz from mobile devize -- This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.

2 2

Notes from BSC telecon Thursday, September 22
by Eve Maler 22 Sep '16

22 Sep '16

http://kantarainitiative.org/confluence/display/BSC/2016-09+%28September+20… Agenda: - Report <http://kantarainitiative.org/confluence/display/BSC/Report+from+the+Blockch…> writing - Search for independent and dependent variables among the "tensions", as inspired by Kathleen and John W for the report - Review use case analysis inputs from John W for the report, if available Attending: Eve, Matisse, Thomas, Colin, Andrew, Marco *News: *News has hit of an "editable" blockchain technology <http://www.econotimes.com/Accenture-creates-Editable-blockchain-prototype-3…> that Accenture has prototyped. This seems...kind of scammy. They seem to have created a private blockchain. Does it require proof of work? Is it really a blockchain? Why would you want to "accelerate...adoption" of blockchain by removing a key defining feature of actual blockchains? Maybe this makes enterprises feel cool, but tamper-evident ledgers can be done right now without having to involve the "b-word". We pronounce this another b-word: bogus. *Tension/theme analysis: *Can a blockchain be considered "a distributed system" in the formal sense? There are a number of resources we could draw on to analyze its characteristics if so: scalability, transparency, etc. See this article <http://www.theserverside.com/feature/Bitcoins-blockchain-architecture-as-a-…>. Matisse supports this analysis, as it's the premise of her PhD. thesis! A neutral way of stating the columns Kathleen has added on the right that our participants are more invested in, for use-case reasons, would be (all, please offer feedback on this): - "Balance of control" in transactions (which can include contracts and data sharing) – enabling individuals to rise to the level of a "peer" to traditionally more empowered entities - "Transactions" is the broadest possible term in common usage - This item is the broad descriptor - "Granularity of control" ?? in transactions – enabling not a totality of trust and liability but an apportioning that is appropriate - Supposedly Bitcoin, a special-purpose blockchain, has protected individuals on this dimension, but each smart contract could still leave individuals open to abuse - "Dynamism of control" ?? in transactions – enabling individual choice both over time and just-in-time When is a public blockchain appropriate, vs. a consortium-model blockchain, vs. a private blockchain? *AI:* Matisse: Share pointers to papers to let us analyze specific blockchain types for next time. Next time: Get into both specific blockchain mentions and use case-specific analysis, and try to flesh out the report intro for good and all. *Eve Maler*ForgeRock Office of the CTO | VP Innovation & Emerging Technology Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl *ForgeRock Summits and UnSummits* are coming to <http://summits.forgerock.com/> *London and Paris!*

2 2

Agenda for BSC telecon Thursday, September 22 (today!)
by Eve Maler 22 Sep '16

22 Sep '16

http://kantarainitiative.org/confluence/display/BSC/2016-09+%28September+20… We meet *Thursdays* at 11am PT / 2pm ET / 7pm UK / 8pm CET for 60 minutes. We use Kantara Line A (US +1-805-309-2350, Skype +99051000000481, international options <https://www.turbobridge.com/international.html>, web interface <https://panel.turbobridge.com/webcall/>, more info <https://www.turbobridge.com/join.html>, code 4022737) and http://join.me/findthomas for screen sharing. See the DG calendar <http://kantarainitiative.org/confluence/display/BSC/Calendar> for our full meeting schedule. Previous meeting minutes are here: July <http://kantarainitiative.org/confluence/display/BSC/2016-07+%28July+2016%29…>, August <http://kantarainitiative.org/confluence/display/BSC/2016-08+%28August+2016%…> . Agenda: - Report <http://kantarainitiative.org/confluence/display/BSC/Report+from+the+Blockch…> writing - Search for independent and dependent variables among the "tensions", as inspired by Kathleen and John W for the report - Review use case analysis inputs from John W for the report, if available *Eve Maler*ForgeRock Office of the CTO | VP Innovation & Emerging Technology Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl *ForgeRock Summits and UnSummits* are coming to <http://summits.forgerock.com/> *London and Paris!*

4 3

Notes from BSC telecon Tuesday, September 20
by Eve Maler 20 Sep '16

20 Sep '16

http://kantarainitiative.org/confluence/display/BSC/2016-09+%28September+20… Agenda: - Report <http://kantarainitiative.org/confluence/display/BSC/Report+from+the+Blockch…> writing - Identify strengths and weaknesses of traditional and new distributed methods of solving use cases Attending: Eve, Scott S, Jeff, Matisse, Andrew, Jim H, Domenico, John W Eve reviewed a graph that Kathleen essayed in private email, with three axes: economic paradigm, (political) governance model, and (openness) community type. (s/oligarchy/oligopoly/) We're enthusiastic about finding out how technologies would get plotted. We wonder if there are exactly three axes and if they're really orthogonal. Can we start by taking the matrix approach in Kathleen's first email, and "checking off" (as in John W's Stellar matrix example) characteristics/features that each technology has? Since there are so many consensus protocols and they change fast, we want to take a relatively high-level approach for a key sampling of these. For the Alice Participates in Bob's Research Study <http://kantarainitiative.org/confluence/display/BSC/Alice+participates+in+B…> use case, what are the strengths and weaknesses of doing things using today's technologies and techniques? - Registries related to particular diseases, such as cancer – clinicaltrials.gov – centralized control systems record the outcome of studies but don't engage with the patient in any way. - To add such functionality, you'd have to bolt something on, or develop a linking mechanism in between the two. How could things be different? - An information sharing agreement (a la JSON-LD) would point to the study (which has a study number) and to the data needed (or a pointer to it). - Consent? - Retrofit? - Efficiency? - Accountability? - Trust mechanism? How do you establish that the next slot in the chain is trustable? To what extent does this involve the "drug of centralization" once again? - Automatability/dynamism? - If solved with "just blockchain", has these S&W - If solved with "smart contracts", has these S&W - If solved with both... - If solved with IPFS... A pattern we're imagining in the report is that many use cases will have similar strength and weakness patterns, and we'll want to discuss those in one big analysis section. Each use case may then have its own small subsection(s) discussing delta as necessary. For example, if we think that "automation vs. manual" is a strength of new tech vs. old tech, and "privacy" is a weakness of new tech vs. old tech, we can say that once in the big analysis section. We might end up* recommending a Work Group that develops an architecture, or set/range of architectures, that targets optimal outcomes among the strengths, and mitigates the risks among the weaknesses.* The ISO now has a blockchain group. Next time: - Search for independent and dependent variables among the "tensions", as inspired by Kathleen and John W for the report - Review use case analysis inputs from John W for the report, if available *Eve Maler*ForgeRock Office of the CTO | VP Innovation & Emerging Technology Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl *ForgeRock Summits and UnSummits* are coming to <http://summits.forgerock.com/> *London and Paris!*

1 0

Agenda for BSC telecon Tuesday, September 20
by Eve Maler 19 Sep '16

19 Sep '16

http://kantarainitiative.org/confluence/display/BSC/2016-09+%28September+20… We meet *Tuesdays* at 7:30am PT / 10:30am ET / 3:30pm UK / 4:30pm CET for 60 minutes. We use Kantara Line A (US +1-805-309-2350, Skype +99051000000481, international options <https://www.turbobridge.com/international.html>, web interface <https://panel.turbobridge.com/webcall/>, more info <https://www.turbobridge.com/join.html>, code 4022737) and http://join.me/findthomas for screen sharing. See the DG calendar <http://kantarainitiative.org/confluence/display/BSC/Calendar> for our full meeting schedule. Previous meeting minutes are here: July <http://kantarainitiative.org/confluence/display/BSC/2016-07+%28July+2016%29…>, August <http://kantarainitiative.org/confluence/display/BSC/2016-08+%28August+2016%…> . Agenda: - Report <http://kantarainitiative.org/confluence/display/BSC/Report+from+the+Blockch…> writing - Identify strengths and weaknesses of traditional and new distributed methods of solving use cases *Eve Maler*ForgeRock Office of the CTO | VP Innovation & Emerging Technology Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl *ForgeRock Summits and UnSummits* are coming to <http://summits.forgerock.com/> *London and Paris!*

1 0

Smart Contracts? – Slaw
by John Wunderlich 19 Sep '16

19 Sep '16

FYI: John Gregory, the author of this piece is a highly respected lawyer http://www.slaw.ca/2016/09/19/smart-contracts/ John Wunderlich, Sent frum a mobile device, Pleez 4give speling erurz "...a world of near-total surveillance and endless record-keeping is likely to be one with less liberty, less experimentation, and certainly far less joy..." A. Michael Froomkin -- This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.

2 1

The Blockchain: Decentralized trust to unlock a decentralized future - FYI
by John Wunderlich 13 Sep '16

13 Sep '16

https://www.oreilly.com/ideas/the-blockchain-decentralized-trust-to-unlock-… -- This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.

1 0

Graphic FYI
by John Wunderlich 12 Sep '16

12 Sep '16

For a talk I'll be giving next month, FYI [image: Inline images 1] Sincerely, John Wunderlich @PrivacyCDN <https://twitter.com/PrivacyCDN> Call: +1 (647) 669-4749 eMail: john(a)wunderlich.ca -- This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.

1 0

User-Managed Identities for Blockchains (using UMA for user-centric control over blockchain identities)
by Thomas Hardjono 11 Sep '16

11 Sep '16

Folks, This may or may not be a use-case proper for BSC-DG, but I thought I'd mention it here because its an "infrastructure" technology that supports scaling of blockchains. (analogy: DNS is not part of Internet routing in TCP/IP, but it sure does help us use the Internet). One of the key concepts we (at MIT) are trying to develop further in CoreID (diagram is here http://www.findthomas.net/blog/) Part of it is the idea of a new kind of identity provider called the "persona provider" (PP) The Persona Provider could be implemented as a combination of an UMA Authorization Server combined with an UMA Resource Server. (PP = AS + RS). When Alice creates an account at the Persona Provider (PP), she convinces the PP initially that she is legit by supplying the PP with signed assertions (blinded assertion) which the Core Identity Issuer (upstream) has created. When Alice needs to transact on the blockchain using an anonymous-verifiable identity, she goes to her account at the PP and self-generates a transaction-identity (transaction-identifier) to be used on the blockchain or within a smart contract. She can self-generate as many transaction-identifiers as she needs -- no limit. The PP provides the crypto-tools to do this (just like bitcoin-wallets / client softwares or PGP). At the same time, she could optionally set policy on the account, treating the the blinded assertions (from the Core Identity Issuer) as resources. The transaction identities (which are anonymous-verifiable strings) can also be treated as resources sitting on the PP. The PP keeps these transaction-identifiers as long as she needs, and may even archive them. The PP also makes available a Identity Verification end-point (API) that allows the counter-party (RP) -- or anyone for that matter -- to verify a transaction-identifier found on a blockchain or in a smart-contract. If this is useful, I can write it up for the use-cases page. /thomas/

11 28

Re: [DG-BSC] "Smart Contract" description resource
by M AV 09 Sep '16

09 Sep '16

Altho this resource is Etherium-related, I found a helpful discussion of how coded smart-contracts work in generalhttps://github.com/ethereum/go-ethereum/wiki/Contracts-and-Transacti… Best, av From: dg-bsc-bounces(a)kantarainitiative.org [mailto:dg-bsc-bounces@kantarainitiative.org] On Behalf Of Eve Maler Sent: Thursday, September 1, 2016 1:19 AM To: dg-bsc(a)kantarainitiative.org Subject: [DG-BSC] Agenda for BSC telecon Tuesday, September 1 http://kantarainitiative.org/confluence/display/BSC/2016-09+%28September+20… We meet Thursdays for 30 minutes at 11am PT / 2pm ET / 7pm UK / 8pm CET. We use Kantara Line A (US +1-805-309-2350, Skype +99051000000481, international options<https://www.turbobridge.com/international.html>, web interface<https://panel.turbobridge.com/webcall/>, more info<https://www.turbobridge.com/join.html>, code 4022737) and http://join.me/findthomas for screen sharing. See the DG calendar<http://kantarainitiative.org/confluence/display/BSC/Calendar> for our full meeting schedule. Previous meeting minutes are here: July<http://kantarainitiative.org/confluence/display/BSC/2016-07+%28July+2016%29…>, August<http://kantarainitiative.org/confluence/display/BSC/2016-08+%28August+2016%…>. Agenda: * Working session on report text to capture sentiment around "central tension" (vs. cooperative "outlet") and action items for fleshing it out * Could result in text in use case(s) and technology/technique description/analysis too Eve Maler ForgeRock Office of the CTO | VP Innovation & Emerging Technology Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl ForgeRock Summits and UnSummits are coming to<http://summits.forgerock.com/> London and Paris!

2 1

Notes from special BSC telecon 2016-09-09
by Eve Maler 09 Sep '16

09 Sep '16

http://kantarainitiative.org/confluence/display/BSC/2016-09+%28September+20… http://kantarainitiative.org/confluence/display/BSC/Report+from+the+Blockch… Agenda: - Informal report writing Attending: Eve, Andrew, Thomas, Domenico, Luk?, Kathleen Thoughts for the report: If some topics aren't "use cases" because they assume technologies/techniques, could we still include them as "tests" (e.g. real-world case studies that use blockchain)? MedRec is one such case study. That would allow us to include a lot of up-to-the-minute information. Also, we would like to include some thread of blockchain vs. smart contracts. We already have this covered in the report outline. We're thinking that maxing out on the number of use cases and case studies (five each, or even less) will be fine; that will elicit the analysis we need. We could easily analyze up to five actual real projects/pilots/POCs ("case studies") out there; there are so many. The distinction in the name is "theoretical vs. actual". Hmm, we might not want to put a limit on case studies as long as we keep illustrating real technologies/techniques. Let's limit theoretical use cases, though. In which case we've probably hit our limit among those submitted. We'd like to propose that our meetings use a pattern in our meetings of using the half-hour for use case work, and a second half-hour for deep-dive report writing (that is to say, doing this *twice* a week). Next week Eve can't attend due to being awesomely in Barcelona. *Can Thomas run the meetings next week? Please confirm to the list.* Kathleen took an action to flesh out some MedRec case study text for next week. *Eve Maler*ForgeRock Office of the CTO | VP Innovation & Emerging Technology Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl *ForgeRock Summits and UnSummits* are coming to <http://summits.forgerock.com/> *London and Paris!*

1 0

Re: [DG-BSC] User-Managed Identities for Blockchains (using UMA for user-centric control over blockchain identities)
by Adrian Gropper 08 Sep '16

08 Sep '16

Luk, I understand "persistent pairwise pseudonyms" (PPP, for short) because that's what FIDO seems to do. I don't understand what you mean by adding "/persona" to the mix. Thomas seems to be drawing - in the diagram on his blog - a distinction where multiple PPPs are derived in a hierarchical deterministic way from a single persona. The persona could be a way to link verifiable claims to the PPP but it's not clear to me how that would work or be standardized. I think W3C Verifiable Claims takes a decent shot at that. I also note that no blockchain is involved yet. Adrian On Thursday, September 8, 2016, Luk Vervenne <luk.vervenne(a)synergetics.be> wrote: > My vote is for different but persistent pairwise pseudonyms/persona (so > per service provider / per web service). > I that sense it is a “fully" persistent pairwise *pseudonymisation / > persona* that can dive into the "deep web serivce call chains" needed to > preform an business service. > > luk > > On 8 Sep 2016, at 14:22, Adrian Gropper <agropper(a)healthurl.com > <javascript:_e(%7B%7D,'cvml','agropper(a)healthurl.com');>> wrote: > > Thomas, > > There are many ways to get where we're headed with personas, verifiable > claims, and non-correlatable transaction identifiers and you are > contributing to a valuable conversation. I love that you are bringing UMA > into the conversation because I tend to consider the authorization server > as a key component of identity and tightly coupled to persona. > > Privacy engineering identity can build on standards (and would-be > standards) including: > > - FIDO (for non-correlatable yet persistent identifiers) > - W3C Verifiable Claims (for a triple blind attribute verification > architecture) > - Hierarchical Deterministic keys in blockchain > - Decentralized UMA authorization servers as online agents and > self-sovereign support technology > - TOR and other anonymization protocols for an UMA authorization server > > The more I learn about decentralized ID (in the Rebooting Web of Trust > context) and blockchains, the harder it is to map this work into > traditional standards and governance like OpenID Connect and IDESG. > > The tools for privacy engineering identity are out there but the > governance model that will put them together in a sustainable decentralized > way remains elusive. > > Adrian > > On Thu, Sep 8, 2016 at 8:18 AM, John Moehrke <johnmoehrke(a)gmail.com > <javascript:_e(%7B%7D,'cvml','johnmoehrke(a)gmail.com');>> wrote: > >> Thomas, >> >> That functionality - usecase - is critical to the use-case I presented on >> "Evidence Notebook". In that case the a human may need many identities, for >> the various things he is working on in his virtual notebooks. These >> identities need to be opaque at times, and later exposed for who they >> represent. I explain this in my use-case, but would very much rather it be >> a common building block concept that could be leveraged rather than >> re-explained. >> >> In my case these 'transaction identities' would be used for years before >> being exposed and retired. Is that timeframe acceptable in your use-case? >> The term 'transaction' tends to lead me to very short term use. >> >> John >> >> John Moehrke >> Principal Engineering Architect: Standards - Interoperability, Privacy, >> and Security >> CyberPrivacy – Enabling authorized communications while respecting Privacy >> M +1 920-564-2067 >> JohnMoehrke(a)gmail.com >> <javascript:_e(%7B%7D,'cvml','JohnMoehrke(a)gmail.com');> >> https://www.linkedin.com/in/johnmoehrke >> https://healthcaresecprivacy.blogspot.com >> "Quis custodiet ipsos custodes?" ("Who watches the watchers?") >> >> On Thu, Sep 8, 2016 at 6:18 AM, John Wunderlich <john(a)wunderlich.ca >> <javascript:_e(%7B%7D,'cvml','john(a)wunderlich.ca');>> wrote: >> >>> Thomas; >>> >>> This aligns well with Canadian privacy views of a 'biographical core' >>> and the social reality that we all have many identities that we present to >>> the world. When I read this and note the piece that I just posted about the >>> potential conflict between the GDPR 'right to erasure' and Blockchain, I >>> think you have correctly identified a normative inverse relationship >>> between "Core Identity" attributes what should be written openly to a >>> blockchain. Exciting work. >>> >>> John Wunderlich, >>> >>> Sent frum a mobile device, >>> Pleez 4give speling erurz >>> >>> "...a world of near-total surveillance and endless record-keeping is >>> likely to be one with less liberty, less experimentation, and certainly far >>> less joy..." A. Michael Froomkin >>> >>> >>> >>> >>> On Thu, Sep 8, 2016 at 12:23 AM -0400, "Thomas Hardjono" < >>> hardjono(a)mit.edu <javascript:_e(%7B%7D,'cvml','hardjono(a)mit.edu');>> >>> wrote: >>> >>> Folks, >>>> >>>> This may or may not be a use-case proper for BSC-DG, but I thought I'd mention it here because its an "infrastructure" technology that supports scaling of blockchains. (analogy: DNS is not part of Internet routing in TCP/IP, but it sure does help us use the Internet). >>>> >>>> One of the key concepts we (at MIT) are trying to develop further in CoreID (diagram is here http://www.findthomas.net/blog/) Part of it is the idea of a new kind of identity provider called the "persona provider" (PP) >>>> >>>> The Persona Provider could be implemented as a combination of an UMA Authorization Server combined with an UMA Resource Server. (PP = AS + RS). >>>> >>>> When Alice creates an account at the Persona Provider (PP), she convinces the PP initially that she is legit by supplying the PP with signed assertions (blinded assertion) which the Core Identity Issuer (upstream) has created. >>>> >>>> When Alice needs to transact on the blockchain using an anonymous-verifiable identity, she goes to her account at the PP and self-generates a transaction-identity (transaction-identifier) to be used on the blockchain or within a smart contract. She can self-generate as many transaction-identifiers as she needs -- no limit. The PP provides the crypto-tools to do this (just like bitcoin-wallets / client softwares or PGP). >>>> >>>> At the same time, she could optionally set policy on the account, treating the the blinded assertions (from the Core Identity Issuer) as resources. The transaction identities (which are anonymous-verifiable strings) can also be treated as resources sitting on the PP. >>>> >>>> The PP keeps these transaction-identifiers as long as she needs, and may even archive them. >>>> >>>> The PP also makes available a Identity Verification end-point (API) that allows the counter-party (RP) -- or anyone for that matter -- to verify a transaction-identifier found on a blockchain or in a smart-contract. >>>> >>>> >>>> If this is useful, I can write it up for the use-cases page. >>>> >>>> /thomas/ >>>> _______________________________________________ >>>> DG-BSC mailing listDG-BSC(a)kantarainitiative.org <javascript:_e(%7B%7D,'cvml','DG-BSC(a)kantarainitiative.org');>http://kantarainitiative.org/mailman/listinfo/dg-bsc >>>> >>>> >>> >>> This email and any files transmitted with it are confidential and >>> intended solely for the use of the individual or entity to whom they are >>> addressed. If you have received this email in error please notify the >>> system manager. This message contains confidential information and is >>> intended only for the individual named. If you are not the named addressee >>> you should not disseminate, distribute or copy this e-mail. Please notify >>> the sender immediately by e-mail if you have received this e-mail by >>> mistake and delete this e-mail from your system. If you are not the >>> intended recipient you are notified that disclosing, copying, distributing >>> or taking any action in reliance on the contents of this information is >>> strictly prohibited. >>> >>> _______________________________________________ >>> DG-BSC mailing list >>> DG-BSC(a)kantarainitiative.org >>> <javascript:_e(%7B%7D,'cvml','DG-BSC(a)kantarainitiative.org');> >>> http://kantarainitiative.org/mailman/listinfo/dg-bsc >>> >>> >> >> _______________________________________________ >> DG-BSC mailing list >> DG-BSC(a)kantarainitiative.org >> <javascript:_e(%7B%7D,'cvml','DG-BSC(a)kantarainitiative.org');> >> http://kantarainitiative.org/mailman/listinfo/dg-bsc >> >> > > > -- > > Adrian Gropper MD > > PROTECT YOUR FUTURE - RESTORE Health Privacy! > HELP us fight for the right to control personal health data. > DONATE: http://patientprivacyrights.org/donate-2/ > _______________________________________________ > DG-BSC mailing list > DG-BSC(a)kantarainitiative.org > <javascript:_e(%7B%7D,'cvml','DG-BSC(a)kantarainitiative.org');> > http://kantarainitiative.org/mailman/listinfo/dg-bsc > > > -- Adrian Gropper MD PROTECT YOUR FUTURE - RESTORE Health Privacy! HELP us fight for the right to control personal health data. DONATE: http://patientprivacyrights.org/donate-2/

1 0

Re: [DG-BSC] Blockchain Technologies and EU 'right to be forgot...
by John Wunderlich 08 Sep '16

08 Sep '16

Luk; The FYI was a flag that I was passing it on for information, not endorsing. That being said, and to your point, transaction audit logs may not be OK if the logs themselves reveal or contain personal information. It is often the case that privacy issues arise with edge cases. Most of the time, for most users, in most circumstances a system will be OK and the edge case will not arise. Developers, especially at startups or with new products, therefore leave edge cases for downstream fixes and consciously accept privacy and security risk to get to version 1.0 release and start generating cash flow. When this logic is applied to blockchain developments you end up with unrecoverable errors. John Wunderlich, Sent frum a mobile device, Pleez 4give speling erurz "...a world of near-total surveillance and endless record-keeping is likely to be one with less liberty, less experimentation, and certainly far less joy..." A. Michael Froomkin _____________________________ From: Luk Vervenne <luk.vervenne(a)synergetics.be> Sent: Thursday, September 8, 2016 7:13 AM Subject: Re: [DG-BSC] Blockchain Technologies and EU 'right to be forgot... To: John Wunderlich <john(a)wunderlich.ca> Cc: <dg-bsc(a)kantarainitiative.org> John, No so fast. Storing personal data with a right to be forgotten policy at hand, might not be.But transaction audit summary logs in blockchain within an ecosystem are ok luk On 8 Sep 2016, at 13:06, John Wunderlich <john(a)wunderlich.ca> wrote: FYI http://www.ibtimes.co.uk/blockchain-technologies-eu-right-be-forgotten-insu… John Wunderlich, Sent frum a mobile device, Pleez 4give speling erurz "...a world of near-total surveillance and endless record-keeping is likely to be one with less liberty, less experimentation, and certainly far less joy..." A. Michael Froomkin This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited._______________________________________________ DG-BSC mailing list DG-BSC(a)kantarainitiative.org http://kantarainitiative.org/mailman/listinfo/dg-bsc -- This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.

1 0

Blockchain Technologies and EU 'right to be forgot...
by John Wunderlich 08 Sep '16

08 Sep '16

FYI http://www.ibtimes.co.uk/blockchain-technologies-eu-right-be-forgotten-insu… John Wunderlich, Sent frum a mobile device, Pleez 4give speling erurz "...a world of near-total surveillance and endless record-keeping is likely to be one with less liberty, less experimentation, and certainly far less joy..." A. Michael Froomkin -- This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.

1 0

No call Thursday; editorial call Friday
by Eve Maler 07 Sep '16

07 Sep '16

A reminder that we're not meeting on Thursday (tomorrow). However, the core team interested to work on a key report section has identified Friday 11am PT/2pm ET/7pm UK/8pm CET as a 60-minute slot during which we can make progress; others are welcome to join if they remember and stick to our meeting goal. ;-) Dial-in details are the same as usual and are on the BSC calendar: http://kantarainitiative.org/confluence/display/BSC/Calendar Eve (sent from my iPhone, possibly with Siri's "help": +1-425-345-6756)

1 0

Notes from BSC telecon Tuesday, September 6 (NOTE: no meeting this Thursday)
by Eve Maler 06 Sep '16

06 Sep '16

http://kantarainitiative.org/confluence/display/BSC/2016-09+%28September+20… Agenda: - Pick a time for an ad hoc report working session - Work on use cases on the call (finally!) Attending: Eve, Kathleen, Jeff S, Adam M, John M, Scott S, Domenico, Adrian, Jim, John W *NOTE:* No BSC telecon this Thursday because we couldn't find a chair pro tem. Eve, Thomas, Kathleen, and Scott D had expressed particular interest in an editing session. We'll work out a time for that and advertise the time. (John W and Domenico have some interest.) Regarding the Stellar Consensus Protocol-involving use case: John W notes: "Disclaimer re: Stellar Consensus Protocol. I work with JLINC Labs which uses the Stellar blockchain for our open source JLINC protocol." John M describes his new "Evidence Notebook" use case <https://healthcaresecprivacy.blogspot.com/2016/08/blockchain-and-smart-cont…>: It's trying to achieve what Jim describes as proof-of-existence in a way that can be private at first. He provides three variations, e.g. to provide signatures. Community peers could even provide counter-signatures even if they can't see the content. He's prepared for lots of discussion over all of this. Adrian ties these ideas to his for doctors signing patient-centric prescriptions, noting that no smart contract is needed in his scenario; for John's use case, the signature is independent and doesn't need smart contracts while the escrow does. Observing commonalities in use cases: John W sees that there are attributes (facts??) that are frozen and verifiable. In the identity space, these might be identity attributes. *Eve Maler*ForgeRock Office of the CTO | VP Innovation & Emerging Technology Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl *ForgeRock Summits and UnSummits* are coming to <http://summits.forgerock.com/> *London and Paris!*

1 0