Compare commits

..
2 Commits
Author SHA1 Message Date
Codex a7698f9cac Remove obsolete Bittrex trading FAQ and exchange listing 2026-11-03 08:27:32 +07:00
Codex 1f1fadd49a Replace PHP website with static Hugo site 2026-11-03 08:20:01 +07:00
1421 changed files with 22631 additions and 20203 deletions

No files matched your search

+2 -11
View File
@@ -1,11 +1,2 @@
# Auto detect text files and perform LF normalization
* text=auto
*.php text diff=php
*.html text
*.css text
*.scss text
*.js text
*.sql text
*.svg -text
# Preserve static asset bytes without newline conversion.
static/** -text -whitespace
-12
View File
@@ -1,12 +0,0 @@
#### Issue Summary
A summary of the issue and the environment in which it occurs. If suitable, include the steps required to reproduce the bug. Please feel free to include screenshots, screencasts, code examples.
#### Steps to Reproduce
1. This is the first step
2. This is the second step
3. Further steps, etc.
Any other information you want to share that is relevant to the issue being reported. Especially, why do you consider this to be a bug? What do you expect to happen instead?
-11
View File
@@ -1,11 +0,0 @@
### Description
<!-- Please describe what the changes are made in this pull request and why the change was necessary. -->
<!--
Please enter each Issue number you are resolving in your PR after one of the following words [Fixes, Closes, Resolves]. This will auto-link these issues and close them when this PR is merged!
e.g.
Fixes #1
Closes #2
-->
### Fixes #
+3 -13
View File
@@ -1,14 +1,4 @@
.sass-cache
.idea
/data/config.php
/data/writeable/*
/web/css/*
/web/js/*.gz
/log
/web/zohoverify
nbproject
composer
.ht*
/vendor/
/public/
/resources/
/.hugo_build.lock
.DS_Store
.php_cs.cache
-3
View File
@@ -1,3 +0,0 @@
[submodule "web/scss/color"]
path = web/scss/color
url = https://github.com/lbryio/color
+484
View File
@@ -0,0 +1,484 @@
# Production site. Build with Hugo before starting Caddy.
{
admin off
auto_https disable_redirects
}
http://lbry.com {
redir https://lbry.com{uri} 301
}
https://lbry.com {
root * {$SITE_ROOT:./public}
route {
# Shared policies; assets cache longer, errors override caching below.
header {
Cache-Control "public, max-age=300"
Content-Security-Policy "frame-ancestors 'none'"
X-Frame-Options "DENY"
Strict-Transport-Security "max-age=31536000"
X-Content-Type-Options "nosniff"
}
@assets path_regexp assets `(?i)[.](?:css|js|png|jpe?g|gif|svg|ico|webp|woff2?|ttf|eot|pdf|zip|apk|exe|dmg|deb|appimage)$`
header @assets Cache-Control "public, max-age=14400"
@unsupported not method GET HEAD
handle @unsupported {
header Allow "GET, HEAD"
header Cache-Control "private, no-cache"
header Content-Type "text/html;charset=UTF-8"
method GET
rewrite * /405/index.html
file_server {
status 405
}
}
# Never expose internal files left in an old build directory.
@internal path_regexp internal `^/_[^/]*(?:/|$)`
handle @internal {
header Cache-Control "private, no-cache"
header Content-Type "text/html;charset=UTF-8"
rewrite * /404/index.html
file_server {
status 404
}
}
vars original_path {http.request.uri.path}
map {query} {query_suffix} {
"" ""
default "?{query}"
}
# One leading slash and no trailing slash, except for the root URL.
uri path_regexp /+ /
uri path_regexp ^(.+?)/+$ $1
# Exact files keep their spelling. Other paths try lowercase URLs.
@needs_lowercase {
path_regexp uppercase_path [A-Z]
not file {path}/index.html {path}
}
route @needs_lowercase {
uri path_regexp A a
uri path_regexp B b
uri path_regexp C c
uri path_regexp D d
uri path_regexp E e
uri path_regexp F f
uri path_regexp G g
uri path_regexp H h
uri path_regexp I i
uri path_regexp J j
uri path_regexp K k
uri path_regexp L l
uri path_regexp M m
uri path_regexp N n
uri path_regexp O o
uri path_regexp P p
uri path_regexp Q q
uri path_regexp R r
uri path_regexp S s
uri path_regexp T t
uri path_regexp U u
uri path_regexp V v
uri path_regexp W w
uri path_regexp X x
uri path_regexp Y y
uri path_regexp Z z
}
vars request_path {http.request.uri.path}
# Public shortlinks and exceptions. Article filename patterns follow below.
map {http.vars.request_path} {redirect_destination} {redirect_status} {
`~^(?:/3d\-contest|/lgbtq|/pewpewpew|/reefermadness|/rubin|/sexed|/shirt\-contest)$` "/" 301
"/3d-printing" "https://open.lbry.com/$/discover?t=3d-printing" 301
`~^(?:/flo|/there|/developer\-program|/news/every\-major\-tech\-company\-hates\-you|/news/lbry\-promo\-video\-raw\-footage|/news/lbry\.io|/news/page/2|/news/page/5|/news/www\.maidsafe\.com|/nothing\-here|/youtube/cdsso)$` "/news" 301
`~^(?:/about|/what\-is\-lbry)$` "/faq/what-is-lbry" 301
`~^(?:/android\-alpha|/dl/lbry_setup\.sh|/faq/why\-care\-about\-lbry|/get/lbry\.appimage|/get/lbry\.deb|/get/lbry\.dmg|/get/lbry\.exe|/get/lbry\.msi|/get/lbry\.pkg|/get/lbry\.pre\.appimage|/get/lbry\.pre\.deb|/get/lbry\.pre\.dmg|/get/lbry\.pre\.exe|/get/lbry\.pre\.msi|/get/lbry\.pre\.pkg|/get/lbrynet\.linux\.zip|/get/lbrynet\.macos\.zip|/get/lbrynet\.osx\.zip|/get/lbrynet\.windows\.zip|/getrubin|/lbry\-linux\-latest\.deb|/lbry\-osx\-latest\.dmg|/news/get|/releases/lbry\-desktop\.appimage|/releases/lbry\-desktop\.deb|/releases/lbry\-desktop\.dmg|/releases/lbry\-desktop\.exe|/releases/lbry\.deb|/releases/lbry\.exe|/releases/lbry\.pkg|/releases/pre/lbry\-desktop\.appimage|/releases/pre/lbry\-desktop\.deb|/releases/pre/lbry\-desktop\.dmg|/releases/pre/lbry\-desktop\.exe)$` "/get" 301
`~^(?:/art|/learn|/news/what)$` "/what" 301
`~^(?:/block\-explorer|/explorer)$` "https://explorer.lbry.com/" 301
`~^(?:/bounty|/faq/bounty|/faq/contributing|/participate)$` "https://lbry.tech/contribute" 301
`~^(?:/bounty/automatic\-app\-updates|/bounty/bittorrent\-support|/bounty/custom\-project|/bounty/http\-support|/bounty/lbry\-club|/bounty/migration\-public\-reference|/bounty/pr\-for\-lbry|/bounty/publish\-open\-content|/bounty/refer\-publisher|/bounty/typos\-and\-edits|/bounty/web\-i18n)$` "https://lbry.tech/contribute" 302
`~^(?:/chat|/discord|/slack)$` "https://chat.lbry.com" 301
`~^(?:/escapeyoutube|/escapeyoutubeiframe|/youtube/status)$` "/youtube" 301
`~^(?:/facebook|/lbryonfacebook)$` "https://www.facebook.com/LBRYcom/" 301
"/faq/q1-17-creditreport" "/credit-reports/2017-Q1" 301
"/faq/q4-credit-report" "/credit-reports/2016-Q4" 301
"/faq/account-sync" "/faq/accounts-and-sync" 301
`~^(?:/faq/account_sync|/faq/community\-top\-bid|/faq/shapeshift|/faq/unable\-to\-stream)$` "/faq" 302
"/faq/api-help" "/faq/how-to-cli" 301
"/faq/claimtrie-implementation" "https://lbry.tech/resources/lbry-claimtrie" 301
"/faq/gpg-key" "/faq/pgp-key" 301
"/faq/how-to-encrypt-wallet" "https://lbry.tech/resources/encrypt-lbrycrd" 301
"/faq/how-to-report-bugs" "/faq/support" 301
"/faq/make-money" "/faq/earn-income" 301
"/faq/no-auction-options" "/faq/naming" 301
"/faq/proof-algorithm" "https://lbry.tech/resources/pow" 301
"/faq/quarterly-report-3q-2016" "/credit-reports/2016-Q3" 301
"/faq/quarterly-report-july-2016" "/credit-reports/2016-Q2" 301
"/faq/referrals" "/faq/invites" 301
"/faq/regtest-setup-guide" "https://lbry.tech/resources/regtest-setup" 301
"/faq/tips" "/faq/appreciation" 301
"/faq/when-referral-payouts" "/faq/referrals" 301
"/feedback" "/learn" 301
"/get.how+to+create+an+identity+lbry+tutorialsfollow" "/faq/identity-requirements" 301
"/getfree" "/news/free-lbry-credits-come-and-get-em" 301
`~^(?:/join\-list|/list)$` "/list/subscribe" 301
"/joinus" "/join-us" 301
`~^(?:/lbryontwitter|/twitter)$` "https://twitter.com/lbrycom" 301
"/lbryonyoutube" "https://www.youtube.com/channel/UCXAcp3dJuPqeUekOacsuyaQ" 301
"/news/$1.2b-market-cap-we-dont-care" "/news/1.2b-market-cap-we-dont-care" 301
`~^(?:/news/040\-tipping\-in\-lbc|/news/040\-tipping\-in\-lbc\.md)$` "/news/tipping-in-lbc{query_suffix}" 301
`~^(?:/news/050\-1\.2b\-market\-cap\-we\-dont\-care|/news/050\-1\.2b\-market\-cap\-we\-dont\-care\.md)$` "/news/1.2b-market-cap-we-dont-care{query_suffix}" 301
`~^(?:/news/138\-always\-gif\-responsibly|/news/138\-always\-gif\-responsibly\.md)$` "/news/always-gif-responsibly{query_suffix}" 301
`~^(?:/news/139\-memesafe|/news/139\-memesafe\.md)$` "/news/memesafe{query_suffix}" 301
`~^(?:/news/144\-howl\-with\-us|/news/144\-howl\-with\-us\.md)$` "/news/howl-with-us{query_suffix}" 301
`~^(?:/news/153\-blockchain\-is\-love\-blockchain\-is\-life|/news/153\-blockchain\-is\-love\-blockchain\-is\-life\.md)$` "/news/blockchain-is-love-blockchain-is-life{query_suffix}" 301
`~^(?:/news/158\-lbry\-in\-2017\-2018|/news/158\-lbry\-in\-2017\-2018\.md)$` "/news/lbry-in-2017-2018{query_suffix}" 301
`~^(?:/news/159\-lbry\-development\-community\-update\-jan\-2018|/news/159\-lbry\-development\-community\-update\-jan\-2018\.md)$` "/news/lbry-development-community-update-jan-2018{query_suffix}" 301
`~^(?:/news/163\-lbry\-development\-community\-update\-feb\-2018|/news/163\-lbry\-development\-community\-update\-feb\-2018\.md)$` "/news/lbry-development-community-update-feb-2018{query_suffix}" 301
`~^(?:/news/165\-lbry\-development\-community\-update\-mar\-2018|/news/165\-lbry\-development\-community\-update\-mar\-2018\.md)$` "/news/lbry-development-community-update-mar-2018{query_suffix}" 301
`~^(?:/news/167\-lbry\-development\-community\-update\-apr\-2018|/news/167\-lbry\-development\-community\-update\-apr\-2018\.md)$` "/news/lbry-development-community-update-apr-2018{query_suffix}" 301
`~^(?:/news/172\-lbry\-development\-community\-update\-may\-2018|/news/172\-lbry\-development\-community\-update\-may\-2018\.md)$` "/news/lbry-development-community-update-may-2018{query_suffix}" 301
`~^(?:/news/176\-lbry\-development\-community\-update\-june\-2018|/news/176\-lbry\-development\-community\-update\-june\-2018\.md)$` "/news/lbry-development-community-update-june-2018{query_suffix}" 301
`~^(?:/news/181\-the\-lbry\-economy|/news/181\-the\-lbry\-economy\.md)$` "/news/the-lbry-economy{query_suffix}" 301
`~^(?:/news/188\-3\-rules\-to\-find\-the\-best\-youtube\-alternative|/news/188\-3\-rules\-to\-find\-the\-best\-youtube\-alternative\.md)$` "/news/3-rules-to-find-the-best-youtube-alternative{query_suffix}" 301
`~^(?:/news/206\-lbry\-evolves|/news/206\-lbry\-evolves\.md)$` "/news/lbry-evolves{query_suffix}" 301
`~^(?:/news/210\-malabarize\-se|/news/210\-malabarize\-se\.md)$` "/news/malabarize-se{query_suffix}" 301
`~^(?:/news/213\-erikson\-sets\-sail|/news/213\-erikson\-sets\-sail\.md)$` "/news/erikson-sets-sail{query_suffix}" 301
`~^(?:/news/217\-franklin\-is\-minted|/news/217\-franklin\-is\-minted\.md)$` "/news/franklin-is-minted{query_suffix}" 301
`~^(?:/news/218\-lbry\-blockchain\-update|/news/218\-lbry\-blockchain\-update\.md)$` "/news/lbry-blockchain-update{query_suffix}" 301
`~^(?:/news/219\-what\-is\-censorship\-resistance\-and\-why\-does\-it\-matter|/news/219\-what\-is\-censorship\-resistance\-and\-why\-does\-it\-matter\.md)$` "/news/what-is-censorship-resistance-and-why-does-it-matter{query_suffix}" 301
`~^(?:/news/220\-butterfly\-flits\-onto\-the\-scene|/news/220\-butterfly\-flits\-onto\-the\-scene\.md)$` "/news/butterfly-flits-onto-the-scene{query_suffix}" 301
`~^(?:/news/255\-2002dtf|/news/255\-2002dtf\.md)$` "/news/2002dtf{query_suffix}" 301
`~^(?:/news/author/jeremy|/news/author/jeremy/2|/news/author/jimmy\-kiselak|/news/author/sam/page/2|/news/author/sam/page/3|/news/author/samuel|/news/meet\-the\-lbry\-founders|/news/tag/team|/news/team)$` "/team" 301
"/news/boom" "/news/boombust" 301
"/news/hacktoberfest" "/hacktoberfest" 301
"/news/ios" "/ios" 301
"/news/news/lbry-app-sneak-peak-big-questions-answered-lbry-on-blocktalk-last-night" "/news/lbry-app-sneak-peak-big-questions-answered-lbry-on-blocktalk-last-night" 301
"/news/news/meet-the-lbry-founders" "/news/meet-the-lbry-founders" 301
"/news/news/ultimate-wizard-meet-alex-grin" "/news/ultimate-wizard-meet-alex-grin" 301
"/news/tag/events" "/roadmap" 301
"/news/tag/freedom-of-information" "/news/crypto-freedom" 301
"/news/windows" "/news/lbry-windows" 301
"/news/www.porcfest.com" "/news/lbry-at-porcfest-first-public-screening-film-via-blockchain" 301
"/odysee" "https://odysee.com/" 301
"/press-kit.zip" "/press-kit" 301
"/privacy" "/privacypolicy" 301
"/publish" "https://odysee.com/$/publish" 301
"/quickstart" "https://lbry.tech/playground" 301
`~^(?:/reddit|/subreddit)$` "https://www.reddit.com/r/lbry/" 301
"/releases/lbry-android.apk" "https://github.com/lbryio/lbry-android/releases/download/0.17.1/browser-0.17.1-release__arm.apk" 302
"/roadmap/1900" "/roadmap" 302
"/shop" "https://shop.lbry.com/" 301
"/speech-admin" "https://github.com/lbryio/spee.ch" 301
"/telegram" "https://t.me/lbryofficial" 301
"/youtube/sync" "/faq/youtube" 301
"/2019goalsreportcard" "https://docs.google.com/spreadsheets/d/1SrHI53hBQnz4Lc7_hKb-rHSH9XiGE6ROATVf8Z-ygKo/edit" 307
`~^(?:/lbry\-deck\.pdf|/deck\.pdf)$` "https://www.dropbox.com/s/0xj4vgucsbi8rtv/lbry-deck.pdf?dl=1" 307
`~^(?:/api|/api\-help)$` "https://lbry.tech/api/sdk" 307
"/doitlive" "https://meet.jit.si/lbry" 307
"/hacktoberfest" "/news/hacktoberfest-2019" 307
"/security" "/faq/security" 307
"/support" "/faq/support" 307
"/swarm" "https://docs.google.com/document/d/1W4chXeUvF4I9T3lVyyeZ-N1SUuyoMrp_QH_ITA9BrZ4/edit#" 307
"/web3july2019" "https://docs.google.com/presentation/d/1oep9pXAT0unYw8EKiPsUSdsQ3DajOxsyGMjwljq43cY/edit" 307
"/youtubecryptocrackdown" "https://docs.google.com/spreadsheets/d/1xGOSn60BW-aqheHEr-5iye8fw5PmgKoOcE1pA20Bpys" 307
"/youtubers" "https://traction.lbry.com/public/question/8dfc23e2-71e7-44cb-9740-0aec18d1da73" 307
`~^(?:/credit\-reports/1900\-q1|/credit\-reports/999\-2017\-q1)$` "/credit-reports" 302
"/credit-reports/999-2017-q1.md" "/credit-reports/2017-q1{query_suffix}" 301
"/news/999-20-01comm.md" "/news/20-01comm{query_suffix}" 301
default "" 301
}
# Never redirect a path to itself, including same-origin absolute URLs.
@public_redirect expression `{redirect_destination} != "" && {redirect_destination} != {http.vars.request_path} && {redirect_destination} != {http.vars.request_path} + {query_suffix} && {redirect_destination} != "https://lbry.com" + {http.vars.request_path} && {redirect_destination} != "https://lbry.com" + {http.vars.request_path} + {query_suffix}`
redir @public_redirect {redirect_destination} {redirect_status}
# Recognized numbered stems, then the generic .md filename alias rule.
map {http.vars.request_path} {article_redirect_target} {
`~^/news/001\-the\-lbry\-opens(?:[.]md)?$` "/news/the-lbry-opens"
`~^/news/002\-as\-reddit\-burns\-it\-powers\-the\-world(?:[.]md)?$` "/news/as-reddit-burns-it-powers-the-world"
`~^/news/003\-5\-questions\-about\-lbry(?:[.]md)?$` "/news/5-questions-about-lbry"
`~^/news/009\-introducing\-lbry\-the\-bitcoin\-of\-content(?:[.]md)?$` "/news/introducing-lbry-the-bitcoin-of-content"
`~^/news/010\-slides\-from\-media\-demo(?:[.]md)?$` "/news/slides-from-media-demo"
`~^/news/011\-testimony\-to\-subcommittee\-on\-hb552\-to\-legalize\-bitcoin\-for\-payments\-of\-taxes\-and\-fees(?:[.]md)?$` "/news/testimony-to-subcommittee-on-hb552-to-legalize-bitcoin-for-payments-of-taxes-and-fees"
`~^/news/012\-why\-not\-use\-bitcoin\-a\-dialogue(?:[.]md)?$` "/news/why-not-use-bitcoin-a-dialogue"
`~^/news/013\-mike\-vine\-joins\-lbry\-as\-technology\-evangelist\-2(?:[.]md)?$` "/news/mike-vine-joins-lbry-as-technology-evangelist-2"
`~^/news/014\-lbry\-gets\-content\-creators\-out\-of\-precarious\-position\-daily\-decrypts\-amanda\-b\-johnson(?:[.]md)?$` "/news/lbry-gets-content-creators-out-of-precarious-position-daily-decrypts-amanda-b-johnson"
`~^/news/015\-renowned\-ip\-attorney\-kinsella\-joins\-lbry\-cryptoapp\-as\-legal\-advisor(?:[.]md)?$` "/news/renowned-ip-attorney-kinsella-joins-lbry-cryptoapp-as-legal-advisor"
`~^/news/016\-digging\-into\-lbry(?:[.]md)?$` "/news/digging-into-lbry"
`~^/news/017\-rpi\-hackers\-meet\-lbry\-rcos\-presentation(?:[.]md)?$` "/news/rpi-hackers-meet-lbry-rcos-presentation"
`~^/news/018\-its\-time\-to\-liberate\-anne\-franks\-diary(?:[.]md)?$` "/news/its-time-to-liberate-anne-franks-diary"
`~^/news/019\-free\-lbry\-credits\-come\-and\-get\-em(?:[.]md)?$` "/news/free-lbry-credits-come-and-get-em"
`~^/news/020\-open\-a\-valve\-to\-gush\-classic\-movies(?:[.]md)?$` "/news/open-a-valve-to-gush-classic-movies"
`~^/news/021\-gmu\-economist\-alex\-tabarrok\-joins\-lbry(?:[.]md)?$` "/news/gmu-economist-alex-tabarrok-joins-lbry"
`~^/news/022\-building\-the\-web\-3\-0\-decentralizing\-content\-in\-an\-age\-of\-centralization(?:[.]md)?$` "/news/building-the-web-3-0-decentralizing-content-in-an-age-of-centralization"
`~^/news/023\-bravenewcoin(?:[.]md)?$` "/news/bravenewcoin"
`~^/news/024\-our\-christmas\-surprise(?:[.]md)?$` "/news/our-christmas-surprise"
`~^/news/025\-huemer\-joins\-lbry\-ethical\-advisor(?:[.]md)?$` "/news/huemer-joins-lbry-ethical-advisor"
`~^/news/026\-jack\-robison\-escaped\-60\-years\-in\-prison\-now\-hes\-revolutionizing\-the\-internet(?:[.]md)?$` "/news/jack-robison-escaped-60-years-in-prison-now-hes-revolutionizing-the-internet"
`~^/news/027\-lbry\-adds\-chief\-growth\-officer\-josh\-finer(?:[.]md)?$` "/news/lbry-adds-chief-growth-officer-josh-finer"
`~^/news/028\-the\-dmcas\-chilling\-effect\-on\-security\-research\-and\-innovation(?:[.]md)?$` "/news/the-dmcas-chilling-effect-on-security-research-and-innovation"
`~^/news/029\-lbry\-app\-sneak\-peak\-big\-questions\-answered\-lbry\-on\-blocktalk\-last\-night(?:[.]md)?$` "/news/lbry-app-sneak-peak-big-questions-answered-lbry-on-blocktalk-last-night"
`~^/news/030\-try\-lbry\-on\-os\-x\-el\-capitan(?:[.]md)?$` "/news/try-lbry-on-os-x-el-capitan"
`~^/news/031\-annefrank2(?:[.]md)?$` "/news/annefrank2"
`~^/news/032\-if\-lbry\-succeeds\-humanity\-wins\-lbry\-ceo\-on\-lions\-of\-liberty\-podcast(?:[.]md)?$` "/news/if-lbry-succeeds-humanity-wins-lbry-ceo-on-lions-of-liberty-podcast"
`~^/news/033\-zarghamjoins(?:[.]md)?$` "/news/zarghamjoins"
`~^/news/035\-why\-doesnt\-lbry\-just\-use\-bitcoin(?:[.]md)?$` "/news/why-doesnt-lbry-just-use-bitcoin"
`~^/news/036\-built\-for\-artists\-by\-autists\-lbry\-takes\-autism\-personally(?:[.]md)?$` "/news/built-for-artists-by-autists-lbry-takes-autism-personally"
`~^/news/038\-information\-gatekeepers\-make\-our\-culture\-sick(?:[.]md)?$` "/news/information-gatekeepers-make-our-culture-sick"
`~^/news/039\-bandcamp\-cool\-growing\-but\-still\-take\-15\-percent(?:[.]md)?$` "/news/bandcamp-cool-growing-but-still-take-15-percent"
`~^/news/041\-apple\-lost\-my\-music(?:[.]md)?$` "/news/apple-lost-my-music"
`~^/news/042\-bittorrents\-new\-streaming\-service(?:[.]md)?$` "/news/bittorrents-new-streaming-service"
`~^/news/043\-ultimate\-wizard\-meet\-alex\-grin(?:[.]md)?$` "/news/ultimate-wizard-meet-alex-grin"
`~^/news/044\-meet\-reilly\-smith\-storyteller(?:[.]md)?$` "/news/meet-reilly-smith-storyteller"
`~^/news/045\-lbry\-blockchain\-live\-mine\-lbc\-now(?:[.]md)?$` "/news/lbry-blockchain-live-mine-lbc-now"
`~^/news/046\-lbry\-at\-porcfest\-first\-public\-screening\-film\-via\-blockchain(?:[.]md)?$` "/news/lbry-at-porcfest-first-public-screening-film-via-blockchain"
`~^/news/047\-beta\-live\-declare\-independence\-big\-media(?:[.]md)?$` "/news/beta-live-declare-independence-big-media"
`~^/news/048\-lbry\-credits\-on\-bittrex(?:[.]md)?$` "/news/lbry-credits-on-bittrex"
`~^/news/049\-mysterious\-100k\-lbc\-revealed(?:[.]md)?$` "/news/mysterious-100k-lbc-revealed"
`~^/news/051\-launch\-a\-disaster(?:[.]md)?$` "/news/launch-a-disaster"
`~^/news/052\-day\-in\-shoes\-venezuelan(?:[.]md)?$` "/news/day-in-shoes-venezuelan"
`~^/news/053\-publish\-tools\-live\-earn\-1000\-dollars(?:[.]md)?$` "/news/publish-tools-live-earn-1000-dollars"
`~^/news/054\-shapeshift\-adds\-lbc(?:[.]md)?$` "/news/shapeshift-adds-lbc"
`~^/news/055\-fight\-of\-century(?:[.]md)?$` "/news/fight-of-century"
`~^/news/056\-mde\-on\-lbry(?:[.]md)?$` "/news/mde-on-lbry"
`~^/news/057\-lbry\-bounties(?:[.]md)?$` "/news/lbry-bounties"
`~^/news/058\-reweighting\-wait\-list(?:[.]md)?$` "/news/reweighting-wait-list"
`~^/news/059\-ui\-publishing\-tools\-upgrades(?:[.]md)?$` "/news/ui-publishing-tools-upgrades"
`~^/news/060\-heckbender\-charney\-on\-lbry(?:[.]md)?$` "/news/heckbender-charney-on-lbry"
`~^/news/061\-nsfw\-lbry\-settings(?:[.]md)?$` "/news/nsfw-lbry-settings"
`~^/news/062\-content\-without\-borders(?:[.]md)?$` "/news/content-without-borders"
`~^/news/063\-joaquin\-pixan\-singleton\-band(?:[.]md)?$` "/news/joaquin-pixan-singleton-band"
`~^/news/064\-500k\-vc\-funds\-pillar(?:[.]md)?$` "/news/500k-vc-funds-pillar"
`~^/news/065\-animal\-robot\-on\-lbry(?:[.]md)?$` "/news/animal-robot-on-lbry"
`~^/news/066\-brookes\-eggleston\-character\-design\-forge(?:[.]md)?$` "/news/brookes-eggleston-character-design-forge"
`~^/news/067\-ray\-carballada\-media\-advisor(?:[.]md)?$` "/news/ray-carballada-media-advisor"
`~^/news/068\-skate\-yrself\-clean(?:[.]md)?$` "/news/skate-yrself-clean"
`~^/news/069\-reddit\-ama\-answers(?:[.]md)?$` "/news/reddit-ama-answers"
`~^/news/070\-fleischer\-superman(?:[.]md)?$` "/news/fleischer-superman"
`~^/news/071\-credit\-policy\-third\-quarter\-report(?:[.]md)?$` "/news/credit-policy-third-quarter-report"
`~^/news/072\-sporthocking(?:[.]md)?$` "/news/sporthocking"
`~^/news/073\-alex\-liebowitz(?:[.]md)?$` "/news/alex-liebowitz"
`~^/news/073\-what\-makes\-lbry\-different(?:[.]md)?$` "/news/what-makes-lbry-different"
`~^/news/074\-lbry\-trailblazers(?:[.]md)?$` "/news/lbry-trailblazers"
`~^/news/075\-roadmap(?:[.]md)?$` "/news/roadmap"
`~^/news/076\-night\-living\-dead(?:[.]md)?$` "/news/night-living-dead"
`~^/news/077\-lbry\-windows(?:[.]md)?$` "/news/lbry-windows"
`~^/news/078\-bellflower\-movie(?:[.]md)?$` "/news/bellflower-movie"
`~^/news/079\-singletree(?:[.]md)?$` "/news/singletree"
`~^/news/080\-tpbafk(?:[.]md)?$` "/news/tpbafk"
`~^/news/081\-acryptypical(?:[.]md)?$` "/news/acryptypical"
`~^/news/082\-coherence(?:[.]md)?$` "/news/coherence"
`~^/news/083\-adult\-swim\-cancels\-show\-for\-supporting\-trump(?:[.]md)?$` "/news/adult-swim-cancels-show-for-supporting-trump"
`~^/news/083\-listenup(?:[.]md)?$` "/news/listenup"
`~^/news/084\-jinglebells(?:[.]md)?$` "/news/jinglebells"
`~^/news/085\-freedomfm(?:[.]md)?$` "/news/freedomfm"
`~^/news/086\-rare\-exports(?:[.]md)?$` "/news/rare-exports"
`~^/news/087\-positive\-returns(?:[.]md)?$` "/news/positive-returns"
`~^/news/088\-cryptoverse(?:[.]md)?$` "/news/cryptoverse"
`~^/news/089\-steal\-this(?:[.]md)?$` "/news/steal-this"
`~^/news/090\-sundance2017(?:[.]md)?$` "/news/sundance2017"
`~^/news/091\-new\-hampshire\-statehouse\-testimony\-on\-virtual\-currencies(?:[.]md)?$` "/news/new-hampshire-statehouse-testimony-on-virtual-currencies"
`~^/news/092\-mike\-hill(?:[.]md)?$` "/news/mike-hill"
`~^/news/093\-1791l(?:[.]md)?$` "/news/1791l"
`~^/news/094\-crypt0(?:[.]md)?$` "/news/crypt0"
`~^/news/095\-gutenberg(?:[.]md)?$` "/news/gutenberg"
`~^/news/096\-timcast(?:[.]md)?$` "/news/timcast"
`~^/news/097\-ohgeegeo(?:[.]md)?$` "/news/ohgeegeo"
`~^/news/098\-crypto\-freedom(?:[.]md)?$` "/news/crypto-freedom"
`~^/news/099\-censored\-gaming(?:[.]md)?$` "/news/censored-gaming"
`~^/news/100\-20000\-illegal\-college\-lectures\-rescued(?:[.]md)?$` "/news/20000-illegal-college-lectures-rescued"
`~^/news/101\-airsoft(?:[.]md)?$` "/news/airsoft"
`~^/news/102\-montage(?:[.]md)?$` "/news/montage"
`~^/news/103\-great\-week\-for\-lbry\-developer\-beta(?:[.]md)?$` "/news/great-week-for-lbry-developer-beta"
`~^/news/104\-blesshay(?:[.]md)?$` "/news/blesshay"
`~^/news/105\-auto\-diy(?:[.]md)?$` "/news/auto-diy"
`~^/news/106\-matt\-sokol(?:[.]md)?$` "/news/matt-sokol"
`~^/news/107\-whoiscapital(?:[.]md)?$` "/news/whoiscapital"
`~^/news/108\-mayer\-makes(?:[.]md)?$` "/news/mayer-makes"
`~^/news/109\-growing\-green(?:[.]md)?$` "/news/growing-green"
`~^/news/110\-julia\-galef(?:[.]md)?$` "/news/julia-galef"
`~^/news/111\-kokesh(?:[.]md)?$` "/news/kokesh"
`~^/news/112\-epicenter(?:[.]md)?$` "/news/epicenter"
`~^/news/113\-trailers(?:[.]md)?$` "/news/trailers"
`~^/news/114\-coinomiwallet(?:[.]md)?$` "/news/coinomiwallet"
`~^/news/115\-juicemedia(?:[.]md)?$` "/news/juicemedia"
`~^/news/116\-acousticlabs(?:[.]md)?$` "/news/acousticlabs"
`~^/news/117\-jordanbpeterson(?:[.]md)?$` "/news/jordanbpeterson"
`~^/news/118\-lukehall(?:[.]md)?$` "/news/lukehall"
`~^/news/119\-fee(?:[.]md)?$` "/news/fee"
`~^/news/120\-slav(?:[.]md)?$` "/news/slav"
`~^/news/121\-makestuff(?:[.]md)?$` "/news/makestuff"
`~^/news/122\-jaylight(?:[.]md)?$` "/news/jaylight"
`~^/news/123\-popup\-open\-beta(?:[.]md)?$` "/news/popup-open-beta"
`~^/news/124\-rocketsaway(?:[.]md)?$` "/news/rocketsaway"
`~^/news/125\-rerez(?:[.]md)?$` "/news/rerez"
`~^/news/126\-casuallyexplained(?:[.]md)?$` "/news/casuallyexplained"
`~^/news/127\-lunduke(?:[.]md)?$` "/news/lunduke"
`~^/news/129\-lbry\-release\-first\-run\-wallet\-invites\-rewards(?:[.]md)?$` "/news/lbry-release-first-run-wallet-invites-rewards"
`~^/news/130\-new\-lbry\-version\-with\-tipping(?:[.]md)?$` "/news/new-lbry-version-with-tipping"
`~^/news/131\-eevblog(?:[.]md)?$` "/news/eevblog"
`~^/news/132\-nurdrage(?:[.]md)?$` "/news/nurdrage"
`~^/news/133\-minutephysics(?:[.]md)?$` "/news/minutephysics"
`~^/news/134\-new\-lbry\-version\-with\-search(?:[.]md)?$` "/news/new-lbry-version-with-search"
`~^/news/135\-kaze(?:[.]md)?$` "/news/kaze"
`~^/news/136\-johncleese(?:[.]md)?$` "/news/johncleese"
`~^/news/137\-nilered(?:[.]md)?$` "/news/nilered"
`~^/news/140\-3blue1brown(?:[.]md)?$` "/news/3blue1brown"
`~^/news/141\-lbry\-is\-trending(?:[.]md)?$` "/news/lbry-is-trending"
`~^/news/142\-unbubbled(?:[.]md)?$` "/news/unbubbled"
`~^/news/143\-nono(?:[.]md)?$` "/news/nono"
`~^/news/145\-chronos(?:[.]md)?$` "/news/chronos"
`~^/news/146\-a\-very\-special\-holiday\-special(?:[.]md)?$` "/news/a-very-special-holiday-special"
`~^/news/147\-lbry\-shifting\-into\-high\-gear(?:[.]md)?$` "/news/lbry-shifting-into-high-gear"
`~^/news/148\-lbry\-development\-community\-update\-1(?:[.]md)?$` "/news/lbry-development-community-update-1"
`~^/news/149\-stop\-net\-banality(?:[.]md)?$` "/news/stop-net-banality"
`~^/news/150\-rubin\-youtubeweek(?:[.]md)?$` "/news/rubin-youtubeweek"
`~^/news/151\-boombust(?:[.]md)?$` "/news/boombust"
`~^/news/152\-why\-do\-tech\-giants\-abuse\-their\-users(?:[.]md)?$` "/news/why-do-tech-giants-abuse-their-users"
`~^/news/154\-how\-ads\-wrecked\-entertainment(?:[.]md)?$` "/news/how-ads-wrecked-entertainment"
`~^/news/155\-the\-birth\-of\-entertainment(?:[.]md)?$` "/news/the-birth-of-entertainment"
`~^/news/156\-sidequest(?:[.]md)?$` "/news/sidequest"
`~^/news/157\-verified\-awesome(?:[.]md)?$` "/news/verified-awesome"
`~^/news/160\-srodalmenara(?:[.]md)?$` "/news/srodalmenara"
`~^/news/161\-nickatnyte(?:[.]md)?$` "/news/nickatnyte"
`~^/news/162\-colinslaststand(?:[.]md)?$` "/news/colinslaststand"
`~^/news/164\-if\-you\-still\-havent\-found\-what\-youre\-searching\-for(?:[.]md)?$` "/news/if-you-still-havent-found-what-youre-searching-for"
`~^/news/166\-imineblocks(?:[.]md)?$` "/news/imineblocks"
`~^/news/168\-we\-are\-hiring\-our\-boss(?:[.]md)?$` "/news/we-are-hiring-our-boss"
`~^/news/169\-what\-is\-chainquery(?:[.]md)?$` "/news/what-is-chainquery"
`~^/news/170\-forking\-for\-asic\-resistance(?:[.]md)?$` "/news/forking-for-asic-resistance"
`~^/news/171\-hf1807(?:[.]md)?$` "/news/hf1807"
`~^/news/173\-lbry\-fund\-launches(?:[.]md)?$` "/news/lbry-fund-launches"
`~^/news/174\-lbry\-desktop\-redesign(?:[.]md)?$` "/news/lbry-desktop-redesign"
`~^/news/175\-austen(?:[.]md)?$` "/news/austen"
`~^/news/177\-app\-release\-023(?:[.]md)?$` "/news/app-release-023"
`~^/news/178\-lbry\-development\-community\-update\-july\-2018(?:[.]md)?$` "/news/lbry-development-community-update-july-2018"
`~^/news/179\-is\-everything\-better\-on\-the\-blockchain(?:[.]md)?$` "/news/is-everything-better-on-the-blockchain"
`~^/news/180\-something\-wicked\-cool\-this\-way\-comes(?:[.]md)?$` "/news/something-wicked-cool-this-way-comes"
`~^/news/181\-lbry\-is\-not\-an\-app(?:[.]md)?$` "/news/lbry-is-not-an-app"
`~^/news/182\-why\-is\-lbry\-android\-only(?:[.]md)?$` "/news/why-is-lbry-android-only"
`~^/news/183\-lbry\-in\-your\-pocket(?:[.]md)?$` "/news/lbry-in-your-pocket"
`~^/news/185\-august\-community\-update(?:[.]md)?$` "/news/august-community-update"
`~^/news/186\-hacktoberfest\-2018(?:[.]md)?$` "/news/hacktoberfest-2018"
`~^/news/187\-sept\-dev\-update(?:[.]md)?$` "/news/sept-dev-update"
`~^/news/189\-to\-hacktoberfest\-and\-beyond(?:[.]md)?$` "/news/to-hacktoberfest-and-beyond"
`~^/news/190\-october\-community\-update(?:[.]md)?$` "/news/october-community-update"
`~^/news/191\-anti\-media(?:[.]md)?$` "/news/anti-media"
`~^/news/192\-what\-to\-look\-for\-in\-a\-spotify\-alternative(?:[.]md)?$` "/news/what-to-look-for-in-a-spotify-alternative"
`~^/news/193\-c\-is\-for\-clarke(?:[.]md)?$` "/news/c-is-for-clarke"
`~^/news/194\-the\-calm(?:[.]md)?$` "/news/the-calm"
`~^/news/195\-nov\-dec\-update(?:[.]md)?$` "/news/nov-dec-update"
`~^/news/196\-thingiverse(?:[.]md)?$` "/news/thingiverse"
`~^/news/197\-the\-revolt(?:[.]md)?$` "/news/the-revolt"
`~^/news/198\-lbry\-is\-turning\-27(?:[.]md)?$` "/news/lbry-is-turning-27"
`~^/news/199\-one\-million\-installs(?:[.]md)?$` "/news/one-million-installs"
`~^/news/200\-our\-android\-is\-getting\-smarter(?:[.]md)?$` "/news/our-android-is-getting-smarter"
`~^/news/201\-bring\-a\-friend\-to\-lbry(?:[.]md)?$` "/news/bring-a-friend-to-lbry"
`~^/news/202\-lbry\-in\-2018\-2019(?:[.]md)?$` "/news/lbry-in-2018-2019"
`~^/news/203\-jan\-community(?:[.]md)?$` "/news/jan-community"
`~^/news/204\-hf1903(?:[.]md)?$` "/news/hf1903"
`~^/news/205\-lbrytech(?:[.]md)?$` "/news/lbrytech"
`~^/news/207\-feb\-19\-update(?:[.]md)?$` "/news/feb-19-update"
`~^/news/208\-claim\-trie\-memory\-reduction(?:[.]md)?$` "/news/claim-trie-memory-reduction"
`~^/news/209\-binance(?:[.]md)?$` "/news/binance"
`~^/news/211\-32\-skidoo(?:[.]md)?$` "/news/32-skidoo"
`~^/news/212\-comm\-update(?:[.]md)?$` "/news/comm-update"
`~^/news/214\-jun\-july\-dev(?:[.]md)?$` "/news/jun-july-dev"
`~^/news/215\-aug\-comm\-update(?:[.]md)?$` "/news/aug-comm-update"
`~^/news/216\-launch\-into\-andromeda(?:[.]md)?$` "/news/launch-into-andromeda"
`~^/news/219\-aug\-dev(?:[.]md)?$` "/news/aug-dev"
`~^/news/221\-comm\-report\-2019\-09(?:[.]md)?$` "/news/comm-report-2019-09"
`~^/news/222\-hacktoberfest\-2019(?:[.]md)?$` "/news/hacktoberfest-2019"
`~^/news/223\-hf1910(?:[.]md)?$` "/news/hf1910"
`~^/news/224\-galileo(?:[.]md)?$` "/news/galileo"
`~^/news/225\-swarm\-intro(?:[.]md)?$` "/news/swarm-intro"
`~^/news/226\-sept\-dev\-2019(?:[.]md)?$` "/news/sept-dev-2019"
`~^/news/227\-lbrycast\-kaccreatve(?:[.]md)?$` "/news/lbrycast-kaccreatve"
`~^/news/228\-unification(?:[.]md)?$` "/news/unification"
`~^/news/229\-lbrycast\-richardharris(?:[.]md)?$` "/news/lbrycast-richardharris"
`~^/news/230\-comm\-2019\-10(?:[.]md)?$` "/news/comm-2019-10"
`~^/news/231\-darknesscast(?:[.]md)?$` "/news/darknesscast"
`~^/news/232\-doppler(?:[.]md)?$` "/news/doppler"
`~^/news/233\-lbrycast\-linuxscoop(?:[.]md)?$` "/news/lbrycast-linuxscoop"
`~^/news/234\-2019\-hacktober(?:[.]md)?$` "/news/2019-hacktober"
`~^/news/235\-dev\-oct19(?:[.]md)?$` "/news/dev-oct19"
`~^/news/236\-moreno(?:[.]md)?$` "/news/moreno"
`~^/news/237\-eljefedave(?:[.]md)?$` "/news/eljefedave"
`~^/news/238\-dadreviews(?:[.]md)?$` "/news/dadreviews"
`~^/news/239\-cryptotips(?:[.]md)?$` "/news/cryptotips"
`~^/news/240\-comm\-2019\-11(?:[.]md)?$` "/news/comm-2019-11"
`~^/news/240\-eclipse(?:[.]md)?$` "/news/eclipse"
`~^/news/241\-scammerrevolts(?:[.]md)?$` "/news/scammerrevolts"
`~^/news/242\-benjaminboyce(?:[.]md)?$` "/news/benjaminboyce"
`~^/news/243\-creator\-rewards(?:[.]md)?$` "/news/creator-rewards"
`~^/news/243\-youtubecryptocrackdown(?:[.]md)?$` "/news/youtubecryptocrackdown"
`~^/news/244\-isaac(?:[.]md)?$` "/news/isaac"
`~^/news/245\-redactedtonight(?:[.]md)?$` "/news/redactedtonight"
`~^/news/246\-nov\-dec\-dev\-2019(?:[.]md)?$` "/news/nov-dec-dev-2019"
`~^/news/247\-fireworks(?:[.]md)?$` "/news/fireworks"
`~^/news/248\-naomiwu(?:[.]md)?$` "/news/naomiwu"
`~^/news/249\-stossel(?:[.]md)?$` "/news/stossel"
`~^/news/250\-joule(?:[.]md)?$` "/news/joule"
`~^/news/251\-wearechange(?:[.]md)?$` "/news/wearechange"
`~^/news/252\-0130quartering(?:[.]md)?$` "/news/0130quartering"
`~^/news/252\-20\-01comm(?:[.]md)?$` "/news/20-01comm"
`~^/news/253\-lbrytv(?:[.]md)?$` "/news/lbrytv"
`~^/news/254\-android\-galaxy(?:[.]md)?$` "/news/android-galaxy"
`~^/news/256\-kelvin(?:[.]md)?$` "/news/kelvin"
`~^/news/257\-lbry\-in\-2019\-2020(?:[.]md)?$` "/news/lbry-in-2019-2020"
`~^/news/258\-dev\-feb20(?:[.]md)?$` "/news/dev-feb20"
`~^/(news|faq|credit-reports)/(.+)[.]md$` "/${1}/${2}"
default ""
}
@article_alias {
expression `{article_redirect_target} != "" && {article_redirect_target} != {http.vars.request_path}`
file {article_redirect_target}/index.html
}
redir @article_alias {article_redirect_target}{query_suffix} 301
@downloads path_regexp downloads `^/(?:releases/(?:pre/)?[^/]+[.][^/]+|get/.+)$`
redir @downloads /get 301
@bounty path_regexp bounty `^/bounty/.*$`
redir @bounty https://lbry.tech/contribute 302
@roadmap path_regexp roadmap `^/roadmap/.*$`
redir @roadmap /roadmap 302
# Retained static replacements for former dynamic URL families.
@list_action path_regexp list_action `^/list/(?:confirm|edit|unsubscribe)/[^/]+$`
rewrite @list_action /list/subscribe
@dmca_action path_regexp dmca_action `^/dmca/[^/]+$`
rewrite @dmca_action /dmca
@youtube_status path_regexp youtube_status `^/youtube/status/[^/]+$`
rewrite @youtube_status /youtube/status/migration-public-reference
@news_category path_regexp news_category `^/news/category/[^/]+$`
rewrite @news_category /news/category/migration-public-reference
@page_or_asset file {path}/index.html {path}
handle @page_or_asset {
# Normalization is public only when an actual destination exists.
@normalized expression `{http.vars.original_path} != {http.vars.request_path}`
redir @normalized {http.vars.request_path}{query_suffix} 301
@team_filename path /team/*.md
header @team_filename Content-Type "text/html;charset=UTF-8"
try_files {path}/index.html {path}
file_server {
disable_canonical_uris
}
}
handle {
header Cache-Control "private, no-cache"
header Content-Type "text/html;charset=UTF-8"
rewrite * /404/index.html
file_server {
status 404
}
}
}
}
http://lbry.tv {
redir https://odysee.com{uri} 301
}
https://lbry.tv {
redir https://odysee.com{uri} 301
}
-21
View File
@@ -1,21 +0,0 @@
# Installation
## Prerequisites
To run this project, you'll need to have either PHP7 or Docker installed, and be using either macOS or Linux.
## Development
- Install [PHP7](http://php.net/downloads.php)
- Possibly install additional PHP extensions: `curl` / `dom` / `mbstring` / `xml`
- Checkout the project and install submodules: `git submodule update --init`
- If you have already cloned the project, be sure to update submodules: `git submodule update --recursive --remote`
- Run `./dev.sh` from the project root
- Access [localhost:8000](http://localhost:8000) in your browser
## Verifying Install
If `localhost:8000` returns the lbry.com website, it's running correctly.
## Additional Notes
- The `dev.sh` script will initialize a configuration based on `data/config.php.example` if `data/config.php` does not exist.
- Some pages and interactions rely on API keys that will not be available to you in your install.
- To run remotely, simply install PHP and configure Apache or your server of choice to serve `web/index.php`.
- If `dev.sh` fails to start with missing php extensions, please install `php-xml`, `php-curl`, and `php-mbstring` according to your OS instructions.
+1 -1
View File
@@ -1,6 +1,6 @@
The MIT License (MIT)
Copyright (c) 2015-2019 LBRY Inc.
Copyright (c) 2015-2020 LBRY Inc.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the
"Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish,
+68 -61
View File
@@ -1,82 +1,89 @@
<h1 align="center">lbry.com</h1>
> This site was rewritten from PHP to a static Hugo site. The previous PHP version is preserved on the [`php-version`](../../tree/php-version) branch. To check it out locally, run `git switch php-version`.
<div align="center">
<strong>We came from the future to help you save the Internet</strong>
</div>
# LBRY website
<div align="center">
Official website for <a href="https://lbry.com">the LBRY protocol</a>.
</div>
A static Hugo site. Building requires Hugo; PHP, Python, a database and the
original source checkout are not needed.
<div align="center">
<img src="https://spee.ch/4/com-2019-march.png" title="Screenshot of lbry.com"/>
</div>
## Build and preview
<div align="center">
<a href="https://github.com/lbryio/lbry.com/blob/master/LICENSE">
<img src="https://img.shields.io/dub/l/vibe-d.svg?style=flat-square"/>
</a>
Use Hugo 0.168.0:
<a href="https://chat.lbry.com">
<img src="https://img.shields.io/discord/362322208485277697.svg?style=flat-square&logo=discord"/>
</a>
</div>
```sh
hugo
hugo server
```
The build is written to `public/`. The built-in Hugo server previews content and
platform download pages. Use Caddy when serving legacy URLs, redirects and
custom HTTP statuses.
## Installation
Please see [INSTALL](INSTALL.md) for comprehensive, easy-to-follow instructions on running this project.
## Serve with Caddy
## Usage
Unless you are planning to contribute to the `lbry.com` website, this project serves little independent purpose.
From this directory, after building:
To access a local copy of `lbry.com`, follow [INSTALL](INSTALL.md) and then access `localhost:8000` in your browser. This will allow you to make changes to the website, test locally, and then submit pull requests.
```sh
caddy run --config Caddyfile --adapter caddyfile
```
## Contributing
Contributions to this project are welcome, encouraged, and compensated. For more details, see [CONTRIBUTING](https://lbry.tech/contribute).
`Caddyfile` contains the complete production configuration, including automatic
HTTPS for `lbry.com`. Set `SITE_ROOT` to override the default `./public` directory:
## License
This project is MIT licensed. For the full license, see [LICENSE](LICENSE).
```sh
SITE_ROOT="$PWD/public" caddy run --config Caddyfile --adapter caddyfile
```
## Build URLs
lbry.com provides functionality for redirecting to build assets of other LBRY repos. The general structure is:
Caddy serves Hugo pages and assets directly. It normalizes repeated and trailing
slashes and tries lowercase paths when an exact file does not exist. Known pages
redirect to their normalized URL; unknown paths receive the normal 404 page.
Exact asset filenames retain their spelling, including uppercase extensions.
`lbry.com/releases/<github_repo_name>.<extension>`
Public shortlinks and recognized article filename aliases remain in `Caddyfile`.
Article aliases check that the canonical destination exists. Query strings are
preserved during URL normalization and article redirects. Asset query strings use
the same underlying file; FAQ and download options are handled by JavaScript.
For example, to get the latest [lbry-desktop](https://github.com/lbryio/lbry-desktop) release on Windows, you would use the URL:
HTML uses a shared five-minute cache policy; common assets use four hours.
Errors use `private, no-cache`. Security headers are shared across responses.
Unsupported methods receive the site's 405 page. The former per-URL HTTP
profiles and captured error/redirect bodies are no longer used.
`lbry.com/releases/lbry-desktop.exe`
HTTP and HTTPS `lbry.tv` requests redirect directly to Odysee, preserving the URI.
`hugo server` previews the site independently and does not use this configuration.
Extension is used to get the release for the appropriate operating system, even if the release asset does not match the extension provided.
## Editing
| Operating System | Extensions
--- | ---
| Windows | msi, exe
| macOS | dmg, pkg
| Linux (Debian) | deb
| Android | apk
- Articles, FAQs, biographies and reports: `content/news/`, `content/faq/`,
`content/team/` and `content/credit-reports/`.
- Other page content: `content/pages/`; indexes: `content/indexes/`.
- Shared document, header and footer: `layouts/_default/baseof.html` and
`layouts/partials/site/`.
- Platform pages: `content/download-platforms/`; download layouts:
`layouts/partials/downloads/`; client-side OS selection: `static/js/download.js`.
- Desktop release data: `data/downloads.json`; platform/store/screenshot data:
`data/download_page.json`. The Android APK redirect target is configured in
`Caddyfile`.
- Roadmap snapshots: `data/roadmaps.yaml`; FAQ grouping:
`data/faq_categories.json`; shared link policy: `data/link_policy.json`.
- Known article filename aliases redirect to their canonical articles through
`Caddyfile`; they no longer generate duplicate HTML pages.
- The older Real Talk article remains at `/news/128-redactedtonight`, separate
from `/news/redactedtonight`.
- Historical blank team filename pages remain in `content/team-file-pages/`.
The asset returned will match the latest release on the appropriate GitHub repo.
On `/get`, JavaScript detects the OS and displays the corresponding production
layout. Explicit platform URLs override detection. `?showall=1` displays the OS
chooser; `?auto=1` starts the desktop download. Without JavaScript, visitors can
choose a platform using normal links.
Release candidates can also be targeted. For release candidates, use the following structure:
`lbry.com/releases/pre/<github_repo_name>.<extension>`
## Security
We take security seriously. Please contact [security@lbry.com](mailto:security@lbry.com) regarding any security issues.
[Our PGP key is here](https://keybase.io/lbry/key.asc) if you need it.
## Contact
The primary contact for this project is [@netoperatorwibby](https://github.com/netoperatorwibby) (paul+github@lbry.com).
## Additional Info and Links
- [https://lbry.com](https://lbry.com) - The live LBRY website
- [Discord Chat](https://chat.lbry.com) - A chat room for the LBRYians
- [LBRY Tech Forum](https://forum.lbry.tech) - LBRY Forum
- [Email us](mailto:hello@lbry.com) - LBRY Support email
- [Twitter](https://twitter.com/@lbryio) - LBRY Twitter page
- [Facebook](https://www.facebook.com/lbryio) - LBRY Facebook page
- [Reddit](https://reddit.com/r/lbry) - LBRY Reddit page
- [Telegram](https://t.me/lbryofficial) - Telegram group
The site unlinks chat.lbry.com and shop.lbry.com references while preserving
inline text. The footer omits Shop and Chat on Discord.
Hugo explicitly allows the repository's trusted HTML and Markdown content.
Templates access shared data through `hugo.Data`.
After upgrading an existing checkout, run `hugo --cleanDestinationDir` once to
remove obsolete generated files from `public/`. The captured response folders
(`_http`, `_family-probes`, `_url-addendum`, `_variants` and
`__migration_missing_reference__`) have been removed. Real assets formerly stored
there now live at their normal public paths.
-73
View File
@@ -1,73 +0,0 @@
<?php
class Autoloader
{
public static $classes = [];
public static function autoload($class)
{
if (class_exists($class, false) || interface_exists($class, false)) {
return true;
}
$class = strtolower($class);
$path = static::$classes[$class] ?? false;
if ($path) {
require_once $path;
return true;
}
return false;
}
public static function reload($reload = false)
{
$key = 'lbry-classes-5';
if (ini_get('apc.enabled') && !$reload) {
$classes = apcu_fetch($key, $success);
if ($success) {
static::$classes = $classes;
return;
}
}
static::$classes = [];
$dir = new RecursiveDirectoryIterator(ROOT_DIR, RecursiveDirectoryIterator::SKIP_DOTS);
$ite = new RecursiveIteratorIterator($dir);
$pathIterator = new RegexIterator($ite, '/.*\.php$/', RegexIterator::GET_MATCH);
foreach ($pathIterator as $paths) {
foreach ($paths as $path) {
static::$classes += static::parseFile($path);
}
}
if (ini_get('apc.enabled')) {
apcu_store($key, static::$classes);
}
}
protected static function parseFile($path)
{
$mapping = [];
$classes = [];
preg_match_all('~^\s*(?:namespace)\s+([^;]+)~mi', file_get_contents($path), $namespaces);
preg_match_all('~^\s*(?:abstract\s+|final\s+)?(?:class|interface)\s+(\w+)~mi', file_get_contents($path), $classes);
if (isset($namespaces[1]) && count($namespaces[1]) > 2) {
throw new RuntimeException('Autoloader cannot handle 2 namespaces in the same file');
}
$prefix = isset($namespaces[1]) && count($namespaces[1]) ? reset($namespaces[1]) . '\\' : '';
foreach ($classes[1] as $class) {
$mapping[strtolower($prefix . $class)] = $path;
}
return $mapping;
}
}
ini_set('unserialize_callback_func', 'spl_autoload_call');
spl_autoload_register('Autoloader::autoload');
Autoloader::reload(true);
-5
View File
@@ -1,5 +0,0 @@
<?php
define('ROOT_DIR', __DIR__);
date_default_timezone_set('Etc/UTC');
require ROOT_DIR . '/autoload.php';
-18
View File
@@ -1,18 +0,0 @@
#!/bin/bash
DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"
ERRORS=0
for FILE in $(find "$DIR" -name '*.php'); do
CHECK=$(php -l $FILE | grep -v "^No syntax errors detected")
if [ -n "$CHECK" ]; then
echo "$CHECK"
ERRORS=1
fi
done
if [ $ERRORS -eq 0 ]; then
echo "Syntax OK"
fi
exit $ERRORS
-18
View File
@@ -1,18 +0,0 @@
{
"name": "lbry/lbry.com",
"require": {
"php": ">=7.0",
"ext-curl": "*",
"ext-mbstring": "*",
"ext-xml": "*",
"ext-pdo": "*",
"ext-pdo_mysql": "*",
"ext-json": "*",
"leafo/scssphp": "0.7.6",
"erusev/parsedown": "^1.6",
"erusev/parsedown-extra": "^0.7.1",
"pelago/emogrifier": "^2.0",
"mustangostang/spyc": "^0.6.2",
"masterminds/html5": "^2.7"
}
}
Generated
-412
View File
@@ -1,412 +0,0 @@
{
"_readme": [
"This file locks the dependencies of your project to a known state",
"Read more about it at https://getcomposer.org/doc/01-basic-usage.md#installing-dependencies",
"This file is @generated automatically"
],
"content-hash": "f19fda681ea968799f6370f24cf03aa9",
"packages": [
{
"name": "erusev/parsedown",
"version": "1.7.3",
"source": {
"type": "git",
"url": "https://github.com/erusev/parsedown.git",
"reference": "6d893938171a817f4e9bc9e86f2da1e370b7bcd7"
},
"dist": {
"type": "zip",
"url": "https://api.github.com/repos/erusev/parsedown/zipball/6d893938171a817f4e9bc9e86f2da1e370b7bcd7",
"reference": "6d893938171a817f4e9bc9e86f2da1e370b7bcd7",
"shasum": ""
},
"require": {
"ext-mbstring": "*",
"php": ">=5.3.0"
},
"require-dev": {
"phpunit/phpunit": "^4.8.35"
},
"type": "library",
"autoload": {
"psr-0": {
"Parsedown": ""
}
},
"notification-url": "https://packagist.org/downloads/",
"license": [
"MIT"
],
"authors": [
{
"name": "Emanuil Rusev",
"email": "hello@erusev.com",
"homepage": "http://erusev.com"
}
],
"description": "Parser for Markdown.",
"homepage": "http://parsedown.org",
"keywords": [
"markdown",
"parser"
],
"time": "2019-03-17T18:48:37+00:00"
},
{
"name": "erusev/parsedown-extra",
"version": "0.7.1",
"source": {
"type": "git",
"url": "https://github.com/erusev/parsedown-extra.git",
"reference": "0db5cce7354e4b76f155d092ab5eb3981c21258c"
},
"dist": {
"type": "zip",
"url": "https://api.github.com/repos/erusev/parsedown-extra/zipball/0db5cce7354e4b76f155d092ab5eb3981c21258c",
"reference": "0db5cce7354e4b76f155d092ab5eb3981c21258c",
"shasum": ""
},
"require": {
"erusev/parsedown": "~1.4"
},
"type": "library",
"autoload": {
"psr-0": {
"ParsedownExtra": ""
}
},
"notification-url": "https://packagist.org/downloads/",
"license": [
"MIT"
],
"authors": [
{
"name": "Emanuil Rusev",
"email": "hello@erusev.com",
"homepage": "http://erusev.com"
}
],
"description": "An extension of Parsedown that adds support for Markdown Extra.",
"homepage": "https://github.com/erusev/parsedown-extra",
"keywords": [
"markdown",
"markdown extra",
"parsedown",
"parser"
],
"time": "2015-11-01T10:19:22+00:00"
},
{
"name": "leafo/scssphp",
"version": "v0.7.6",
"source": {
"type": "git",
"url": "https://github.com/leafo/scssphp.git",
"reference": "585f6ae84de62ffecf69c23805f25d78d7e4b794"
},
"dist": {
"type": "zip",
"url": "https://api.github.com/repos/leafo/scssphp/zipball/585f6ae84de62ffecf69c23805f25d78d7e4b794",
"reference": "585f6ae84de62ffecf69c23805f25d78d7e4b794",
"shasum": ""
},
"require": {
"php": ">=5.4.0"
},
"require-dev": {
"phpunit/phpunit": "~4.6",
"squizlabs/php_codesniffer": "~2.5"
},
"bin": [
"bin/pscss"
],
"type": "library",
"autoload": {
"psr-4": {
"Leafo\\ScssPhp\\": "src/"
}
},
"notification-url": "https://packagist.org/downloads/",
"license": [
"MIT"
],
"authors": [
{
"name": "Leaf Corcoran",
"email": "leafot@gmail.com",
"homepage": "http://leafo.net"
}
],
"description": "scssphp is a compiler for SCSS written in PHP.",
"homepage": "http://leafo.github.io/scssphp/",
"keywords": [
"css",
"less",
"sass",
"scss",
"stylesheet"
],
"time": "2018-05-24T02:18:53+00:00"
},
{
"name": "masterminds/html5",
"version": "2.7.0",
"source": {
"type": "git",
"url": "https://github.com/Masterminds/html5-php.git",
"reference": "104443ad663d15981225f99532ba73c2f1d6b6f2"
},
"dist": {
"type": "zip",
"url": "https://api.github.com/repos/Masterminds/html5-php/zipball/104443ad663d15981225f99532ba73c2f1d6b6f2",
"reference": "104443ad663d15981225f99532ba73c2f1d6b6f2",
"shasum": ""
},
"require": {
"ext-ctype": "*",
"ext-dom": "*",
"ext-libxml": "*",
"php": ">=5.3.0"
},
"require-dev": {
"phpunit/phpunit": "^4.8.35",
"sami/sami": "~2.0",
"satooshi/php-coveralls": "1.0.*"
},
"type": "library",
"extra": {
"branch-alias": {
"dev-master": "2.7-dev"
}
},
"autoload": {
"psr-4": {
"Masterminds\\": "src"
}
},
"notification-url": "https://packagist.org/downloads/",
"license": [
"MIT"
],
"authors": [
{
"name": "Matt Butcher",
"email": "technosophos@gmail.com"
},
{
"name": "Matt Farina",
"email": "matt@mattfarina.com"
},
{
"name": "Asmir Mustafic",
"email": "goetas@gmail.com"
}
],
"description": "An HTML5 parser and serializer.",
"homepage": "http://masterminds.github.io/html5-php",
"keywords": [
"HTML5",
"dom",
"html",
"parser",
"querypath",
"serializer",
"xml"
],
"time": "2019-07-25T07:03:26+00:00"
},
{
"name": "mustangostang/spyc",
"version": "0.6.2",
"source": {
"type": "git",
"url": "https://github.com/mustangostang/spyc.git",
"reference": "23c35ae854d835f2d7bcc3e3ad743d7e57a8c14d"
},
"dist": {
"type": "zip",
"url": "https://api.github.com/repos/mustangostang/spyc/zipball/23c35ae854d835f2d7bcc3e3ad743d7e57a8c14d",
"reference": "23c35ae854d835f2d7bcc3e3ad743d7e57a8c14d",
"shasum": ""
},
"require": {
"php": ">=5.3.1"
},
"require-dev": {
"phpunit/phpunit": "4.3.*@dev"
},
"type": "library",
"extra": {
"branch-alias": {
"dev-master": "0.5.x-dev"
}
},
"autoload": {
"files": [
"Spyc.php"
]
},
"notification-url": "https://packagist.org/downloads/",
"license": [
"MIT"
],
"authors": [
{
"name": "mustangostang",
"email": "vlad.andersen@gmail.com"
}
],
"description": "A simple YAML loader/dumper class for PHP",
"homepage": "https://github.com/mustangostang/spyc/",
"keywords": [
"spyc",
"yaml",
"yml"
],
"time": "2017-02-24T16:06:33+00:00"
},
{
"name": "pelago/emogrifier",
"version": "v2.2.0",
"source": {
"type": "git",
"url": "https://github.com/MyIntervals/emogrifier.git",
"reference": "2472bc1c3a2dee8915ecc2256139c6100024332f"
},
"dist": {
"type": "zip",
"url": "https://api.github.com/repos/MyIntervals/emogrifier/zipball/2472bc1c3a2dee8915ecc2256139c6100024332f",
"reference": "2472bc1c3a2dee8915ecc2256139c6100024332f",
"shasum": ""
},
"require": {
"ext-dom": "*",
"ext-libxml": "*",
"php": "^5.5.0 || ~7.0.0 || ~7.1.0 || ~7.2.0 || ~7.3.0",
"symfony/css-selector": "^3.4.0 || ^4.0.0"
},
"require-dev": {
"friendsofphp/php-cs-fixer": "^2.2.0",
"phpmd/phpmd": "^2.6.0",
"phpunit/phpunit": "^4.8.0",
"squizlabs/php_codesniffer": "^3.3.2"
},
"type": "library",
"extra": {
"branch-alias": {
"dev-master": "3.0.x-dev"
}
},
"autoload": {
"psr-4": {
"Pelago\\": "src/"
}
},
"notification-url": "https://packagist.org/downloads/",
"license": [
"MIT"
],
"authors": [
{
"name": "Oliver Klee",
"email": "github@oliverklee.de"
},
{
"name": "Zoli Szabó",
"email": "zoli.szabo+github@gmail.com"
},
{
"name": "John Reeve",
"email": "jreeve@pelagodesign.com"
},
{
"name": "Jake Hotson",
"email": "jake@qzdesign.co.uk"
},
{
"name": "Cameron Brooks"
},
{
"name": "Jaime Prado"
}
],
"description": "Converts CSS styles into inline style attributes in your HTML code",
"homepage": "https://www.myintervals.com/emogrifier.php",
"keywords": [
"css",
"email",
"pre-processing"
],
"time": "2019-09-04T16:07:59+00:00"
},
{
"name": "symfony/css-selector",
"version": "v4.3.4",
"source": {
"type": "git",
"url": "https://github.com/symfony/css-selector.git",
"reference": "c6e5e2a00db768c92c3ae131532af4e1acc7bd03"
},
"dist": {
"type": "zip",
"url": "https://api.github.com/repos/symfony/css-selector/zipball/c6e5e2a00db768c92c3ae131532af4e1acc7bd03",
"reference": "c6e5e2a00db768c92c3ae131532af4e1acc7bd03",
"shasum": ""
},
"require": {
"php": "^7.1.3"
},
"type": "library",
"extra": {
"branch-alias": {
"dev-master": "4.3-dev"
}
},
"autoload": {
"psr-4": {
"Symfony\\Component\\CssSelector\\": ""
},
"exclude-from-classmap": [
"/Tests/"
]
},
"notification-url": "https://packagist.org/downloads/",
"license": [
"MIT"
],
"authors": [
{
"name": "Fabien Potencier",
"email": "fabien@symfony.com"
},
{
"name": "Jean-François Simon",
"email": "jeanfrancois.simon@sensiolabs.com"
},
{
"name": "Symfony Community",
"homepage": "https://symfony.com/contributors"
}
],
"description": "Symfony CssSelector Component",
"homepage": "https://symfony.com",
"time": "2019-08-20T14:07:54+00:00"
}
],
"packages-dev": [],
"aliases": [],
"minimum-stability": "stable",
"stability-flags": [],
"prefer-stable": false,
"prefer-lowest": false,
"platform": {
"php": ">=7.0",
"ext-curl": "*",
"ext-mbstring": "*",
"ext-xml": "*",
"ext-pdo": "*",
"ext-pdo_mysql": "*",
"ext-json": "*"
},
"platform-dev": []
}
BIN
View File
Binary file not shown.
+18
View File
@@ -0,0 +1,18 @@
{
"title": "LBRY - Content Freedom",
"url": "/",
"type": "homepage",
"source_url": "https://lbry.com/",
"build": {
"list": "never"
},
"description": "Meet LBRY, a content sharing and publishing platform that is decentralized and owned by its users.",
"images": [
"https://lbry.com/img/og-image.png?_cache=2026-10-31"
],
"og_type": "article",
"twitter_card": "summary_large_image",
"news_feed": false,
"footer_email_href": "/cdn-cgi/l/email-protection#38505d54545778545a4a41165b5755",
"footer_email_code": "a8c0cdc4c4c7e8c4cadad186cbc7c5"
}
-13
View File
@@ -1,13 +0,0 @@
---
name: Akinwale Ariwodola
role: Mobile Engineer
email: akinwale@lbry.com
twitter: akinwale
github: akinwale
---
It was Akinwale’s search for lucrative crypto mining that brought him to LBRY. As he learned more about the project, his interest quickly turned to helping the team build the content sharing platform of the future.
Akinwale has worked on everything from rewriting a new block explorer from the ground up, improvements to the app’s interface, as well as leading the effort to successfully get the daemon running on Android.
When he’s not working on LBRY, he actively participates in competitive programming contests on Topcoder, and is a two-time champion of the annual Topcoder Open event.
-9
View File
@@ -1,9 +0,0 @@
---
name: Alex Grintsvayg
role: Founder, Chief Technical Officer
email: grin@lbry.com
twitter: lyoshenka
github: lyoshenka
---
Alex, AKA Grin, drives technology development at LBRY and manages infrastructure growth. Grin has previously designed and managed scalable infrastructure solutions for SaaS firms. Bringing LBRY to mainstream scale is his primary goal. Alex holds degrees in Computer Science and Psychology from Rensselaer Polytechnic Institute.
-10
View File
@@ -1,10 +0,0 @@
---
name: Alex Tabarrok
role: Economic Advisor
---
Alex Tabarrok is Bartley J. Madden Chair in Economics at the [Mercatus Center](http://mercatus.org) and a professor of economics at [George Mason University](https://gmu.edu). He specializes in intellectual property reform, the effectiveness of markets, and the justice system.
Tabarrok is the coauthor, with Mercatus colleague Tyler Cowen, of the popular economics blog [_Marginal Revolution_](http://www.marginalrevolution.com) and cofounder of the online educational platform [Marginal Revolution University](http://mruniversity.com). He is the coauthor of _[Modern Principles of Economics](http://www.amazon.com/Modern-Principles-Economics-Tyler-Cowen/dp/1429239972)_, and author of the recent book _[Launching the Innovation Renaissance](http://www.amazon.com/Launching-The-Innovation-Renaissance-Market-ebook/dp/B006C1HX24)_. His articles have appeared in the _New York Times_, the _Washington Post_, the _Wall Street Journal_, and many other prestigious publications.
Tabarrok received his PhD in economics from [George Mason University](http://en.wikipedia.org/wiki/George_Mason_University "George Mason University").
-6
View File
@@ -1,6 +0,0 @@
---
name: Andrey
role: LBRY.tv Engineer
email: Andrey@lbry.com
---
Andrey got into web programming twenty years ago and has done it all, from Perl CGI programming to UI design. At a turning point decided to focus on server-side applications, making exciting technologies accessible to both fellow developers and users. Easily fascinated by distributed and decentralized things. Values understandable code and can agonize over naming a variable for days. Works mostly when everyone is asleep. When not working, travels around South-East Asia, doing scuba diving wherever there’s water around.
-13
View File
@@ -1,13 +0,0 @@
---
name: Antoniy Shumanov
role: C++ Engineer
email: antoniy@lbry.com
---
Antoniy Shumanov, aka bvbfan, is a man of many talents. Some of his accomplishments and attitudes include:
* Numerous contributions to open source projects like KDE and Godot
* Works on blockchain LBRY, steem forks as well past year
* Design and develop clean and reusable c++ code
* Master engineer degree in computer science and electronics
* Enjoys watching satiric TV shows like The Simpsons and Family Guy
* Takes a work as a hobby, so working on enjoyable projects only
-11
View File
@@ -1,11 +0,0 @@
---
name: Brannon King
role: Senior Blockchain Engineer
email: brannon@lbry.com
---
Brannon King merges talent, precision, and prudence with experience and a passion for simplicity.
Prior to becoming a blockchain engineer, Brannon developed autonomous driving software, primarily in C++ and C#. This included a lot of work in search algorithms, geometry, threading, and pub/sub frameworks.
In his spare time Brannon plays the piano, cares for his six children, and reads. In 2006 he was influenced heavily through a reading of the _The Bastiat Collection_, which set him on a life course destined to intercept cryptocurrencies.
-13
View File
@@ -1,13 +0,0 @@
---
name: Brinck Slattery
role: Director of Communications
email: brinck@lbry.com
twitter: LazerLotus777
github: Feanor78
---
Brinck’s range of experience includes national political campaigns, crisis PR, SEO writing and optimization, digital marketing, RV sales, construction labor, and a variety of other strange and interesting pursuits (feel free to ask).
An inveterate music and media lover, Brinck remembers the pain of Kazaa and Limewire, and is seriously psyched about living in the future where it’s easy to compensate artists directly for their work.
He lives in Manchester, NH and can be regularly found lurking wherever the latest music is blaring.
-12
View File
@@ -1,12 +0,0 @@
---
name: Jack Robison
role: Founder, Protocol Engineer
email: jack@lbry.com
github: jackrobison
---
Jack's path to development with LBRY is fairly typical: [face sixty years in prison for innocent chemistry experiments](http://www.masslive.com/localbuzz/index.ssf/2009/06/actionreaction_how_one_teens_c.html); lose interest in chemistry; [program insane electric guitars for Kiss](https://www.youtube.com/watch?v=dXZi4UZjiiI&t=10); decide to revolutionize the internet.
Jack was one of the first people to discover LBRY and took to it so fast he may understand more about it than anyone.
Jack has Asperger's Syndrome and is actively involved in the autism community. He was a regular on Wrong Planet's Autism Talk TV, has appeared on _National Public Radio_, the _New York Times_, and presents around the country.
-13
View File
@@ -1,13 +0,0 @@
---
name: James Biller
role: Former Marketing Intern
email: james@lbry.com
twitter: billerjames
github: jamesbiller
---
James came to LBRY through Praxis, a company that offers apprenticeships to young entrepreneurial types.
Originally brought on to help with recruiting YouTubers, James showed up to the office with a 3D printed LBRYopoly board and was the original person who championed the use of the LBRY protocol for 3D printing.
He has a passion for philosophy, 3D printing, and writing fiction.
-13
View File
@@ -1,13 +0,0 @@
---
name: Jeremy Kauffman
role: Founder, Chief Executive Officer
email: jeremy@lbry.com
twitter: jeremykauffman
github: kauffj
---
Jeremy knows how to build and scale a startup starting from day one. He knows how to deliver usable products and get those products in front of the right people.
Jeremy created LBRY because he fell in love with the idea of shared, global content registry that is owned and controlled by no one. Unsurprisingly, he is a longtime supporter of decentralized technology and freedom of information.
Prior to LBRY, Jeremy founded [TopScore](//usetopscore.com), a startup that processes millions of dollars monthly in event and activity registrations. He attended [Rensselaer Polytechnic Institute](//rpi.edu), where he received degrees in physics and computer science.
-11
View File
@@ -1,11 +0,0 @@
---
name: Jimmy Kiselak
role: Founder, Core Engineer
email: jimmy@lbry.com
---
Jimmy is the second comp science/physics graduate from Rensselaer. After, he found himself mired in government bureaucracy, spending too much time to get too little done.
Ready to work on a project he believed in, Jimmy left a national security programming job to start LBRY. Jimmy created the LBRY protocol and the first LBRY application.
Jimmy is a Bitcoin fanatic and has been since its early days. He has long been interested in the benefits of decentralization.
-13
View File
@@ -1,13 +0,0 @@
---
name: Josh Finer
role: Founder, Director of Operations and Analytics
email: josh@lbry.com
twitter: finer9
github: finer9
---
Josh is the swiss army knife of the squad.
He has founded and sold financial companies, run millions of dollars in Adwords campaigns, and been an early actor in several crypto projects.
To LBRY, he has been the go-to glue guy and ultimate problem solver. If you’re a crypto-nerd or have ideas on making LBRY more accessible to the masses, Finer is your man.
-11
View File
@@ -1,11 +0,0 @@
---
name: Kay Kurokawa
role: Protocol Engineer
email: kay@lbry.com
twitter: kaykurokawa
github: kaykurokawa
---
Kay Kurokawa contributes to the LBRY blockchain, the foundation of the LBRY protocol. Kay first discovered Bitcoin in 2013 and immediately saw its potential. Before LBRY, he provided consultation services to blockchain startups and contributed to various open source projects such as Electrum, Litecoin, Dogecoin, and Blocknet.
Before his work on blockchain technology, Kay worked at a high frequency trading firm as a software engineer. He also spent time developing algorithms for spectrometry devices, and has several published papers on the topic. He earned a B.S. and an M.S. from Carnegie Mellon University in electrical and computer engineering.
-11
View File
@@ -1,11 +0,0 @@
---
name: Lex Berezhny
role: Protocol Engineer
email: lex@lbry.com
twitter: eukreign
github: eukreign
---
Lex learned to write Python in High School, not far from where the language was first created, and even participated in some of the first Python user groups hosted by Guido, himself. In 2000, still a very young man, Lex gave his first public talk, titled "Yorktown High School Becomes a Python Workshop" at the International Python Conference. Needless to say, Lex and Python go way back.
Lex spends his time on the full stack of LBRY backends, such as the wallet, protocol, and blockchain, and is currently wading deep into the improvement of test coverage and performance of various LBRY components. If you want to trade notes on Dart, and dish on a possible ideal use case for Dart at LBRY, Lex wants to hear from you!
-14
View File
@@ -1,14 +0,0 @@
---
name: Mark Beamer
role: Backend and Database Engineer
email: mark@lbry.com
github: tiger5226
---
Mark Beamer is an inveterate entrepreneur. Ever since he founded his first company (Beamer Lawn Service) at 16, he's pursued new and interesting business ideas.
While running his first computer business, Mark discovered the joys of coding - especially the joys of using coding to eliminate annoying tasks with automation.
His continued passion for software led him to close the business after 4 years and pursue a BS in computational science and mathematics.
Mark has been developing software ever since. He found LBRY summer of 2017 on a leisurely weekend, saw the coding maxims and was sucked in instantly. LBRY has been his focus since.
-8
View File
@@ -1,8 +0,0 @@
---
name: Michael Huemer
role: Ethics Advisor
---
Michael Huemer is Professor of Philosophy and Ethics at the [University of Colorado](//www.colorado.edu), where he has taught since 1998\. He has published three single-author scholarly books (including _[Ethical Intuitionism](http://www.amazon.com/Ethical-Intuitionism-Michael-Huemer/dp/0230573746)_), one edited anthology, and more than fifty academic articles in epistemology, ethics, political philosophy, and metaphysics.
Huemer's articles have appeared in such journals as the _Philosophical Review_, _Mind_, the _Journal of Philosophy_, _Ethics_, and others. His materials are used as readings in classrooms nationwide. He received a B.A. from UC Berkeley and a Ph.D. from Rutgers University.
-9
View File
@@ -1,9 +0,0 @@
---
name: Mike Vine
role: .
email: hello@lbry.com
---
Mike was one of the early team members of LBRY.
He contributed to marketing and branding in the earliest days of the app.
-15
View File
@@ -1,15 +0,0 @@
---
name: Niko Storni
role: DevOps Engineer
email: Niko@lbry.com
twitter: Nikooo777
github: Nikooo777
---
Niko isn't scared of putting his hands in the code to write solutions to make user’s lives easier.
After graduating as an IT Engineer in Switzerland, Niko joined the LBRY community as a miner and volunteer contributor for almost 2 years before quitting his job to pursue his real passion: LBRY.
Running a gaming community for almost 10 years, Niko has developed a lot of experience with managing and serving professional solutions on Linux servers.
Together with his professional background, he is in charge of providing LBRY with the right server infrastructure, vital for everyone to enjoy a smooth and safe experience. When he's not sitting behind a monitor, Niko enjoys riding his motorcycle, hiking the Alps, reading, swimming, and much more!
-15
View File
@@ -1,15 +0,0 @@
---
name: Reilly Smith
role: Former Director of Content
email: reilly@lbry.com
twitter: reillysmith
github: reillysmith
---
For nearly a decade, Reilly has developed, produced, championed and contributed to dozens of film projects big and small.
The only thing that rivals his love of film is the marriage between content and blockchain.
If you come from the world of film, television or web content, he's your sherpa on Mount Blockchain.
Reilly's work has been seen from Oxford, Mississippi to Sundance Film Festival, and he has produced content for Fox Digital Studios and Disney LOL.
-13
View File
@@ -1,13 +0,0 @@
---
name: Rob Smith
role: VP of Growth
email: rob@lbry.com
twitter: robdoes
github: robvsmith
---
Rob focuses on ensuring users get a top notch experience with LBRY, from the earliest brand engagement to running the app and follow up communications.
He believes in wielding design, technology, and art to deliver joyful experiences that connect people with the things they care most about. Rob's background is in game design, game publishing, software business development, and project management.
Rob has a Bachelors of Science from The Art Institute of California - San Francisco, and a Master of Business Administration from California State University, Stanislaus.
-9
View File
@@ -1,9 +0,0 @@
---
name: Samuel Bryan
role: Pen Name
email: hello@lbry.com
twitter: lbryio
github: lbryio
---
Much of our writing is a collaboration between LBRY team members, so we use SamueL BRYan to share credit. Sam has become a friend... an imaginary friend... even though we're adults...
-13
View File
@@ -1,13 +0,0 @@
---
name: Sean Yesmunt
role: App Engineer
email: sean@lbry.com
twitter: seanyesmunt
github: seanyesmunt
---
Sean is an app engineer focused on user experience, which means he spends his time making the LBRY app easier to use. Sean was part way through an Aerospace Engineering degree at Penn State, when he decided he didn’t want to end up working on rockets for the government.
So, he did what many LBRYians have done, and dropped out to focus on coding. His excitement for crypto and open-source projects focused on decentralization, led him to discover LBRY, which he began working on the very same day.
His passion for developing intuitive experiences has brought immense value to users all around the world who use LBRY.
-8
View File
@@ -1,8 +0,0 @@
---
name: Stephan Kinsella
role: Legal Advisor
---
Stephan Kinsella is a registered patent attorney and has over twenty years' experience in patent, intellectual property, and general commercial and corporate law. He is the founder and director of the [Center for the Study of Innovative Freedom](http://c4sif.org). Kinsella has published numerous articles and books on intellectual property law and legal topics including [_International Investment, Political Risk, and Dispute Resolution: A Practitioner's Guide_](http://www.amazon.com/International-Investment-Political-Dispute-Resolution/dp/0379215225) and [_Against Intellectual Property_](https://mises.org/library/against-intellectual-property-0) .
He received an LL.M. in international business law from [King's College London](http://www.kcl.ac.uk), a JD from the Paul M. Hebert Law Center at [Louisiana State University](//lsu.edu), as well as BSEE and MSEE degrees. His websites are [stephankinsella.com](http://stephankinsella.com) and [kinsellalaw.com](http://kinsellalaw.com)
-11
View File
@@ -1,11 +0,0 @@
---
name: Tom Zarebczan
role: Community Support and Engagement
email: tom@lbry.com
twitter: TomZarebczan
github : tzarebczan
---
Tom discovered LBRY, as many have, through mining. His time spent in the LBRY Slack channels quickly grew his interest in the concept that was being developed, and the team doing the development. Tom found his place on the team providing top-notch support for (and driving the growth of) the LBRY user community, in addition to many other invaluable functions.
Tom holds a Bachelors in Computer Engineering from the New Jersey Institute of Technology, a Masters in Systems Engineering from Stevens Institute of Technology, and served his country proudly as a Civilian in the US Army for 7 years. When he's not monitoring LBRY Twitter, Reddit, Slack, and/or Discord looking for users in distress, Tom can be found doing geek-y stuff, or snowboarding in really cool places around the world.
-11
View File
@@ -1,11 +0,0 @@
---
name: You
role: Engineer, Designer, Economist, Marketer, Investor, ???
email: jeremy@lbry.com
---
Do you think opening up information would facilitate human flourishing?
Do you want to join a bright core of people with an obsession for upending broken systems?
[Say hello](mailto:jeremy@lbry.com).
-34
View File
@@ -1,34 +0,0 @@
---
title: "Quarterly Credit Report: Third Quarter 2016"
sheet: https://docs.google.com/spreadsheets/d/1zPG58YuLPqpB3yzypntRWouoEVc4saDOifpnvnwS8Rc/edit?ts=57f28d0e#gid=799352054
category: policy
---
## Summary
This is LBRY's second quarterly report. This quarter we outlaid only 267,778 of the 2,000,000 allocated Community credits. 100,000 operational credits were exchanged with Shapeshift to provide liquidity. No institutional credits were moved or spent.
## Overview By Fund
### Community Fund
- 10,600 LBRY credits outlaid to community managers
- 171,251 LBRY credits outlaid to Alpha and Beta testers
- 19,150 LBRY credits outlaid to community members for completing bounties
- 75,777 LBRY credits outlaid in Slack tips*
*Some tip outlays were for bounties and to reward early people who stepped up to manage the community before we had a formal program. We have ceased using Slack tips for bounties and community management and will be able to better differentiate these moving forward.*
Over the next quarter we anticipate continued substantial use of the Community credits to grow both the user base and the publishing base. We expect these outlays to match or exceed those of this quarter, but not to dramatically exceed these outlays.
### Operational Fund
- 100,000 LBRY credits exchanged to ShapeShift to provide liquidity on their platform.
ShapeShift required ownership over a pool of LBRY credits to maintain their exchange services. These credits were sold at near-market rates.
We do not anticipate any expenditures from this fund through Q2 2017.
### Institutional Fund
We have no current plans to expend any LBRY credits from this fund this quarter, but are examining possibilities. Any institutional fund expenditures at this time would likely come with restrictions that prevent exchange or sale.
-34
View File
@@ -1,34 +0,0 @@
---
title: "Quarterly Credit Report: Fourth Quarter 2016"
sheet: https://docs.google.com/spreadsheets/d/11nKwFXN3gIQHnE7jYjEK5AFClyAde9aFs6UlnGX3Uzg/edit#gid=799352054
category: policy
---
## Summary
This quarter we did not move any community credits from cold storage. We spent 293,604 already moved community credits on line items detailed below. No operational credits were moved or spent. No institutional credits were moved or spent.
As the LBRY protocol performance and reliability has increased, we anticipate increased outlays in Q1 2017. We will be redeeming many if not all beta invites, as well as launching a new program offering credits to developers. We also may begin the first institutional outlays, but any outlays here will be pilot programs and come with spending restrictions.
## Overview By Fund
### Community Fund
- Community managers received 261,109 LBRY credits this quarter
- Beta invitees received 22,400 LBRY credits this quarter
- Bounty participants received 5,750 LBRY credits this quarter
- 4,345 LBRY credits were used for "other" purposes, mostly given to developers
This quarter was a down quarter in credit outlays because we declined to send beta invites to users while the protocol was showing poor reliability.
As reliability has been increasing, we anticipate inviting many if not all users on the beta waitlist. This will represent a significant uptick in credit outlays, possibly as much as 1-2 million LBC. We will also be launching a new program offering credits to developers.
### Operational Fund
- No activity this quarter
We anticipate no usage of credits from this fund this quarter.
### Institutional Fund
No activity this quarter
We may run our first institutional pilot programs this quarter. Any outlays from this fund this quarter will be minimal and are likely to come with restrictions that prevent them from going to market.
@@ -1,12 +1,29 @@
---
title: "Quarterly Credit Report: Second Quarter 2016"
sheet: https://docs.google.com/spreadsheets/d/1r7puheE4Ut4c08R47uCDZbDdMHAoQa0WDqw470gjMIw/edit#gid=0
category: policy
---
{
"title": "Quarterly Credit Report: Second Quarter 2016",
"meta_title": "Quarterly Credit Report: Second Quarter 2016 - LBRY",
"url": "/credit-reports/2016-q2",
"aliases": [
"/credit-reports/2016-Q2"
],
"type": "report",
"source_url": "https://lbry.com/credit-reports/2016-q2",
"source_file": "content/credit-reports/2016-Q2.md",
"description": "Quarterly Credit Report: Second Quarter 2016",
"images": [
"https://lbry.com/img/og-image.png?_cache=2026-10-31"
],
"og_type": "article",
"twitter_card": "summary_large_image",
"news_feed": false,
"sheet": "https://docs.google.com/spreadsheets/d/1r7puheE4Ut4c08R47uCDZbDdMHAoQa0WDqw470gjMIw/edit",
"category": "policy",
"footer_email_href": "/cdn-cgi/l/email-protection#95fdf0f9f9fad5f9f7e7ecbbf6faf8",
"footer_email_code": "365e535a5a59765a54444f1855595b",
"source_sheet": "https://docs.google.com/spreadsheets/d/1r7puheE4Ut4c08R47uCDZbDdMHAoQa0WDqw470gjMIw/edit#gid=0"
}
## Summary
This is LBRY's first quarterly report. We enter with zero credits expended. We anticipate zero institutional expenditures, zero or limited organizational expenditures, and light community expenditures.
This is LBRY's first quarterly report. We enter with zero Credits expended. We anticipate zero institutional expenditures, zero or limited organizational expenditures, and light community expenditures.
## Overview By Fund
+51
View File
@@ -0,0 +1,51 @@
{
"title": "Quarterly Credit Report: Third Quarter 2016",
"meta_title": "Quarterly Credit Report: Third Quarter 2016 - LBRY",
"url": "/credit-reports/2016-q3",
"aliases": [
"/credit-reports/2016-Q3"
],
"type": "report",
"source_url": "https://lbry.com/credit-reports/2016-q3",
"source_file": "content/credit-reports/2016-Q3.md",
"description": "Quarterly Credit Report: Third Quarter 2016",
"images": [
"https://lbry.com/img/og-image.png?_cache=2026-10-31"
],
"og_type": "article",
"twitter_card": "summary_large_image",
"news_feed": false,
"sheet": "https://docs.google.com/spreadsheets/d/1zPG58YuLPqpB3yzypntRWouoEVc4saDOifpnvnwS8Rc/edit?ts=57f28d0e",
"category": "policy",
"footer_email_href": "/cdn-cgi/l/email-protection#f29a979e9e9db29e90808bdc919d9f",
"footer_email_code": "d2bab7bebebd92beb0a0abfcb1bdbf",
"source_sheet": "https://docs.google.com/spreadsheets/d/1zPG58YuLPqpB3yzypntRWouoEVc4saDOifpnvnwS8Rc/edit?ts=57f28d0e#gid=799352054"
}
## Summary
This is LBRY's second quarterly report. This quarter we outlaid only 267,778 of the 2,000,000 allocated Community Credits. 100,000 operational Credits were exchanged with Shapeshift to provide liquidity. No institutional Credits were moved or spent.
## Overview By Fund
### Community Fund
- 10,600 LBRY Credits outlaid to community managers
- 171,251 LBRY Credits outlaid to Alpha and Beta testers
- 19,150 LBRY Credits outlaid to community members for completing bounties
- 75,777 LBRY Credits outlaid in Slack tips*
*Some tip outlays were for bounties and to reward early people who stepped up to manage the community before we had a formal program. We have ceased using Slack tips for bounties and community management and will be able to better differentiate these moving forward.*
Over the next quarter we anticipate continued substantial use of the Community Credits to grow both the user base and the publishing base. We expect these outlays to match or exceed those of this quarter, but not to dramatically exceed these outlays.
### Operational Fund
- 100,000 LBRY Credits exchanged to ShapeShift to provide liquidity on their platform.
ShapeShift required ownership over a pool of LBRY Credits to maintain their exchange services. These Credits were sold at near-market rates.
We do not anticipate any expenditures from this fund through Q2 2017.
### Institutional Fund
We have no current plans to expend any LBRY Credits from this fund this quarter, but are examining possibilities. Any institutional fund expenditures at this time would likely come with restrictions that prevent exchange or sale.
+51
View File
@@ -0,0 +1,51 @@
{
"title": "Quarterly Credit Report: Fourth Quarter 2016",
"meta_title": "Quarterly Credit Report: Fourth Quarter 2016 - LBRY",
"url": "/credit-reports/2016-q4",
"aliases": [
"/credit-reports/2016-Q4"
],
"type": "report",
"source_url": "https://lbry.com/credit-reports/2016-q4",
"source_file": "content/credit-reports/2016-Q4.md",
"description": "Quarterly Credit Report: Fourth Quarter 2016",
"images": [
"https://lbry.com/img/og-image.png?_cache=2026-10-31"
],
"og_type": "article",
"twitter_card": "summary_large_image",
"news_feed": false,
"sheet": "https://docs.google.com/spreadsheets/d/11nKwFXN3gIQHnE7jYjEK5AFClyAde9aFs6UlnGX3Uzg/edit",
"category": "policy",
"footer_email_href": "/cdn-cgi/l/email-protection#b8d0ddd4d4d7f8d4dacac196dbd7d5",
"footer_email_code": "d2bab7bebebd92beb0a0abfcb1bdbf",
"source_sheet": "https://docs.google.com/spreadsheets/d/11nKwFXN3gIQHnE7jYjEK5AFClyAde9aFs6UlnGX3Uzg/edit#gid=799352054"
}
## Summary
This quarter we did not move any community Credits from cold storage. We spent 293,604 already moved community Credits on line items detailed below. No operational Credits were moved or spent. No institutional credits were moved or spent.
As the LBRY protocol performance and reliability has increased, we anticipate increased outlays in Q1 2017. We will be redeeming many if not all beta invites, as well as launching a new program offering Credits to developers. We also may begin the first institutional outlays, but any outlays here will be pilot programs and come with spending restrictions.
## Overview By Fund
### Community Fund
- Community managers received 261,109 LBRY Credits this quarter
- Beta invitees received 22,400 LBRY Credits this quarter
- Bounty participants received 5,750 LBRY Credits this quarter
- 4,345 LBRY Credits were used for "other" purposes, mostly given to developers
This quarter was a down quarter in credit outlays because we declined to send beta invites to users while the protocol was showing poor reliability.
As reliability has been increasing, we anticipate inviting many if not all users on the beta waitlist. This will represent a significant uptick in credit outlays, possibly as much as 1-2 million LBC. We will also be launching a new program offering Credits to developers.
### Operational Fund
- No activity this quarter
We anticipate no usage of Credits from this fund this quarter.
### Institutional Fund
No activity this quarter
We may run our first institutional pilot programs this quarter. Any outlays from this fund this quarter will be minimal and are likely to come with restrictions that prevent them from going to market.
-37
View File
@@ -1,37 +0,0 @@
---
title: "Quarterly Credit Report: First Quarter 2017"
sheet: https://docs.google.com/spreadsheets/d/1c-8CR1ro7lKOANHhWhivF7bZ19_ppgCq-d-HD_u43vM/edit#gid=799352054
category: policy
---
## Summary
This quarter we moved 3 million community credits from cold storage. We spent 1,186,244 total community credits on line items detailed below. No operational credits were moved or spent. No institutional credits were moved or spent.
As the LBRY protocol performance and reliability has again increased, we anticipate increased outlays in Q2 2017. This will primarily be driven by the redemption of beta invites. We also may begin the first institutional outlays, but any outlays here will be pilot programs and come with spending restrictions.
## Overview By Fund
### Community Fund
Bounty 14,500 LBRY Credits
Testing 181,243 LBRY Credits
Invite Refill 15,955 LBRY Credits
Quickstart 506,000 LBRY Credits
Publishing 13,250 LBRY Credits
Modpay 394,600 LBRY Credits
Dev_Eval 5,000 LBRY Credits
Other 55,696 LBRY Credits
As reliability has been increasing, we anticipate inviting many, if not, all users on the beta waitlist. This will represent a significant uptick in credit outlays, possibly as much as 1-2 million LBC.
### Operational Fund
No activity this quarter.
We anticipate no usage of credits from this fund this quarter.
### Institutional Fund
No activity this quarter.
We may run our first institutional pilot programs this quarter. Any outlays from this fund this quarter will be minimal and are likely to come with restrictions that prevent them from going to market.
+54
View File
@@ -0,0 +1,54 @@
{
"title": "Quarterly Credit Report: First Quarter 2017",
"meta_title": "Quarterly Credit Report: First Quarter 2017 - LBRY",
"url": "/credit-reports/2017-q1",
"aliases": [
"/credit-reports/2017-Q1"
],
"type": "report",
"source_url": "https://lbry.com/credit-reports/2017-q1",
"source_file": "content/credit-reports/2017-Q1.md",
"description": "Quarterly Credit Report: First Quarter 2017",
"images": [
"https://lbry.com/img/og-image.png?_cache=2026-10-31"
],
"og_type": "article",
"twitter_card": "summary_large_image",
"news_feed": false,
"sheet": "https://docs.google.com/spreadsheets/d/1c-8CR1ro7lKOANHhWhivF7bZ19_ppgCq-d-HD_u43vM/edit",
"category": "policy",
"footer_email_href": "/cdn-cgi/l/email-protection#c5ada0a9a9aa85a9a7b7bceba6aaa8",
"footer_email_code": "b7dfd2dbdbd8f7dbd5c5ce99d4d8da",
"source_sheet": "https://docs.google.com/spreadsheets/d/1c-8CR1ro7lKOANHhWhivF7bZ19_ppgCq-d-HD_u43vM/edit#gid=799352054"
}
## Summary
This quarter we moved 3 million community Credits from cold storage. We spent 1,186,244 total community Credits on line items detailed below. No operational Credits were moved or spent. No institutional Credits were moved or spent.
As the LBRY protocol performance and reliability has again increased, we anticipate increased outlays in Q2 2017. This will primarily be driven by the redemption of beta invites. We also may begin the first institutional outlays, but any outlays here will be pilot programs and come with spending restrictions.
## Overview By Fund
### Community Fund
Bounty 14,500 LBRY Credits
Testing 181,243 LBRY Credits
Invite Refill 15,955 LBRY Credits
Quickstart 506,000 LBRY Credits
Publishing 13,250 LBRY Credits
Modpay 394,600 LBRY Credits
Dev_Eval 5,000 LBRY Credits
Other 55,696 LBRY Credits
As reliability has been increasing, we anticipate inviting many, if not, all users on the beta waitlist. This will represent a significant uptick in credit outlays, possibly as much as 1-2 million LBC.
### Operational Fund
No activity this quarter.
We anticipate no usage of Credits from this fund this quarter.
### Institutional Fund
No activity this quarter.
We may run our first institutional pilot programs this quarter. Any outlays from this fund this quarter will be minimal and are likely to come with restrictions that prevent them from going to market.
@@ -1,12 +1,28 @@
---
title: "Quarterly Credit Report: Second Quarter 2017"
sheet: https://docs.google.com/spreadsheets/d/1APKXW-JIH6Wq-pWqiDaUfj0MTRKz01QL9yIDVZU7LZI/
category: policy
---
{
"title": "Quarterly Credit Report: Second Quarter 2017",
"meta_title": "Quarterly Credit Report: Second Quarter 2017 - LBRY",
"url": "/credit-reports/2017-q2",
"aliases": [
"/credit-reports/2017-Q2"
],
"type": "report",
"source_url": "https://lbry.com/credit-reports/2017-q2",
"source_file": "content/credit-reports/2017-Q2.md",
"description": "Quarterly Credit Report: Second Quarter 2017",
"images": [
"https://lbry.com/img/og-image.png?_cache=2026-10-31"
],
"og_type": "article",
"twitter_card": "summary_large_image",
"news_feed": false,
"sheet": "https://docs.google.com/spreadsheets/d/1APKXW-JIH6Wq-pWqiDaUfj0MTRKz01QL9yIDVZU7LZI/",
"category": "policy",
"footer_email_href": "/cdn-cgi/l/email-protection#462e232a2a29062a24343f6825292b",
"footer_email_code": "345c5158585b745856464d1a575b59"
}
## Summary
This quarter we did not move any credits from cold storage. We spent 704,306 total community credits on line items detailed below. No operational credits were moved or spent. No institutional credits were moved or spent.
This quarter we did not move any Credits from cold storage. We spent 704,306 total community Credits on line items detailed below. No operational Credits were moved or spent. No institutional Credits were moved or spent.
As the LBRY protocol performance and reliability has again increased, we anticipate increased outlays in Q3 2017. We will continue to redeem many if not all beta invites, which could total several million LBC. Additionally, LBRY will begin move several hundred thousand LBC to market from operational funds. No institutional outlays are expected, but a pilot program could happen.
## Overview By Fund
@@ -1,12 +1,28 @@
---
title: "Quarterly Credit Report: Third Quarter 2017"
sheet: https://docs.google.com/spreadsheets/d/15wm2cEVa9eQnHQVHDg7muRXm1dzFXJ6ftqEJBuNixGM/edit?usp=sharing
category: policy
---
{
"title": "Quarterly Credit Report: Third Quarter 2017",
"meta_title": "Quarterly Credit Report: Third Quarter 2017 - LBRY",
"url": "/credit-reports/2017-q3",
"aliases": [
"/credit-reports/2017-Q3"
],
"type": "report",
"source_url": "https://lbry.com/credit-reports/2017-q3",
"source_file": "content/credit-reports/2017-Q3.md",
"description": "Quarterly Credit Report: Third Quarter 2017",
"images": [
"https://lbry.com/img/og-image.png?_cache=2026-10-31"
],
"og_type": "article",
"twitter_card": "summary_large_image",
"news_feed": false,
"sheet": "https://docs.google.com/spreadsheets/d/15wm2cEVa9eQnHQVHDg7muRXm1dzFXJ6ftqEJBuNixGM/edit?usp=sharing",
"category": "policy",
"footer_email_href": "/cdn-cgi/l/email-protection#9df5f8f1f1f2ddf1ffefe4b3fef2f0",
"footer_email_code": "c0a8a5acacaf80aca2b2b9eea3afad"
}
## Summary
This quarter we did not move any credits from cold storage. We spent 867,956 total community credits on line items detailed below. 1,000,000 operational credits were moved to markets. No institutional credits were moved or spent.
This quarter we did not move any Credits from cold storage. We spent 867,956 total community Credits on line items detailed below. 1,000,000 operational Credits were moved to markets. No institutional Credits were moved or spent.
As the LBRY protocol performance and reliability has again increased, we anticipate similar or increased outlays in Q4 2017. We will continue to incentivize new users and other beneficial behavior, which could total several million LBC. Additionally, LBRY may move 1,000,000 LBC to market from operational funds. No institutional outlays are expected, but a pilot program could happen.
@@ -1,12 +1,28 @@
---
title: "Quarterly Credit Report: Fourth Quarter 2017"
sheet: https://docs.google.com/spreadsheets/d/1MjzKv6Cr-Yj9x4dJgaHzi0YT51ib4FBje-3nPfUtQOg/edit?usp=sharing
category: policy
---
{
"title": "Quarterly Credit Report: Fourth Quarter 2017",
"meta_title": "Quarterly Credit Report: Fourth Quarter 2017 - LBRY",
"url": "/credit-reports/2017-q4",
"aliases": [
"/credit-reports/2017-Q4"
],
"type": "report",
"source_url": "https://lbry.com/credit-reports/2017-q4",
"source_file": "content/credit-reports/2017-Q4.md",
"description": "Quarterly Credit Report: Fourth Quarter 2017",
"images": [
"https://lbry.com/img/og-image.png?_cache=2026-10-31"
],
"og_type": "article",
"twitter_card": "summary_large_image",
"news_feed": false,
"sheet": "https://docs.google.com/spreadsheets/d/1MjzKv6Cr-Yj9x4dJgaHzi0YT51ib4FBje-3nPfUtQOg/edit?usp=sharing",
"category": "policy",
"footer_email_href": "/cdn-cgi/l/email-protection#cea6aba2a2a18ea2acbcb7e0ada1a3",
"footer_email_code": "a3cbc6cfcfcce3cfc1d1da8dc0ccce"
}
## Summary
This quarter we moved 5,000,000 credits from cold storage. We spent 645,021 total community credits on line items detailed below. 5,000,000 operational credits were moved to markets to improve capitalization. 639,869 credits were sold to a crypto education club. No institutional credits were moved or spent.
This quarter we moved 5,000,000 Credits from cold storage. We spent 645,021 total community Credits on line items detailed below. 5,000,000 operational Credits were moved to markets to improve capitalization. 639,869 Credits were sold to a crypto education club. No institutional Credits were moved or spent.
Q4 2017 operational token use was significantly above expectations set in the previous quarterly report, but was deemed a strong time to improve the capitalization of the company. LBRY will not hesitate to deviate from previous report predictions should the circumstances warrant it.
@@ -34,9 +50,9 @@ LBRY is also exploring a more quantified and specific reward program for new You
LBRY sold 5,000,000 LBC on the open market.
LBRY sold 639,869 credits to a crypto education club.
LBRY sold 639,869 Credits to a crypto education club.
LBRY will continue to move credits to market to improve financial positioning and productive capacity. It is likely that we will move 2-5,000,000 credits this quarter.
LBRY will continue to move Credits to market to improve financial positioning and productive capacity. It is likely that we will move 2-5,000,000 Credits this quarter.
### Institutional Fund
-42
View File
@@ -1,42 +0,0 @@
---
title: "Quarterly Credit Report: First Quarter 2018"
sheet: https://docs.google.com/spreadsheets/d/17GIrc-cmoXEY9x3NYhtxd45g2mHnuJ7cjUy_TfmhLMA/edit?usp=sharing
category: policy
---
## Summary
This quarter we moved ~~no~~ 5,000,000 credits from cold storage. We spent 393,585 total community credits on line items detailed below. ~~No operational credits were moved to markets.~~ 5,000,000 operational credits were moved to markets to improve capitalization. 136,008 credits were sold to a crypto education club. No institutional credits were moved or spent. We anticipate comparable or larger total outlays in Q2 2018. Operational spending may increase, but not significantly, and community spending is likely to be higher. We will continue to incentivize new users and other beneficial behavior, which is likely to involve 500,000 to 3,000,000+ LBC. Additionally, LBRY has started a program for YouTubers that will scale up credit outlays. Finally, as it has now become de rigueur to state, no institutional outlays are expected, but a pilot program could happen.
## Overview By Fund
### Community Fund
393,585 credits were spent from the community fund, in the following areas:
| Category | Amount |
|---|---|
| Bounties | 37,130 LBRY Credits |
| User Engagement | 70,000 LBRY Credits |
| Community Management | 36,126 LBRY Credits |
| Technical Contributions | 111,273 LBRY Credits |
| New Publishers | 54,250 LBRY Credits |
| Acquisition | 37,185 LBRY Credits |
| Testing | 47,621 LBRY Credits |
### Operational Fund
* 135,000 credits were used for an employee equity swap
* LBRY sold ~~no~~ 5,000,000 LBC on the open market
* LBRY sold 136,008 to a crypto education club.
LBRY does not anticipate moving credits to market this quarter due to both market conditions and our favorable cash position. However, should market conditions or our needs change, we reserve the right to move credits to market as needed.
### Institutional Fund
No activity this quarter.
We may run our first institutional pilot programs this quarter. Any outlays from this fund this quarter will be minimal.
NOTE: This report edited for accuracy 8/2019
-39
View File
@@ -1,39 +0,0 @@
---
title: "Quarterly Credit Report: Second Quarter 2018"
sheet: https://docs.google.com/spreadsheets/d/1aRmrjTNfiKQwzW5WB_tcVJzHR-UXrCz6vHpINMfTVWs/edit?usp=sharing
category: policy
---
## Summary
This quarter we moved no credits from cold storage. We spent 738,027 total community credits on line items detailed below. No operational credits were moved to markets. We sold 327,352 credits to a crypto education club. No institutional credits were moved or spent. We anticipate comparable or larger total outlays in Q3 2018. Operational spending may increase, but not significantly, and community spending is likely to be higher. We will continue to incentivize new users and other beneficial behavior, which is likely to involve 300,000 to 1,500,000+ LBC. LBRY is also likely to form it's first institutional partnership, with spending anticipated to be around 500,000 LBC.
## Overview By Fund
### Community Fund
738,027 credits were spent from the community fund, in the following areas:
| Category | Amount |
|---|---|
| Bounties | 48,606 LBRY Credits |
| User Engagement | 275,000 LBRY Credits |
| Community Management | 35,810 LBRY Credits |
| Technical Contributions | 148,880 LBRY Credits |
| New Publishers | 108,495 LBRY Credits |
| Acquisition | 85,133 LBRY Credits |
| Testing | 3103 LBRY Credits |
| LBRY.fund | 33,333 LBRY Credits |
### Operational Fund
* LBRY sold no LBC on the open market
* LBRY sold 327,352 credits to a crypto education club.
LBRY does not anticipate moving credits to market this quarter due to both market conditions and our favorable cash position. However, should market conditions or our needs change, we reserve the right to move credits to market as needed.
### Institutional Fund
No activity this quarter.
We may run our first institutional pilot programs this quarter. Any outlays from this fund this quarter will be minimal.
+58
View File
@@ -0,0 +1,58 @@
{
"title": "Quarterly Credit Report: First Quarter 2018",
"meta_title": "Quarterly Credit Report: First Quarter 2018 - LBRY",
"url": "/credit-reports/2018-q1",
"aliases": [
"/credit-reports/2018-Q1"
],
"type": "report",
"source_url": "https://lbry.com/credit-reports/2018-q1",
"source_file": "content/credit-reports/2018-Q1.md",
"description": "Quarterly Credit Report: First Quarter 2018",
"images": [
"https://lbry.com/img/og-image.png?_cache=2026-10-31"
],
"og_type": "article",
"twitter_card": "summary_large_image",
"news_feed": false,
"sheet": "https://docs.google.com/spreadsheets/d/17GIrc-cmoXEY9x3NYhtxd45g2mHnuJ7cjUy_TfmhLMA/edit?usp=sharing",
"category": "policy",
"footer_email_href": "/cdn-cgi/l/email-protection#452d2029292a052927373c6b262a28",
"footer_email_code": "39515c55555679555b4b40175a5654"
}
## Summary
This quarter we moved ~~no~~ 5,000,000 Credits from cold storage. We spent 393,585 total community Credits on line items detailed below. ~~No operational Credits were moved to markets.~~ 5,000,000 operational Credits were moved to markets to improve capitalization. 136,008 Credits were sold to a crypto education club. No institutional Credits were moved or spent. We anticipate comparable or larger total outlays in Q2 2018. Operational spending may increase, but not significantly, and community spending is likely to be higher. We will continue to incentivize new users and other beneficial behavior, which is likely to involve 500,000 to 3,000,000+ LBC. Additionally, LBRY has started a program for YouTubers that will scale up Credit outlays. Finally, as it has now become de rigueur to state, no institutional outlays are expected, but a pilot program could happen.
## Overview By Fund
### Community Fund
393,585 Credits were spent from the community fund, in the following areas:
| Category | Amount |
|---|---|
| Bounties | 37,130 LBRY Credits |
| User Engagement | 70,000 LBRY Credits |
| Community Management | 36,126 LBRY Credits |
| Technical Contributions | 111,273 LBRY Credits |
| New Publishers | 54,250 LBRY Credits |
| Acquisition | 37,185 LBRY Credits |
| Testing | 47,621 LBRY Credits |
### Operational Fund
* 135,000 Credits were used for an employee equity swap
* LBRY sold ~~no~~ 5,000,000 LBC on the open market
* LBRY sold 136,008 to a crypto education club.
LBRY does not anticipate moving Credits to market this quarter due to both market conditions and our favorable cash position. However, should market conditions or our needs change, we reserve the right to move Credits to market as needed.
### Institutional Fund
No activity this quarter.
We may run our first institutional pilot programs this quarter. Any outlays from this fund this quarter will be minimal.
NOTE: This report edited for accuracy 8/2019
+55
View File
@@ -0,0 +1,55 @@
{
"title": "Quarterly Credit Report: Second Quarter 2018",
"meta_title": "Quarterly Credit Report: Second Quarter 2018 - LBRY",
"url": "/credit-reports/2018-q2",
"aliases": [
"/credit-reports/2018-Q2"
],
"type": "report",
"source_url": "https://lbry.com/credit-reports/2018-q2",
"source_file": "content/credit-reports/2018-Q2.md",
"description": "Quarterly Credit Report: Second Quarter 2018",
"images": [
"https://lbry.com/img/og-image.png?_cache=2026-10-31"
],
"og_type": "article",
"twitter_card": "summary_large_image",
"news_feed": false,
"sheet": "https://docs.google.com/spreadsheets/d/1aRmrjTNfiKQwzW5WB_tcVJzHR-UXrCz6vHpINMfTVWs/edit?usp=sharing",
"category": "policy",
"footer_email_href": "/cdn-cgi/l/email-protection#7a121f1616153a1618080354191517",
"footer_email_code": "325a575e5e5d725e50404b1c515d5f"
}
## Summary
This quarter we moved no Credits from cold storage. We spent 738,027 total community Credits on line items detailed below. No operational Credits were moved to markets. We sold 327,352 Credits to a crypto education club. No institutional Credits were moved or spent. We anticipate comparable or larger total outlays in Q3 2018. Operational spending may increase, but not significantly, and community spending is likely to be higher. We will continue to incentivize new users and other beneficial behavior, which is likely to involve 300,000 to 1,500,000+ LBC. LBRY is also likely to form it's first institutional partnership, with spending anticipated to be around 500,000 LBC.
## Overview By Fund
### Community Fund
738,027 Credits were spent from the community fund, in the following areas:
| Category | Amount |
|---|---|
| Bounties | 48,606 LBRY Credits |
| User Engagement | 275,000 LBRY Credits |
| Community Management | 35,810 LBRY Credits |
| Technical Contributions | 148,880 LBRY Credits |
| New Publishers | 108,495 LBRY Credits |
| Acquisition | 85,133 LBRY Credits |
| Testing | 3103 LBRY Credits |
| LBRY.fund | 33,333 LBRY Credits |
### Operational Fund
* LBRY sold no LBC on the open market
* LBRY sold 327,352 Credits to a crypto education club.
LBRY does not anticipate moving Credits to market this quarter due to both market conditions and our favorable cash position. However, should market conditions or our needs change, we reserve the right to move Credits to market as needed.
### Institutional Fund
No activity this quarter.
We may run our first institutional pilot programs this quarter. Any outlays from this fund this quarter will be minimal.
@@ -1,18 +1,34 @@
---
title: "Quarterly Credit Report: Third Quarter 2018"
sheet: https://docs.google.com/spreadsheets/d/1SqRGHtfZ7-gokvaHk8w3_72aD9zR98Sf345tGX-a7K0/edit?usp=sharing
category: policy
---
{
"title": "Quarterly Credit Report: Third Quarter 2018",
"meta_title": "Quarterly Credit Report: Third Quarter 2018 - LBRY",
"url": "/credit-reports/2018-q3",
"aliases": [
"/credit-reports/2018-Q3"
],
"type": "report",
"source_url": "https://lbry.com/credit-reports/2018-q3",
"source_file": "content/credit-reports/2018-Q3.md",
"description": "Quarterly Credit Report: Third Quarter 2018",
"images": [
"https://lbry.com/img/og-image.png?_cache=2026-10-31"
],
"og_type": "article",
"twitter_card": "summary_large_image",
"news_feed": false,
"sheet": "https://docs.google.com/spreadsheets/d/1SqRGHtfZ7-gokvaHk8w3_72aD9zR98Sf345tGX-a7K0/edit?usp=sharing",
"category": "policy",
"footer_email_href": "/cdn-cgi/l/email-protection#355d5059595a755957474c1b565a58",
"footer_email_code": "4129242d2d2e012d2333386f222e2c"
}
## Summary
This quarter we moved no credits from cold storage. We spent 958,201 total community credits on line items detailed below. Under 50,000 operational credits were used for the LBRY employee LBC purchase program. 100,000 institutional credits were spent from the institutional fund as part of a new partnership with a media organization.
This quarter we moved no Credits from cold storage. We spent 958,201 total community Credits on line items detailed below. Under 50,000 operational Credits were used for the LBRY employee LBC purchase program. 100,000 institutional Credits were spent from the institutional fund as part of a new partnership with a media organization.
We anticipate comparable or larger total outlays in Q4 2018. Operational spending may increase, but not significantly, and community spending is likely to be higher. We will continue to incentivize new users and other beneficial behavior, which is likely to involve 300,000 to 1,500,000+ LBC. It is also possible that LBRY will continue to explore usage of it's institutional fund.
## Overview By Fund
### Community Fund
958,201 credits were spent from the community fund, in the following areas:
958,201 Credits were spent from the community fund, in the following areas:
| Category | Amount |
|---|---|
@@ -33,7 +49,7 @@ LBRY also launched a more quantified and specific reward program for new YouTube
* LBRY sold no LBC on the open market
* LBRY issued 38,000 LBC to employees
LBRY does not anticipate moving credits to market this quarter due to both market conditions and our favorable cash position. However, should market conditions or our needs change, we reserve the right to move credits to market as needed.
LBRY does not anticipate moving Credits to market this quarter due to both market conditions and our favorable cash position. However, should market conditions or our needs change, we reserve the right to move Credits to market as needed.
### Institutional Fund
@@ -1,17 +1,35 @@
---
title: "Quarterly Credit Report: Fourth Quarter 2018"
sheet: https://docs.google.com/spreadsheets/d/1PSDn5igtZ51ml2Bd4lNlq9fSYgDbb-z1jePf7G-Ae6s/edit#gid=0
category: policy
---
{
"title": "Quarterly Credit Report: Fourth Quarter 2018",
"meta_title": "Quarterly Credit Report: Fourth Quarter 2018 - LBRY",
"url": "/credit-reports/2018-q4",
"aliases": [
"/credit-reports/2018-Q4"
],
"type": "report",
"source_url": "https://lbry.com/credit-reports/2018-q4",
"source_file": "content/credit-reports/2018-Q4.md",
"description": "Quarterly Credit Report: Fourth Quarter 2018",
"images": [
"https://lbry.com/img/og-image.png?_cache=2026-10-31"
],
"og_type": "article",
"twitter_card": "summary_large_image",
"news_feed": false,
"sheet": "https://docs.google.com/spreadsheets/d/1PSDn5igtZ51ml2Bd4lNlq9fSYgDbb-z1jePf7G-Ae6s/edit",
"category": "policy",
"footer_email_href": "/cdn-cgi/l/email-protection#aac2cfc6c6c5eac6c8d8d384c9c5c7",
"footer_email_code": "462e232a2a29062a24343f6825292b",
"source_sheet": "https://docs.google.com/spreadsheets/d/1PSDn5igtZ51ml2Bd4lNlq9fSYgDbb-z1jePf7G-Ae6s/edit#gid=0"
}
## Summary
This quarter we moved 118,635 operational and 240,000 institutional credits from cold storage. We spent 1,084,796 total community credits on line items detailed below. 118,635 operational credits were used for the LBRY employee LBC purchase program. 100,000 institutional credits were spent from the institutional fund as a second payment of a new media partnership.
This quarter we moved 118,635 operational and 240,000 institutional Credits from cold storage. We spent 1,084,796 total community Credits on line items detailed below. 118,635 operational Credits were used for the LBRY employee LBC purchase program. 100,000 institutional Credits were spent from the institutional fund as a second payment of a new media partnership.
We anticipate comparable or larger total outlays in Q1 2019. Operational spending may increase, but not significantly. Community spending is likely to be comparable or higher. We will continue to incentivize new users and other beneficial behavior, which is likely to involve 1,000,000+ LBC from our community fund. Institutional spending is expected to be less than 1,000,000 LBC.
## Overview By Fund
### Community Fund
1,084,796 credits were spent from the community fund, in the following areas:
1,084,796 Credits were spent from the community fund, in the following areas:
| Category | Amount |
|---|---|
@@ -30,11 +48,10 @@ As reliability and interest has been increasing, we anticipate continuing to rew
* LBRY sold no LBC on the open market
* LBRY issued 118,635 LBC to employees
LBRY does not anticipate moving credits to market this quarter due to both market conditions and our favorable cash position. However, should market conditions or our needs change, we reserve the right to move credits to market as needed.
LBRY does not anticipate moving Credits to market this quarter due to both market conditions and our favorable cash position. However, should market conditions or our needs change, we reserve the right to move Credits to market as needed.
### Institutional Fund
* 100,000 LBC re-issued for a 3Q transaction sent from the wrong fund
* 140,000 LBC issued for our media partnership with Anti-Media
-38
View File
@@ -1,38 +0,0 @@
---
title: "Quarterly Credit Report: First Quarter 2019"
sheet: https://docs.google.com/spreadsheets/d/1asnI5mGCVYb6zbcsxDhZaYu2IbXgWkGEBZcJ7VXt9XQ/edit?usp=sharing
category: policy
---
## Summary
This quarter we moved 146,289 operational credits from cold storage. We spent 1,695,734 total community credits on line items detailed below. 146,289 operational credits were used for the LBRY employee LBC purchase program.
We significantly larger community outlays throughout the rest of 2019 and starting in Q2 2019. Operational spending may increase at any time, but is not expected to increase significantly. Institutional spending is expected to be less than 1,000,000 LBC
## Overview By Fund
### Community Fund
1,695,734 credits were spent from the community fund, in the following areas:
| Category | Amount |
|---|---|
| Bounties | 328,380 |
| User Engagement | 291,000 |
| Community Engagement | 175,000 |
| Publishing | 10,000 |
| Acquisition | 286,990 |
| Testing | 1,100 |
| LBRY.fund | 203,264 |
| Swarm | 400,000 |
As reliability and interest has been increasing, we anticipate continuing to reward new users, community contributions, and other beneficial activity. This is likely to represent 1-2 million LBC.
### Operational Fund
* LBRY sold no LBC on the open market
* LBRY issued 146,289 LBC to employees
LBRY does not anticipate moving credits to market this quarter. However, should market conditions or our needs change, we reserve the right to move credits to market as needed.
### Institutional Fund
There were no institutional moves or spends this quarter.
-37
View File
@@ -1,37 +0,0 @@
---
title: "Quarterly Credit Report: Second Quarter 2019"
sheet: https://docs.google.com/spreadsheets/d/1CYQSj06imiDkPFGcVX0EpAoo42Y0oh4u2ZjSUCJFfw0/edit#gid=0
category: policy
---
## Summary
This quarter we moved no credits from cold storage. We spent 9,823,975 total community credits on line items detailed below. 100,320 operational credits were used for the LBRY team member LBC purchase program. 140,000 credits from the institutional fund were used for an ongoing media partnership.
We anticipate significantly larger community outlays throughout the rest of 2019. This quarter’s community outlay was significantly impacted by an influx of YouTube channel syncs starting in mid-June. Operational spending may increase at any time, but is not expected to increase significantly. Institutional spending is expected to be less than 1,000,000 LBC.
## Overview By Fund
### Community Fund
9,823,975 credits were spent from the community fund, in the following areas:
| Category | Amount |
|---|---|
| Bounties | 205,700 |
| User Engagement | 7,196,200 |
| Community Engagement | 160,150 |
| Publishing | 62,100 |
| Acquisition | 273.300 |
| Testing | 10 |
| LBRY.fund | 330,800 |
| Swarm | 1,595,715|
As interest has been increasing, we anticipate continuing to reward new users, youtube channel owners, community contributions, and other beneficial activity. We are setting 7.5 million LBC as the expected spend this quarter, but it could easily be substantially lower or higher.
### Operational Fund
* LBRY sold no LBC on the open market
* LBRY issued 100,320 LBC to employees
LBRY does not anticipate moving credits to market this quarter. However, should market conditions or our needs change, we reserve the right to move credits to market as needed.
### Institutional Fund
140,000 credits were moved as part of the Antimedia partner deal.
-37
View File
@@ -1,37 +0,0 @@
---
title: "Quarterly Credit Report: Third Quarter 2019"
sheet: https://docs.google.com/spreadsheets/d/1MNUTEUdQNKKxumjvcpW56DcDhVqvdzfCZA0rzD0MTMI/edit#gid=799352054
category: policy
---
## Summary
This quarter we moved no credits from cold storage. We spent 7,959,189 total community credits on line items detailed below. 304,425 operational credits were used for the LBRY team member LBC purchase program. No institutional credits were moved.
We anticipate significantly larger community outlays throughout the rest of 2019. Operational spending may increase at any time, but is not expected to increase significantly. Institutional spending is expected to be less than 1,000,000 LBC.
## Overview By Fund
### Community Fund
7,959,189 credits were spent from the community fund, in the following areas:
| Category | Amount |
|---|---|
| Bounties | 385,100 |
| User Engagement | 4,662,600 |
| Community Engagement | 432,000 |
| Publishing | 52,198 |
| Acquisition | 378,286 |
| Testing | 105 |
| LBRY.fund | 332,900 |
| Swarm | 1,725,000 |
As interest has been increasing, we anticipate continuing to reward new users, youtube channel owners, community contributions, and other beneficial activity. We are setting 7.5 million LBC as the expected spend this quarter, but it could easily be substantially lower or higher.
### Operational Fund
* LBRY sold no LBC on the open market
* LBRY issued 304,425 LBC to employees
LBRY does not anticipate moving credits to market this quarter. However, should market conditions or our needs change, we reserve the right to move credits to market as needed.
### Institutional Fund
No credits were moved or used.
+55
View File
@@ -0,0 +1,55 @@
{
"title": "Quarterly Credit Report: First Quarter 2019",
"meta_title": "Quarterly Credit Report: First Quarter 2019 - LBRY",
"url": "/credit-reports/2019-q1",
"aliases": [
"/credit-reports/2019-Q1"
],
"type": "report",
"source_url": "https://lbry.com/credit-reports/2019-q1",
"source_file": "content/credit-reports/2019-Q1.md",
"description": "Quarterly Credit Report: First Quarter 2019",
"images": [
"https://lbry.com/img/og-image.png?_cache=2026-10-31"
],
"og_type": "article",
"twitter_card": "summary_large_image",
"news_feed": false,
"sheet": "https://docs.google.com/spreadsheets/d/1asnI5mGCVYb6zbcsxDhZaYu2IbXgWkGEBZcJ7VXt9XQ/edit?usp=sharing",
"category": "policy",
"footer_email_href": "/cdn-cgi/l/email-protection#aec6cbc2c2c1eec2ccdcd780cdc1c3",
"footer_email_code": "d3bbb6bfbfbc93bfb1a1aafdb0bcbe"
}
## Summary
This quarter we moved 146,289 operational Credits from cold storage. We spent 1,695,734 total community Credits on line items detailed below. 146,289 operational Credits were used for the LBRY employee LBC purchase program.
We significantly larger community outlays throughout the rest of 2019 and starting in Q2 2019. Operational spending may increase at any time, but is not expected to increase significantly. Institutional spending is expected to be less than 1,000,000 LBC
## Overview By Fund
### Community Fund
1,695,734 Credits were spent from the community fund, in the following areas:
| Category | Amount |
|---|---|
| Bounties | 328,380 |
| User Engagement | 291,000 |
| Community Engagement | 175,000 |
| Publishing | 10,000 |
| Acquisition | 286,990 |
| Testing | 1,100 |
| LBRY.fund | 203,264 |
| Swarm | 400,000 |
As reliability and interest has been increasing, we anticipate continuing to reward new users, community contributions, and other beneficial activity. This is likely to represent 1-2 million LBC.
### Operational Fund
* LBRY sold no LBC on the open market
* LBRY issued 146,289 LBC to employees
LBRY does not anticipate moving Credits to market this quarter. However, should market conditions or our needs change, we reserve the right to move Credits to market as needed.
### Institutional Fund
There were no institutional moves or spends this quarter.
+55
View File
@@ -0,0 +1,55 @@
{
"title": "Quarterly Credit Report: Second Quarter 2019",
"meta_title": "Quarterly Credit Report: Second Quarter 2019 - LBRY",
"url": "/credit-reports/2019-q2",
"aliases": [
"/credit-reports/2019-Q2"
],
"type": "report",
"source_url": "https://lbry.com/credit-reports/2019-q2",
"source_file": "content/credit-reports/2019-Q2.md",
"description": "Quarterly Credit Report: Second Quarter 2019",
"images": [
"https://lbry.com/img/og-image.png?_cache=2026-10-31"
],
"og_type": "article",
"twitter_card": "summary_large_image",
"news_feed": false,
"sheet": "https://docs.google.com/spreadsheets/d/1CYQSj06imiDkPFGcVX0EpAoo42Y0oh4u2ZjSUCJFfw0/edit",
"category": "policy",
"footer_email_href": "/cdn-cgi/l/email-protection#fb939e979794bb97998982d5989496",
"footer_email_code": "29414c45454669454b5b50074a4644",
"source_sheet": "https://docs.google.com/spreadsheets/d/1CYQSj06imiDkPFGcVX0EpAoo42Y0oh4u2ZjSUCJFfw0/edit#gid=0"
}
## Summary
This quarter we moved no Credits from cold storage. We spent 9,823,975 total community Credits on line items detailed below. 100,320 operational Credits were used for the LBRY team member LBC purchase program. 140,000 Credits from the institutional fund were used for an ongoing media partnership.
We anticipate significantly larger community outlays throughout the rest of 2019. This quarter’s community outlay was significantly impacted by an influx of YouTube channel syncs starting in mid-June. Operational spending may increase at any time, but is not expected to increase significantly. Institutional spending is expected to be less than 1,000,000 LBC.
## Overview By Fund
### Community Fund
9,823,975 Credits were spent from the community fund, in the following areas:
| Category | Amount |
|---|---|
| Bounties | 205,700 |
| User Engagement | 7,196,200 |
| Community Engagement | 160,150 |
| Publishing | 62,100 |
| Acquisition | 273.300 |
| Testing | 10 |
| LBRY.fund | 330,800 |
| Swarm | 1,595,715|
As interest has been increasing, we anticipate continuing to reward new users, youtube channel owners, community contributions, and other beneficial activity. We are setting 7.5 million LBC as the expected spend this quarter, but it could easily be substantially lower or higher.
### Operational Fund
* LBRY sold no LBC on the open market
* LBRY issued 100,320 LBC to employees
LBRY does not anticipate moving Credits to market this quarter. However, should market conditions or our needs change, we reserve the right to move Credits to market as needed.
### Institutional Fund
140,000 Credits were moved as part of the Antimedia partner deal.
+55
View File
@@ -0,0 +1,55 @@
{
"title": "Quarterly Credit Report: Third Quarter 2019",
"meta_title": "Quarterly Credit Report: Third Quarter 2019 - LBRY",
"url": "/credit-reports/2019-q3",
"aliases": [
"/credit-reports/2019-Q3"
],
"type": "report",
"source_url": "https://lbry.com/credit-reports/2019-q3",
"source_file": "content/credit-reports/2019-Q3.md",
"description": "Quarterly Credit Report: Third Quarter 2019",
"images": [
"https://lbry.com/img/og-image.png?_cache=2026-10-31"
],
"og_type": "article",
"twitter_card": "summary_large_image",
"news_feed": false,
"sheet": "https://docs.google.com/spreadsheets/d/1MNUTEUdQNKKxumjvcpW56DcDhVqvdzfCZA0rzD0MTMI/edit",
"category": "policy",
"footer_email_href": "/cdn-cgi/l/email-protection#ff979a939390bf939d8d86d19c9092",
"footer_email_code": "cea6aba2a2a18ea2acbcb7e0ada1a3",
"source_sheet": "https://docs.google.com/spreadsheets/d/1MNUTEUdQNKKxumjvcpW56DcDhVqvdzfCZA0rzD0MTMI/edit#gid=799352054"
}
## Summary
This quarter we moved no Credits from cold storage. We spent 7,959,189 total community Credits on line items detailed below. 304,425 operational Credits were used for the LBRY team member LBC purchase program. No institutional Credits were moved.
We anticipate significantly larger community outlays throughout the rest of 2019. Operational spending may increase at any time, but is not expected to increase significantly. Institutional spending is expected to be less than 1,000,000 LBC.
## Overview By Fund
### Community Fund
7,959,189 Credits were spent from the community fund, in the following areas:
| Category | Amount |
|---|---|
| Bounties | 385,100 |
| User Engagement | 4,662,600 |
| Community Engagement | 432,000 |
| Publishing | 52,198 |
| Acquisition | 378,286 |
| Testing | 105 |
| LBRY.fund | 332,900 |
| Swarm | 1,725,000 |
As interest has been increasing, we anticipate continuing to reward new users, youtube channel owners, community contributions, and other beneficial activity. We are setting 7.5 million LBC as the expected spend this quarter, but it could easily be substantially lower or higher.
### Operational Fund
* LBRY sold no LBC on the open market
* LBRY issued 304,425 LBC to employees
LBRY does not anticipate moving Credits to market this quarter. However, should market conditions or our needs change, we reserve the right to move Credits to market as needed.
### Institutional Fund
No Credits were moved or used.
+57
View File
@@ -0,0 +1,57 @@
{
"title": "Quarterly Credit Report: Fourth Quarter 2019",
"meta_title": "Quarterly Credit Report: Fourth Quarter 2019 - LBRY",
"url": "/credit-reports/2019-q4",
"aliases": [
"/credit-reports/2019-Q4"
],
"type": "report",
"source_url": "https://lbry.com/credit-reports/2019-q4",
"source_file": "content/credit-reports/2019-Q4.md",
"description": "Quarterly Credit Report: Fourth Quarter 2019",
"images": [
"https://lbry.com/img/og-image.png?_cache=2026-10-31"
],
"og_type": "article",
"twitter_card": "summary_large_image",
"news_feed": false,
"sheet": "https://docs.google.com/spreadsheets/d/1H7uYR5XLNlf4Y-elrIS8mHdv4QnVQ-7BbM8YAR_u_W0/edit",
"category": "policy",
"footer_email_href": "/cdn-cgi/l/email-protection#d5bdb0b9b9ba95b9b7a7acfbb6bab8",
"footer_email_code": "4a222f2626250a2628383364292527",
"source_sheet": "https://docs.google.com/spreadsheets/d/1H7uYR5XLNlf4Y-elrIS8mHdv4QnVQ-7BbM8YAR_u_W0/edit#gid=799352054"
}
## Summary
This quarter we moved no Credits from cold storage. We spent 9,397,854 total community Credits on line items detailed below. 269,328 operational Credits were used for the LBRY team member LBC purchase program. No institutional Credits were moved.
We anticipate significantly larger community outlays throughout 2020. Operational spending may increase at any time, but is not expected to increase significantly. Institutional spending is expected to be less than 1,000,000 LBC.
## Overview By Fund
### Community Fund
9,397,854 Credits were spent from the community fund, in the following areas:
| Category | Amount |
|---|---|
| Bounties | 1,196,600 |
| User Engagement | 4,250,000 |
| Community Engagement | 379,000 |
| Publishing | 11,100 |
| Acquisition | 1,073,000 |
| Testing | 8,304 |
| LBRY.fund | 493,500 |
| Swarm | 1,986,350 |
| Other | 162,000 |
As interest has been increasing, we anticipate continuing to reward new users, youtube channel owners, community contributions, and other beneficial activities. We are setting 7.5 million LBC as the expected spend this quarter, but it could easily be substantially lower or higher.
### Operational Fund
* LBRY sold no LBC on the open market
* LBRY issued 269,328 LBC to employees
LBRY may move Credits to market if conditions allow.
### Institutional Fund
No Credits were moved or used.
+61
View File
@@ -0,0 +1,61 @@
{
"title": "Quarterly Credit Report: First Quarter 2020",
"meta_title": "Quarterly Credit Report: First Quarter 2020 - LBRY",
"url": "/credit-reports/2020-q1",
"aliases": [
"/credit-reports/2020-Q1"
],
"type": "report",
"source_url": "https://lbry.com/credit-reports/2020-q1",
"source_file": "content/credit-reports/2020-Q1.md",
"description": "Quarterly Credit Report: First Quarter 2020",
"images": [
"https://lbry.com/img/og-image.png?_cache=2026-10-31"
],
"og_type": "article",
"twitter_card": "summary_large_image",
"news_feed": false,
"sheet": "https://docs.google.com/spreadsheets/d/12_4RFTiEjV1RVdhOOPURa724ZSS8RDBxfnn8MiOvEDQ/edit?usp=sharing",
"category": "policy",
"footer_email_href": "/cdn-cgi/l/email-protection#afc7cac3c3c0efc3cdddd681ccc0c2",
"footer_email_code": "b6ded3dadad9f6dad4c4cf98d5d9db"
}
## Summary
This quarter we moved 10MM operational, 23MM community Credits, and 3MM institutional Credits from master cold storage. We spent 16,026,383 total community Credits on line items detailed below. 126,352 operational Credits were used for the LBRY team member LBC purchase program. 3MM institutional Credits were granted to lbry.org. We anticipate similar community outlays throughout 2020. Operational spending may increase at any time, but is not expected to increase significantly. Institutional spending could be substantial at any time, but would be expected to be coupled with sensible and sensitive distribution rules.
## Overview By Fund
### Community Fund
23,026,383 Credits were spent from the community fund, in the following areas:
| Category | Amount |
|---|---|
| Bounties | 743,036 |
| User Engagement | 9,056,100 |
| Community Engagement | 370,847 |
| Publishing | 70,100 |
| Acquisition | 835,700 |
| Testing | 100 |
| Swarm | 664,000 |
| LBRY funds staked | 4,115,000 |
| Special Creator USB Sticks | 7,000,000 |
As interest has been increasing, we anticipate continuing to reward new users, YouTube channel owners, community contributions, and other beneficial activities.
Rewards are likely to be adjusted downwards, even if current growth flatlines rather than continues. Swarm funds are from a legacy program and are expected to be zero moving forward, and then removed.
We are setting 10,000,000 million LBC as the expected spend this quarter, but it could easily be substantially lower or higher.
It should be noted that LBRY funds staked are recoverable.
### Operational Fund
* LBRY sold 2,971,644 LBC on the open market
* LBRY issued 126,352 LBC to employees
LBRY may move Credits to market if conditions allow. LBRY is likely to announce new ways to acquire LBC in Q2 2020.
### Institutional Fund
3MM Institutional were granted to lbry.org, an independently run and organized entity.
+65
View File
@@ -0,0 +1,65 @@
{
"title": "Quarterly Credit Report: Second Quarter 2020",
"meta_title": "Quarterly Credit Report: Second Quarter 2020 - LBRY",
"url": "/credit-reports/2020-q2",
"aliases": [
"/credit-reports/2020-Q2"
],
"type": "report",
"source_url": "https://lbry.com/credit-reports/2020-q2",
"source_file": "content/credit-reports/2020-Q2.md",
"description": "Quarterly Credit Report: Second Quarter 2020",
"images": [
"https://lbry.com/img/og-image.png?_cache=2026-10-31"
],
"og_type": "article",
"twitter_card": "summary_large_image",
"news_feed": false,
"sheet": "https://docs.google.com/spreadsheets/d/1Ckcba-AsoC1GuG6xGYR7LbpOiMAqLjdjhDywvt4MrdA/edit",
"category": "policy",
"footer_email_href": "/cdn-cgi/l/email-protection#bcd4d9d0d0d3fcd0decec592dfd3d1",
"footer_email_code": "fe969b929291be929c8c87d09d9193",
"source_sheet": "https://docs.google.com/spreadsheets/d/1Ckcba-AsoC1GuG6xGYR7LbpOiMAqLjdjhDywvt4MrdA/edit#gid=799352054"
}
## Summary
This quarter we moved 5MM operational, 30MM community Credits, and 50MM institutional Credits from master cold storage. We spent 25,445,103 total community Credits on line items detailed below. 7,822,697 operational Credits were used for the LBRY team member LBC purchase program, contract obligations, and secondary market sales. 40MM institutional Credits were loaned to Altonomy for market liquidity.
Community outlays this quarter were unprecedented due to tremendous growth in new users and views, especially in May (nearly 9M). Rewards were decreased accordingly in June, and are expected to be lowered to 2-3M per month.
Operational spending may increase or decrease at any time, but is not expected to increase significantly in Q3. Institutional spending could be substantial at any time, but would be expected to be coupled with sensible and sensitive distribution rules
## Overview By Fund
### Community Fund
25,445,103 Credits were spent from the community fund, in the following areas:
| Category | Amount |
|---|---|
| Bounties | 570,380 |
| User Engagement | 21,733,000 |
| Community Engagement | 449,507 |
| Publishing | 78,700 |
| Acquisition | 1,702,033 |
| Testing | 11,484 |
| Swarm | 40,000 |
| LBRY funds staked | 860,000 |
Several hundred thousand users received rewards and nearly 10,000 new YouTubers enrolled in our partner program. This resulted in a much more substantial outlay than anticipated.
Rewards were adjusted doward in June and are expected to continue to be adjusted downward. The view reward program will be adjusted to use a fixed size ([more](lbry://@lbry#3f/monetizationtwopointoh#5)), and rewards for new YouTube syncs based on audience size will also change.
We still anticipate spending over 10,000,000 LBC this quarter, with a wide range of possibilities.
### Operational Fund
* LBRY sold 7,028,356 LBC on the open market
* LBRY issued 359,341 LBC to employees
* LBRY sold 435,000 LBC via Moonpay.io
LBRY may move Credits to market if conditions allow.
### Institutional Fund
40MM Institutional Credits were loaned to Altonomy, an independent market-making firm, to provide liquidity. More at [lbry://@lbry#3f/market-making](lbry://@lbry#3f/market-making).
+59
View File
@@ -0,0 +1,59 @@
{
"title": "Quarterly Credit Report: Third Quarter 2020",
"meta_title": "Quarterly Credit Report: Third Quarter 2020 - LBRY",
"url": "/credit-reports/2020-q3",
"aliases": [
"/credit-reports/2020-Q3"
],
"type": "report",
"source_url": "https://lbry.com/credit-reports/2020-q3",
"source_file": "content/credit-reports/2020-Q3.md",
"description": "Quarterly Credit Report: Third Quarter 2020",
"images": [
"https://lbry.com/img/og-image.png?_cache=2026-10-31"
],
"og_type": "article",
"twitter_card": "summary_large_image",
"news_feed": false,
"sheet": "https://docs.google.com/spreadsheets/d/1t3zVnBgXNy1fQLdEVw7jr7x5izVxZ3tlQvBgizqvcGE/edit?usp=sharing",
"category": "policy",
"footer_email_href": "/cdn-cgi/l/email-protection#0e666b6262614e626c7c77206d6163",
"footer_email_code": "422a272e2e2d022e20303b6c212d2f"
}
## Summary
This quarter we moved 10MM operational, 20MM community Credits, and no institutional Credits from master cold storage. We spent 13,455,301 total community Credits on line items detailed below. 10,217,739 operational Credits were used for the LBRY team member LBC purchase program, contract obligations, and secondary market sales.
Operational spending may increase or decrease at any time, but is not expected to increase significantly in Q4. Institutional spending could be substantial at any time, but would be expected to be coupled with sensible and sensitive distribution rules
## Overview By Fund
### Community Fund
13,455,301 Credits were spent from the community fund, in the following areas:
| Category | Amount |
|---|---|
| Bounties | 693,065 |
| User Engagement | 7,551,200 |
| Community Engagement | 664,168 |
| Publishing | 49,350 |
| Acquisition | 3,295,018 |
| Testing | 1,000 |
| Swarm | 1,500 |
| LBRY funds staked | 1,200,000 |
We still anticipate spending around 12,000,000 LBC this quarter, with a wide range of possibilities. We’re trying to bring community spending under 3,000,000 LBC per month, but it may remain over this until YouTube monthly payouts end in Q1 2021.
### Operational Fund
* LBRY sold 8,000,000 LBC on the open market
* LBRY issued 367,739 LBC to employees
* LBRY sold 1,350,000 LBC via Moonpay.io
* LBRY sold 500,000 LBC to CoinEx for liquidity
LBRY may move Credits to market if conditions allow.
### Institutional Fund
No Institutional Credits were moved.
+36
View File
@@ -0,0 +1,36 @@
{
"title": "Get LBRY Android",
"url": "/android",
"type": "download-listing",
"source_url": "https://lbry.com/android",
"description": "Experience content freedom! Download the latest version of LBRY for Windows, mac OS, or Linux.",
"images": [
"https://lbry.com/img/og-image.png?_cache=2026-10-31"
],
"og_type": "article",
"twitter_card": "app",
"news_feed": false,
"twitter_app": [
{
"name": "twitter:app:country",
"content": "US"
},
{
"name": "twitter:app:name:googleplay",
"content": "LBRY beta"
},
{
"name": "twitter:app:id:googleplay",
"content": "io.lbry.browser"
},
{
"name": "twitter:app:url:googleplay",
"content": "https://play.google.com/store/apps/details?id=io.lbry.browser"
}
],
"footer_email_href": "/cdn-cgi/l/email-protection#80e8e5ececefc0ece2f2f9aee3efed",
"footer_email_code": "177f727b7b78577b75656e3974787a",
"meta_title": "Get LBRY Android",
"download_os": "android"
}
+36
View File
@@ -0,0 +1,36 @@
{
"title": "Get Odysee for iOS - LBRY",
"url": "/ios",
"type": "download-listing",
"source_url": "https://lbry.com/ios",
"description": "Experience content freedom! Download the latest version of LBRY for Windows, mac OS, or Linux.",
"images": [
"https://lbry.com/img/og-image.png?_cache=2026-10-31"
],
"og_type": "article",
"twitter_card": "app",
"news_feed": false,
"twitter_app": [
{
"name": "twitter:app:country",
"content": "US"
},
{
"name": "twitter:app:name:googleplay",
"content": "LBRY beta"
},
{
"name": "twitter:app:id:googleplay",
"content": "io.lbry.browser"
},
{
"name": "twitter:app:url:googleplay",
"content": "https://play.google.com/store/apps/details?id=io.lbry.browser"
}
],
"footer_email_href": "/cdn-cgi/l/email-protection#533b363f3f3c133f31212a7d303c3e",
"footer_email_code": "533b363f3f3c133f31212a7d303c3e",
"meta_title": "Get Odysee for iOS - LBRY",
"download_os": "ios"
}
+36
View File
@@ -0,0 +1,36 @@
{
"title": "Get LBRY Desktop for Linux",
"url": "/linux",
"type": "download-listing",
"source_url": "https://lbry.com/linux",
"description": "Experience content freedom! Download the latest version of LBRY for Windows, mac OS, or Linux.",
"images": [
"https://lbry.com/img/og-image.png?_cache=2026-10-31"
],
"og_type": "article",
"twitter_card": "app",
"news_feed": false,
"twitter_app": [
{
"name": "twitter:app:country",
"content": "US"
},
{
"name": "twitter:app:name:googleplay",
"content": "LBRY beta"
},
{
"name": "twitter:app:id:googleplay",
"content": "io.lbry.browser"
},
{
"name": "twitter:app:url:googleplay",
"content": "https://play.google.com/store/apps/details?id=io.lbry.browser"
}
],
"footer_email_href": "/cdn-cgi/l/email-protection#e088858c8c8fa08c829299ce838f8d",
"footer_email_code": "6e060b0202012e020c1c17400d0103",
"meta_title": "Get LBRY Desktop for Linux",
"download_os": "linux"
}
+36
View File
@@ -0,0 +1,36 @@
{
"title": "Get LBRY Desktop for macOS",
"url": "/osx",
"type": "download-listing",
"source_url": "https://lbry.com/osx",
"description": "Experience content freedom! Download the latest version of LBRY for Windows, mac OS, or Linux.",
"images": [
"https://lbry.com/img/og-image.png?_cache=2026-10-31"
],
"og_type": "article",
"twitter_card": "app",
"news_feed": false,
"twitter_app": [
{
"name": "twitter:app:country",
"content": "US"
},
{
"name": "twitter:app:name:googleplay",
"content": "LBRY beta"
},
{
"name": "twitter:app:id:googleplay",
"content": "io.lbry.browser"
},
{
"name": "twitter:app:url:googleplay",
"content": "https://play.google.com/store/apps/details?id=io.lbry.browser"
}
],
"footer_email_href": "/cdn-cgi/l/email-protection#ef878a838380af838d9d96c18c8082",
"footer_email_code": "eb838e878784ab87899992c5888486",
"meta_title": "Get LBRY Desktop for macOS",
"download_os": "osx"
}
+36
View File
@@ -0,0 +1,36 @@
{
"title": "Get LBRY Desktop for Windows",
"url": "/windows",
"type": "download-listing",
"source_url": "https://lbry.com/windows",
"description": "Experience content freedom! Download the latest version of LBRY for Windows, mac OS, or Linux.",
"images": [
"https://lbry.com/img/og-image.png?_cache=2026-10-31"
],
"og_type": "article",
"twitter_card": "app",
"news_feed": false,
"twitter_app": [
{
"name": "twitter:app:country",
"content": "US"
},
{
"name": "twitter:app:name:googleplay",
"content": "LBRY beta"
},
{
"name": "twitter:app:id:googleplay",
"content": "io.lbry.browser"
},
{
"name": "twitter:app:url:googleplay",
"content": "https://play.google.com/store/apps/details?id=io.lbry.browser"
}
],
"footer_email_href": "/cdn-cgi/l/email-protection#5139343d3d3e113d3323287f323e3c",
"footer_email_code": "81e9e4ededeec1ede3f3f8afe2eeec",
"meta_title": "Get LBRY Desktop for Windows",
"download_os": "windows"
}
+43
View File
@@ -0,0 +1,43 @@
{
"title": "LBRY US 2257 Statement",
"url": "/faq/2257",
"type": "faq",
"source_url": "https://lbry.com/faq/2257",
"description": "LBRY & US 2257 18 USC 2257 Statement: LBRY.COM / LBRY.TV LBRY.COM / LBRY.TV is not a producer (primary or…",
"images": [
"https://lbry.com/img/og-faq.png?_cache=2026-10-31"
],
"og_type": "article",
"twitter_card": "summary_large_image",
"news_feed": false,
"footer_email_href": "/cdn-cgi/l/email-protection#3b535e5757547b5759494215585456",
"footer_email_code": "aec6cbc2c2c1eec2ccdcd780cdc1c3",
"meta_title": "LBRY US 2257 Statement",
"category": "other",
"source_file": "content/faq/2257.md",
"edit_url": "https://github.com/lbryio/lbry.com/tree/master/content/faq/2257.md",
"protected_emails": {
"hello@lbry.com": {
"address": "hello@lbry.com",
"text_only": true,
"text_code": "4028252c2c2f002c2232396e232f2d",
"standalone_href": "/cdn-cgi/l/email-protection"
}
},
"weight": 81
}
## LBRY & US 2257
18 USC 2257 Statement: LBRY.COM / LBRY.TV
LBRY.COM / LBRY.TV is not a producer (primary or secondary) of any and all of the content found on the any LBRY INC server or website (LBRY.COM / LBRY.TV). With respect to the records as per 18 USC 2257 for any and all content found on this site, please kindly direct your request to the site for which the content was produced.
LBRY.COM / LBRY.TV is a video sharing protocol and website which allows for the uploading, sharing and general viewing of various types of adult content and while LBRY.COM / LBRY.TV does the best it can with verifying compliance, it may not be 100% accurate.
LBRY.COM / LBRY.TV abides by the following procedures to ensure compliance:
Requiring all users to be 18 years of age to upload videos.
When uploading, user must verify the content; assure he/she is 18 years of age; certify that he/she keeps records of the models in the content and that they are over 18 years of age.
For further assistance and/or information in finding the content's originating site, please contact hello@lbry.com
LBRY.COM / LBRY.TV allows content to be flagged as inappropriate. Should any content be flagged as illegal, unlawful, harassing, harmful, offensive or various other reasons, LBRY.COM / LBRY.TV shall remove it from the site without delay.
-26
View File
@@ -1,26 +0,0 @@
---
title: How does the Bounty Program work?
category: other
---
You can earn LBRY Credits (LBC) for completing tasks as part of the LBRY Bounty Program.
### What bounties are available?
All bounties can be seen on the [bounty home page](/bounty).
### How do I claim a bounty?
To claim a bounty, please email [bounty@lbry.com](mailto:bounty@lbry.com). Please include a link to the bounty. If it is programming-related, please include a link to the pull request.
### How do I get compensated?
People who complete bounties are rewarded LBRY credits (LBC). These credits will be transferred to a LBRY wallet address of your choice and are yours, with no restrictions to do as you like.
### I have questions about a specific bounty or seek assistance in completing a bounty.
The best place to get real-time help is our [Discord chat](https://chat.lbry.com). You can also email our bounty team [bounty@lbry.com](mailto:bounty@lbry.com).
### I want to complete a bounty that is not listed.
Please send an email to our bounty team at [bounty@lbry.com](mailto:bounty@lbry.com).
@@ -1,6 +0,0 @@
---
title: Contributing to LBRY
category: other
---
This Document now lives at https://lbry.tech/contribute
@@ -1,10 +0,0 @@
---
title: What is LBRY's development status right now? Plans for the future?
category: developer
---
LBRY is currently in invite-only beta, with desktop apps for Linux, MacOS, and a pre-release version of Windows. There are approximately 5K active users and hundreds of content creators. The network already hosts big-name content like the [feature film *It's A Disaster*](/news/launch-a-disaster) and videos from [Adult Swim's MillionDollarExtreme](/news/mde-on-lbry). We announce new featured content every Thursday on our [blog](/news), [Twitter](https://twitter.com/lbryio), and [Facebook](https://www.facebook.com/lbryio).
The waitlist to get into the beta is ~150K people long. This shocks even us, and we're racing to get the user experience and backend technologies to a level where we're comfortable opening the beta to everyone. The target for open beta is this winter. Mushy target, we know, but these things are hard to time.
In the meantime, we could use your encouragement. This is a difficult project that cannot succeed without people demonstrating they want an alternative to Silicon Valley megacorp media services. So [join the beta](/get), [share our blog posts](/news), and [join our subreddit /r/lbry](https://www.reddit.com/r/lbry). Your excitement is like Red Bull to our weary coders!
@@ -1,6 +0,0 @@
---
title: How do I stop LBRY from the command line?
category: setup
---
You can press `ctrl-c` or run `lbrynet-cli daemon_stop`. It is natural for the program to take 2-3 seconds to close.
-49
View File
@@ -1,49 +0,0 @@
//archiving for now while shapeshift is not implemented in the app (https://github.com/lbryio/lbry-desktop/issues/2019)
---
title: How can I convert my crypto into LBC?
category: wallet
---
The ability to convert your cryptoassets into LBRY Credits (LBC) is available directly within the LBRY app, powered by [ShapeShift](https://info.shapeshift.io/about). LBRY Inc. does not handle any of the incoming funds, and the LBC are sent from ShapeShift directly.
*Note: ShapeShift is unavailable in New York and Washington (and possibly surrounding areas based on IP geolocation). You will see an `HTTP status code: 403` error if this happens. Please see [ShapeShift](https://shapeshift.io) for more information.*
## Convert Crypto to LBC
1. Open the LBRY app, Click on the Wallet tab to expand. Click on **Get Credits**
![credit](https://spee.ch/f/credit.jpeg)
2. In the **Convert Crypto to LBC** section, choose from BCH, BTC, DASH, ETH, LTC or XMR to convert into LBC
![credits](https://spee.ch/3/rew.png)
3. Review the given rate of exchange and min/max amount. ShapeShift charges a small [fee](https://info.shapeshift.io/miner-fee) for the transaction
4. Enter the return address for the cryptoasset in case something were to go wrong with the process (if the address is not provided, you'll need to contact ShapeShift about your refund).
![credits](https://spee.ch/d/creditk.jpeg)
5. Click **Begin Conversion** to start your request.
![beginconversion](https://spee.ch/d/reww.png)
6.You will now be presented with the deposit address for your conversion.
![depositaddress](https://spee.ch/7/depo.jpeg)
7. Using your crypto wallet, send any amount between the min and max to the deposit address specified. Click **VIEW THE STATUS ON SHAPESHIFT.IO** to track in real-time. You can also bookmark this transaction for your records. We are not currently storing any information about the transaction after it confirms and you receive the LBC in your wallet.
<img src="https://spee.ch/4/convertcrypto4.JPG" width="80%" height="80%">
8. Once your transaction is confirmed, you will be presented with the completion screen. Click **Done** to start a new conversion.
<img src="https://spee.ch/2/convertcrypto5.JPG" width="80%" height="80%">
9. Verify that LBC has been received on the **Transaction** tab under wallet. It should be updated in the transaction history.
<img src="https://spee.ch/e4821232d4c60540e3a6889c42470ba2b7f04487/verifr.jpeg"/>
10. Thanks for acquiring some LBC!
### I need help with my conversion, who can I reach out to?
If you initiated your conversion but are having trouble sending the cryptoasset or receiving LBC, please reach out to [ShapeShift directly](https://shapeshift.zendesk.com/hc/en-us/requests/new) as LBRY is not responsible for the conversion process.
### How else can I acquire LBRY Credits?
Please see our [earn credits](/faq/earn-credits) FAQ on how to acquire additional LBC.
### I need help with the LBRY app, who can I reach out to?
Of course, we are always here to help! Check out our [help page](/faq/support) on how to reach us.
-36
View File
@@ -1,36 +0,0 @@
---
title: How do I see the list of API functions I can call, and how do I call them?
category: developer
---
**This FAQ is subsumed by specific read-mes and lbry.tech**
## The LBRY API
The best way to learn how to use the LBRY API is to go through our [quickstart](/quickstart).
A full list of API calls provided by LBRY is available in [the API documentation](/api).
If you're new to LBRY, this is probably the API you want.
## The LBRY Blockchain API (lbrycrd)
Ensure that `lbrycrd` is running with the `-server` flag, which enables the JSON-RPC API. Then use one of the following methods to make API calls.
Many (though not all) of the calls are the same as those for bitcoin core, which are
documented [here](https://en.bitcoin.it/wiki/Original_Bitcoin_client/API_calls_list). To see the full list of API calls, use the `help` API call.
### lbrycrd-cli
lbrycrd-cli help
### curl
curl --user USER:PASSWORD --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "help", "params": [] }' -H 'content-type: text/plain;' http://127.0.0.1:9245/
- `USER` and `PASSWORD` can be found in your lbrycrd.conf file.
- The `method` field can be any of the supported methods like `getbalance` or `getnewaddress`.
- `9245` is the default port used, but if you chose a custom port for the server, you'd need to use that instead.
- If the command accepts parameters, they can be passed inside the `params` array.
See Also: [important directories](/faq/lbry-directories).
@@ -1,82 +0,0 @@
---
title: The ClaimTrie Implementation in LBRY
category: developer
---
## Introduction
This document describes the implementation detail of the ClaimTrie in LBRY. The ClaimTrie is the data structure which LBRY uses to store claims to names. It uses a [Trie](https://en.wikipedia.org/wiki/Trie) to efficiently store all claimed names, which can then be hashed the same way a [Merkle Tree](https://en.wikipedia.org/wiki/Merkle_tree) is hashed. The root hash of the ClaimTrie is stored in the blockheader of each LBRY block, enabling nodes in the LBRY network to efficiently and securely validate the state of the ClaimTrie.
Bids to claim a name must win out against other claims for the same name before they can be inserted into the ClaimTrie. The short summary is that the bid with the most LBRY credits assigned to it will win the right to claim a name, but the implementation detail is more involved and, this is what we aim to cover in this document. Bids to claim a name have four properties tied to it :
1. *Name* : The name is a human-readable address and is the property that the bids compete to obtain.
2. *Value* : The value is the data that is attached to the name.
3. *Quantity* : The quantity is the number of LBRY credits assigned to the bid.
4. *Claim Id* : A unique ID used to identify the bid.
There are also three different bid types: claim, update, and support.
1. *Claim*: A claim represent new bids for a name. If a user wants to make a claim to a brand new name, or submit a competing claim to an existing name, this bid type is used.
2. *Support*: A support adds to the total quantity of credits assigned to any bid by referring to a bid's Claim Id. A support bid can be made by anyone on any bid. It does not have its own Value or its own Claim Id, but it does contain the Claim Id of the bid that it is supporting.
3. *Update*: An update can modify the value and the quantity for a pre-existing claim without changing the Claim Id or the name that it is bidding on. Since the Claim Id of the original bid is not changed, an updated bid will still retain all the supports attached to the original bid.
## ClaimTrie Bid States
This section describes how bids are processed by the ClaimTrie in order to determine which bids have won the rights to claim a particular name. There are 6 states a bid can be in, and they are explained below.
1. *Not accepted*: This bid is in a transaction which has not yet been included in a block which has been included in the blockchain.
2. *Accepted*: This bid has been accepted into the blockchain. This happens when the transaction containing the TXout which contains the bid is included in a block which is included in the blockchain.
3. *Active*: This bid is capable of controlling a name. Active bids must be in the "accepted" state and not "expired" or "spent". Bids are "active" when either of the two conditions below is met:
* The current block height exceeds the height of the block at which the bid became accepted plus the activation delay for the name as calculated at either the block at which the bid was accepted or any block after the bid was accepted. The activation delay is calculated as follows:
* If, immediately before this block was included in the blockchain, there were no 'active' bids for the name and therefore no 'controlling' bids, the delay is 0.
* If there is a "controlling" bid for the name: Delay = (HeightB - HeightA) / 32
* HeightA = the most recent height at which the bid controlling the name changed
* HeightB = the current height
* Maximum delay is 7 days of blocks at 2.5 min/block (or 4032 blocks). Thus maximum delay can be reached in 224 (7x32) days.
* The bid's Claim Id matches the Claim Id of the bid which was the controlling bid immediately before the block containing this bid was included in the blockchain. In other words, it is either an update to the previous controlling bid or update to update to the previous controlling bid if the bid was updated twice in this block, etc.
4. *Controlling*: This bid currently controls the name. When clients ask which bid controls the name as of the current block, this is the bid that will be returned. Must be in the "active" state and only one bid for any name may be in this state. A support cannot be in the "controlling" state. To determine which "active" bid is the "controlling" bid for each name:
* Add the quantity of each 'active' bid to the quantity of all 'active' supports for that bid, and take whichever is greatest. If two bids have the same quantity, older bids take precedence over newer bids.
* If the bid with the greatest amount does not have the same claimID as the bid which was 'controlling' prior to including the current block, change the delay for the name as of the current block to 0, redetermine which bids and supports should be active, and then perform the previous calculation again.
* At this point, the bid calculated to have the greatest amount behind it is the 'controlling' bid as of this block
5. *Spent*: A transaction has been included in the blockchain which spends the TXout which contains the bid. Must be in the 'accepted' state.
6. *Expired*: All bids 'expire' regardless of what state they are in when the current block height exceeds the height of the block at which the bid was accepted plus 52416 blocks, or 91 days ( currently this is set to 262974 blocks, or 456 days, which will be fixed in a future hard fork ). Updated claims will restart the expiration timer at the block height of the update.
## ClaimTrie Transaction Implementation
This section describes how the three ClaimTrie bid types are implemented as transactions on the blockchain. Readers should have prior knowledge of Bitcoin [transactions](https://en.bitcoin.it/wiki/Transaction) and the Bitcoin [scripting system](https://en.bitcoin.it/wiki/Script). LBRY supports three op codes that do not exist in Bitcoin: OP_CLAIM_NAME, OP_SUPPORT_CLAIM, and OP_UPDATE_CLAIM (in Bitcoin they are respectively OP_NOP6, OP_NOP7, and OP_NOP8). Each op code will push a zero on to the execution stack, and in addition, will trigger the ClaimTrie to perform calculations necessary for each bid type. Below are the three supported transactions scripts using these op codes.
```python
OP_CLAIM_NAME <Name> <Value> OP_2DROP OP_DROP [script pubkey]
OP_UPDATE_CLAIM <Name> <ClaimId> <Value> OP_2DROP OP_2DROP [script pubkey]
OP_SUPPORT_CLAIM <Name> <ClaimId> OP_2DROP OP_DROP [script pubkey]
```
[script pubkey] can be any valid Bitcoin payout script, thus it can be something like a standard "pay to pubkey" script to a user controlled address. Also note that the zero pushed onto the stack by the ClaimTrie op codes, and the ClaimTrie vectors, are all dropped by the preceding OP_2DROP and OP_DROP. This means that ClaimTrie transactions exist as prefixes to Bitcoin payout scripts and can be spent in the same way as is expected in Bitcoin.
For example, a claim transaction using a pay to pubkey script will have the below full payout script. Let's also say that this claim is for the name "Fruit" to be set to value "Apple".
```python
OP_CLAIM_NAME <Fruit> <Apple> OP_2DROP OP_DROP OP_DUP OP_HASH160 <LBRY_Address_A> OP_EQUALVERIFY OP_CHECKSIG
```
Like any standard Bitcoin transaction output script, it will be associated with a transaction hash and a transaction output index. The transaction hash and transaction output index is concatenated and hashed using RIPEMD-160 to create the Claim Id for this claim. For the example above, let's say it has a Claim Id X. A support for this bid will have the below full payout script.
```python
OP_SUPPORT_CLAIM <Fruit> <X> OP_2DROP OP_DROP OP_DUP OP_HASH160 <LBRY_Address_B> OP_EQUALVERIFY OP_CHECKSIG
```
And now let's say we want to update the original claim to change the value to "Banana". An update transaction has a special requirement that it must spend the existing claim that it wishes to update in its redeem script. Otherwise, it will be considered invalid and will not make it into the ClaimTrie. Thus it will have the below redeem script to spend the claim created to set name "Fruit" to "Apple". Note that this is identical to the standard way of redeeming a "pay to pubkey" script in Bitcoin.
```python
<Signature> <Public_key_for_LBRY_Address_A>
```
And the payout script for the update transaction is below.
```python
OP_UPDATE_CLAIM <Fruit> <X> <Banana> OP_2DROP OP_2DROP OP_DUP OP_HASH160 <LBRY_Address_C> OP_EQUALVERIFY OP_CHECKSIG
```
@@ -1,28 +0,0 @@
---
title: ARCHIVEDHow does the Community Top Bids section of the LBRY App work?
category: publisher
order: 3
---
### What are Community Top Bids?
Community Top Bids is a public space on the LBRY application that allows for community controlled content.
In this area, the LBRY URLs `lbry://one` through `lbry://ten` are displayed.
Anyone can share their content with the rest of the LBRY community by issuing a winning claim for one of these URLs. This mechanism enables users to promote their content and via the LBRY naming system.
Note that when claiming one of these URLs, no LBC is ever lost or destroyed (absent a very small transaction fee).
For more details on how naming works, please see: [Naming](/faq/naming)
### How do I publish to the Community Top Bids area?
1. Begin a standard publish by clicking the "PUBLISH" button at the top of the App.
2. When filling out the Content URL, enter the desired claim you want to bid on (one, two, five, eight, etc.)
3. After you have entered the desired URL, the system will automatically show you the minimum amount of LBC you need to deposit to get the claim. This LBC remains yours, and the deposit can be undone at any time.
4. Finish the rest of the publishing process.
### How do I know if my content is overtaken?
We do not have a mechanism in place to notify users when they are outbid, but one is planned for a future release. For now, you can monitor the Community Top Bids section to see if your content is still available.
@@ -1,16 +0,0 @@
---
title: How do I encrypt my wallet?
category: wallet
---
**THIS FAQ WAS MOVED TO LBRY.TECH ***
*Note: The below instructions are the [LBRYCrd Full Blockchain wallet](https://github.com/lbryio/lbrycrd) and not the default wallet that ships with the LBRY App. We are still working on an encryption solution for this.*
You can use `lbrycrd-cli encryptwallet <passphrase>` to encrypt your wallet.
You can use `lbrycrd-cli walletpassphrase <passphrase> <timeout>` to temporarily unlock the wallet. The <timeout> parameter is in seconds.
For example, `lbrycrd-cli walletpassphrase 'open sesame 321' 300` would unlock your wallet for five minutes, assuming your passphrase was `open sesame 321`. (In reality, you should choose a harder-to-guess passphrase than that.)
If you set <timeout> too low, it might expire before you get done using your wallet. If you set it too high, you might forget that you left your wallet unlocked.
@@ -1,12 +0,0 @@
---
title: How do I run LBRY with lbrycrdd?
category: mining
---
***WARNING: Currently, the LBRY app does not support the LBRYcrd wallet, but this functionality may be available in the future***
Start LBRY with the `--wallet` flag set:
lbrynet-daemon --wallet=lbrycrd
Note: when you change the wallet, it is persistent until you specify you want to use another wallet - lbryum - with the --wallet flag again.
@@ -1,24 +0,0 @@
---
title: What is LBRY's proof algorithm?
category: mining
---
## What is LBRY's proof algorithm?
LBRY uses [proof of work](https://en.bitcoin.it/wiki/Proof_of_work) the same way that Bitcoin does. The
only difference is the hash function. LBRY uses a slightly different algorithm that achieves the same ends but slightly delayed the development of a GPU miner and gave early adopters a chance to mine without specialized hardware.
LBRY's algorithm is
```python
intermediate = sha512(sha256(sha256(data))) # compute the sha512() of the double-sha256() of the data
left = ripemd(intermediate[:len(intermediate)/2]) # separately ripemd160 the left half
right = ripemd(intermediate[len(intermediate)/2:]) # and the right half
proof = sha256(sha256(left + right)) # concatenate the two halves, and double-sha256() it again
```
For comparison, Bitcoin's algorithm is
```python
proof = sha256(sha256(data))
```
@@ -1,206 +0,0 @@
---
title: How do I setup an isolated regtest network to test LBRY?
category: developer
---
## Why use a regtest server
A regtest server provides for a way to instantly generate blocks so that transactions can be instantaneous, so ultimately no waiting for confirmations from the blockchain. Also, no problem if you accidentally corrupt your wallet, since no real funds are lost! Delete the files and setup a new one.
## Setup
To begin setting up the network, there are a few things you need.
You'll need a Linux or a Mac distribution to run all this. A virtual machine is fine.
Note: These instructions specifically were tested on Ubuntu version 16.04.
### Virtual Environment
First up it's a good idea to create a Python virtual environment. This requires you to have a functional python2.7 setup, with the Python package manager `pip` installed. To create a new virtual environment in a folder `lbry-env`, run this:
`virtualenv -p /usr/bin/python2.7 lbry-env`
To enter the environment, run:
`source lbry-env/bin/activate`.
### lbrycrd
You need to download a build of `lbrycrd` from [here](https://github.com/lbryio/lbrycrd/releases), no installation required. To configure `lbrycrd` you need to create a file at `~/.lbrycrd/lbrycrd.conf`,
containing the following.
```ini
rpcuser=test
rpcpassword=test
rpcport=18332
regtest=1
server=1
txindex=1
daemon=1
listen=0
discover=0
```
### lbryum-server
To install lbryum-server, you first need to install the package `leveldb`. After that, download the source from [here](https://github.com/lbryio/lbryum-server/releases), and run the following _not_ inside the environment.
```bash
cd lbryum-server
sudo pip2 install -r requirements.txt
```
If you're not running debian/*buntu or a derivative of those, you need to edit the `configure` file a bit. In line 11, remove the `apt-get` line and manually install the required packages. In line 51, change `adduser` to `useradd` and on the same line, change `--disabled-password` to `-p !`.
```bash
sudo ./configure
sudo python2 setup.py install
```
The `sudo ./configure` command creates a new user in the system by the name "lbryum", which is the user through which we'll be the running the server. lbryum-server also need W/R access to `/var/lbryum-server`
To do that run:
```bash
sudo chown -R lbryum /var/lbryum-server
```
When installed, append/use the following config options to the `/etc/lbryum.conf` file.
```ini
[lbrycrdd]
lbrycrdd_host = localhost
lbrycrdd_port = 18332
# user and password from lbrycrd.conf
lbrycrdd_user = test
lbrycrdd_password = test
[network]
type=lbrycrd_regtest
```
### lbryum
To install lbryum, first, download the source from [here](https://github.com/lbryio/lbryum/releases). To install it, run the following inside the virtual environment.
```bash
cd lbryum
pip2 install -r requirements.txt
pip2 install -e .
```
After installation completes, you must set the config option for lbryum using:
```bash
lbryum setconfig default_servers '{ "localhost": { "t": "50001" }}'
lbryum setconfig chain 'lbrycrd_regtest'
```
Alternatively, you can create a file `touch ~/.lbryum/config` and paste the following config:
```json
{
"chain": "lbrycrd_regtest",
"default_servers": {
"localhost": {
"t": "50001"
}
}
}
```
### lbry
Download source from [here](https://github.com/lbryio/lbry/releases), and run the following inside the environment.
```bash
cd lbry
pip2 install -r requirements.txt
pip2 install -e .
mkdir ~/.lbrynet
touch ~/.lbrynet/daemon_settings.yml
```
Append the following in the newly created `~/.lbrynet/daemon_settings.yml` file
```yml
blockchain_name: lbrycrd_regtest
lbryum_servers:
- localhost:50001
reflect_uploads: false
share_usage_data: false
use_upnp: false
```
### Last step
Go to the `lbryum` folder once again and run:
```bash
pip2 install -e .
```
This is to ensure that `lbrynet-daemon` uses the correct wallet.
## Firing up the regtest server
### Wallet backup
To start off, if you've already used LBRY on your machine, you need to backup the wallet by copying the folders `~/.lbrynet` and `~/.lbryum`, then delete them to start from fresh. Run
`mkdir ~/.lbryum`
Now it should be all set-up, just execute the commands in the following order, and the regtest server should be good to go.
### 1) lbrycrd
To run the `lbrycrd` daemon, run the following in the `lbrycrd` folder.
`./lbrycrdd`
To generate blocks, run `./lbrycrd-cli generate <num_of_blocks>`
You'll need to generate some blocks to get the network going. Start off by generating at least 100.
`./lbrycrd-cli generate 173`
If you'd prefer a more verbose output from lbrycrdd, run lbrycrd using
`./lbrycrdd -printtoconsole`
### 2) lbryum-server
To run the server, run:
```bash
sudo runuser -l lbryum -c 'lbryum-server --conf=/etc/lbryum.conf'
```
Note: conf flag can be left out if the config is in the default directory(default: `/etc/lbryum.conf`)
### 3) lbryum
To run the lbryum, run:
```bash
lbryum daemon start
```
Generate some more blocks, get a wallet address by running:
`lbryum getunusedaddress`
and then send some credits to your wallet by doing
`./lbrycrd-cli sendtoaddress <address> <num_of_credits>`
### 4) lbry
You can now run `lbrynet-daemon`, and it should connect to the `lbryum`. Now you can use the regtest stack as you would normally use lbryum.
## Shutdown
To stop the network, run `lbrynet-cli daemon_stop`, `lbryum daemon stop`, and kill the `lbryum-server` process and stop lbrycrd by `lbrycrdd-cli stop`. If you want to use your wallet and the official servers again, backup the new regtest wallet, and replace it with your own.
## Note 1
You need to generate a few blocks everytime you make a new transaction in the form of send, receive, claim, update, publish, support, tip etc. for it to show up in the daemon and lbryum etc.
## Note 2
If something goes wrong and you get a "Block not found" error, remember to delete `/var/lbryum-server` before trying again.
## Cheatsheet
#### Required processes in the correct order
```bash
lbrycrdd
sudo runuser -l lbryum -c 'lbryum-server --conf=/etc/lbryum.conf'
lbryum daemon start
lbrynet-daemon
```
#### Generate blocks
```bash
lbrycrd-cli generate 5
```
#### Get a wallet address
```bash
lbryum getunsusedaddress
```
#### Send credits from lbrycrd to your wallet
```bash
lbrycrd-cli sendtoaddress <address> <num_of_credits>
```
@@ -1,6 +0,0 @@
---
title: How can I see the log in the terminal?
category: developer
---
Simply run `lbry`, or the daemon `lbrynet-daemon`, in a terminal.
@@ -1,20 +0,0 @@
---
title: Unable to Stream any LBRY Content?
category: troubleshooting
order: 2
---
If you are having trouble streaming any LBRY content, there may be an issue with your connectivity to the LBRY network. Sometimes simply restarting the LBRY app and daemon completely could fix the problem - this is usually what you want to try first. Both PC and router firewall settings, as well as other applications which limit internet connectivity (i.e. Antiviruses or Internet security applications), may prevent your app from successfully connecting to the LBRY network. You can try disabling these or allowing LBRY to bypass them. Other times, it may be a hosting issue with the particular piece of content you are trying to download. Please report in the #help channel on [Discord](https://chat.lbry.com).
Another common cause of this issue is the lack of access to UDP port 4444. LBRY employs UPnP (if enabled) in order to forward this port on your router automatically. If UPnP is disabled, it must either be enabled, or the port must be forwarded in your router configuration. We have also seen instances where some ISPs may block UDP port 4444, and for LBRY to download content properly, this port must be manually configured - see steps below.
### How to manually set the DHT (Content Network) port
1. Shutdown LBRY and lbrynet (check running processes using Task Manager on Windows or Activity Monitor on Mac OS.)
2. Go to your [lbrynet folder](/faq/lbry-directories).
3. If you have a `daemon_settings.yml` file, add this line to it at the end (4444 is an example, can be changed): `dht_node_port: 4444`.
4. If you don't have the `daemon_settings.yml` file, you can create one or download/copy [this sample](https://goo.gl/a5uJq5) into the `lbrynet` folder.
5. Start LBRY and try to download a couple of items from the homepage. Be patient, if it doesn't work, leave the page and try again or a different video.
6. Depending on your network, you may need UDP port 4444 (the new port you just set up) forwarded. Also, for file sharing to work properly, you may need TCP port 3333 open/forwarded. This can be verified by using a [port checker tool](http://www.canyouseeme.org) on port 3333. Port 4444 will fail since it's UDP.
If you continue to experience issues streaming/downloading content after completing the above steps, please [reach out to us](/faq/how-to-report-bugs) for additional support.
@@ -1,12 +0,0 @@
---
title: How is LBRY different from Decent / SingularDTV / Alexandria?
category: differences
---
The first and biggest difference is that LBRY exists and has significant traction. As of this writing, Alexandria is the only one of these to release a client to the public, and there hasn't been much progress since that release.
It's difficult to compare LBRY to something that doesn't exist yet, but as we understand it, no alternative is providing a human-friendly namespace and discovery mechanisms like LBRY.
Additionally, LBRY is the only one of these three to see significant backing outside of the cryptocurrency niche. While we love crypto, we're aiming to be a mainstream, household technology. To that extent, the fact that LBRY has backing from major VCs, tech companies, and Hollywood studios says a lot.
Finally, unlike almost every blockchain company, we've never hosted an ICO or sold coins to the public. We've put ourselves in a position where the only way we make money is if LBRY achieves long-term success. To us, having "skin in the game" is a moral imperative.
@@ -1,32 +0,0 @@
---
title: How do I check my LBC address?
category: wallet
---
## Using lbrynet (the usual way)
To get your current, unused address
lbrynet-cli wallet_unused_address
To create a new address
lbrynet-cli wallet_new_address
To list all addresses in your wallet
lbrynet-cli wallet_list
To get your balance
lbrynet-cli wallet_balance
## Using lbrycrd (the old way)
In order to check your LBC address, you must first find out the name of the account you are interested in:
lbrycrd-cli listaccounts
Now you just have to check that account address:
lbrycrd-cli getaccountaddress ""
@@ -1,8 +0,0 @@
---
title: How do I check my mining balance?
category: mining
---
You can use `lbrycrd-cli getbalance`, or `lbrycrd-cli getwalletinfo` for more detailed information.
It takes 100 confirmed blocks (roughly a bit over 4 hours) for mined LBC to show up in your confirmed balance,
but you can see these credits in your immature balance in getwalletinfo.
+20 -5
View File
@@ -1,8 +1,23 @@
---
title: Acceptable use policy
category: other
---
{
"title": "Acceptable use policy",
"url": "/faq/acceptable-use-policy",
"type": "faq",
"source_url": "https://lbry.com/faq/acceptable-use-policy",
"description": "If you've read Art in the Internet Age, you know that LBRY believes we are in a post-scarcity age in…",
"images": [
"https://lbry.com/img/og-faq.png?_cache=2026-10-31"
],
"og_type": "article",
"twitter_card": "summary_large_image",
"news_feed": false,
"footer_email_href": "/cdn-cgi/l/email-protection#dfb7bab3b3b09fb3bdada6f1bcb0b2",
"footer_email_code": "c4aca1a8a8ab84a8a6b6bdeaa7aba9",
"meta_title": "Acceptable use policy - LBRY",
"category": "other",
"source_file": "content/faq/acceptable-use-policy.md",
"edit_url": "https://github.com/lbryio/lbry.com/tree/master/content/faq/acceptable-use-policy.md",
"weight": 70
}
If you've read [Art in the Internet Age,](/what) you know that LBRY believes we are in a post-scarcity age in terms of the reproduction of content. There are two things that are still scarce; good quality content, and good reputations. We take respecting the rights of creators very seriously, and we expect the same when it comes to our brand name. Here is how we go about protecting that.
Our trademarks include our name, LBRY, and our official logo, which are owned by LBRY, Inc, a Delaware Corporation. We encourage the use of LBRY's trademarked name and official logo while maintaining control of them in order to thwart vandalism, theft, and any future misconduct that offends the collective sensibility of LBRY users creates legal hazards or otherwise inhibits the free expression and open transactions we prize.
-35
View File
@@ -1,35 +0,0 @@
---
title: lbry.tv account and wallet syncing
category: getstarted
order: 3
---
Users expect consistent experiences across devices and sessions. This includes everything from account preferences to subscriptions to account balances. In the land of central servers, this is straightforward, but in blockchain land, it is tricky. This article explains how we provide this functionality, various options in using it, and it's limitations.
## How it works
1. Every user, whether on LBRY Desktop, Android, or [lbry.tv](https://lbry.tv), has a single wallet file. This file stores your private keys (like a password) that controls your channels and account balances. The keys in this file are the only way to move or spend LBC or publish to your channel.
1. On an ongoing basis, your account preferences and other settings are written to your wallet file.
1. If you create a lbry.tv login and turn on account sync (backup), your wallet file will be copied to and from a LBRY, Inc. server each time you login and at regular intervals.
1. Each time this happens, your preferences, channels, subscriptions, and other data will be updated on the new device.
1. If your wallet file has a password on it, LBRY, Inc. cannot see into your wallet or do anything with it, including reset your password.
## Using wallet sync
### Sync limitations
As of writing, current limitations are:
- Can't set or change passwords (coming soon). Only Android allows setting of a password on new accounts currently.
- Cannot remove a previously synced account (i.e. which you don't know the password to). This process is currently manual, please [contact us](/faq/support)
- On Desktop, if you sign out and back in with a different email, these wallets and accounts will be merged. Do not do this unless it's intentional and you expect the new email to be used by the same person. To prevent this, rename/remove the [default_wallet file in the lbryum folder](/faq/lbry-directories) and quit the app with Ctrl-Q after signing out.
### Desktop
1. If running the desktop app for the first time, you will be prompted during the first-run process to opt-in.
1. If you want to opt-in later, click the Settings button in the top right and enable Sync.
1. If you previously had sync configured with a password (i.e on Android), you'll be prompted for this. If you do not remember, please [reach out to us](mailto:hello@lbry.com) so we can remove the existing synced account.
### Android
1. If running the Android app for the first time, you will be prompted during the first-run process to opt-in.
1. If you want to opt-in later, click your balance or navigate to the Wallet area and you will see the option to turn this on.
### lbry.tv
Syncing is automatically on for lbry.tv users and cannot be disabled. After all, what good would lbry.tv be if you could no longer use it once you signed out! If you have balances on other devices, these will not be reflected at this time.
## I'm having trouble
If you have any trouble using or enrolling in account sync, check out this [FAQ article](/faq/how-to-report-bugs) on how to report this to us.
+104
View File
@@ -0,0 +1,104 @@
{
"title": "Odysee.com and LBRY accounts and wallet syncing",
"url": "/faq/accounts-and-sync",
"type": "faq",
"source_url": "https://lbry.com/faq/accounts-and-sync",
"description": "Users expect consistent experiences across devices and sessions. This includes everything from account preferences to subscriptions to account balances. In…",
"images": [
"https://spee.ch/2/b23ed850c8de1a54.png",
"https://spee.ch/9/944f70da8357d672.png",
"https://spee.ch/6/passwords-add.png",
"https://spee.ch/1/ac248a1824fbe30b.png",
"https://spee.ch/7/3378478fa7bb3b36.png"
],
"og_type": "article",
"twitter_card": "summary_large_image",
"news_feed": false,
"footer_email_href": "/cdn-cgi/l/email-protection#99f1fcf5f5f6d9f5fbebe0b7faf6f4",
"footer_email_code": "6008050c0c0f200c0212194e030f0d",
"meta_title": "Odysee.com and LBRY accounts and wallet syncing",
"category": "getstarted",
"source_file": "content/faq/accounts-and-sync.md",
"edit_url": "https://github.com/lbryio/lbry.com/tree/master/content/faq/accounts-and-sync.md",
"protected_emails": {
"hello@lbry.com": {
"address": "hello@lbry.com",
"href": "/cdn-cgi/l/email-protection#5a323f3636351a3638282374393537"
}
},
"source_order": 3,
"weight": 10
}
Users expect consistent experiences across devices and sessions. This includes everything from account preferences to subscriptions to account balances. In the land of central servers, this is straightforward, but in blockchain land, it is tricky. This article explains how we provide this functionality, various options in using it, and it's limitations.
Users can establish accounts on all of our applications, but for some apps, like LBRY android and LBRY desktop, creating an account isn't mandatory. You'll be required to create an account with password and confirm that your email exists to use all features on Odysee.com. You can sign into existing accounts via the password or via email confirmation.
## Account passwords and logging in
When signing up for a new account, user will be prompted to set a password and also confirm that the email belongs to them. **It is important to set a strong password to ensure no one else can access your account, LBRY Credits, and published content.**. This password can be reset via email, using the "Forgot Password?" option while logging in, or changed on the Settings page in the app.
Users creating account on Odysee.com will be offered option to [sync](/faq/youtube) their YouTube channel to Odysee. It's also possible to apply to the sync after creating the account.
![](https://spee.ch/2/b23ed850c8de1a54.png)
If you are logging back in or from another device, you can do so with your account password or via an email confirmation (magic link option).
![](https://spee.ch/9/944f70da8357d672.png)
### Existing accounts without a password
Users can set a password for existing accounts via the Settings page if password log in is preferred over email confirmation.
![](https://spee.ch/6/passwords-add.png)
### Resetting account password
On the login screen, you'll have the option to reset an account password via email. Once you get the email, click the confirmation link and setup a new password.
![](https://spee.ch/1/ac248a1824fbe30b.png)
### Changing account password
You can update your account password on the Settings page. You'll be prompted for your old password, and the new one. Existing sessions will be kept active. If you need them signed out for security reasons, please [contact us](/faq/support).
![](https://spee.ch/7/3378478fa7bb3b36.png)
### Account vs encrypted wallet passwords
Account passwords are separate from wallet passwords. Users with encrypted wallets will still be required to enter their wallet password when logging in to Odysee.com and about every 2 weeks when the passwords expire. Setting wallet passwords is a [current limitation](#limitations) of our wallet sync process.
## How syncing of wallet and account data works
1. Every user, whether on LBRY Desktop, mobile, or [Odysee.com](https://odysee.com), has a single wallet file. This file stores your private keys (like a password) that controls your channels and account balances. The keys in this file are the only way to move or spend LBC or publish to your channel.
1. On an ongoing basis, your account preferences and other settings are written to your wallet file.
1. If you create an email login on LBRY desktop app and turn on account sync (backup), your wallet file will be backed up to and from a LBRY, Inc. server each time you log in and at regular intervals.
1. Each time this happens, your preferences, channels, subscriptions, and other data will be updated on the new device.
1. If your wallet file has a password on it, LBRY, Inc. cannot see into your wallet or do anything with it, including reset your password.
## Using wallet sync
### I want to remove my wallet and synced data from Odysee.com
This process is currently manual, please [contact us](/faq/support).
### Wallet Sync limitations {#limitations}
As of writing, current limitations are:
- Can't set or change wallet passwords (coming in mid 2021) if you previously did not have one. If you'd like to do this manually, please [contact us](/faq/support). Wallet passwords are separate from account passwords, and they cannot be reset or changed if lost/forgotten. LBRY Inc ensures wallet files are secured on their servers and properly hashed in the database, with access locked down to the files.
- On Desktop, if you sign out and back in with a different email, these wallets and accounts will be merged. Do not do this unless it's intentional and you expect the new email to be used by the same person. To prevent this, rename/remove the [default_wallet file in the lbryum/wallets folder](/faq/lbry-directories) and quit the app with Ctrl-Q after signing out.
### Desktop
1. If running the desktop app for the first time, you will be prompted during the first-run process to create an account, if you want to opt-in to the wallet sync check "Backup your account and wallet data." option.
1. If you want to opt-in later, click the Settings button in the top right and enable Sync.
1. If you previously had sync configured with a password (i.e on Android), you'll be prompted for this. If you do not remember, please [reach out to us](mailto:hello@lbry.com) so we can remove the existing synced account.
### Android
On android you can enable sync from the "Wallet" page.
### Odysee.com
Syncing is automatically on for Odysee.com users and cannot be disabled. After all, what good would Odysee.com be if you could no longer use it once you signed out! If you have a wallet on other devices with sync turned on, it will be reflected here as well.
## I'm having trouble
If you're having any trouble using or enrolling in account sync, check out this [FAQ article](/faq/how-to-report-bugs) on how to report this to us.
+63 -34
View File
@@ -1,10 +1,39 @@
---
title: LBRY for Android basics
category: getstarted
order: 2
---
The LBRY Browser for Android allows you to view free and paid content via the Explore and Trending sections, search for content on LBRY, send/receive LBRY Credits (LBC) and earn credits through LBRY Rewards.
{
"title": "LBRY for Android basics",
"url": "/faq/android-basics",
"type": "faq",
"source_url": "https://lbry.com/faq/android-basics",
"description": "The LBRY Browser for Android allows you to view free and paid content via the Explore and Trending sections, search…",
"images": [
"https://thumbs.spee.ch/view/d/290c0ad650d757bb.jpg",
"https://thumbs.spee.ch/view/c/c8f75c95b1dbd35c.jpg",
"https://thumbs.spee.ch/view/1/fa62fd26d18fba12.jpg",
"https://thumbs.spee.ch/view/d/9380dfd641fcb4b2.jpg",
"https://thumbs.spee.ch/view/1/6f75ed8649b5ef1c.jpg",
"https://thumbs.spee.ch/view/a/5085234b9874d903.jpg",
"https://thumbs.spee.ch/view/b/b8c644252ec6c7b3.jpg",
"https://thumbs.spee.ch/view/6/ae467011c0904d4f.jpg",
"https://thumbs.spee.ch/view/5/dec91d6d33fb780a.jpg"
],
"og_type": "article",
"twitter_card": "summary_large_image",
"news_feed": false,
"footer_email_href": "/cdn-cgi/l/email-protection#9cf4f9f0f0f3dcf0feeee5b2fff3f1",
"footer_email_code": "afc7cac3c3c0efc3cdddd681ccc0c2",
"meta_title": "LBRY for Android basics",
"category": "getstarted",
"source_file": "content/faq/android-basics.md",
"edit_url": "https://github.com/lbryio/lbry.com/tree/master/content/faq/android-basics.md",
"protected_emails": {
"help@lbry.com": {
"address": "help@lbry.com",
"href": "/cdn-cgi/l/email-protection#95fdf0f9e5d5f9f7e7ecbbf6faf8"
}
},
"source_order": 2,
"weight": 8
}
The LBRY Browser for Android allows you to view free and paid content via the Explore and Trending sections, search for content on LBRY, send/receive LBRY Credits (LBC) and earn Credits through LBRY Rewards.
The app runs on top of the [LBRY protocol](/faq/what-is-lbry) which is a peer-to-peer (P2P), decentralized file sharing and payment network secured by blockchain technology.
@@ -14,43 +43,43 @@ The purpose of this FAQ is to answer questions about some of the basic functiona
Emails are collected to authenticate a lbry.tv account and [uniquely identify](/faq/phone) users so that they can be eligible for [LBRY Rewards](#rewards), sync wallet data/preferences, and to stay up to date on the latest LBRY happenings.
No other data is stored with your email login. All other data, including your [wallet](#wallet), [downloads](#data) and published content are stored [locally on your device](/faq/lbry-directories#android). You will be asked to create a [password to secure your account](/faq/account_sync).
No other data is stored with your email login. All other data, including your [wallet](#wallet), [downloads](#data), and published content are stored [locally on your device](/faq/lbry-directories#android). You will be asked to create a [password to secure your account](/faq/account_sync).
## How do I change my LBRY connected email?
If you ever need to change your LBRY Android App email address or sign out, please see [this guide](/faq/how-to-change-email#android). Clearing data or uninstalling leads to a loss of wallet if you don't have one synced.
If you sign into a new email and need to transfer your wallet/verification status, you'll need to [reach out to us](mailto:help@lbry.com) in order to link your accounts. Please do not verify again to obtain rewards on a 2nd account; your Rewards account may be disabled for abuse.
If you sign in to a new email and need to transfer your wallet/verification status, you'll need to [reach out to us](mailto:help@lbry.com) to link your accounts. Please do not verify again to obtain rewards on a 2nd account; your Rewards account may be disabled for abuse.
## Syncing of wallets and other data
The Android app allow syncing of your account/wallet and secures it with a password. Please read the [sync FAQ](/faq/account_sync) in more detail to understand how this works.
The Android app allows syncing of your account/wallet and secures it with a password. Please read the [sync FAQ](/faq/account_sync) in more detail to understand how this works.
## What are LBRY Rewards? {#rewards}
[LBRY Rewards](/faq/rewards) are used to distribute LBRY Credits (LBC) to new and existing users by allowing them to explore app functions and complete tasks which generate LBC as an award.
[LBRY Rewards](/faq/rewards) are used to distribute LBRY Credits (LBC) to new and existing users by allowing them to explore app functions and complete tasks that generate LBC as an award.
In order to be eligible for Rewards, you need to verify your identity [phone number](/faq/phone) or [chat](https://chat.lbry.com) which uniquely identifies you as an LBRY user.
To be eligible for Rewards, you need to verify your identity [phone number](/faq/phone) or [chat](https://chat.lbry.com) which uniquely identifies you as an LBRY user.
## What is a wallet And how do I find it? {#wallet}
A wallet is a secure digital file used to store, send and receive cryptocurrencies like LBRY Credits (LBC).
A wallet is a secure digital file used to store, send, and receive cryptocurrencies like LBRY Credits (LBC).
The LBRY Android App comes with its own wallet and is stored locally on your phone and nowhere else!
If you do not opt for the [sync program](/faq/account_sync), it is critical that you [backup your own wallet](/faq/how-to-backup-wallet#android) locally or else the credits, channels, and publishes will be lost.
If you do not opt for the [sync program](/faq/account_sync), it is critical that you [backup your own wallet](/faq/how-to-backup-wallet#android) locally or else the Credits, channels, and publishes will be lost.
To find your wallet in the LBRY Android app, click on the 3 horizontal bars at the upper left side of the app next to the Search bar. Clicking on it will open a sidebar and then click on Wallet. This will open the Wallet page which shows your wallet address, balance and recent transactions.
To find your wallet in the LBRY Android app, click on the 3 horizontal bars at the upper left side of the app next to the Search bar. Clicking on it will open a sidebar and then click on Wallet. This will open the Wallet page which shows your wallet address, balance, and recent transactions.
![Find wallet](https://spee.ch/f/wallet-option.jpg)
![Find wallet](https://thumbs.spee.ch/view/d/290c0ad650d757bb.jpg)
## Where do I find my LBC wallet address?
![balance](https://spee.ch/e7f125b643e30f8bac2d8c4657bc14874a60e25e/WALLETADD1.jpg)
![balance](https://thumbs.spee.ch/view/c/c8f75c95b1dbd35c.jpg)
## Where do I find my recent transactions
Scroll down in the Wallet menu to find recent transactions, or click `View All` to see anything older than 7 days.
![Recent tx](https://spee.ch/daa89fcca6411ad2505cdc6e092fcaf4f22f4802/recent1.jpg)
![Recent tx](https://thumbs.spee.ch/view/1/fa62fd26d18fba12.jpg)
The LBRY wallet is different from other wallets - it also stores your shared content's metadata in the form of [claims](/faq/naming) when using the publishing features.
@@ -60,57 +89,57 @@ The LBRY wallet is different from other wallets - it also stores your shared con
2. Select the option for `New publish`
![Click the Publish Button](https://spee.ch/d/publish-button.png)
![Click the Publish Button](https://thumbs.spee.ch/view/d/9380dfd641fcb4b2.jpg)
3. Choose the option for publishing your content either by recording a live video, taking a picture or picking a file from your gallery.
3. Choose the option for publishing your content either by recording a live video, taking a picture, or picking a file from your gallery.
![Choose an option]https://spee.ch/4/chooses.png)
![Choose an option](https://thumbs.spee.ch/view/1/6f75ed8649b5ef1c.jpg)
4. Enter a `Title` and `Description` for your content.
5. Next you can add tags to your content which will help categorize it for [discovery purposes](https://lbry.com/faq/trending). If it's intended for mature audiences, please add the pink `mature` tag. Next, determine any other tags that relate to the content you are publishing. Please be mindful of accuracy when tagging content as this is currently up to the publisher only and cannot be edited. If incorrect/inappropriate tags are used, your content may be filtered to provide a better user experience. In the future, this will be done through community voting and building a web of trust.
5. Next, you can add `tags` to your content which will help categorize it for [discovery purposes](https://lbry.com/faq/trending). If it's intended for mature audiences, please add the pink `mature` tag. Next, determine any other tags that relate to the content you are publishing. Please be mindful of accuracy when tagging content as this is currently up to the publisher only and cannot be edited. If incorrect/inappropriate tags are used, your content may be filtered to provide a better user experience. In the future, this will be done through community voting and building a web of trust.
![publish process](https://spee.ch/1/pub4.png)
![publish process](https://thumbs.spee.ch/view/a/5085234b9874d903.jpg)
6. You have the option to select/create the channel you would like to publish the content under. If no channel is selected, it will be posted anonymously.
![Select Channel or Anonymous](https://spee.ch/c/chan-anonym.png)
![Select Channel or Anonymous](https://thumbs.spee.ch/view/b/b8c644252ec6c7b3.jpg)
7.Under the `Price`, first, determine if you want to make your content free or set a price in LBC per view.
7. Under the `Price`, first, determine if you want to make your content free or set a price in LBC per view.
8. Type in the URL you want the content to be found under, along with a minimum of 0.00000001 LBC deposit for the upload (default amount is higher due to publishing fees). If you are trying to outbid a user-friendly/common URL, the system will suggest a minimum bid to take over the content at that vanity URL. There may be a delay for this takeover. Making your bid higher will result in (better discovery)[https://lbry.com/faq/trending) for your content. For more details regarding the URL or bid, check out our [naming document](/faq/naming).
8. Type in the URL you want the content to be found under, along with a minimum of 0.00000001 LBC deposit for the upload (default amount is higher due to publishing fees). If you are trying to outbid a user-friendly/common URL, the system will suggest a minimum bid to take over the content at that vanity URL. There may be a delay for this takeover. Making your bid higher will result in [better discovery](/faq/trending) for your content. For more details regarding the URL or bid, check out our [naming document](/faq/naming).
![Video URL and Deposit](https://spee.ch/8/video-url.png)
![Video URL and Deposit](https://thumbs.spee.ch/view/6/ae467011c0904d4f.jpg)
9. Next, there is `Show extra fields` which gives you an option to select language and license. Default language is set to `English`, and the License is set to `None`. If a change is needed, click the dropdown menus and select the appropriate choice.
9. Next, there is `Show extra fields` which gives you an option to select language and license. The default language is set to `English`, and the License is set to `None`. If a change is needed, click the dropdown menus and select the appropriate choice.
*please review our terms of service before publishing [terms of service](/termsofservice)*
Click `Publish`.
The file will process in the background and will be added to the LBRY Blockchain. It is a good idea to leave LBRY open for a while after this to make sure the app is able to share your file to at least one peer on the data network. Larger files will take longer to upload depending on your network speed.
The file will process in the background and will be added to the LBRY Blockchain. It is a good idea to leave LBRY open for a while after this to make sure the app is able to share your file with at least one peer on the data network. Larger files will take longer to upload depending on your network speed.
Claim related [wallet transactions](/faq/transaction-types) ensure that the blockchain uniquely identifies your content and the payment/tips can be routed appropriately.
## How do I claim Rewards in the Android app? {#rewards}
You'll receive daily random rewards just for watching the videos you love! All you need to do is open your LBRY app and start watching. Comeback everyday for a different reward. For other rewards that can be claimed, see the Rewards page.
You'll receive daily random rewards just for watching the videos you love! All you need to do is open your LBRY app and start watching. Come back every day for a different reward. For other rewards that can be claimed, see the Rewards page.
## How do I enable background media playback? {#backgroundmediaplayback}
When playing anything on the LBRY android app, it will stop playing when you minimize the app or switch to another application. Since we aren't YouTube and won't make you pay for subscription to enable background media playback, you can enable this feature in the app settings.
1. Swipe your phone screen to the right to reveal the menu, select Settings.
2. Tap the `Enable background media playback` toggle on the right hand side, this will change the status of that option from grey to green.
2. Tap the `Enable background media playback` toggle on the right-hand side, this will change the status of that option from grey to green.
![settings](https://spee.ch/6169bbad4908bee2378f09a7ea048b981a79ebe5/enable.jpg)
![settings](https://thumbs.spee.ch/view/5/dec91d6d33fb780a.jpg)
Now you will be able to keep your media playing in the background without leaving the app open.
*To disable this feature, please tap the option to enable background media player to change the status from green to grey.*
## How do I stop the LBRY service from running in the background? {#stoplbryservice}
You might have noticed the LBRY icon in your notifications with the status, `LBRY service is running in the background`. We keep the app open in the background to stay up-to-date with the blockchain, which helps the app load contents faster as it arrives. In the future, you'll be able to support the LBRY network and earn hosting rewards, but for now, the hosting features are disabled.
You might have noticed the LBRY icon in your notifications with the status, `LBRY service is running in the background`. We keep the app open in the background to stay up-to-date with the blockchain, which helps the app load content faster as it arrives. In the future, you'll be able to support the LBRY network and earn hosting rewards, but for now, the hosting features are disabled.
However, if you do not want the LBRY service to be running in the background, you can disable this in the settings page by tapping `Keep the daemon background service running after closing the app` - this will change the status of that option from green to grey. Now close the LBRY app by clicking back multiple times or swipe the app to close - the notification icon should disappear.
However, if you do not want the LBRY service to be running in the background, you can disable this in the settings page by tapping `Keep the daemon background service running after closing the app` - this will change the status of that option from green to grey. Now close the LBRY app by swiping it from quickswitch to close - the notification icon should disappear.
+26 -5
View File
@@ -1,8 +1,29 @@
---
title: Appreciation for contributing
category: other
---
{
"title": "Appreciation for contributing",
"url": "/faq/appreciation",
"type": "faq",
"source_url": "https://lbry.com/faq/appreciation",
"description": "If you've been linked or directed to this page, it's most likely because we've noticed you made a contribution to…",
"images": [
"https://lbry.com/img/og-faq.png?_cache=2026-10-31"
],
"og_type": "article",
"twitter_card": "summary_large_image",
"news_feed": false,
"footer_email_href": "/cdn-cgi/l/email-protection#254d4049494a654947575c0b464a48",
"footer_email_code": "e9818c858586a9858b9b90c78a8684",
"meta_title": "Appreciation for contributing - LBRY",
"category": "other",
"source_file": "content/faq/appreciation.md",
"edit_url": "https://github.com/lbryio/lbry.com/tree/master/content/faq/appreciation.md",
"protected_emails": {
"hello@lbry.com": {
"address": "hello@lbry.com",
"href": "/cdn-cgi/l/email-protection#1d75787171725d717f6f64337e7270"
}
},
"weight": 71
}
If you've been linked or directed to this page, it's most likely because we've noticed you made a contribution to LBRY. So first of all, ***THANK YOU*** from the LBRY team and all other LBRYians (of which you should now count yourself!).
Public contributions are crucial for the development and continued success of the LBRY application and network. Whether it's a good suggestion, a code submission, a thorough bug report or just raising awareness of LBRY, it all strengthens the community and network.
+21 -6
View File
@@ -1,8 +1,23 @@
---
title: How do I backup and/or migrate my LBRY data?
category: troubleshooting
---
{
"title": "How do I backup and/or migrate my LBRY data?",
"url": "/faq/backup-data",
"type": "faq",
"source_url": "https://lbry.com/faq/backup-data",
"description": "We have covered LBRY wallet backup procedures in the guide here, but the purpose of this guide will be how…",
"images": [
"https://lbry.com/img/og-faq.png?_cache=2026-10-31"
],
"og_type": "article",
"twitter_card": "summary_large_image",
"news_feed": false,
"footer_email_href": "/cdn-cgi/l/email-protection#90f8f5fcfcffd0fcf2e2e9bef3fffd",
"footer_email_code": "0d65686161624d616f7f74236e6260",
"meta_title": "How do I backup and/or migrate my LBRY data?",
"category": "troubleshooting",
"source_file": "content/faq/backup-data.md",
"edit_url": "https://github.com/lbryio/lbry.com/tree/master/content/faq/backup-data.md",
"weight": 38
}
We have covered LBRY wallet backup procedures in the guide [here](/faq/how-to-backup-wallet), but the purpose of this guide will be how to backup and/or migrate all your LBRY data which includes your downloads, hosted data, wallet and other settings. To follow this guide effectively, it's a good idea to familiarize yourself with LBRY [working directories](/faq/lbry-directories), especially the `lbrynet` and `lbryum` folders. ***In the case of Mac OS, the `lbrynet` folder contents are stored inside the `LBRY` folder as detailed on the directories page.***
In addition to those two directories, users may also want to copy their LBRY downloads - this directory is normally set to your local Downloads folder but can also be configured via the LBRY app. To check your LBRY Downloads directory, open the LBRY app and go to Settings - it is listed in the `Download Directory` section. If you chose not to copy over your Downloads folder, the content could be regenerated from the data in your `lbrynet` folder at a later time via the LBRY app.
@@ -23,7 +38,7 @@ To summarize, the main directories to consider when backing up or migrating a LB
## How do I migrate all LBRY related data to a new installation?
1. Install [LBRY](/get) onto the target PC. Close LBRY after the initial startup. LBRY minimizes to the system tray by defailt, so make sure that is is completely closed.
1. Install [LBRY](/get) onto the target PC. Close LBRY after the initial startup. LBRY minimizes to the system tray by default, so make sure that is is completely closed.
2. Copy the `lbrynet` folder from the previous section into the appropriate [location](/faq/lbry-directories) on your new installation.
3. Copy the `lbryum` folder from the previous section into the appropriate [location](/faq/lbry-directories) on your new installation.
4. Copy your LBRY Downloads from the previous section into the appropriate location.
+23 -8
View File
@@ -1,13 +1,28 @@
---
title: How does LBRY benefit content consumers? Why should I bother caring?
category: LBRY 101
order: 2
---
{
"title": "How does LBRY benefit content consumers? Why should I bother caring?",
"url": "/faq/benefit-consumers",
"type": "faq",
"source_url": "https://lbry.com/faq/benefit-consumers",
"description": "Do you watch YouTube? Imagine paying a few cents to eliminate all ads. 100% of the payment will go directly…",
"images": [
"https://lbry.com/img/og-faq.png?_cache=2026-10-31"
],
"og_type": "article",
"twitter_card": "summary_large_image",
"news_feed": false,
"footer_email_href": "/cdn-cgi/l/email-protection#a0c8c5cccccfe0ccc2d2d98ec3cfcd",
"footer_email_code": "89e1ece5e5e6c9e5ebfbf0a7eae6e4",
"meta_title": "How does LBRY benefit content consumers? Why should I bother caring?",
"category": "LBRY 101",
"source_file": "content/faq/benefit-consumers.md",
"edit_url": "https://github.com/lbryio/lbry.com/tree/master/content/faq/benefit-consumers.md",
"source_order": 2,
"weight": 2
}
Do you watch YouTube? Imagine paying a few cents to eliminate all ads. 100% of the payment will go directly to the content creator – and they'll still be earning more than YouTube offers, so they'll want to make even more of the content you love.
Do you use BitTorrent? Imagine getting paid to seed files into the network. Because there is a marketplace for these files, you can finally find rare songs and films that can't support a torrent swarm based on popularity alone.
Do you use BitTorrent? Imagine getting [paid to seed](https://lbry.com/faq/host-content) files into the network. Because there is a marketplace for these files, you can finally find rare songs and films that can't support a torrent swarm based on popularity alone.
Do you shop on the iTunes Store? Imagine paying less for songs, TV episodes, and music videos while having 100% of the cost go directly to the creators.
LBRY is a digital media library at your fingertips. It can store any kind of content and make it available at low cost on demand. In a few years time, LBRY may become your one-stop-shop for everything digital, from ebooks to video games to movies. One app to rule them all – but still leaving more power in your hands because it is decentralized by design.
LBRY is a digital media library at your fingertips. It can store any kind of content and make it available at low cost on demand. In a few years, LBRY may become your one-stop-shop for everything digital, from ebooks to video games to movies. One app to rule them all – but still leaving more power in your hands because it is decentralized by design.
+34 -16
View File
@@ -1,41 +1,59 @@
---
title: What is mining and what are the LBRY block rewards?
category: mining
order: 1
---
{
"title": "What is mining and what are the LBRY block rewards?",
"url": "/faq/block-rewards",
"type": "faq",
"source_url": "https://lbry.com/faq/block-rewards",
"description": "What is mining? Mining is a process where computing power is used to verify transactions on the LBRY network and…",
"images": [
"https://lbry.com/img/og-faq.png?_cache=2026-10-31"
],
"og_type": "article",
"twitter_card": "summary_large_image",
"news_feed": false,
"footer_email_href": "/cdn-cgi/l/email-protection#d2bab7bebebd92beb0a0abfcb1bdbf",
"footer_email_code": "066e636a6a69466a64747f2865696b",
"meta_title": "What is mining and what are the LBRY block rewards?",
"category": "mining",
"source_file": "content/faq/block-rewards.md",
"edit_url": "https://github.com/lbryio/lbry.com/tree/master/content/faq/block-rewards.md",
"source_order": 1,
"weight": 61
}
## What is mining?
Mining is a process where computing power is used to verify transactions on the LBRY network and add them to the public ledger (LBRY blockchain). It is also a process of how additional new LBRY credits (LBC) are created as a reward for the successful miners (see details below). The process uses the mining software to calculate complex mathematical puzzles in order to secure the transactions.
Mining is a process where computing power is used to verify transactions on the LBRY network and add them to the public ledger (LBRY blockchain). It is also the process of how new LBRY Credits (LBC) are created as a reward for the successful miners (see details below). The process uses the mining software to calculate complex mathematical puzzles in order to secure the transactions.
Both CPU and GPU hardware can be used for mining, but the current market is dominated by GPU and ASIC mining. LBRY uses a mix of SHA512, SHA256 and RIPEMD hash functions in its algorithm. To put it in the most simple terms: mining enables secure and fast LBC transactions.
## Only trust the source
The source code, and not this file, is the only true definition of the block rewards. That source file is located here in [`master`]:
[https://github.com/lbryio/lbrycrd/blob/master/src/validation.cpp](https://github.com/lbryio/lbrycrd/blob/master/src/validation.cpp#L1025)
The source code, and not this file, is the only true definition of the block rewards. That source file is located [here](https://github.com/lbryio/lbrycrd/blob/v0.17.3.2/src/validation.cpp#L1025).
## Mining reward schedule
Eventually 1,083,202,000<sup>1</sup> LBRY credits will exist.
Eventually 1,083,202,000<sup>1</sup> LBRY Credits will exist.
<sup>1</sup>This value was [updated from 1B](https://github.com/lbryio/lbry.com/commit/4b4a8401d8ada40203d2bfb232066f42c4ac7a84) (which was a nice round number for a FAQ) on 09/21/2018 with the goal of increasing accuracy and transparency. [View the calculation here to verify](https://www.onlinegdb.com/r1NQOiyYQ) the source code referenced above.
They are awarded on the following schedule:
* The genesis block creates 400,000,000 credits to be administered by LBRY, Inc. 300,000,000 of these will be strategically allocated to partners, many of whom have a direct interest in the naming layer. It also includes 100,000,000 earmarked for charity. Additionally, some may be given directly to the public in ways that add value and make sense. 100,000,000 are owned by LBRY directly.
* The genesis block created 400,000,000 Credits to be administered by LBRY, Inc. 300,000,000 of these will be strategically allocated to partners, many of whom have a direct interest in the naming layer. It also includes 100,000,000 earmarked for charity. Additionally, some may be given directly to the public in ways that add value and make sense. 100,000,000 are owned by LBRY directly.
* The remaining 600,000,000 are mined in 3 stages:
1. The first stage goes from block 1 to block 5100 and will take roughly 9 days. Every block in this stage has a reward of 1 credit. This is the testing stage, to ensure that there are no glaring problems with the blockchain.
1. The first stage went from block 1 to block 5100 and took roughly 9 days. Every block in this stage had a reward of 1 credit. This was the testing stage, to ensure that there were no glaring problems with the blockchain.
2. The second stage is the ramp-up. It goes from block 5101 to block 55000 (roughly 3 months of mining). During this stage, the block reward increases linearly from 2 to 500. 500 is the largest block reward available.
2. The second stage was the ramp-up. It went from block 5101 to block 55000 (roughly 3 months of mining). During this stage, the block reward increased linearly from 2 to 500. 500 was the largest block reward available.
3. The final stage is the "normal" mining stage. From block 55001 onward, the block reward decreases logarithmically over the course of 20 years.
3. The final and current stage is the "normal" mining stage. From block 55001 onward, the block reward decreases logarithmically over the course of 20 years.
* Block rewards ramp up slowly because we want to ensure that users are given some time to get LBRY up and running, and to avoid unfairly benefiting the earliest users.
* Block rewards ramped up slowly because we wanted to ensure that users were given some time to get LBRY up and running, and to avoid unfairly benefiting the earliest users.
* To see the current block reward, visit the [LBRY Blockchain Explorer](https://explorer.lbry.com) and explore the latest block details.
## Other Information
The LBRY blockchain has a targeted block time of 2.5 minutes. This doesn't mean that a block will be confirmed exactly every 2.5 minutes, just that the average time between blocks is about that length.
The max size of each block is currently around 2 MB. In an average block, this translates to around 1800 transactions.
## Where can I see this visually?
The [Stats page on the Explorer](https://explorer.lbry.com/stats) has this information, including inflation rates and emission schedule. It can be exported to CSV.
+20 -8
View File
@@ -1,9 +1,21 @@
---
title: Do you have a blockchain explorer?
category: other
---
{
"title": "Do you have a blockchain explorer?",
"url": "/faq/blockchain-explorer",
"type": "faq",
"source_url": "https://lbry.com/faq/blockchain-explorer",
"description": "Yep. You can see it at https://explorer.lbry.com.",
"images": [
"https://lbry.com/img/og-faq.png?_cache=2026-10-31"
],
"og_type": "article",
"twitter_card": "summary_large_image",
"news_feed": false,
"footer_email_href": "/cdn-cgi/l/email-protection#95fdf0f9f9fad5f9f7e7ecbbf6faf8",
"footer_email_code": "741c1118181b341816060d5a171b19",
"meta_title": "Do you have a blockchain explorer? - LBRY",
"category": "other",
"source_file": "content/faq/blockchain-explorer.md",
"edit_url": "https://github.com/lbryio/lbry.com/tree/master/content/faq/blockchain-explorer.md",
"weight": 74
}
Yep. You can see it at [https://explorer.lbry.com](https://explorer.lbry.com).
If the enslaved squirrels that run our community block explorer are sleeping, try
[https://lbrypool.com/explorer/LBC](https://lbryexplorer.tech/)
-171
View File
@@ -1,171 +0,0 @@
---
title: How do I use the Telegram bot?
category: bots
order: 1
---
LBRY Telegram bot is member of the [LBRY official Telegram group](https://t.me/lbryofficial). And running 24/7 on [lbry.melroy.org](https://lbry.melroy.org).
The bot is able to support you with all your basic questions regarding LBRY, including but not limited to listing the top channels, the latest LBRY token (LBC) price, mining data, address/transaction(s)/tip information and so much more.
**Hint:** Since the bot is part of the channel group, you can directly start typing the command starting with `/`; Telegram could support you by auto-completing the commands. Starting the commands with `!`-sign is also supported.
**Good to know:** LBRY Telegram bot is currently hosted on [gitlab.melroy.org](https://gitlab.melroy.org/melroy/lbry-bot) with a mirror on [Github.com](https://github.com/danger89/LBRY-Bot). You are free to create pull-requests with bug fixes or new features.
## Basic commands
### Help
The only command you really need to remember is `/help`, which should point you in the right direction.
- `/help@LBRY_telegram_bot`
![](https://spee.ch/@Melroy:3/help.png)
### Status
Retrieve Lbrynet, Lbrycrd, Chainquery status. Including current versions of the services used by the bot.
- `/status`
![](https://spee.ch/@Melroy:3/status.png)
### Network info
Get some general LBRY Networking info.
- `/networkinfo`
![](https://spee.ch/@Melroy:3/networkinfo.png)
### Stats
Get blockchain, mining information (hashrate, difficulty and reward) and exchange statistics.
- `/stats`
![](https://spee.ch/@Melroy:3/stats.png)
### Price
Get the latest market price, percentage of change and more.
- `/price`
![](https://spee.ch/@Melroy:3/price2.png)
### Latest content
Get the latest uploaded content, with links to the content.
- `/lastcontent`
![](https://spee.ch/@Melroy:3/lastcontent.png)
### Latest channels
Get the last created channels, with links to the channels.
- `/lastchannels`
![](https://spee.ch/@Melroy:3/lastchannels.png)
### Latest blocks
Get the last 10 mined blocks.
- `/lastblocks`
![](https://spee.ch/@Melroy:3/lastblocks.png)
### Top 10
Top 10 biggest transactions & top 10 most subscribed (popular) channels.
- `/top10`
![](https://spee.ch/@Melroy:3/top10.png)
## Advance commands
There are advanced bot commands that require additional user input.
### File
Retrieve content by URL, with thumbnail and link to the content as well.
- `/file <URL>`
![](https://spee.ch/@Melroy:3/file2.png)
### Tips
Get the top 10 highest tips of the given name (channel or content).
- `/tips <name>`
![](https://spee.ch/@Melroy:3/tips.png)
### Content Tips
Get the top 10 highest tips of given content URI.
- `/contenttips <content URI>`
![](https://spee.ch/@Melroy:3/contenttips.png)
### Transaction
Get transaction information, like amount, block-height, in/out.
- `/transaction <hash>`
![](https://spee.ch/@Melroy:3/transaction.png)
### Address
Get address information, like 'balance'.
- `/address <address>`
![](https://spee.ch/@Melroy:3/address.png)
### Transactions
Get the transaction list of a given address.
- `/transactions <address>`
![](https://spee.ch/@Melroy:3/transactions.png)
### Block
Get block information, like block size, difficulty, confirmations and more.
- `/block <hash or block height>`
![](https://spee.ch/@Melroy:3/block.png)
## Do you have questions?
The bot helps you to answer some basics FAQs as well:
### Why LBRY?
- `/why`
![](https://spee.ch/@Melroy:3/why.png)
### What is LBRY?
- `/what`
### How does LBRY work?
- `/how`
### How long has LBRY existed?
- `/age`
![](https://spee.ch/@Melroy:3/age.png)
Loaded 100 of 1421 files, more files were not shown because too many files have changed in this diff. Show more