LBRYFoundation/lbry.com
1
0
Fork 0
mirror of https://github.com/LBRYFoundation/lbry.com.git synced 2025-08-27 15:31:29 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

formatting on hf1807.md

Browse source
This commit is contained in:
kay kurokawa 2018-07-11 14:58:48 -04:00
parent 8abe604adb
commit 58dbb527b6
1 changed files with 1 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
content/news/171-hf1807.md
View file

@ -6,9 +6,7 @@ date: '2018-06-05 07:00:00'
**Update 2018-07-11 9:51am EST**: The fork is live. Block 400155 occurred on July 9 at 11:40am EST. Block 401019 (the block with the first difference between forks) occurred on July 11 at 2:43am EST. The prefork chain halted at that block, while the postfork chain is proceeding normally (at block 401361 at the time of writing).
**Update 2018-07-11 2:35pm EST**: Some users have reported that blocks are coming in slowly or not at all. If you were running an old version (< version 0.12.2.0) until block 401019 or after, and then updated, you will be stuck on the old chain. To check if you are stuck on the old chain, run the command, "getblockhash 401019" to check the blockhash on block 401019. If the output is not equal to 40c852eea4184aa5597eb075328921a3e600eb9f930561cc0c463a63276c609b you are on the wrong chain.
To fix this, you will need to reindex. Run lbrycrdd with the reindex option: "./lbrycrdd -reindex" . You may also need to clear your ban list with command "clearbanned" to unban any post fork nodes.
**Update 2018-07-11 2:35pm EST**: Some users have reported that blocks are coming in slowly or not at all. If you were running an old version (< version 0.12.2.0) until block 401019 or after, and then updated, you will be stuck on the old chain. To check if you are stuck on the old chain, run the command, `getblockhash 401019` to check the blockhash on block 401019. If the output is not equal to 40c852eea4184aa5597eb075328921a3e600eb9f930561cc0c463a63276c609b you are on the wrong chain. To fix this, you will need to reindex. Run lbrycrdd with the reindex option: `./lbrycrdd -reindex` . You may also need to clear your ban list with command `clearbanned` to unban any post fork nodes.
## What's Changing