Compare commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
5246059b93 | ||
|
|
ac46949bb5 | ||
|
|
f447be0c5a | ||
|
|
b5d40c8165 | ||
|
|
94a285e468 | ||
|
|
8853a9620f |
No files matched your search
@@ -1,11 +0,0 @@
|
||||
# To get started with Dependabot version updates, you'll need to specify which
|
||||
# package ecosystems to update and where the package manifests are located.
|
||||
# Please see the documentation for all configuration options:
|
||||
# https://docs.github.com/github/administering-a-repository/configuration-options-for-dependency-updates
|
||||
|
||||
version: 2
|
||||
updates:
|
||||
- package-ecosystem: "composer" # See documentation for possible values
|
||||
directory: "/" # Location of package manifests
|
||||
schedule:
|
||||
interval: "daily"
|
||||
+1
-2
@@ -11,5 +11,4 @@ composer
|
||||
.ht*
|
||||
/vendor/
|
||||
.DS_Store
|
||||
.php_cs.cache
|
||||
.php-cs-fixer.cache
|
||||
.php_cs.cache
|
||||
@@ -0,0 +1,6 @@
|
||||
[submodule "web/scss/color"]
|
||||
path = web/scss/color
|
||||
url = https://github.com/lbryio/color
|
||||
[submodule "web/components"]
|
||||
path = web/components
|
||||
url = https://github.com/lbryio/components
|
||||
+7
-5
@@ -1,12 +1,13 @@
|
||||
# Installation
|
||||
|
||||
## Prerequisites
|
||||
To run this project, you'll need PHP 8.5 or newer, Composer, and macOS or Linux.
|
||||
To run this project, you'll need to have either PHP7 or Docker installed, and be using either macOS or Linux.
|
||||
|
||||
## Development
|
||||
- Install [PHP 8.5 or newer](https://www.php.net/downloads.php)
|
||||
- Install the PHP extensions `curl`, `dom`, `intl`, `mbstring`, `pdo_mysql`, and `xml`
|
||||
- Check out the project
|
||||
- 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
|
||||
|
||||
@@ -16,4 +17,5 @@ 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.
|
||||
- For production, configure Nginx and PHP-FPM to use `web/index.php` as the front controller.
|
||||
- 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,6 +1,6 @@
|
||||
The MIT License (MIT)
|
||||
|
||||
Copyright (c) 2015-2020 LBRY Inc.
|
||||
Copyright (c) 2015-2019 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,
|
||||
|
||||
@@ -9,9 +9,7 @@
|
||||
</div>
|
||||
|
||||
<div align="center">
|
||||
<a href="https://lbry.com">
|
||||
<img src="https://user-images.githubusercontent.com/24932514/113429766-a5137900-940b-11eb-91fa-2b2b7060df4b.png">
|
||||
</a>
|
||||
<img src="https://spee.ch/4/com-2019-march.png" title="Screenshot of lbry.com"/>
|
||||
</div>
|
||||
|
||||
<div align="center">
|
||||
@@ -22,10 +20,10 @@
|
||||
<a href="https://chat.lbry.com">
|
||||
<img src="https://img.shields.io/discord/362322208485277697.svg?style=flat-square&logo=discord"/>
|
||||
</a>
|
||||
</a>
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
## Installation
|
||||
Please see [INSTALL](INSTALL.md) for comprehensive, easy-to-follow instructions on running this project.
|
||||
|
||||
@@ -45,7 +43,7 @@ lbry.com provides functionality for redirecting to build assets of other LBRY re
|
||||
|
||||
`lbry.com/releases/<github_repo_name>.<extension>`
|
||||
|
||||
For example, to get the latest [lbry-desktop](https://github.com/lbryio/lbry-desktop) release on Windows, you would use the URL:
|
||||
For example, to get the latest [lbry-desktop](github.com/lbryio/lbry-desktop) release on Windows, you would use the URL:
|
||||
|
||||
`lbry.com/releases/lbry-desktop.exe`
|
||||
|
||||
@@ -67,18 +65,16 @@ Release candidates can also be targeted. For release candidates, use the followi
|
||||
## Security
|
||||
We take security seriously. Please contact [security@lbry.com](mailto:security@lbry.com) regarding any security issues.
|
||||
|
||||
[Our PGP key is here](https://lbry.com/faq/pgp-key) if you need it.
|
||||
[Our PGP key is here](https://keybase.io/lbry/key.asc) if you need it.
|
||||
|
||||
## Contact
|
||||
The primary contact for this project is [@lyoshenka](https://github.com/lyoshenka) (grin@lbry.com).
|
||||
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/@lbrycom) - LBRY Twitter page
|
||||
- [Facebook](https://www.facebook.com/lbrycom) - LBRY Facebook page
|
||||
- [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
|
||||
|
||||
+72
-1
@@ -1,2 +1,73 @@
|
||||
<?php
|
||||
require_once ROOT_DIR . '/vendor/autoload.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);
|
||||
+6
-31
@@ -1,42 +1,17 @@
|
||||
{
|
||||
"name": "lbry/lbry.com",
|
||||
"description": "Official website for the LBRY protocol",
|
||||
"license": "MIT",
|
||||
"require": {
|
||||
"php": "^8.5",
|
||||
"php": ">=7.0",
|
||||
"ext-curl": "*",
|
||||
"ext-dom": "*",
|
||||
"ext-iconv": "*",
|
||||
"ext-intl": "*",
|
||||
"ext-mbstring": "*",
|
||||
"ext-xml": "*",
|
||||
"ext-pdo": "*",
|
||||
"ext-pdo_mysql": "*",
|
||||
"ext-json": "*",
|
||||
"scssphp/scssphp": "^2.1",
|
||||
"erusev/parsedown": "^1.8",
|
||||
"erusev/parsedown-extra": "^0.9",
|
||||
"pelago/emogrifier": "^8.2",
|
||||
"mustangostang/spyc": "^0.6.3",
|
||||
"masterminds/html5": "^2.10"
|
||||
},
|
||||
"require-dev": {
|
||||
"roave/security-advisories": "dev-latest"
|
||||
},
|
||||
"autoload": {
|
||||
"classmap": [
|
||||
"controller/",
|
||||
"lib/",
|
||||
"model/",
|
||||
"view/"
|
||||
]
|
||||
},
|
||||
"scripts": {
|
||||
"test": "@php tests/smoke.php"
|
||||
},
|
||||
"config": {
|
||||
"platform": {
|
||||
"php": "8.5.0"
|
||||
}
|
||||
"leafo/scssphp": "0.7.6",
|
||||
"erusev/parsedown": "^1.6",
|
||||
"erusev/parsedown-extra": "^0.7.1",
|
||||
"pelago/emogrifier": "^2.0",
|
||||
"mustangostang/spyc": "^0.6.2"
|
||||
}
|
||||
}
|
||||
Generated
+74
-2241
File diff suppressed because it is too large.
Load diff
Binary file not shown.
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: Akinwale Ariwodola
|
||||
role: Mobile Engineer
|
||||
role: Mobile Developer
|
||||
email: akinwale@lbry.com
|
||||
twitter: akinwale
|
||||
github: akinwale
|
||||
|
||||
@@ -2,10 +2,8 @@
|
||||
name: Alex Grintsvayg
|
||||
role: Founder, Chief Technical Officer
|
||||
email: grin@lbry.com
|
||||
twitter: grin_io
|
||||
twitter: lyoshenka
|
||||
github: lyoshenka
|
||||
---
|
||||
|
||||
Grin drives technology development and manages infrastructure growth. Bringing LBRY to mainstream scale is his primary goal. Before LBRY, Grin designed and managed scalable infrastructure solutions for SaaS firms. He holds degrees in Computer Science and Psychology from Rensselaer Polytechnic Institute.
|
||||
|
||||
On the side, Grin is a competitive ultimate frisbee player, a father of two, and an occasional writer at [grin.io](https://grin.io).
|
||||
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.
|
||||
@@ -0,0 +1,9 @@
|
||||
---
|
||||
name: Alex Liebowitz
|
||||
role: App Developer
|
||||
email: aliebowitz@lbry.com
|
||||
---
|
||||
|
||||
Alex is responsible for the LBRY browsing application. An economist turned web developer, Alex joins an assortment of polymaths at LBRY.
|
||||
|
||||
Prior to joining LBRY, Alex helped build web and mobile apps for large national corporations. Alex also helps run a large podcasting network and brings knowledge and experience of the publishing industry.
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
name: Amit Tulshyan
|
||||
role: Protocol Developer Intern
|
||||
email: hackrush@lbry.com
|
||||
twitter: amittulshyan
|
||||
github: hackrush01
|
||||
---
|
||||
|
||||
Amit arrived at LBRY through mining. Diving into the world of cryptocurrency, he discovered LBRY Credits amongst the most profitable to mine. A few Slack messages later, he was making pull requests to the backend python code on GitHub.
|
||||
|
||||
When he’s not contributing his talents to LBRY, he loves practicing synth, guitar, and deeply contemplating quantum computing.
|
||||
|
||||
Amit is an IT undergraduate at National Institute of Technology - Durgapur in Durgapur, West Bengal, India.
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: Andrey Beletsky
|
||||
role: Backend Engineer
|
||||
email: andrey@lbry.com
|
||||
name: Andrey
|
||||
role: LBRY.tv Developer
|
||||
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.
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
name: Bill Bittner
|
||||
role: Former App Developer
|
||||
email: bill@lbry.com
|
||||
twitter: billbitt2000
|
||||
github: billbitt
|
||||
---
|
||||
|
||||
Bill's primary contributions were to [spee.ch](https://spee.ch), an open-source web application built on the LBRY Protocol.
|
||||
|
||||
Bill’s long-standing fascination with web applications eventually led him to utility-driven blockchains and, naturally, LBRY.
|
||||
|
||||
When he is not hacking on web apps, he enjoys drawing, playing soccer, and slowly working his way through his Steam library.
|
||||
@@ -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.
|
||||
@@ -1,12 +0,0 @@
|
||||
---
|
||||
name: Drew Hancock
|
||||
role: Community Coordinator
|
||||
email: drew@lbry.com
|
||||
twitter: lockoutdays
|
||||
---
|
||||
|
||||
Drew's role is to spread awareness of LBRY and get as many people using it as possible.
|
||||
He's active in the LBRY community, which means he spends a lot of time on social media.
|
||||
He also produces video content for the official LBRY and Odysee channels.
|
||||
|
||||
Drew is from Missouri and is an avid Kansas City Chiefs fan.
|
||||
@@ -1,7 +0,0 @@
|
||||
---
|
||||
name: Eliza Zheng
|
||||
role: Community Coordinator
|
||||
email: eliza.zheng@odysee.com
|
||||
---
|
||||
|
||||
Coming soon
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
name: Igor Gassmann
|
||||
role: App Developer Intern
|
||||
email: igor@lbry.com
|
||||
twitter: i_gassmann
|
||||
github: IGassmann
|
||||
---
|
||||
|
||||
Igor primarily contributed to the application. By the time he turned 16, Igor’s driving passion was clear (and it was not high school). So, he dropped out, and moved to Switzerland to build a career in software development.
|
||||
|
||||
It was Igor’s participation in [Praxis programs](http://discoverpraxis.com) that led him to LBRY. His long time interest in the crypto market and blockchain technology, coupled with his desire to work in a start-up environment, made LBRY seemed like a perfect fit (and the team agreed!).
|
||||
|
||||
When he is not coding, Igor enjoys discussing economics, philosophy, and politics.
|
||||
@@ -1,11 +1,11 @@
|
||||
---
|
||||
name: Jack Robison
|
||||
role: Founder, Protocol Engineer
|
||||
role: Founder, Protocol Developer
|
||||
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's path to developer 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.
|
||||
|
||||
|
||||
@@ -1,9 +0,0 @@
|
||||
---
|
||||
name: Jessop Breth
|
||||
role: App Engineer
|
||||
email: jessop@lbry.com
|
||||
twitter: giuseppe_aaron
|
||||
github: jessopb
|
||||
---
|
||||
|
||||
do not fight he com̡e̶s, ̕h̵is un̨ho͞ly radiańcé destro҉ying all enli̍̈́̂̈́ghtenment, HTML tags lea͠ki̧n͘g fr̶ǫm ̡yo͟ur eye͢s̸ ̛l̕ik͏e liquid pain, the song of re̸gular expression parsing will extinguish the voices of mortal man from the sphere I can see it can you see ̲͚̖͔̙î̩́t̲͎̩̱͔́̋̀ it is beautiful the final snuffing of the lies of Man ALL IS LOŚ͖̩͇̗̪̏̈́T ALL IS LOST the pon̷y he comes he c̶̮omes he comes the ichor permeates all MY FACE MY FACE ᵒh god no NO NOO̼OO NΘ stop the an*̶͑̾̾̅ͫ͏̙̤g͇̫͛͆̾ͫ̑͆l͖͉̗̩̳̟̍ͫͥͨe̠̅s ͎a̧͈͖r̽̾̈́͒͑e not rè̑ͧ̌aͨl̘̝̙̃ͤ͂̾̆ ZA̡͊͠͝LGΌ ISͮ̂҉̯͈͕̹̘̱ TO͇̹̺ͅƝ̴ȳ̳ TH̘Ë͖́̉ ͠P̯͍̭O̚N̐Y̡ H̸̡̪̯ͨ͊̽̅̾̎Ȩ̬̩̾͛ͪ̈́̀́͘ ̶̧̨̱̹̭̯ͧ̾ͬC̷̙̲̝͖ͭ̏ͥͮ͟Oͮ͏̮̪̝͍M̲̖͊̒ͪͩͬ̚̚͜Ȇ̴̟̟͙̞ͩ͌͝S̨̥̫͎̭ͯ̿̔̀ͅ
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: Jimmy Kiselak
|
||||
role: Founder, Core Engineer
|
||||
role: Founder, Core Developer
|
||||
email: jimmy@lbry.com
|
||||
---
|
||||
|
||||
|
||||
@@ -0,0 +1,9 @@
|
||||
---
|
||||
name: Job Evers-Meltzer
|
||||
role: VP of Engineering
|
||||
email: jobevers@lbry.com
|
||||
---
|
||||
|
||||
Job was early to discover LBRY and made himself indispensable almost immediately. Job manages the engineering team, project roadmap, and reviews most code changes. Job also handles LBRY builds, quality assurance, analytics, and an assortment of ad hoc projects.
|
||||
|
||||
Job attended the Massachusetts Institute of Technology, where he obtained a degree in mathematics. Job has experience in quantitative finance, analytical development, and data engineering.
|
||||
@@ -1,17 +0,0 @@
|
||||
---
|
||||
name: Johnny Nelson
|
||||
role: Senior Machine Learning Engineer
|
||||
email: jbn@lbry.com
|
||||
twitter: generativist
|
||||
github: jbn
|
||||
---
|
||||
|
||||
Johnny thinks a lot about how attention works on the internet. Having started programming in elementary
|
||||
school, he became infatuated with how we communicate with and through computers. Eventually, he did
|
||||
a Ph.D. studying belief systems computationally. Immediately afterwards he left academia, intent on
|
||||
putting what he learned into practice.
|
||||
|
||||
Johnny cares about the systems we inhabit -- how they allow us to exchange ideas and find each other.
|
||||
In short, he's motivated by the premise that we can "engineer the noosphere." The internet and
|
||||
everything after is still in early development! Given that he believes censorship-resistance is a
|
||||
long-term evolutionary pressure, it doesn't make sense to work on a platform that doesn't treat it as a given.
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: Josh Finer
|
||||
role: Founder, Director of Operations
|
||||
role: Founder, Director of Operations and Analytics
|
||||
email: josh@lbry.com
|
||||
twitter: finer9
|
||||
github: finer9
|
||||
|
||||
@@ -1,8 +0,0 @@
|
||||
---
|
||||
name: Julian Chandra
|
||||
role: Chief Marketing Officer
|
||||
email: julian@lbry.com
|
||||
github: julianchandra
|
||||
---
|
||||
|
||||
Julian brings a wealth of business, marketing, digital content and startup experience to LBRY. Since leaving TikTok, Julian's focus has been on how to take LBRY to the next level.
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: Kay Kurokawa
|
||||
role: Protocol Engineer
|
||||
role: Protocol Developer
|
||||
email: kay@lbry.com
|
||||
twitter: kaykurokawa
|
||||
github: kaykurokawa
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: Lex Berezhny
|
||||
role: Protocol Engineer
|
||||
role: Protocol Developer
|
||||
email: lex@lbry.com
|
||||
twitter: eukreign
|
||||
github: eukreign
|
||||
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
name: Liam Cardenas
|
||||
role: App Developer
|
||||
email: liam@lbry.com
|
||||
twitter: ljcio
|
||||
github: liamcardenas
|
||||
---
|
||||
|
||||
As a lifelong entrepreneur and crypto-anarchist, the LBRY project was of high interest to Liam on many levels – meeting the team and learning more about app development goals made his decision to become a full-fledged LBRYian an easy one.
|
||||
|
||||
Liam’s sincere passion for making distributed censorship-resistant software easy to use has been a boon to the team.
|
||||
|
||||
In addition to his work with LBRY, Liam is also an advisor to several startups and blockchain projects.
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: Mark Beamer
|
||||
role: Backend Engineer
|
||||
role: Elastic Search and Database Developer
|
||||
email: mark@lbry.com
|
||||
github: tiger5226
|
||||
---
|
||||
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
name: Natalie Mitchell
|
||||
role: Former Director of Growth and Branding
|
||||
email: natalie@lbry.com
|
||||
twitter: blockchainbandi
|
||||
github: blckchnprncss
|
||||
---
|
||||
|
||||
Natalie has been interested in blockchain technology and open-source everything since the early days of Bitcoin, and has been recruiting, managing operations, and coaching top notch talent to success for even longer.
|
||||
|
||||
She contributed to procedures, and communications efforts that help the team to work to its potential and remain efficient as the LBRY project grows.
|
||||
|
||||
Externally, she contributed to authentically representing the LBRY mission and the team working tirelessly to keep it moving forward, through creative partnerships, sometimes-hair-brained schemes, and a drive to connect with everyone.
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: Niko Storni
|
||||
role: Infrastructure Engineer
|
||||
role: DevOps Engineer/Developer
|
||||
email: Niko@lbry.com
|
||||
twitter: Nikooo777
|
||||
github: Nikooo777
|
||||
|
||||
@@ -0,0 +1,8 @@
|
||||
---
|
||||
name: Paul Webb
|
||||
role: Web Developer
|
||||
email: paul@lbry.com
|
||||
---
|
||||
|
||||
Paul Webb is an “architech” who loves designing and building great experiences. He is self-taught and got his start in the recession of ’08 and later gained an apprenticeship from Thoughtbot. The rest, as they say, is history.
|
||||
When he isn’t building for the web, you can find him building in Fortnite and failing fantabulously.
|
||||
@@ -0,0 +1,11 @@
|
||||
---
|
||||
name: Reilly Smith
|
||||
role: Former Community Manager
|
||||
email: reilly@lbry.com
|
||||
---
|
||||
|
||||
Reilly holds a BA in Film and Media Studies from the University of Oklahoma and consequently has spent a significant amount of time washing dishes.
|
||||
|
||||
His films have shown at Sundance, SXSW, Dallas IFF, and LA Film Fest and he has produced series for Zero Day Fox and Disney.
|
||||
|
||||
Reilly is passionate about eliminating middlemen in show business.
|
||||
@@ -1,18 +0,0 @@
|
||||
---
|
||||
name: Roy Lee
|
||||
role: Blockchain Engineering Manager
|
||||
email: roylee@lbry.com
|
||||
github: roylee17
|
||||
---
|
||||
|
||||
Roy is an outdoor enthusiast, an avid hiker, who has day hiked a few 14ners, including Mt. Whitney,
|
||||
Langley, Shasta. Recently, he enjoyed his inaugural season of snowboarding at Tahoe, and can’t wait
|
||||
for more seasons to come.
|
||||
|
||||
Professionally, he is passionate about building software as well as teams. The broad interest in
|
||||
software architectures, system design, distributed systems, and product development has led him
|
||||
to the latest endeavor in LBRY.
|
||||
|
||||
Prior to LBRY, he has built and scaled out the Cloud Native Edge Platform at TikTok, which serves
|
||||
huge traffics around the globe. Before that, he also prototyped and led EMV payment products
|
||||
developments in PayPal.
|
||||
@@ -1,9 +1,9 @@
|
||||
---
|
||||
name: Sean Yesmunt
|
||||
role: App Engineer
|
||||
role: App Developer
|
||||
email: sean@lbry.com
|
||||
twitter: seanyesmunt
|
||||
github: neb-b
|
||||
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.
|
||||
|
||||
@@ -3,6 +3,6 @@ name: Stephan Kinsella
|
||||
role: Legal Advisor
|
||||
---
|
||||
|
||||
N. Stephan Kinsella is an attorney in Houston with over twenty-nine years' experience in patent, intellectual property, and general commercial and corporate law. He was previously General Counsel for Applied Optoelectronics, Inc., a partner with Duane Morris, and adjunct law professor at South Texas College of Law. He is the founder and director of the [Center for the Study of Innovative Freedom](http://c4sif.org/), serves on the Advisory Board to the [Open Crypto Alliance](https://www.opencryptoalliance.org/) and other groups and publications; and has published numerous articles and books on intellectual property law and legal topics including *[Against Intellectual Propert*y](https://mises.org/library/against-intellectual-property-0) (Mises Institute, 2008) *[International Investment, Political Risk, and Dispute Resolution: A Practitioner's Guid*e](http://www.kinsellalaw.com/iipr/) (Oxford, 2020), *[Law in a Libertarian World: Legal Foundations of a Free Societ*y](http://www.stephankinsella.com/llw/) (2021), and *[Copy This Book: The Case for Abolishing Intellectual Propert*y](http://www.stephankinsella.com/copy-this-book/) (forthcoming).
|
||||
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. (international business law) from [King's College London-University of London](http://www.kcl.ac.uk/), a JD from the Paul M. Hebert Law Center at [Louisiana State University](https://lsu.edu/), as well as BSEE and MSEE degrees from LSU. He is licensed to practice law in Texas, Louisiana, and Pennsylvania, and before the US Patent & Trademark Office. His websites are [StephanKinsella.com](http://stephankinsella.com/) and [KinsellaLaw.com](http://kinsellalaw.com/).
|
||||
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)
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: Tom Zarebczan
|
||||
role: Community Support & Engagement
|
||||
role: Community Support and Engagement
|
||||
email: tom@lbry.com
|
||||
twitter: TomZarebczan
|
||||
github : tzarebczan
|
||||
|
||||
@@ -1,7 +0,0 @@
|
||||
---
|
||||
name: Victor Shyba
|
||||
role: Protocol Engineer
|
||||
github: shyba
|
||||
---
|
||||
|
||||
Coming soon
|
||||
@@ -1,8 +0,0 @@
|
||||
---
|
||||
name: Xander Luciano
|
||||
role: Application Engineer
|
||||
email: xander@lbry.com
|
||||
github: DispatchCommit
|
||||
---
|
||||
|
||||
Xander works on the apps and livestreaming.
|
||||
+1
-1
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: You
|
||||
role: Engineer, Designer, Economist, Marketer, Investor, ???
|
||||
role: Developer, Designer, Economist, Marketer, Investor, ???
|
||||
email: jeremy@lbry.com
|
||||
---
|
||||
|
||||
|
||||
@@ -0,0 +1,18 @@
|
||||
---
|
||||
category: browser
|
||||
title: Internationalization of LBRY App
|
||||
award: 2000
|
||||
status: complete
|
||||
date: '2016-07-01'
|
||||
---
|
||||
|
||||
The LBRY App is currently lacking support for internationalization.
|
||||
|
||||
To complete this bounty, [lbry-desktop](https://github.com/lbryio/lbry-desktop) must be modified as follows:
|
||||
|
||||
- Add [gettext](https://en.wikipedia.org/wiki/Gettext) internationalization calls to the React app
|
||||
- Store selected language in the user settings
|
||||
- Load and perform translation based on language settings
|
||||
- Existing component text and messaging must be wrapped in translation calls
|
||||
|
||||
It is probably a good idea to consult with our development team on [Discord chat](https://chat.lbry.com) or via [email](mailto:hello@lbry.com) before completing this bounty in its entirety.
|
||||
@@ -0,0 +1,18 @@
|
||||
---
|
||||
category: browser
|
||||
title: Automatic App Updates
|
||||
award: 1000
|
||||
status: complete
|
||||
date: '2017-07-22'
|
||||
---
|
||||
|
||||
The LBRY app currently does not update itself automatically, however electron does support this feature.
|
||||
|
||||
To complete this bounty, [lbry-desktop](https://github.com/lbryio/lbry-desktop) must be modified as follows:
|
||||
|
||||
- Detect when a new latest release is available, download it and prompt the user with a "Restart LBRY" / "I'll do it later" dialog to have the update take effect.
|
||||
- Parse the changelog for the latest release. If it contains `Security` items, carry out the update automatically without presenting the "I'll do it later" option.
|
||||
- When an update begins store an update-history tracking file detailing what the version being updated is, what version it is being updated to, and when the update happened.
|
||||
- Upon starting the app after an update, alert the user that the update was successful (and note if it contained security updates), and update the history file to indicate that the update was successful.
|
||||
|
||||
It is probably a good idea to consult with our development team on [Discord chat](https://chat.lbry.com) or via email before completing this bounty in its entirety.
|
||||
@@ -0,0 +1,50 @@
|
||||
---
|
||||
category: daemon
|
||||
title: Add Support for BitTorrent
|
||||
award: 10000
|
||||
status: completed
|
||||
date: '2016-07-01'
|
||||
---
|
||||
|
||||
Add support for the BitTorrent protocol to [`lbrynet`](https://github.com/lbryio/lbry) and [`lbryschema`](https://www.github.com/lbryio/lbryschema).
|
||||
|
||||
The LBRY blockchain supports storing metadata that can be resolved by a human friendly URI.
|
||||
This metadata is defined by a flexible protobuf based schema, [lbryschema](https://www.github.com/lbryio/lbryschema).
|
||||
|
||||
A simple example looks like:
|
||||
|
||||
```
|
||||
{
|
||||
"version": "_0_0_1",
|
||||
"claimType": "streamType",
|
||||
"stream": {
|
||||
"source": {
|
||||
"source": "d5169241150022f996fa7cd6a9a1c421937276a3275eb912790bd07ba7aec1fac5fd45431d226b8fb402691e79aeb24b",
|
||||
"version": "_0_0_1",
|
||||
"contentType": "video/mp4",
|
||||
"sourceType": "lbry_sd_hash"
|
||||
},
|
||||
"version": "_0_0_1",
|
||||
"metadata": {
|
||||
"license": "LBRY inc",
|
||||
"description": "What is LBRY? An introduction with Alex Tabarrok",
|
||||
"language": "en",
|
||||
"author": "Samuel Bryan",
|
||||
"title": "What is LBRY?",
|
||||
"version": "_0_1_0",
|
||||
"nsfw": false,
|
||||
"licenseUrl": "",
|
||||
"preview": "",
|
||||
"thumbnail": "https://s3.amazonaws.com/files.lbry.io/logo.png"
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
The [source field](https://github.com/lbryio/lbryschema/blob/master/lbryschema/proto/source.proto) is designed to be extended and support resolution to multiple protocols. To complete this, lbryschema and lbrynet must be modified to:
|
||||
|
||||
- Support the BitTorrent protocol via `python-libtorrent` or similar.
|
||||
- Support the `sourceType` of `btih` in source.proto in lbryschema
|
||||
- Add a BitTorrent downloader and factory for use in `EncryptedFileManager`, to be used as an alternative to `ManagedEncryptedFileDownloader`
|
||||
- Use all of this to resolve a BTIH from a claim and download data via BitTorrent when requested
|
||||
- Probably a lot more stuff!
|
||||
@@ -0,0 +1,33 @@
|
||||
---
|
||||
category: code
|
||||
title: Bulk Sync/Upload Utility
|
||||
award: 500
|
||||
status: completed
|
||||
date: '2018-03-20'
|
||||
---
|
||||
|
||||
Completed in: https://github.com/marcdeb1/lbry_uploader
|
||||
|
||||
This bounty is to create a utility that can bulk upload a series of videos to LBRY. A LBRY term intern started implementing this in https://github.com/filipnyquist/lbrysync - this can be used as a base to fill in the rest of the required features.
|
||||
|
||||
This utility is for semi-technical users who have a large amount of content they want to sync. A good example use case would be the videos from a conference.
|
||||
|
||||
The typical input to the utility would be a CSV exported from a spreadsheet. The following columns would be included:
|
||||
|
||||
- Title
|
||||
- File name, relative file path, or absolute file path
|
||||
- Description
|
||||
- Thumbnail URL
|
||||
- Channel name
|
||||
- Desired LBRY URL (optional - can be created from file name)
|
||||
- Desired bid amount (optional - can default to amount across all files)
|
||||
- Possibly something else sensible that the bounty writer has neglected to include ;)
|
||||
|
||||
The utility must:
|
||||
|
||||
- Process each line and perform an upload
|
||||
- Give good feedback as to the state of the sync (e.g. it should give me feedback as it progresses)
|
||||
- Properly finish the sync (i.e. it shouldn't exit until it confirms all content has actually published and synced)
|
||||
- Be fully idempotent (stopping / halting the script midway and restarting it should never cause a problem)
|
||||
|
||||
The utility can assume at least moderate technical competency. While we always support user-friendliness, this tool would only be used by a user of at least moderate sophistication.
|
||||
@@ -0,0 +1,11 @@
|
||||
---
|
||||
category: other
|
||||
title: Custom Project
|
||||
award: 250-50000+
|
||||
status: available
|
||||
date: '2016-07-01'
|
||||
---
|
||||
|
||||
Have a great idea on how to improve or spread LBRY? Let's talk.
|
||||
|
||||
Come to us with a specific proposal of how you can help LBRY grow and we'll let you know what it's worth.
|
||||
@@ -0,0 +1,15 @@
|
||||
---
|
||||
category: design
|
||||
title: Nice 404 Page for lbry.com
|
||||
award: 250
|
||||
status: complete
|
||||
date: '2017-09-07'
|
||||
---
|
||||
|
||||
Our 404 page is very bland. We'd like something that's more
|
||||
|
||||
- **helpful** - tell the user what happened, and give them some things to do next
|
||||
- **pretty** - we spent very little time on the one we have
|
||||
- **humorous** - everyone likes funny things
|
||||
|
||||
For more ideas, [try Google](https://www.google.com/search?q=great+404+page+design).
|
||||
@@ -0,0 +1,19 @@
|
||||
---
|
||||
category: code
|
||||
title: Hardware Wallet Integration
|
||||
award: 750
|
||||
status: available
|
||||
date: '2018-05-25'
|
||||
---
|
||||
|
||||
Since LBRY is a fork of Bitcoin Core, integrating into existing hardware wallet platforms should be fairly straightforward. Two of the most popular hardware wallet platforms are Ledger and Trezor. You can find all the LBRY specific blockchain modifications on our [LBRYcrd GitHub repo](https://github.com/lbryio/lbrycrd) and more specifically in the [chain params code](https://github.com/lbryio/lbrycrd/blob/master/src/chainparams.cpp).
|
||||
|
||||
The Trezor integration is a bit more involved and thus includes a 30% bonus on top of the stated bounty amount.
|
||||
- [Ledger GitHub](https://github.com/LedgerHQ/ledger-nano-s) - Ledger Nano GitHub respository with guidelines on how to develop. This will involve setting up their SDK and creating a Chrome app.
|
||||
- [Trezor GitHub](https://github.com/trezor) - Please see Trezor's [developer guide](https://doc.satoshilabs.com/trezor-tech) for more information on integrations.
|
||||
|
||||
Status:
|
||||
Ledger - In Progress:
|
||||
https://github.com/LedgerHQ/ledger-live-common/pull/49
|
||||
https://github.com/LedgerHQ/blue-app-btc/pull/47
|
||||
https://github.com/LedgerHQ/lib-ledger-core/pull/24
|
||||
@@ -0,0 +1,23 @@
|
||||
---
|
||||
category: daemon
|
||||
title: Add Support for HTTP
|
||||
award: 3000
|
||||
status: completed
|
||||
date: '2016-11-01'
|
||||
---
|
||||
|
||||
Add support for resolution via HTTP to [`lbry`](https://github.com/lbryio).
|
||||
|
||||
The LBRY blockchain supports storing metadata about media content. A simplified, sample entry looks like:
|
||||
|
||||
```
|
||||
title: "What is LBRY?",
|
||||
language: "en",
|
||||
description: "What is LBRY? An introduction with Alex Tabarrok",
|
||||
author: "Samuel Bryan",
|
||||
sources: {
|
||||
lbry_sd_hash : "d5169241150022f996fa7cd6a9a1c421937276a3275eb912790bd07ba7aec1fac5fd45431d226b8fb402691e79aeb24b"
|
||||
}
|
||||
```
|
||||
|
||||
The `sources` field is designed to be extended and support resolution to multiple protocols. To complete this the LBRY daemon must be modified to read `http` as a source key and use this key to access the data via HTTP (or HTTPS) when present.
|
||||
@@ -0,0 +1,29 @@
|
||||
---
|
||||
category: code
|
||||
title: LBRY Binding in Any Programming Language
|
||||
award: 250
|
||||
status: available
|
||||
date: '2018-05-25'
|
||||
---
|
||||
|
||||
When the LBRY daemon is running, it provides a set of API calls available via a webserver running on localhost.
|
||||
|
||||
We want to make it as easy as possible to interact with LBRY in every programming language.
|
||||
|
||||
Completing this bounty involves creating a simple library to make it as easy as possible to interact with the LBRY protocol in a language we do not already have a binding for. Ideally, this also includes the LBRYcrd API. See php example below for details.
|
||||
|
||||
An example of a binding can be found in the [php-api](https://github.com/lbryio/php-api) repo and the entire listing can be found on [lbry.tech](https://lbry.tech/resources/api-wrappers).
|
||||
|
||||
A binding can typically be written using cURL in less than 100 lines of code. The repo should be well documented for the wrapper language and have install/setup instructions and tests.
|
||||
|
||||
If you are pursuing this effort, please [email us](mailto:hello@lbry.com) so we can update this bounty with the current progress.
|
||||
|
||||
Bounty Status:
|
||||
Ruby - Completed
|
||||
Lua - Completed
|
||||
Java - Completed
|
||||
Javascript - Completed
|
||||
Rust - Started/Claimed
|
||||
C++ - Completed
|
||||
Python - Completed
|
||||
Dart - Completed
|
||||
@@ -0,0 +1,19 @@
|
||||
---
|
||||
category: human
|
||||
title: LBRY Community Rep
|
||||
award: 300
|
||||
status: available
|
||||
date: '2016-07-01'
|
||||
---
|
||||
|
||||
Excited about LBRY? Earn some credits for it!
|
||||
|
||||
We're looking for people who can introduce and provide expertise to specific communities. This could be a college, music scene, city, or online community.
|
||||
|
||||
Participants in this program will:
|
||||
|
||||
- Receive invites for their group
|
||||
- Receive additional credits to share with their group
|
||||
- Communicate regularly with LBRY team members
|
||||
|
||||
This bounty is not open to just anyone. Please contact [Jeremy](mailto:jeremy@lbry.com) and let him know what community you would like to introduce LBRY to.
|
||||
@@ -0,0 +1,21 @@
|
||||
---
|
||||
category: code
|
||||
title: Mining Inflation Chart
|
||||
award: 300
|
||||
status: completed
|
||||
date: '2018-05-25'
|
||||
---
|
||||
|
||||
LBRY Credits (LBC) are distributed via the mining process on the blockchain approximately every 150 seconds (2.5 minutes), also known as the block interval. There is a total supply of 1 Billion credits, of which LBRY [controls 400M](/faq/credit-policy) for funding, rewarding users and partnerships. The other 600M will be mined over a period of around 20 years from inception (June 2016).
|
||||
|
||||
The [mining schedule](/faq/block-rewards) details how these credits will be distributed. We are currently in the logarithmically decreasing phase of the mining process where, at the time of this writing (May 20, 2018), the current block reward is 359 LBC. You can find the current block reward by visiting the [explorer](https://explorer.lbry.com) page and clicking the latest block to find the first output.
|
||||
|
||||
The goal of this bounty is to analyze and visualize the impact of mining inflation on coin supply. The end result would be the calculation code and web embeddable supply chart. Click [here](https://www.bitcoinmining.com/how-are-new-bitcoins-created) to find an example. At minimum, the x-axis should display dates and the y-axis is the cumulative LBC available.
|
||||
|
||||
Hints:
|
||||
- [Sample PHP Program](https://drive.google.com/open?id=19LXPIBhZnd-SEnQlrke2tb-ZwESrbK2D) to calculate estimated block reward at any given time
|
||||
- Use actual block times from [explorer.lbry.com](https://explorer.lbry.com) (or (Chainquery)[https://github.com/lbryio/chainquery) if it's available) for historical data
|
||||
|
||||
Bonus: Overlay with circulating supply information from CoinMarketCap.com
|
||||
|
||||
Status: Completed - https://github.com/marcdeb1/lbry-supply-chart
|
||||
@@ -0,0 +1,22 @@
|
||||
---
|
||||
category: code
|
||||
title: Modified Block Explorer
|
||||
award: 1500
|
||||
status: complete
|
||||
date: '2016-07-01'
|
||||
---
|
||||
|
||||
LBRY currently maintains and runs a block explorer at [explorer.lbry.com](https://explorer.lbry.com).
|
||||
|
||||
This explorer is a fork of Iquidus Explorer and is [on GitHub](https://github.com/lbryio/lbry-explorer).
|
||||
|
||||
Iquidus Explorer is great, but does not currently support LBRY specific operations.
|
||||
|
||||
The explorer should be modified to:
|
||||
|
||||
- Display name claims in a transaction and link to claim info provided a txid
|
||||
- Display a support transaction and link to claim info provided a txid
|
||||
- Display claim information (name, claim txid, value, total amount, supports, and previous updates) provided a claim id
|
||||
- Display information for contesting name claims provided a lbry name
|
||||
|
||||
This will likely require polling for changes in the result of `lbrycrd-cli getclaimsintrie` after each block, and subsequently populating values from `lbrycrd-cli getclaimsforname` and `lbrycrd-cli getclaimsfortx`.
|
||||
@@ -0,0 +1,9 @@
|
||||
---
|
||||
category: code
|
||||
title: LBC Paper Wallet
|
||||
award: 300
|
||||
status: complete
|
||||
date: '2017-09-12'
|
||||
---
|
||||
|
||||
Fork [bitaddress.org](https://www.bitaddress.org) for LBC.
|
||||
@@ -0,0 +1,14 @@
|
||||
---
|
||||
category: osx
|
||||
title: PKG Installer for OS X
|
||||
award: 1500
|
||||
status: complete
|
||||
pr: https://github.com/lbryio/lbry-desktop/pull/99
|
||||
date: '2016-07-01'
|
||||
---
|
||||
|
||||
Currently, [`lbry`](https://github.com/lbryio/lbry) is packaged as a DMG for OS X installs.
|
||||
|
||||
To claim this bounty, the install process should be done via a `.pkg` file instead.
|
||||
|
||||
This process must be done in a way that is repeatable in our CircleCI continuous integration environment.
|
||||
@@ -0,0 +1,16 @@
|
||||
---
|
||||
category: human
|
||||
title: Write, Broadcast or Share LBRY
|
||||
award: 250
|
||||
status: available
|
||||
date: '2016-07-01'
|
||||
---
|
||||
|
||||
This bounty is for writers, podcasters, streamers, or others in the media industry. To be eligible, you must:
|
||||
|
||||
- Create a piece of content about LBRY
|
||||
- Have the content accessed by over 2,000 people
|
||||
- Have over 100 of those people join the LBRY beta
|
||||
|
||||
We reserve the right to deny this bounty if we feel the article or generated traffic/signups are non-genuine.
|
||||
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
category: code
|
||||
title: Publish Open Content
|
||||
award: 500-10000+
|
||||
status: complete
|
||||
date: '2016-07-01'
|
||||
---
|
||||
|
||||
There are a large number of open content sources. Everything from public domain movies on [Internet Archive](https://archive.org/details/movies) to books from [Project Gutenberg](https://www.gutenberg.org).
|
||||
|
||||
This project is to programmatically index, download, and port this content to the LBRY network.
|
||||
|
||||
Credits will vary on the difficulty and usefulness of the source. We will provide credits to reserve the names for content. You must open-source any code created for this bounty.
|
||||
@@ -0,0 +1,15 @@
|
||||
---
|
||||
category: human
|
||||
title: Refer a Publisher to LBRY
|
||||
award: 250
|
||||
status: complete
|
||||
date: '2016-07-01'
|
||||
---
|
||||
|
||||
LBRY is offering big incentives to content creators as part of our [Publisher Partnership Program](/publish).
|
||||
|
||||
If you refer someone that is accepted into the program, you will receive this bounty award.
|
||||
|
||||
**Note: Do not notify us to claim this bounty. When we accept publishers into the program, we will ask who referred them.**
|
||||
|
||||
This award will remain open as long as the publisher program continues to run.
|
||||
@@ -0,0 +1,15 @@
|
||||
---
|
||||
category: slack
|
||||
title: Create a Slack Greeter
|
||||
award: 250
|
||||
status: complete
|
||||
date: '2016-07-01'
|
||||
---
|
||||
|
||||
Create a script that will automatically message all new members of our Slack channel.
|
||||
|
||||
The message sent must be loaded dynamically from a URL.
|
||||
|
||||
This [GitHub project](https://github.com/orliesaurus/greetingslack) is a good example of what's required. However, a few modifications are required:
|
||||
- Message must be regularly pulled in from a dynamic URL
|
||||
- Must run on Digital Ocean instance
|
||||
@@ -0,0 +1,15 @@
|
||||
---
|
||||
category: slack
|
||||
title: Create a URL Handler for Slack
|
||||
award: 1000
|
||||
status: complete
|
||||
date: '2016-07-01'
|
||||
---
|
||||
|
||||
Create a script for Slackbot that will:
|
||||
|
||||
- Use the Slack API to monitor all messages in all channels
|
||||
- Detect messages sent with LBRY URLs (e.g. `lbry://oprahbees`)
|
||||
- Look up LBRY URLs
|
||||
- Detect if the image resolves to a GIF/GIFV and has no license payment
|
||||
- Fetch and display the image
|
||||
@@ -0,0 +1,17 @@
|
||||
---
|
||||
category: design
|
||||
title: Create Social Media Cover Images
|
||||
award: 500
|
||||
status: complete
|
||||
date: '2016-07-01'
|
||||
---
|
||||
|
||||
**Update: we have received new cover images that we like a lot more than our old ones! We're leaving this open because there is always room for improvement, but this won't be an easy one to win.**
|
||||
|
||||
The current background images on our [Twitter](https://twitter.com/lbryio) and [Facebook](https://facebook.com/lbryio) are the same stock photo that is on our homepage. We'd like to do something a little more unique.
|
||||
|
||||
Candidate replacements could be either a photo or a graphic design. Either way, the image should:
|
||||
|
||||
- Connote what LBRY is about: openness and fun
|
||||
- Be unique to LBRY or otherwise not be in significant use
|
||||
- Suitable for white or LBRY green (#155B4A) text on top
|
||||
@@ -0,0 +1,18 @@
|
||||
---
|
||||
category: browser
|
||||
title: Add Transaction History to LBRY Browser
|
||||
award: 2000
|
||||
status: complete
|
||||
pr: https://github.com/lbryio/lbry-web-ui/pull/46
|
||||
date: '2016-07-01'
|
||||
---
|
||||
|
||||
Add a screen showing transaction history on the LBRY Browser [`lbry-web-ui`](https://github.com/lbryio/lbry-web-ui).
|
||||
|
||||
The screen must:
|
||||
- Display past outgoing and incoming transactions
|
||||
- Link to the LBRY [block explorer](https://explorer.lbry.com) for transactions
|
||||
|
||||
The LBRY daemon already supports an API call, `get_transaction_history`, to retrieve transaction history. While running LBRY, type the following in your browser console:
|
||||
|
||||
`lbry.call('get_transaction_history', {}, function(response) { console.log(response); });`
|
||||
@@ -0,0 +1,18 @@
|
||||
---
|
||||
category: code
|
||||
title: Twitter Tip Bot
|
||||
award: 300
|
||||
status: completed
|
||||
date: '2018-02-13'
|
||||
---
|
||||
|
||||
This bounty is to create a tipbot that can be used to send/receive LBRY Credits(LBC) on Twitter.
|
||||
|
||||
References to other LBRY tipbots:
|
||||
[Reddit tipbot](https://github.com/lbryio/lbry-social-tipbot)
|
||||
[Discord tipbot](https://github.com/lbryio/lbry-tipbot)
|
||||
|
||||
Possible starting point:
|
||||
https://github.com/Crowndev/Twitter-Tip
|
||||
|
||||
Please initiate a pull request on GitHub to receive this bounty.
|
||||
@@ -0,0 +1,15 @@
|
||||
---
|
||||
category: web
|
||||
title: Typos and Edits
|
||||
award: 2
|
||||
status: available
|
||||
date: '2016-11-01'
|
||||
---
|
||||
|
||||
This bounty is awarded for finding and correcting a typo, misspelling, or poor phrasing in anything created by LBRY, Inc.
|
||||
|
||||
This includes everything from low-level help messages or comments in code to the copy of the website itself.
|
||||
|
||||
Please initiate a pull request on GitHub to receive this bounty.
|
||||
|
||||
Note: Bounty award may be higher or lower depending on the nature of the change(s).
|
||||
@@ -0,0 +1,15 @@
|
||||
---
|
||||
category: browser
|
||||
title: Add Wallet Interface to LBRY Browser
|
||||
award: 2000
|
||||
status: complete
|
||||
pr: https://github.com/lbryio/lbry-web-ui/pull/23
|
||||
date: '2016-07-01'
|
||||
---
|
||||
|
||||
Add a basic wallet interface to the LBRY Browser [`lbry-desktop`](https://github.com/lbryio/lbry-desktop).
|
||||
|
||||
The interface must support:
|
||||
- Generating a new wallet address.
|
||||
- Sending a variable number of credits to a specified address from the active wallet.
|
||||
- Displaying an address to receive credits.
|
||||
@@ -0,0 +1,16 @@
|
||||
---
|
||||
category: web
|
||||
title: Internationalization of lbry.com
|
||||
award: 1000
|
||||
status: complete
|
||||
date: '2016-07-01'
|
||||
---
|
||||
|
||||
lbry.com already has a partial internationalization framework and some translations, but additional work is required before they can be enabled.
|
||||
|
||||
To complete this bounty, lbry.com must be modified to:
|
||||
- Allow modification of your selected language in the navigation
|
||||
- Storing selected language in the user session
|
||||
- Reverse look-up your IP and choose a default language if a user has not selected one
|
||||
|
||||
[`lbry.com` on GitHub](https://github.com/lbryio/lbry.com)
|
||||
@@ -6,7 +6,7 @@ category: policy
|
||||
|
||||
## 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
|
||||
|
||||
|
||||
@@ -6,29 +6,29 @@ 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.
|
||||
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*
|
||||
- 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.
|
||||
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.
|
||||
- 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.
|
||||
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.
|
||||
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.
|
||||
@@ -6,26 +6,26 @@ 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.
|
||||
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
|
||||
- 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.
|
||||
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.
|
||||
We anticipate no usage of credits from this fund this quarter.
|
||||
|
||||
### Institutional Fund
|
||||
|
||||
|
||||
@@ -6,7 +6,7 @@ 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.
|
||||
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
|
||||
@@ -28,7 +28,7 @@ As reliability has been increasing, we anticipate inviting many, if not, all use
|
||||
|
||||
No activity this quarter.
|
||||
|
||||
We anticipate no usage of Credits from this fund this quarter.
|
||||
We anticipate no usage of credits from this fund this quarter.
|
||||
|
||||
### Institutional Fund
|
||||
|
||||
|
||||
@@ -6,7 +6,7 @@ category: policy
|
||||
|
||||
## 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
|
||||
|
||||
@@ -6,7 +6,7 @@ category: policy
|
||||
|
||||
## 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.
|
||||
|
||||
|
||||
@@ -6,7 +6,7 @@ category: policy
|
||||
|
||||
## 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 +34,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
|
||||
|
||||
|
||||
@@ -5,13 +5,13 @@ 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.
|
||||
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:
|
||||
393,585 credits were spent from the community fund, in the following areas:
|
||||
|
||||
| Category | Amount |
|
||||
|---|---|
|
||||
@@ -26,11 +26,11 @@ This quarter we moved ~~no~~ 5,000,000 Credits from cold storage. We spent 393,5
|
||||
|
||||
### Operational Fund
|
||||
|
||||
* 135,000 Credits were used for an employee equity swap
|
||||
* 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.
|
||||
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
|
||||
|
||||
@@ -5,13 +5,13 @@ 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.
|
||||
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:
|
||||
738,027 credits were spent from the community fund, in the following areas:
|
||||
|
||||
| Category | Amount |
|
||||
|---|---|
|
||||
@@ -27,9 +27,9 @@ This quarter we moved no Credits from cold storage. We spent 738,027 total comm
|
||||
### Operational Fund
|
||||
|
||||
* LBRY sold no LBC on the open market
|
||||
* LBRY sold 327,352 Credits to a crypto education club.
|
||||
* 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.
|
||||
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
|
||||
|
||||
@@ -5,14 +5,14 @@ category: policy
|
||||
---
|
||||
|
||||
## 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 +33,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
|
||||
|
||||
@@ -4,14 +4,14 @@ sheet: https://docs.google.com/spreadsheets/d/1PSDn5igtZ51ml2Bd4lNlq9fSYgDbb-z1j
|
||||
category: policy
|
||||
---
|
||||
## 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,7 +30,7 @@ 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
|
||||
|
||||
@@ -4,14 +4,14 @@ sheet: https://docs.google.com/spreadsheets/d/1asnI5mGCVYb6zbcsxDhZaYu2IbXgWkGEB
|
||||
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.
|
||||
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:
|
||||
1,695,734 credits were spent from the community fund, in the following areas:
|
||||
|
||||
| Category | Amount |
|
||||
|---|---|
|
||||
@@ -31,7 +31,7 @@ As reliability and interest has been increasing, we anticipate continuing to rew
|
||||
* 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.
|
||||
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
|
||||
|
||||
|
||||
@@ -4,14 +4,14 @@ sheet: https://docs.google.com/spreadsheets/d/1CYQSj06imiDkPFGcVX0EpAoo42Y0oh4u2
|
||||
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.
|
||||
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:
|
||||
9,823,975 credits were spent from the community fund, in the following areas:
|
||||
|
||||
| Category | Amount |
|
||||
|---|---|
|
||||
@@ -30,8 +30,8 @@ As interest has been increasing, we anticipate continuing to reward new users, y
|
||||
* 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.
|
||||
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.
|
||||
140,000 credits were moved as part of the Antimedia partner deal.
|
||||
@@ -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.
|
||||
@@ -1,39 +0,0 @@
|
||||
---
|
||||
title: "Quarterly Credit Report: Fourth Quarter 2019"
|
||||
sheet: https://docs.google.com/spreadsheets/d/1H7uYR5XLNlf4Y-elrIS8mHdv4QnVQ-7BbM8YAR_u_W0/edit#gid=799352054
|
||||
category: policy
|
||||
---
|
||||
## 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.
|
||||
@@ -1,44 +0,0 @@
|
||||
---
|
||||
title: "Quarterly Credit Report: First Quarter 2020"
|
||||
sheet: https://docs.google.com/spreadsheets/d/12_4RFTiEjV1RVdhOOPURa724ZSS8RDBxfnn8MiOvEDQ/edit?usp=sharing
|
||||
category: policy
|
||||
---
|
||||
## 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.
|
||||
@@ -1,47 +0,0 @@
|
||||
---
|
||||
title: "Quarterly Credit Report: Second Quarter 2020"
|
||||
sheet: https://docs.google.com/spreadsheets/d/1Ckcba-AsoC1GuG6xGYR7LbpOiMAqLjdjhDywvt4MrdA/edit#gid=799352054
|
||||
category: policy
|
||||
---
|
||||
## 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).
|
||||
@@ -1,42 +0,0 @@
|
||||
---
|
||||
title: "Quarterly Credit Report: Third Quarter 2020"
|
||||
sheet: https://docs.google.com/spreadsheets/d/1t3zVnBgXNy1fQLdEVw7jr7x5izVxZ3tlQvBgizqvcGE/edit?usp=sharing
|
||||
category: policy
|
||||
---
|
||||
## 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.
|
||||
@@ -1,20 +0,0 @@
|
||||
---
|
||||
title: LBRY US 2257 Statement
|
||||
category: other
|
||||
---
|
||||
|
||||
## 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.
|
||||
@@ -15,7 +15,7 @@ To claim a bounty, please email [bounty@lbry.com](mailto:bounty@lbry.com). Pleas
|
||||
|
||||
### 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.
|
||||
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.
|
||||
|
||||
|
||||
@@ -3,7 +3,7 @@ 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/lbrycom), and [Facebook](https://www.facebook.com/lbrycom).
|
||||
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.
|
||||
|
||||
|
||||
@@ -7,17 +7,17 @@ category: developer
|
||||
|
||||
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 :
|
||||
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.
|
||||
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.
|
||||
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.
|
||||
|
||||
|
||||
|
||||
@@ -5,4 +5,4 @@ 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.
|
||||
but you can see these credits in your immature balance in getwalletinfo.
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Acceptable use policy
|
||||
title: Acceptable Use Policy
|
||||
category: other
|
||||
---
|
||||
|
||||
@@ -7,25 +7,25 @@ If you've read [Art in the Internet Age,](/what) you know that LBRY believes we
|
||||
|
||||
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.
|
||||
|
||||
## Our trademark policy has three objectives:
|
||||
#### Our trademark policy has three objectives:
|
||||
|
||||
* We want it to be very easy for anyone creating content or services on the LBRY network to use the official name and logo.
|
||||
* We want to be clear about how and when you can use the LBRY name and logo, as well as providing examples of uses that are not acceptable.
|
||||
* We want to make it difficult for anyone to use the LBRY name or logo to confuse or defraud people.
|
||||
|
||||
## Obtain your license
|
||||
### Obtain Your License
|
||||
|
||||
If you are producing video or other content for LBRY or if you've downloaded our client, you've got a license to use the LBRY name and official logo on your blog or website where you promote your work. That's all there is to it, just stick to the fair use rules if you're sampling or otherwise using copyright content from somewhere else.
|
||||
|
||||
If you are a developer, you will need to complete the verification process before you use the LBRY name and official logo to promote your service or site. The creation of fraudulent sites that appear official is a common problem for blockchain projects. This happened to LBRY early in its history, and this process exists to reduce the potential for another such event.
|
||||
|
||||
## Examples of acceptable uses
|
||||
### Examples Of Acceptable Uses
|
||||
|
||||
* Create brand new content. Entertain, educate, become famous, or change the world.
|
||||
* Build a service based on LBRY. Help make the internet a better, freer place!
|
||||
* Staying within the bounds of Fair Use, sample, derive, criticize, or otherwise use someone else's copyright work to make something new.
|
||||
|
||||
## Examples of unacceptable uses
|
||||
### Examples of Unacceptable Uses
|
||||
|
||||
* Creating any service that uses LBRY and presenting it as an official product, such as an online wallet.
|
||||
* Presenting yourself or implying that you are a representative or agent of LBRY, Inc.
|
||||
@@ -33,7 +33,7 @@ If you are a developer, you will need to complete the verification process befor
|
||||
* Uploading someone else's copyrighted work without their permission, either for free or attempting to profit.
|
||||
* Uploading content that is itself a crime.
|
||||
|
||||
## LBRY service trademark usage policy
|
||||
### LBRY Service Trademark Usage Policy
|
||||
|
||||
As a statement of principle, you are encouraged to associate your project, product, service, domain, or company name with LBRY, so long as you're a credit to the community.
|
||||
|
||||
|
||||
@@ -0,0 +1,42 @@
|
||||
---
|
||||
title: LBRY 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 desktop, android, or 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 an account with LBRY Inc and turn on account sync, 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, enrolling in wallet sync is not possible if:
|
||||
- You had a balance prior to October 2019
|
||||
- You have a balance on multiple separate devices or installs
|
||||
Additionally, if you sign out of your account and accrue a balance, but then want to enable sync again, this will not work.
|
||||
We expect these limitations to be removed in subsequent releases. If the above applies to you and you really want to use it immediately, you can follow [these steps](#bypass).
|
||||
|
||||
#### 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 your balance and you will see the option on your wallet page.
|
||||
|
||||
#### 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.
|
||||
|
||||
### Bypassing Limitations {#bypass}
|
||||
If the above limitations apply to you, you are technically competent, and you do not want to wait, you can use sync today by taking the following steps:
|
||||
1. Shut down any running LBRY apps or wallet clients.
|
||||
1. Rename your [current default_wallet file](/faq/lbry-directories) to anything other than default_wallet.
|
||||
1. Launch LBRY again and sign out. Then sign back in.
|
||||
Note that this will leave you with an extra wallet file containing your channels and balance, which you will have to unify.
|
||||
|
||||
### 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.
|
||||
@@ -1,79 +0,0 @@
|
||||
---
|
||||
title: Odysee.com and LBRY accounts 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.
|
||||
|
||||
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.
|
||||
|
||||

|
||||
|
||||
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).
|
||||
|
||||

|
||||
|
||||
### 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.
|
||||
|
||||

|
||||
|
||||
### 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.
|
||||
|
||||

|
||||
|
||||
### 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).
|
||||
|
||||

|
||||
|
||||
### 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.
|
||||
@@ -1,116 +1,134 @@
|
||||
---
|
||||
title: LBRY for Android basics
|
||||
title: LBRY Android App 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.
|
||||
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.
|
||||
|
||||
The purpose of this FAQ is to answer questions about some of the basic functionality available in the LBRY Android App. Please see our [other FAQ entries](/faq) for additional information.
|
||||
|
||||
## Why does LBRY want my email address?
|
||||
**Important notes:**
|
||||
|
||||
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.
|
||||
- We are aware of issues with playing videos on some mobile networks. You can try on wifi, or use [https://beta.lbry.tv](https://beta.lbry.tv) for now**
|
||||
|
||||
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).
|
||||
- If you are getting stuck at the loading screen, try uninstalling/reinstalling the Android app.
|
||||
|
||||
## How do I change my LBRY connected email?
|
||||
- Wallets do not sync between Desktop and Mobile yet, see our [wallet sync FAQ](https://lbry.com/faq/how-to-backup-wallet#sync)
|
||||
|
||||
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.
|
||||
### Why Does LBRY Want My Email Address?
|
||||
|
||||
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.
|
||||
Emails are collected to authenticate and [uniquely identify](/faq/phone) users so that they can be eligible for [LBRY Rewards](#rewards), sync subscription data and to stay up to date on the latest LBRY happenings.
|
||||
|
||||
## Syncing of wallets and other data
|
||||
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](https://lbry.com/faq/how-to-backup-wallet#sync).
|
||||
|
||||
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.
|
||||
### How Do I Change My LBRY Connected Email?
|
||||
|
||||
## What are LBRY Rewards? {#rewards}
|
||||
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 currently, please [backup your wallet data](/faq/how-to-backup-wallet#android).
|
||||
|
||||
[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.
|
||||
If you sign into a new email and need to transfer your 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.
|
||||
|
||||
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.
|
||||
### Syncing of Accounts
|
||||
|
||||
## What is a wallet And how do I find it? {#wallet}
|
||||
The Android app allow syncing of your account/wallet and secures it with a password. Please read the [wallet FAQ](https://lbry.com/faq/how-to-backup-wallet#sync) in more detail to understand how this works.
|
||||
|
||||
A wallet is a secure digital file used to store, send, and receive cryptocurrencies like LBRY Credits (LBC).
|
||||
### What If I Want To Run LBRY On Multiple Android Devices?
|
||||
|
||||
If you want to run the LBRY app on multiple PCs or on other platforms like Android, you can sign in with the same email on all devices. Each installation will still have its separate wallet and download data (as mentioned above).
|
||||
|
||||
Any rewards earned will be sent locally to the wallet where they are claimed. In the future, our goal to enable an opt-in wallet syncing service across devices.
|
||||
|
||||
### 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.
|
||||
|
||||
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.
|
||||
|
||||
### 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).
|
||||
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 [wallet sync program](https://lbry.com/faq/how-to-backup-wallet#sync), it is critical that you backup your own wallet locally or else the credits 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.
|
||||
|
||||

|
||||

|
||||
|
||||
## Where do I find my LBC wallet address?
|
||||
### Where Do I Find My LBC Wallet Address?
|
||||
|
||||

|
||||

|
||||
|
||||
## Where do I find my recent transactions
|
||||
### 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.
|
||||
|
||||

|
||||

|
||||
|
||||
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.
|
||||
|
||||
## How do I publish content? {#publish}
|
||||
### How do I Publish content? {#publish}
|
||||
|
||||
1. Tap on the 3 horizontal bars on the upper left side of the app next to the Search bar.
|
||||
|
||||
2. Select the option for `New publish`
|
||||
|
||||

|
||||

|
||||
|
||||
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)
|
||||
|
||||
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.
|
||||
|
||||

|
||||

|
||||
|
||||
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.
|
||||
|
||||

|
||||

|
||||
|
||||
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](/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)[https://lbry.com/faq/trending) for your content. For more details regarding the URL or bid, check out our [naming document](/faq/naming).
|
||||
|
||||

|
||||

|
||||
|
||||
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)*
|
||||
|
||||
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.
|
||||
|
||||
*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 with 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 to 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}
|
||||
### 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. Come back every day 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. Comeback everyday for a different reward.Incase for some reason the reward does not show up in your wallet after watching a video everyday, go to rewards and click on the daily rewards.
|
||||
|
||||
## How do I enable background media playback? {#backgroundmediaplayback}
|
||||
To check whether your wallet is updated, you need to swipe your screen to show the menu bar, click on Wallet and you will see your overall updated balance. Check [How to Backup Your Wallet](/faq/how-to-backup-wallet)
|
||||
|
||||
### 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.
|
||||
|
||||

|
||||

|
||||
|
||||
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}
|
||||
### 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 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.
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Appreciation for contributing
|
||||
title: Appreciation for Contributing
|
||||
category: other
|
||||
---
|
||||
|
||||
|
||||
+2
-2
@@ -160,7 +160,7 @@ 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
|
||||
and then send some credits to your wallet by doing
|
||||
`./lbrycrd-cli sendtoaddress <address> <num_of_credits>`
|
||||
|
||||
### 4) lbry
|
||||
@@ -200,7 +200,7 @@ lbrycrd-cli generate 5
|
||||
lbryum getunsusedaddress
|
||||
```
|
||||
|
||||
#### Send Credits from lbrycrd to your wallet
|
||||
#### Send credits from lbrycrd to your wallet
|
||||
```bash
|
||||
lbrycrd-cli sendtoaddress <address> <num_of_credits>
|
||||
```
|
||||
@@ -8,22 +8,22 @@ We have covered LBRY wallet backup procedures in the guide [here](/faq/how-to-ba
|
||||
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.
|
||||
|
||||
To summarize, the main directories to consider when backing up or migrating a LBRY installation are as follows:
|
||||
- LBRY Wallet - `lbryum`
|
||||
- Data/Settings - `lbrynet` (`LBRY` on Mac)
|
||||
- File Downloads - Typically your local Downloads directory (Check settings in LBRY app).
|
||||
##### - LBRY Wallet - `lbryum`
|
||||
##### - Data/Settings - `lbrynet` (`LBRY` on Mac)
|
||||
##### - File Downloads - Typically your local Downloads directory (Check settings in LBRY app).
|
||||
|
||||
*\*Please note: both the Data/Settings and File Downloads directories may be large if you have downloaded lots of LBRY content*
|
||||
##### *\*Please note: both the Data/Settings and File Downloads directories may be large if you have downloaded lots of LBRY content*
|
||||
|
||||
## How do I backup all LBRY related data?
|
||||
### How do I backup all LBRY related data?
|
||||
|
||||
1. Refer to the LBRY [working directories](/faq/lbry-directories) to find your data folders
|
||||
2. Make a copy of the `lbrynet` (`LBRY` folder if on Mac) folder to a secure location
|
||||
3. Make a copy of the `lbryum` folder to a secure location
|
||||
4. Make a copy of your LBRY Downloads directory to a secure location
|
||||
|
||||
## How do I migrate all LBRY related data to a new installation?
|
||||
### 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 default, 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 defailt, 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.
|
||||
@@ -35,10 +35,10 @@ To summarize, the main directories to consider when backing up or migrating a LB
|
||||
|
||||
*\*Note 2: If you get startup errors after this procedure: check if the `daemon_settings.yml` file from the `lbrynet` folder points to the correct LBRY file download directory. If it does not, edit the file with correct file path and restart the app. You can view and edit this file with any text editor.*
|
||||
|
||||
## How do I backup just my wallet?
|
||||
### How do I backup just my wallet?
|
||||
|
||||
Please see [our FAQ on wallet backup procedures](https://lbry.com/faq/how-to-backup-wallet)
|
||||
|
||||
## I'm in need of some assistance, can you help?
|
||||
### I'm in need of some assistance, can you help?
|
||||
|
||||
Of course, we are always here to help! Check out our [help page](/faq/how-to-report-bugs) on how to reach us. If you are having trouble starting LBRY after migration, sending us your [log file](/faq/how-to-find-lbry-log-file) will expedite the resolution.
|
||||
@@ -6,8 +6,8 @@ order: 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](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 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 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, 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 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.
|
||||
@@ -1,44 +1,42 @@
|
||||
---
|
||||
title: What is mining and what are the LBRY block rewards?
|
||||
title: What is Mining and what are the LBRY Block Rewards?
|
||||
category: mining
|
||||
order: 1
|
||||
---
|
||||
|
||||
## What is mining?
|
||||
## 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 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.
|
||||
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.
|
||||
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
|
||||
## 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](https://github.com/lbryio/lbrycrd/blob/v0.17.3.2/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 in [`master`]:
|
||||
|
||||
## Mining reward schedule
|
||||
[https://github.com/lbryio/lbrycrd/blob/master/src/validation.cpp](https://github.com/lbryio/lbrycrd/blob/master/src/validation.cpp#L1025)
|
||||
|
||||
Eventually 1,083,202,000<sup>1</sup> LBRY Credits will exist.
|
||||
## Mining Reward Schedule
|
||||
|
||||
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 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 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 remaining 600,000,000 are mined in 3 stages:
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
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.
|
||||
3. The final stage is the "normal" mining stage. From block 55001 onward, the block reward decreases logarithmically over the course of 20 years.
|
||||
|
||||
* 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.
|
||||
* 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.
|
||||
|
||||
* 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.
|
||||
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.
|
||||
|
||||
@@ -4,3 +4,7 @@ category: other
|
||||
---
|
||||
|
||||
Yep. You can see it at [https://explorer.lbry.com](https://explorer.lbry.com).
|
||||
|
||||
If the enslaved squirrels that run our primary explorer are sleeping, try
|
||||
[https://lbrypool.com/explorer/LBC](https://lbrypool.com/explorer/LBC)
|
||||
|
||||
Loaded 100 of 612 files, more files were not shown because too many files have changed in this diff.
Show more
Reference in new issue
Block a user