LBRYCommunity/spec
1
0
Fork 0
Code Issues 5 Pull requests Projects Releases Packages Wiki Activity

add status to intro

Browse source
This commit is contained in:
Jeremy Kauffman 2019-02-12 09:47:50 -05:00 committed by GitHub
parent 42bccd91c9
commit a426da29c7
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
index.md
View file

@ -26,7 +26,11 @@ This document assumes that the reader is familiar with distributed hash tables (
### Overview
This document defines the LBRY protocol, its components, and how they fit together. LBRY consists of several discrete components that are used together in order to provide the end-to-end capabilities of the protocol. There are two distributed data stores (blockchain and DHT), a peer-to-peer protocol for exchanging data, and specifications for data structure, encoding, and retrieval.
This document defines the LBRY protocol, its components, and how they fit together. LBRY consists of several discrete components that are used together in order to provide the end-to-end capabilities of the protocol. There are two distributed data stores (blockchain and DHT), a peer-to-peer protocol for exchanging data, and specifications for data structure, encoding, and retrieval.
### Status
LBRY is not a theoretical system design, but one that has been in live usage since June 2016. As of February 2019, approximately 750,000 pieces of digital content have been published via the LBRY protocol. On a monthly basis, tens of thousands of users will access hundreds of thousands of pieces of content, downloading and uploading terrabytes of data. Graphical, end-user consumer browsers and wallets exist on all major operating systems and are available on LBRY's consumer portal at [lbry.io/get](https://lbry.io/get).
### Conventions and Terminology