Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
Categories
Special pages
All pages
Search
Search
Appearance
Log in
Personal tools
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
LBRY
(section)
Page
Discussion
English
Read
Edit
Edit source
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
Edit source
View history
General
What links here
Related changes
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
= Downloading Files From the LBRY Blockchain = Downloading from LBRY goes two ways. Note that this is a technical dive on how downloading works -- if you just want a file, click the Download button on whatever interface you're using and forget about it. == Odysee == If you download via Odysee, you're downloading straight from them and not hitting the blockchain at all. They do still seed to people downloading via other means, but they make the whole process opaque to you. You're just grabbing it over HTTP. == Native LBRY Clients == Native LBRY clients follow a process that resembles something like a torrent: # Consult the blockchain for the SHA-384 hash of the file's <code>sd_hash</code> (stream descriptor hash), which contains metadata about the rest of the file # Consult the DHT (yes, the torrent DHT) for seeders that advertise the <code>sd_hash</code> we just acquired # Reach out to a selected peer to download the stream descriptor blob # Read the stream descriptor blob to see what blobs we need to acquire the file # Repeat 2-3 for every blob we need # Assemble the blobs into a file # (Optional) Advertise to the DHT that we have all the blobs for this file and seed them to the cluster The process of downloading blobs is parallelized by default. This method of acquiring data is as resilient to malice and tampering as the SHA-384 checksum. The address of every blob is ''also'' the mechanism by which you ensure it hasn't been corrupted in transit.
Summary:
Please note that all contributions to GunCAD Wiki are considered to be released under the Creative Commons Attribution-NonCommercial-ShareAlike (see
GunCAD Wiki:Copyrights
for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource.
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)
Search
Search
Editing
LBRY
(section)
Add topic