mirror of
https://github.com/Decentralized-ID/decentralized-id.github.io.git
synced 2025-08-19 03:18:07 -04:00
add info
This commit is contained in:
infominer
parent
4fc36a4b50
commit
f1f878a055
6 changed files with 823 additions and 35 deletions
|
|
@ -10,27 +10,31 @@ redirect_from:
|
|||
- id-initiatives/bitcoin/
|
||||
- id-initiatives/bitcoin
|
||||
categories: ["Blockchain","Bitcoin"]
|
||||
last_modified_at: 2019-07-11T11:22:33-23:00
|
||||
|
||||
---
|
||||
|
||||
|
||||
|
||||
## Contents
|
||||
|
||||
* [BTCR](#btcr)
|
||||
* [RWoT BTCR](#rwot-btcr)
|
||||
* [Bitnation](#bitnation)
|
||||
* [Spidchain](#spidchain)
|
||||
## ION
|
||||
|
||||
<blockquote class="twitter-tweet"><p lang="en" dir="ltr">I'm excited to share with you an early look at our work on a scalable, open src, permissionless Layer 2 network for Decentralized Identifiers that runs atop Bitcoin, developed and supported by Microsoft as an open public infrastructure for all - meet ION: <a href="https://t.co/9TOl8oyEVB">https://t.co/9TOl8oyEVB</a></p>— Daniel Ƀ (@csuwildcat) <a href="https://twitter.com/csuwildcat/status/1127926974054391809?ref_src=twsrc%5Etfw">May 13, 2019</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
|
||||
|
||||
<iframe src="//www.slideshare.net/slideshow/embed_code/key/e4v6fZdFL5fdu3" width="595" height="485" frameborder="0" marginwidth="0" marginheight="0" scrolling="no" style="border:1px solid #CCC; border-width:1px; margin-bottom:5px; max-width: 100%;" allowfullscreen> </iframe> <div style="margin-bottom:5px"> <strong> <a href="//www.slideshare.net/SSIMeetup/introduction-to-ion-a-layer-2-network-for-decentralized-identifiers-with-bitcoin-daniel-buchner" title="Introduction to Ion – a layer 2 network for Decentralized Identifiers with Bitcoin - Daniel Buchner" target="_blank">Introduction to Ion – a layer 2 network for Decentralized Identifiers with Bitcoin - Daniel Buchner</a> </strong> from <strong><a href="https://www.slideshare.net/SSIMeetup" target="_blank">SSIMeetup</a></strong> </div>
|
||||
|
||||
{% include video id="agPVWVe0p3Q" provider="youtube" %}
|
||||
|
||||
* [decentralized-identity/ion](https://github.com/decentralized-identity/ion)
|
||||
|
||||
<iframe src="https://castbox.fm/app/castbox/player/id1098037/id155192208?v=8.3.0&autoplay=0" frameborder="0" width="100%" height="500"></iframe>
|
||||
|
||||
## BTCR
|
||||
|
||||
### BTCR
|
||||
* <a href="https://github.com/w3c-ccg/didm-btcr" target="_blank">/w3c-ccg/didm-btcr</a> - WORK ITEM: BTCR DID Method Spec
|
||||
* did:btcr: - [BTCR DID Method](https://w3c-ccg.github.io/didm-btcr/)
|
||||
* The Bitcoin Reference DID method (did:btcr) supports DIDs on the public Bitcoin blockchain. The Bitcoin Reference method has minimal design goals: a DID trust anchor based on the Bitcoin blockchain, updates publicly visible and auditable via Bitcoin transactions, and optionally, additional DID Document information referenced in the transaction OP_RETURN data field. No other Personal Identifiable Information (PII) would be placed on the immutable blockchain.
|
||||
* [btcr tx conversion playground](https://weboftrustinfo.github.io/btcr-tx-playground.github.io/)
|
||||
|
||||
|
||||
### RWot BTCR
|
||||
|
||||
* <a href="https://github.com/WebOfTrustInfo/btcr-tx-playground.github.io" target="_blank">/WebOfTrustInfo/btcr-tx-playground.github.io</a>
|
||||
* <a href="https://github.com/WebOfTrustInfo/btcr-did-tools-js" target="_blank">/WebOfTrustInfo/btcr-did-tools-js</a>
|
||||
* <a href="https://github.com/WebOfTrustInfo/btcr-hackathon" target="_blank">/WebOfTrustInfo/btcr-hackathon</a> - Virtual hackathon to create spec and code for Bitcoin-based Decentralized Identifiers (DIDs)
|
||||
|
|
|
|||
|
|
@ -10,8 +10,64 @@ redirect_from:
|
|||
- id-initiatives/handshake/
|
||||
categories: ["Blockchain","DNS"]
|
||||
tags: ["Handshake"]
|
||||
last_modified_at: 2019-07-11T11:22:33-23:00
|
||||
|
||||
---
|
||||
|
||||
<img src="https://i.imgur.com/lhHnC8w.png"/>
|
||||
|
||||
* [Handshake](https://handshake.org) [[**wp**](https://handshake.org/files/handshake.txt)] [[**D**](https://handshake-org.github.io/)] - 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](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.
|
||||
|
||||
|
||||
|
||||
## GitHub [@handshake-org](https://github.com/handshake-org)
|
||||
|
||||
* [@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/blog](https://github.com/handshake-org/blog) - the Handshake project's blog
|
||||
* [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)
|
||||
|
||||
|
|
|
|||
|
|
@ -10,14 +10,34 @@ redirect_from:
|
|||
- id-initiatives/blockstack/
|
||||
categories: ["Blockchain"]
|
||||
tags: ["Blockpass"]
|
||||
last_modified_at: 2019-07-11T11:22:33-23:00
|
||||
|
||||
---
|
||||
|
||||
|
||||
|
||||
## General
|
||||
|
||||
* [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).
|
||||
* [Extending Existing Blockchains with Virtualchain](https://www.zurich.ibm.com/dccl/papers/nelson_dccl.pdf)
|
||||
* [Onename](https://onename.com/) — "a product built on Blockstack that allows people to register identities"
|
||||
* [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/9)**]
|
||||
* [App Mining](https://app.co/mining)
|
||||
* [/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)
|
||||
|
||||
## DID Related
|
||||
|
||||
* [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.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue