.github | ||
docs | ||
lbrynet | ||
scripts | ||
tests | ||
.gitattributes | ||
.gitignore | ||
.pylintrc | ||
.travis.yml | ||
CHANGELOG.md | ||
CONTRIBUTING.md | ||
Dangerfile | ||
example_daemon_settings.yml | ||
INSTALL.md | ||
lbry.png | ||
LICENSE | ||
mkdocs.yml | ||
README.md | ||
setup.py | ||
tox.ini |
LBRY
LBRY is an open-source protocol providing distribution, discovery, and purchase of digital content (data) via a decentralized peer-to-peer network. It utilizes the LBRY blockchain as a global namespace and database of digital content. Blockchain entries contain searchable content metadata, identities, rights and access rules. LBRY also provides a data network that consists of peers (seeders) uploading and downloading data from other peers, possibly in exchange for payments, as well as a distributed hash table used by peers to discover other peers.
This project provides an SDK for building applications using the LBRY protocol. The SDK is written in Python 3.7+ using Twisted. For other languages or platforms, a JSON-RPC API is provided.
Installation
Our releases page contains pre-built binaries of the latest release, pre-releases, and past releases for macOS, Debian-based Linux, and Windows. Automated travis builds are also available for testing.
Usage
Run lbrynet start
to launch the API server.
By default, lbrynet
will provide a JSON-RPC server at http://localhost:5279
. It is easy to interact with via cURL or sane programming languages.
Our quickstart guide provides a simple walkthrough and examples for learning.
The full API is documented here.
Running from source
Installing from source is also relatively painless. Full instructions are in INSTALL.md
Contributing
Contributions to this project are welcome, encouraged, and compensated. For more details, please check this link.
License
This project is MIT licensed. For the full license, see LICENSE.
Security
We take security seriously. Please contact security@lbry.io regarding any security issues. Our GPG key is here if you need it.
Contact
The primary contact for this project is @jackrobison.
Additional information and links
The documentation for the API can be found here.