The LBRY SDK for building decentralized, censorship resistant, monetized, digital content apps.
Find a file
2020-04-25 08:25:29 -04:00
.github/workflows postgres 2020-04-12 11:06:05 -04:00
docker prom port off by default 2020-01-27 13:55:44 -05:00
docs updated docs 2020-04-08 12:57:24 -04:00
icons moved lbry up one level 2020-01-01 15:57:56 -05:00
lbry cleaning up wallet directory, mostly moving things to blockchain 2020-04-25 08:25:29 -04:00
scripts parsing and inserting works 2020-04-08 19:03:01 -04:00
tests increase timeout for wallet server payment service 2020-04-12 16:14:18 -04:00
.gitignore reproduce issue with lbrycrd -reindex 2020-04-08 19:03:01 -04:00
.gitlab-ci.yml linux build of LBRY SDK for Ubuntu 16.05 Xenial 2020-02-12 14:20:06 -05:00
CHANGELOG.md changelog note 2019-12-28 12:39:46 -05:00
CONTRIBUTING.md Update CONTRIBUTING.md 2019-04-01 16:12:49 -04:00
example_daemon_settings.yml moved lbry up one level 2020-01-01 15:57:56 -05:00
INSTALL.md split integration tests into three jobs 2020-01-01 15:57:56 -05:00
lbry.png moved lbry up one level 2020-01-01 15:57:56 -05:00
LICENSE update year 2020-02-03 04:04:51 +07:00
Makefile updating scripts after moving lbry up one level 2020-01-01 15:57:56 -05:00
MANIFEST.in split integration tests into three jobs 2020-01-01 15:57:56 -05:00
README.md fix readme urls 2020-01-01 16:02:16 -05:00
setup.cfg pylint 2020-04-11 20:15:04 -04:00
setup.py setup.py 2020-04-12 09:26:59 -04:00
tox.ini postgresql support added 2020-04-11 17:27:41 -04:00

LBRY LBRY SDK Gitlab CI Badge

LBRY is a decentralized peer-to-peer protocol for publishing and accessing digital content. 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.

LBRY SDK for Python is currently the most fully featured implementation of the LBRY Network protocols and includes many useful components and tools for building decentralized applications. Primary features and components include:

  • Built on Python 3.7+ and asyncio.
  • Kademlia DHT (Distributed Hash Table) implementation for finding peers to download from and announcing to peers what we have to host (lbry.dht).
  • Blob exchange protocol for transferring encrypted blobs of content and negotiating payments (lbry.blob_exchange).
  • Protobuf schema for encoding and decoding metadata stored on the blockchain (lbry.schema).
  • Wallet implementation for the LBRY blockchain (lbry.wallet).
  • Daemon with a JSON-RPC API to ease building end user applications in any language and for automating various tasks (lbry.extras.daemon).

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.

With the daemon running, lbrynet commands will show you a list of commands.

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.com regarding any security issues. Our GPG key is here if you need it.

Contact

The primary contact for this project is @eukreign.

The documentation for the API can be found here.

Daemon defaults, ports, and other settings are documented here.

Settings can be configured using a daemon-settings.yml file. An example can be found here.