Implement a hard fork for extended/infinite claim expiration times #112
1 changed files with 9 additions and 48 deletions
57
README.md
57
README.md
|
@ -1,51 +1,21 @@
|
||||||
LBRYcrd integration/staging tree
|
# LBRYcrd - The LBRY blockchain
|
||||||
=====================================
|
|
||||||
|
|
||||||
http://lbry.io
|
|
||||||
|
|
||||||
What is LBRYcrd?
|
## What is LBRYcrd?
|
||||||
----------------
|
|
||||||
|
|
||||||
LBRYcrd is a fork of bitcoin core designed for use in the LBRY network.
|
LBRYcrd uses a blockchain similar to bitcoin's to implement an index and payment system for content on the LBRY network. It is a fork of bitcoin core.
|
||||||
|
|
||||||
LBRYcrd uses a blockchain similar to bitcoin's to implement a unique naming system in which the person who dedicates the largest amount of LBC to a name has control over that name.
|
|
||||||
|
|
||||||
What is Bitcoin?
|
## Development Process
|
||||||
----------------
|
|
||||||
|
|
||||||
Bitcoin is an experimental new digital currency that enables instant payments to
|
|
||||||
anyone, anywhere in the world. Bitcoin uses peer-to-peer technology to operate
|
|
||||||
with no central authority: managing transactions and issuing money are carried
|
|
||||||
out collectively by the network. Bitcoin Core is the name of open source
|
|
||||||
software which enables the use of this currency.
|
|
||||||
|
|
||||||
For more information, as well as an immediately useable, binary version of
|
|
||||||
the Bitcoin Core software, see https://bitcoin.org/en/download, or read the
|
|
||||||
[original whitepaper](https://bitcoincore.org/bitcoin.pdf).
|
|
||||||
|
|
||||||
License
|
|
||||||
-------
|
|
||||||
|
|
||||||
Bitcoin Core is released under the terms of the MIT license. See [COPYING](COPYING) for more
|
|
||||||
information or see https://opensource.org/licenses/MIT.
|
|
||||||
|
|
||||||
Development Process
|
|
||||||
-------------------
|
|
||||||
|
|
||||||
The `master` branch is regularly built and tested, but is not guaranteed to be
|
The `master` branch is regularly built and tested, but is not guaranteed to be
|
||||||
completely stable. [Tags](https://github.com/bitcoin/bitcoin/tags) are created
|
completely stable. [Releases](https://github.com/lbryio/lbrycrd/releases) are created
|
||||||
regularly to indicate new official, stable release versions of Bitcoin Core.
|
regularly to indicate new official, stable release versions.
|
||||||
|
|
||||||
The contribution workflow is described in [CONTRIBUTING.md](CONTRIBUTING.md).
|
The contribution workflow is described in [CONTRIBUTING.md](CONTRIBUTING.md).
|
||||||
|
|
||||||
The developer [mailing list](https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev)
|
|
||||||
should be used to discuss complicated or controversial changes before working
|
|
||||||
on a patch set.
|
|
||||||
|
|
||||||
Developer IRC can be found on Freenode at #bitcoin-core-dev.
|
## Testing
|
||||||
|
|
||||||
Testing
|
|
||||||
-------
|
|
||||||
|
|
||||||
Testing and code review is the bottleneck for development; we get more pull
|
Testing and code review is the bottleneck for development; we get more pull
|
||||||
requests than we can review and test on short notice. Please be patient and help out by testing
|
requests than we can review and test on short notice. Please be patient and help out by testing
|
||||||
|
@ -72,16 +42,7 @@ code. This is especially important for large or high-risk changes. It is useful
|
||||||
to add a test plan to the pull request description if testing the changes is
|
to add a test plan to the pull request description if testing the changes is
|
||||||
not straightforward.
|
not straightforward.
|
||||||
|
|
||||||
Translations
|
|
||||||
------------
|
|
||||||
|
|
||||||
Changes to translations as well as new translations can be submitted to
|
## License
|
||||||
[Bitcoin Core's Transifex page](https://www.transifex.com/projects/p/bitcoin/).
|
|
||||||
|
|
||||||
Translations are periodically pulled from Transifex and merged into the git repository. See the
|
MIT
|
||||||
[translation process](doc/translation_process.md) for details on how this works.
|
|
||||||
|
|
||||||
**Important**: We do not accept translation changes as GitHub pull requests because the next
|
|
||||||
pull from Transifex would automatically overwrite them again.
|
|
||||||
|
|
||||||
Translators should also subscribe to the [mailing list](https://groups.google.com/forum/#!forum/bitcoin-translators).
|
|
||||||
|
|
Loading…
Reference in a new issue