LBRYFoundation/lbry.com
1
0
Fork 0
mirror of https://github.com/LBRYFoundation/lbry.com.git synced 2025-08-23 17:47:26 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

added post-fork update (#1003)

Browse source
This commit is contained in:
Brannon King 2019-03-25 13:44:04 -06:00 • committed by netop:// ウェッブ
parent e4f4bbf2de
commit 8e7cd9a6ec
1 changed files with 8 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
content/news/204-hf1903.md
View file

@ -5,6 +5,14 @@ date: '2019-02-19 10:00:00'
category: technical
---
**Update 2019-Mar-25 1pm EST**: The fork is live. Block 539941 occurred on March 24th about 1:40pm EST. The post-fork chain is now proceeding normally. Thank you for your cooperation and support in this. You can validate that you are on the correct fork using the command line:
`./lbrycrd-cli getblockhash 539941` = 7d3034e02879c3224aa324063e22368cee28d5e791290caeaaa595e3b06d161b
`./lbrycrd-cli getblockhash 540444` = c466452ad520a41b0d491e078eb3ec6f2529ce636b46b288c2c23992b8b5a09b
When the fork occurred there was still strong hashing on the old chain. This continued for six hours afterward; many continued on the wrong chain. While hashing on the old chain has died down now, many may need to take action to get on the correct chain. Updating to the latest release of LBRYcrd is the first step. However, if you have proceeded down the wrong chain, you may have data in your blocks that is now considered invalid. Unfortunately, the newer LBRYcrd will fail its block validation with a crash in this scenario. If you are not utilizing the wallet in lbrycrd, you may safely clear your data (rename the ~/.lbrycrd folder) and resync. Otherwise you may need to selectively remove some data and bans or rollback using the previous version of the software. Please contact support for help on this: https://lbry.com/contact
Also, please ensure that you have 4GB of RAM for running the current version of LBRYcrd. The next release will significantly reduce this requirement.
## What's Changing
The LBRY blockchain will experience a hard fork (named HF1903) on March 21st to fix the way names are compared and claims are grouped.