Filecoin Weekly-54: The Filecoin Test Reward Program was launched on 7.20, are you ready?

 

Co-edited by Steven Li and Iris

【Project Introduction】

Filecoin is a decentralized storage network that transforms cloud storage into an algorithm market .

Miners - obtain FIL by providing data storage and retrieval

Clients- allow miners to provide storage, distribution and retrieval data services by paying FIL

 

[Project progress: Testnet phase2 ]

[Filecoin Weekly] 54: The Filecoin test reward program was launched on 7.20, are you ready?

test version:

  • lotus v0.4.0 (The network has been reset)

Test objectives:

  • Four implementations including lotus and go-filecoin complete interoperability

  • Security audit of network and code

  • Hardware configuration/proof structure/economic structure

  • Filecoin test reward program (expected 3 weeks)

project progress:

  • The test reward program is postponed until July 20th

  • Juan led his team to start a new AMA event

 

[Hot Spots of Last Week]

  • On June 24, Coinlist issued an announcement stating that the Filecoin mainnet will be launched in mid-August or at the end of this month, so that investors will be ready to receive FIL.

[Filecoin Weekly] 54: The Filecoin test reward program was launched on 7.20, are you ready?

 

[Progress of testnet last week]

1) After the test network was reset, it experienced fluctuations, and the current operation effect basically met the expectations of the Force Zone.

2) Test network operation status:

[Filecoin Weekly] 54: The Filecoin test reward program was launched on 7.20, are you ready?

Screenshot of filscan.io (14:00)

[Filecoin Weekly] 54: The Filecoin test reward program was launched on 7.20, are you ready?

  • After the network reset, the system runs for more than 8 days, the number of active miners remains above 4000, and the system produces stable blocks

    • Last week, the block height was close to 29,000, and the effective computing power of the entire network was close to 9.18 PiB. A weekly increase of about 7PiB, an average daily increase of 1.0PiB, this is the fastest growing week since Filecoin network testing

    • Last week, the block reward was around 18.26FIL, and the reward declined exponentially according to the rules, in line with expectations

    • Block generation is relatively stable. The average block interval is about 25s, and there are few empty block rounds; the average number of blocks in each round remains at about 2.6, which has decreased compared with the initial reset.

    • The current average number of messages is about 31, indicating that many miners have participated in the test recently and the network is relatively active

    • The current message size is about 960 bytes, which is basically the same as last week, mainly to prove the message

3) Main issues:

  • Predictable election issues-design issues (non-implementation issues): repair in progress, slightly more complicated

  • Faucet stability issue-fixed

  • beacon verification problem 

  • Chain synchronization Race Condition-fixed

 

[Development progress last week]

  • Code additions and bug fixes:

    • Improve the block election algorithm and increase the randomness of block rights-in progress

    • Improved spec-storage, providing sector removal support, allowing customers to delete their own data locally

    • Documentation update

    • Sector upgrade support-in progress

    • Parallel processing of block verification

    • WindowedPoSt Improvement: Proof should be stopped when an error occurs

    • Storage/retrieval market improvement: support multiaddr addresses, enable/disable retrieval transactions; increase the priority of deal-related sectors; provide more API support for retrieval

    • Mortgage mechanism implementation-in progress

    • Improve the calculation method of error sectors

  • Design and certification update:

    • Proof of replication-implementation layer-related challenges

    • Parallel WindowedPoSt synthesize

    • Further realization of NSE algorithm

Guess you like

Origin blog.csdn.net/IPFSForce/article/details/107026407