The LBRY SDK for building decentralized, censorship resistant, monetized, digital content apps.
Go to file
Antonio Quartulli d827b4d5af platform ip: ensure daemon retrieves IPv4 address only
When contacting jsonip.com to retrieve the node external IP,
the connection might be established with IPv6 and thus return
an address belonging to that family.

This address is then used to initialize the external_ip member of
Daemon session, but unfortunately IPv6 is not yet handled well.

Using an IPv6 as external IP is currently breaking parts of the
Daemon resulting in no peer connectivity at all.

We should stick to IPv4 for time being.

http://jsonip.com/about says "ipv4-only":"https://ipv4.jsonip.com"

therefore, change the IP retrieval URL to ipv4.jsonip.com to
make sure the connection is established only using an IPv4 address.

Closes: https://github.com/lbryio/lbry/issues/971
Signed-off-by: Antonio Quartulli <antonio@mandelbit.com>
2017-10-31 06:59:40 -04:00
.github add --version flag, remove simplejson dependency 2017-03-15 16:24:25 -04:00
build no datas 2017-08-09 19:10:11 -04:00
docs docs 2017-10-25 18:58:20 -04:00
lbrynet platform ip: ensure daemon retrieves IPv4 address only 2017-10-31 06:59:40 -04:00
scripts add routing_table_get 2017-10-11 12:54:40 -04:00
uri_handler remove packaging 2017-02-16 14:09:59 -06:00
.appveyor.yml updated appveyor build configuration 2017-09-29 12:02:36 +01:00
.bumpversion.cfg update bumpversion 2017-08-22 12:56:23 -04:00
.gitattributes use union merge on CHANGELOG.md 2017-02-20 21:37:50 -06:00
.gitignore build daemon separately in teamcity 2017-04-19 14:59:06 -04:00
.gitmodules remove submodule 2016-06-20 20:43:47 -05:00
.pylintrc pylint type checking 2017-04-25 14:36:14 -04:00
.travis.yml disable sourceclear again 2017-10-25 12:52:41 -04:00
app.icns update status bar app 2016-03-02 02:00:45 -05:00
CHANGELOG.md platform ip: ensure daemon retrieves IPv4 address only 2017-10-31 06:59:40 -04:00
CONTRIBUTING.md contributing 2017-09-28 08:14:36 -04:00
Dangerfile fix because the danger.systems code example was wrong 2017-02-07 23:08:35 -06:00
ez_setup.py initial commit 2015-08-20 11:27:15 -04:00
FAQ.md Update FAQ.md 2017-03-31 11:13:27 +08:00
INSTALL.md add raspbian instructions 2017-06-01 14:23:59 -04:00
LICENSE Update the year in the LICENSE 2017-10-11 19:54:56 -05:00
mkdocs.yml add cli docs 2017-06-09 12:14:03 -04:00
README.md readme edit 2017-09-18 13:03:34 -04:00
requirements.txt Bump version 0.17.1rc5 --> 0.17.1 2017-10-25 17:33:55 -04:00
setup.py Bump version 0.17.1rc5 --> 0.17.1 2017-10-25 17:33:55 -04:00

Build Status Coverage Status

LBRY

LBRY is an open-source protocol providing distribution, discovery, and purchase of digital content (data) via a decentralized network.

This repo is a reference implementation of the LBRY API.

It provides a daemon that can interact with the network via a json-rpc interface over HTTP.

Installing

Note: This project no longer bundles a graphic interface (browser). If you want to use LBRY via a GUI, use the LBRY App.

Our releases page contains pre-built binaries of the latest release, pre-releases, and past releases, for macOS, Debian-based Linux, and Windows.

Installing from source is also relatively painless, full instructions are in INSTALL.md

Running

Run lbrynet-daemon to launch the daemon.

Using

By default, lbrynet-daemon 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.

What is LBRY?

LBRY is a protocol that provides a fully decentralized network for the discovery, distribution, and payment of data.

It utilizes the LBRY blockchain as a global namespace and database of digital content. Blockchain entries contain searchable content metadata, identities, and rights and access rules.

LBRY also provides a data network 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.

Contributions

To contribute, join us on Slack or contact jeremy@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 jeremy@lbry.io.

License

See LICENSE