mirror of
https://github.com/Decentralized-ID/decentralized-id.github.io.git
synced 2024-12-11 08:34:30 -05:00
cleanup\move projects to own page
This commit is contained in:
⧉ infominer
parent
24711974ab
commit
d58af13c81
@ -11,20 +11,23 @@ layout: single
|
||||
classes: wide
|
||||
permalink: /blockchain/
|
||||
categories: ["Blockchain"]
|
||||
tags: ["Blockpass","Ontology","Blockstack","Handshake","Democracy Earth"]
|
||||
last_modified_at: 2020-01-11
|
||||
last_modified_at: 2020-11-10
|
||||
toc: false
|
||||
---
|
||||
|
||||
## Blockchain Identity
|
||||
|
||||
* [](https://www.tcs.com/content/dam/tcs-bancs/protected-pdf/Impact%20of%20Blockchain%20on%20Digital%20identity.pdf)
|
||||
* [Impact of Blockchain on Digital Identity](https://www.tcs.com/content/dam/tcs-bancs/protected-pdf/Impact%20of%20Blockchain%20on%20Digital%20identity.pdf)
|
||||
> Starting from plain vanilla guidelines of security such as using a complex password to deploying cutting-edge technologies such as Biometrics, Machine Learning and Robotic Process Automation, multiple methods are being evaluated for digital identity protection.
|
||||
>
|
||||
> Effective though they are, when applied on a Centralized Digital Identity Management system, these solutions prove costly and sometimes not as effective. One of the main drawbacks of such a centralized system is that the control of data remains with one entity
|
||||
* [Self-Sovereign Identity: Why Blockchain?](https://www.ibm.com/blogs/blockchain/2018/06/self-sovereign-identity-why-blockchain/)
|
||||
> This question tends to stem from the notion that data associated with a person’s identity is destined to be stored, shared and used for verification on some form of distributed ledger technology. My hope is that this article with help to debunk that notion and provide a basic foundational understanding of how distributed ledger technology is being used to solve our identity infrastructure dilemma and resolve the impacts of the internet lacking an identity layer.
|
||||
* [Deployment of a Blockchain-Based Self-Sovereign Identity - Delft](https://arxiv.org/pdf/1806.01926.pdf)
|
||||
> Digital identity is unsolved: after many years of research there is still no trusted communication over the Internet. To provide identity within the context of mutual distrust, this paper presents a blockchain-based digital identity solution. Without depending upon a single trusted third party, the proposed solution achieves passport-level legally valid identity. This solution for making identities Self-Sovereign, builds on a generic provable claim model for which attestations of truth from third parties need to be collected. The claim model is then shown to be both blockchain structure and proof method agnostic. Four different implementations in support of these two claim model properties are shown to offer sub-second performance for claim creation and claim verification. Through the properties of Self-Sovereign Identity, legally valid status and acceptable performance, our solution is considered to be fit for adoption by the general public.
|
||||
* [**_A Taxonomic Approach to Understanding Emerging Blockchain Identity Management Systems_**](https://arxiv.org/pdf/1908.00929.pdf) NIST CYBERSECURITY WHITE PAPER (DRAFT) BLOCKCHAIN IDENTITY MANAGEMENT APPROACHES
|
||||
JULY 9, 2019
|
||||
> Identity management systems (IDMSs) are widely used to provision user identities while managing authentication, authorization, and data sharing both within organizations as well as on the Internet more broadly. Traditional identity systems typically suffer from single points of failure, lack of interoperability, and privacy issues such as encouraging mass data collection and user tracking. Blockchain technology has the potential to support novel data ownership and governance models with built-in control and consent mechanisms, which may benefit both users and businesses by alleviating these concerns; as a result, blockchain-based IDMSs are beginning to proliferate. This work categorizes these systems into a taxonomy based on differences in architecture, governance models, and other salient features. We provide context for the taxonomy by describing related terms, emerging standards, and use cases, while highlighting relevant security and privacy considerations.
|
||||
* [Identity Management with Blockchain: The Definitive Guide (2019)](https://tykn.tech/identity-management-blockchain/)
|
||||
> Learn everything about how Blockchain is used for Identity Management. This Definitive Guide to Identity Management with Blockchain has the answers.
|
||||
> In identity management, a distributed ledger (a “blockchain”) enables everyone in the network to have the same source of truth about which credentials are valid and who attested to the validity of the data inside the credential, without revealing the actual data.
|
||||
* [Phil Windley (@windley)](https://twitter.com/windley/status/1071469217650638848)
|
||||
> If ledger isn’t used, then every issuer of a credential has to maintain infrastructure or contract service provider to respond to DID resolution & revocation requests. And, credential issuers would know when the credential was used, impacting privacy.
|
||||
|
||||
@ -35,16 +38,24 @@ JULY 9, 2019
|
||||
[Blockchain Identity – Success Factors and Challenges](https://www.kuppingercole.com/blog/kuppinger/blockchain-identity-success-factors-and-challenges) by Martin Kuppinger
|
||||
> When new things arrive, which are still in the pioneering stage and far from reaching maturity, there is always a lot of discussion. This is even more true for Blockchain Identity, where the massive hype around Blockchains, a long history of clever ideas failing, and a few interesting technical and security challenges come together. During my keynote at this year’s EIC, I addressed the challenges and success factors for Blockchain ID as well. That led to a discussion on Twitter about whether some of these success factors are contradictory.
|
||||
* [GDPR - A reflection on the 'self-sovereign identity' and the Blockchain](https://www.linkedin.com/pulse/gdpr-reflection-self-sovereign-identity-blockchain-nicolas-ameye/)
|
||||
> The GDPR is taking for granted a centralized identity model, meaning a centralized model of digital data storage and transmission. Those centralized models of digital data storage are relying on the principles that the data custodians are trustworthy and are mandated to steward personal data. The GDPR, while being technology-neutral by nature, is articulated around the idea that personal data are being stewarded by centralized authorities.
|
||||
|
||||
<iframe src="https://channel9.msdn.com/Shows/Blocktalk/Decentralized-Identity-and-Blockchain/player" width="640" height="360" allowFullScreen frameBorder="0" title="Decentralized Identity and Blockchain - Microsoft Channel 9 Video"></iframe>
|
||||
|
||||
* [Towards Self-Sovereign Identity using Blockchain Technology](https://essay.utwente.nl/71274/1/Baars_MA_BMS.pdf)
|
||||
> Blockchain technology could function as the foundation of such system being a network for decentralized trust and exchange. Because everyone can participate as issuer or acquirer (and both), there are low adoption barriers and low costs. This allows new business opportunities for governments, banks and other authorities and more transparency and control for end-users.
|
||||
* [Identity and Distributed Ledger - Today and Tomorrow - June 26 - Identiverse 2019](https://www.youtube.com/watch?v=l04AHP7kPPw)
|
||||
> Join our expert panel, moderated by Paul Madsen, as they discuss and debate the future of distributed identity technology and its applications in solving identity problems.
|
||||
* [Self-Sovereign Identity and the Legitimacy of Permissioned Ledgers](http://www.windley.com/archives/2016/09/self-sovereign_identity_and_the_legitimacy_of_permissioned_ledgers.shtml)
|
||||
> This post justifies the claim that an identity system based on a permissioned distributed ledger is legitimately self-sovereign. The post also examines the claims to legitimacy that social login and distributed ledger identity systems make.
|
||||
* [Distributed Ledger Technologies, IAM, and the Truth in Things - June 27 - Identiverse 2019](https://www.youtube.com/watch?v=VV2rLgH9TUE) - Robert Brown
|
||||
> The Internet of Things has a problem with data silos – it’s difficult for data to move across domains and prove where it came from. Users of IoT data must understand how Things were made and kept up-to-date if they are to know the data received is truthful. Yet keeping Things healthy is not the sole responsibility of a single actor; components of a Thing may be shared amongst hardware and software vendors, system integrators, retailers, system operators, owners, regulators or third parties. Safety and security rests with all involved in authorizing updates, how and when they are applied as well as the right to repair when Things are no longer officially supported. Shared device lifecycle assurance is the basis for verifiable service histories of Things which give data provenance. When data can be proven to originate from reliable sources, its value increases while reducing the risk of using it. Enabling third parties to build value from data would unlock the true value of IoT which in turn could fund its upkeep. This talk will outline how identity and shared ledger technology have key roles to building Truth in Things for a sustainable IoT.
|
||||
* [Decentralized Identity: Intersection of Identity and Distributed Ledger - June 25 - Identiverse 2019](https://www.youtube.com/watch?v=bjlnZyMTf1M) - Preeti Rastogi
|
||||
> Decentralization in Identity is a shiny object, promising amazing benefits – but sometimes it is nice to just see how the protocols work. Join this session for an overview of the distributed ledger landscape and a discussion of the role it plays in the identity world, as well as the new challenges it introduces. We will talk about how public keys stored on a ledger might act as an anchor for digital trust and what architectures are evolving to leverage that trust.
|
||||
* [Blockchain for Identity - Myth or Potential](https://www.kuppingercole.com/blog/kuppinger/blockchain-for-identity-myth-or-potential)
|
||||
|
||||
> Authentication might definitely become simpler, by having various authenticators and IDs, from eIDs to social logins, associated with a wallet. Just one simple store to get access. Yes, there are challenges in creating secure, easy-to-use wallets, but there is potential as well.
|
||||
|
||||
|
||||
|
||||
## Assorted Blockchain ID Initiatives
|
||||
|
||||
@ -68,93 +79,6 @@ JULY 9, 2019
|
||||
* [We can do better than selling our data](http://blogs.harvard.edu/doc/2018/09/18/data/)-Doc Searls(*IIW*)
|
||||
|
||||
|
||||
## Blockpass
|
||||
|
||||
<img src="https://imgur.com/mMZ4E2rl.png" />
|
||||
|
||||
* [Blockpass](https://www.blockpass.org/) [[**T**](https://twitter.com/BlockpassOrg)] [[**wp**](https://www.blockpass.org/downloads/BlockpassWhitepaper.v1.3.3.pdf)]
|
||||
* [Edinburgh Identity Lab](https://identity-lab.blockpass.org/) [[**ϟ**](https://www.newsbtc.com/2018/09/28/worlds-first-blockchain-identity-lab-launched-today-in-edinburgh/)]
|
||||
|
||||
## Ontology
|
||||
|
||||
|
||||
* [ONTology](https://ont.io/) [[**G**](https://github.com/ontio/ontology-DID)]— "a "Distributed Trust Network" which combines a cross-chain identity system, peer-to-peer data transmission, data authorization mechanisms, distributed data storage, attestation, and various industry-specific modules. It also includes an Ontology Crypto Package (OCP) and an Ontology Marketplace (OM)."
|
||||
|
||||
## Blockstack
|
||||
|
||||
|
||||
|
||||
* [Blockstack](https://blockstack.org/) • [[**G**](https://github.com/blockstack)]ithub • [[**F**](https://forum.blockstack.org/)]orum • [[**B**](https://blockstack.org/blog)]log • [[**T**](https://twitter.com/blockstack)]witter • [[**W**](https://blockstack.org/whitepaper.pdf)]hitepaper • [[**bitcoinwiki**](https://en.bitcoinwiki.org/wiki/BlockStack)]
|
||||
* a network of computers that collectively maintain a global registry of domain names, public keys, and cryptographic hashes. With this registry, Blockstack serves as a decentralized domain name system (DNS) and a decentralized public key infrastructure (PKI).
|
||||
* [dantrevino/awesome-blockstack](https://github.com/dantrevino/awesome-blockstack) [[**ϟ**](https://gitlab.com/dantrevino/awesome-blockstack)]
|
||||
* [Onename](https://onename.com/) — "a product built on Blockstack that allows people to register identities"
|
||||
* [App Mining](https://app.co/mining)
|
||||
* [Launch HN: Stacks (YC S14) – The first SEC-qualified crypto token offering](https://news.ycombinator.com/item?id=20413420) -news.ycombinator
|
||||
* [Introducing Clarity, a language for predictable smart contracts](https://blog.blockstack.org/introducing-clarity-the-language-for-predictable-smart-contracts/)
|
||||
* [Extending Existing Blockchains with Virtualchain](https://www.zurich.ibm.com/dccl/papers/nelson_dccl.pdf)
|
||||
* [Breaking Down Blockstack — Whitepaper Review](https://tokeneconomy.co/breaking-down-blockstack-whitepaper-review-3c828788f3e9)
|
||||
* [Breaking Down Blockstack — Stack Tokens](https://tokeneconomy.co/breaking-down-blockstack-pt-2-stack-tokens-7718578cfeae)
|
||||
* [app.co/blockstack](https://app.co/blockstack)
|
||||
* [docs.blockstack.org/core/naming/did.html](https://docs.blockstack.org/core/naming/did.html)
|
||||
>BNS nodes are compliant with the emerging Decentralized Identity Foundation protocol specification for decentralized identifiers (DIDs).
|
||||
>
|
||||
>Each name in BNS has an associated DID. The DID format for BNS is:
|
||||
>
|
||||
> `did:stack:v0:{address}-{index}`
|
||||
* [Blockstack DID Spec](https://github.com/blockstack/blockstack-core/blob/master/docs/blockstack-did-spec.md)[[**ϟ**](https://forum.blockstack.org/t/did-method-at-identity-foundation/4287)]
|
||||
* [Bringing decentralized identity to traditional apps](https://www.larrysalibra.com/blog/adding-blockstack-auth-to-discourse/)
|
||||
>TL;DR: In this technical post for developers, I walk through how we added Blockstack ID support to the Discourse forum software.
|
||||
|
||||
## Handshake
|
||||
<img src="https://i.imgur.com/lhHnC8w.png"/>
|
||||
|
||||
* [Handshake](https://handshake.org)
|
||||
* [WhitePaper](https://handshake.org/files/handshake.txt)
|
||||
* [Docs](https://handshake-org.github.io/)
|
||||
* [twitter.com/HNS](https://twitter.com/hns)
|
||||
* [github.com/handshake-org](https://github.com/handshake-org)
|
||||
|
||||
Handshake is a UTXO-based blockchain protocol which manages the registration, renewal and transfer of DNS top-level domains (TLDs). Our naming protocol differs from its predecessors in that it has no concept of namespacing or subdomains at the consensus layer. Its purpose is not to replace DNS, but to replace the root zone file and the root servers.
|
||||
|
||||
>Handshake is public blockchain that will serve as a global list of top-level domain names. By pointing your browser to resolve requests via the Handshake network instead of at your local DNS resolving server, you’ll essentially be looking up websites’ IP addresses on the Handshake blockchain, instead of those maintained on DNS resolvers that are centralized. - [The Case for Handshake](https://medium.com/amentum/the-case-for-handshake-9b0af0d989fe) A Compelling Bid to Decentralize Domain Names
|
||||
Steven McKie
|
||||
|
||||
>Many fail to realize that DNS is already decentralized, with the exception of a single, critical component, of which trust is centralized: the root zone, or simply, a collection of top level domains (TLDs). And this trust anchor is kept by a small federation of authoritative bodies, where ICANN is currently the ultimate authority. - [Everything You Didn’t Know About the Handshake Naming System](https://hackernoon.com/everything-you-didnt-know-about-the-handshake-naming-system-how-this-blockchain-project-will-483464309f33)
|
||||
|
||||
>Certificate Authorities in the DNS network constructed the way it is today are the trusted stewards for the operation of the Internet. These stewards, as explained in the project paper, are profit-maximizing entities. Meaning, ICANN has no altruistic incentive to act honestly, yet has every incentive to maintain its natural monopoly over the riches that come with governing a critical layer of the Internet. And even if CAs intend to be good stewards, the premise of the decentralization movement posits that we should not ever need to rely on any single authority, especially one that acts as the gatekeeper to the highway of all human knowledge - [Everything You Didn’t Know About the Handshake Naming System](https://hackernoon.com/everything-you-didnt-know-about-the-handshake-naming-system-how-this-blockchain-project-will-483464309f33)
|
||||
|
||||
* [Handshake: An experimental peer-to-peer root DNS (handshake.org)](https://news.ycombinator.com/item?id=17676312) -news.ycombinator.com
|
||||
>This seems like a neat idea but the economics are that of a for profit business, and I think we learned that handing domains to a for profit (NetworkSolutions) was a bad idea.
|
||||
>
|
||||
>7% going to contributors and 7% going to financial backers is a pretty big incentive. [0]
|
||||
>
|
||||
>I’d rather see this set up as a non profit foundation or a community driven trust and run in an OSS way for the financial elements. As it is, I don’t think we should create a decentralized network with such significant financial incentives.
|
||||
>
|
||||
>[0] https://handshake.org/how-it-works
|
||||
* [Handshake Whitepaper](https://namebase.io/handshake-whitepaper/)
|
||||
> This is a formatted and annotated version of the original Handshake whitepaper hosted by Namebase, a Handshake registrar and exchange. Last updated November 29, 2018.
|
||||
>
|
||||
>If you have questions about the whitepaper, message the Telegram group or email whitepaper@namebase.io and we will add a relevant annotation to the whitepaper.
|
||||
|
||||
### [handshake-org](https://github.com/handshake-org) - github
|
||||
|
||||
* [@handshake-org](https://github.com/handshake-org)
|
||||
* [handshake-org/hsd](https://github.com/handshake-org/hsd) - Handshake Daemon & Full Node
|
||||
* [handshake-org/hs-client](https://github.com/handshake-org/hs-client) - REST, websocket, and RPC client for hsd
|
||||
* [handshake-org/urkel](https://github.com/handshake-org/urkel) - Cryptographically provable database (i.e. an urkel tree)
|
||||
* [handshake-org/goosig](https://github.com/handshake-org/goosig) - Anonymous RSA signatures
|
||||
* [handshake-org/handshake-org.github.io](https://github.com/handshake-org/handshake-org.github.io) - Handshake developer documentation site
|
||||
* [handshake-org/hnsd](https://github.com/handshake-org/hnsd) - Handshake SPV name resolver
|
||||
* [handshake-org/hs-miner](https://github.com/handshake-org/hs-miner) - Mining infrastructure for handshake
|
||||
* [handshake-org/hs-airdrop](https://github.com/handshake-org/hs-airdrop) - Decentralized airdrop to open source developers
|
||||
* [handshake-org/hs-names](https://github.com/handshake-org/hs-names) - Pre-reserved Handshake Names
|
||||
* [handshake-org/hs-tree-data](https://github.com/handshake-org/hs-tree-data)
|
||||
* [handshake-org/hdns](https://github.com/handshake-org/hdns) - Handshake-capable DNS module for node.js
|
||||
* [handshake-org/bcuckoo](https://github.com/handshake-org/bcuckoo) - Cuckoo Cycle in pure javascript
|
||||
* [handshake-org/faucet-tool](https://github.com/handshake-org/faucet-tool) - A tool to generate mnemonic seeds, keys and addresses for the Handshake Faucet
|
||||
* [handshake-org/hndshkBot](https://github.com/handshake-org/hndshkBot) - IRC Bot for developer faucet
|
||||
* [handshake-org/libhns](https://github.com/handshake-org/libhns) -C library for resolving handshake names (fork of c-ares)
|
||||
|
||||
## Democracy Earth
|
||||
|
||||
|
||||
|
||||
Loading…
Reference in New Issue
Block a user