[DG-BSC] Blockstack identity services

James Hazard james.g.hazard at gmail.com
Wed Aug 3 09:08:43 CDT 2016


Though "Blockchain" is in the title of this discussion group, it need not
be in all of the solutions.  "Blockchains" have large privacy and data
security challenges built into maintaining consensus on the state of the
ledger (database).  Most real life situations have available a range of
alternative means of validating the state of the ledger.  For instance, a
regulator.

So, we might view it as a bug, rather than a feature, if a "smart contract"
solution requires execution on a blockchain.

Organizations and humans will want to be able to efficiently manage large
numbers of ledger entries, in efficient databases (SQL, graph, IPFS), not
blockchains.  They will need to be able to run the smart contracts on those
other platforms.

Data replication should be minimized, and temporary to the extent
possible.  This will, I think, also be required by GDPR.

The necessary point of agreement, the waist of the Zittrain hourglass, is
very small - a format for ledger entries.  CommonAccord asserts (I assert
on its behalf) that the key to this is ... key/values, a way of resolving
references, and inheritance.  For good reasons, JSON is a likely to be the
most common "punctuation" (Eve's word) for exchange of ledger entries.  Our
current rendering engine uses plain text and carriage returns.  That is the
lightest "punctuation" and may be the best for collaboration on big texts,
notably for collaboration among lawyers and regulators on Github.  It
closely parallels the presentation of software source code.  But this
barely matters.  What matters is a common approach to linking and
inheritance.










On Wed, Aug 3, 2016 at 6:53 AM, John Wunderlich <john at wunderlich.ca> wrote:

> Domenico;
>
> As soon as the use case makes Alice's role that of a "Citizen" a whole
> raft of non-technical issues arise that should be addressed. How do you
> implement privacy protection into the architecture to avoid abuse by
> authoritarian regimes? If I think of all the cases where I'm asked to
> present government issued ID as proof of identity, and then ask, "Would it
> be a good thing if there was an permanent audit trail available to the
> government (any state agency) of all those interactions?"
>
> I would restate your problem definition to see if we can design a wide
> identity ecosystem use case for managing citizen identities that enables
> (or better, only works if) citizens control their own identities.
>
> (PS, see my signature block below, apropos of this issue)
>
> 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: Domenico Catalano <domenico.catalano at oracle.com>
> Sent: Wednesday, August 3, 2016 4:47 AM
> Subject: [DG-BSC] Blockstack identity services
> To: <dg-bsc at kantarainitiative.org>
>
>
> Hi all,
>
> maybe, you already know blockstack id technology for identity services, at
> blockstack.org <https://blockstack.org/docs/how-blockstack-works>
>
> I think it’s quite useful for investigation and for defining use cases.
>
> I was wondering whether we can provide a wide identity ecosystem use case
> for managing citizen identities.
>
> Consider the following high level use case:
>
> - The Citizen is identified by a Blockchain-ready Registry.
> - The Citizen requests to register with the Registry through a specific
> mobile app, which provides the necessary cryptographic key pairs with which
> the request is signed.
> - The Registry includes the request in the blockchain which is distributed
> among the nodes, as smart contract.
> - The mobile app and the cryptographic keys are now able to provides
> strong authentication mechanisms for citizen online access.
>
> Citizen Identity can be enriched through the blockchain nodes (special
> nodes) interactions which provide attribute/profile attestation.
>
> I hope it’s useful for further discussions.
>
> Thanks
> Domenico
>
>
>
>
>
> 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 at kantarainitiative.org
> http://kantarainitiative.org/mailman/listinfo/dg-bsc
>
>


-- 
@commonaccord
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://kantarainitiative.org/pipermail/dg-bsc/attachments/20160803/605fd4d7/attachment-0001.html>


More information about the DG-BSC mailing list