Madiator2011/lbry-sdk
1
0
Fork 0
forked from LBRYCommunity/lbry-sdk
Code Pull requests Activity
The LBRY SDK for building decentralized, censorship resistant, monetized, digital content apps.
437 commits 111 branches 641 tags 30 MiB
Python 99.8%
Shell 0.1%
Go to file
Jack c10e7b2b41 fix import
2016-05-30 15:39:27 -04:00
lbrynet fix import 2016-05-30 15:39:27 -04:00
packaging update from master 2016-05-24 17:50:01 -04:00
tests get channel id from slack for test bot 2016-02-26 11:20:31 -05:00
.gitignore update daemon 2016-02-27 13:19:26 -05:00
.gitmodules update from master 2016-05-24 17:50:01 -04:00
.travis.yml add developer id to travis.yml 2016-05-25 21:02:30 -04:00
app.icns update status bar app 2016-03-02 02:00:45 -05:00
ez_setup.py initial commit 2015-08-20 11:27:15 -04:00
INSTALL.md update from master 2016-05-24 17:50:01 -04:00
LICENSE initial commit 2015-08-20 11:27:15 -04:00
MANIFEST.in fixes so we can build an sdist 2016-03-22 22:15:07 -04:00
README.md update from master 2016-05-24 17:50:01 -04:00
requirements.txt add base58 2016-04-09 15:43:25 -04:00
RUNNING.md update documentation to reflect using lbryum by default 2016-03-09 12:26:07 -05:00
setup.py update from master 2016-05-24 17:50:01 -04:00
setup_win32.py update win32 setup script to include lbryum 2016-02-28 12:45:21 -05:00

README.md

Build Status

LBRYnet

LBRYnet is a fully decentralized network for distributing data. It consists of peers uploading and downloading data from other peers, possibly in exchange for payments, and a distributed hash table, used by peers to discover other peers.

Installation

Download the latest release or see INSTALL.md for manual installation.

Overview

On LBRYnet, data is broken into chunks, and each chunk is specified by its sha384 hash sum. This guarantees that peers can verify the correctness of each chunk without having to know anything about its contents, and can confidently re-transmit the chunk to other peers. Peers wishing to transmit chunks to other peers announce to the distributed hash table that they are associated with the sha384 hash sum in question. When a peer wants to download that chunk from the network, it asks the distributed hash table which peers are associated with that sha384 hash sum. The distributed hash table can also be used more generally. It simply stores IP addresses and ports which are associated with 384-bit numbers, and can be used by any type of application to help peers find each other. For example, an application for which clients don't know all of the necessary chunks may use some identifier, chosen by the application, to find clients which do know all of the necessary chunks.

For Developers

LBRY comes with an file sharing application, called 'lbrynet-console', which breaks files into chunks, encrypts them with a symmetric key, computes their sha384 hash sum, generates a special file called a 'stream descriptor' containing the hash sums and some other file metadata, and makes the chunks available for download by other peers. A peer wishing to download the file must first obtain the 'stream descriptor' and then may open it with his 'lbrynet-console' client, download all of the chunks by locating peers with the chunks via the DHT, and then combine the chunks into the original file, according to the metadata included in the 'stream descriptor'.

For detailed instructions, see INSTALL.md and RUNNING.md.

Documentation: doc.lbry.io (may be out of date)

Source code: https://github.com/lbryio/lbry

To contribute, join us on Slack or contact josh@lbry.io. Pull requests are also welcome.

Support

Please open an issue and describe your situation in detail. We will respond as soon as we can.

For private issues, contact josh@lbry.io.

License

See LICENSE