LBRYCommunity/lbrycrd
1
0
Fork 0
Code Issues 29 Pull requests 1 Packages Projects Releases 32 Wiki Activity

32 Releases 42 Tags

RSS feed
  • v0.17.1.0 36ccf3e903

    v0.17.1.0 - Rebased on 0.17 Pre-release

    BrannonKing released this 2019-07-01 22:44:28 +02:00 | 100 commits to master since this release

    This is a pre-release of lbrycrd, which is now based upon the Bitcoin 0.17.0 codebase. Unless we find some showstoppers, we will release another build next week with significant RAM usage reductions. This build does not have the RAM reductions, and requires over 5GB of RAM for a full blockchain sync. (Restarting after the you are up to date on the current block will significantly reduce RAM usage.)

    Breaking changes:

    1. RPC methods now return UTF-8 data. Claim names that cannot be represented in UTF-8 will utilize standard JSON escape sequences.
    2. Claim values (aka, metadata) is returned has hexadecimal strings. They will not utilize escape characters as they have in the past.
    3. RPC method getclaimsintrie is now deprecated and getclaimtrie is removed. Use getnamesintrie instead.
    4. Issue #119 was repaired.
    5. There is a one-time upgrade of the existing data when running this build. Copy your ~/.lbrycrd/ folder first should you need to go back.

    Other changes:

    1. Everything that was added to bitcoin after 0.12 through 0.17! See https://bitcoin.org/en/version-history . This includes the removal of built-in CPU mining.
    2. Reproducible_build.sh is now build.sh, and utilizes the "depends" build system.
    3. Unicode updated to v11 to match Python3.
    4. The Windows build is now 64bit.

    Known issue:

    1. RPC methods that query for names may return longer names that have the same characters. This is fixed in the coming build.
    2. Claim OPs may not play well appended with Segwit transactions, and the other parts of the LBRY stack definitely won't play well with them.
    3. Blocks that include supports followed by updates for a given name may fail to verify in the initial verification stage. Block 567082 is the most recent known block with this issue. This is fixed in the coming build.

    SHA256 values:

    Linux: 1bafac6dbc9b3d3cf64be1cdb4fa4c3a2c48153dccb86a94d731e2818bce51e9
    Windows: 9ac3d143a3da8ebe5fc69f7be4dd512e466b64b8dc56b0913e10698047c0c83d
    Darwin: 48632c89e7a9015dbb02cf9ba958c748a912b8461072388b1435e38a9cfc0872

    Downloads