Filecoin Weekly-Issue 56: The test reward plan may be postponed for 1 to 2 weeks

 

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] Issue 56: The test reward plan may be postponed for 1 to 2 weeks

test version:

  • lotus v0.4.0

Test objectives:

  • Security audit of network and code
  • Hardware configuration/proof structure/economic structure
  • Filecoin test reward program (expected 3 weeks)

project progress:

  • The test reward plan may be postponed for 1 to 2 weeks
  • Butterfly version launched

 

[Hot Spots of Last Week]

  • On July 11th, @Why spoke in Slack, saying that due to requests from many miners, he was considering postponing the test reward plan. If confirmed, it may be postponed for 1 to 2 weeks.

[Filecoin Weekly] Issue 56: The test reward plan may be postponed for 1 to 2 weeks

 

[Progress of testnet last week]

1) Test network operation status:

[Filecoin Weekly] Issue 56: The test reward plan may be postponed for 1 to 2 weeks

Screenshot of filscan.io (14:00)

[Filecoin Weekly] Issue 56: The test reward plan may be postponed for 1 to 2 weeks

  • After the network reset, the system has been running for more than 22 days, the number of active miners has remained above 4000, and the system has stable block production
    • The block height exceeded 77,100 last week, and the effective computing power of the entire network reached 19.920 PiB, an increase of nearly 3.4 PiB in a single week, and an average daily increase of about 0.5 PiB, which was halved compared with the previous week. Some big miners stopped increasing their computing power
    • Last week, the block reward was around 18.22FIL to 18.18FIL
    • 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 stays at about 3.22, which is significantly higher than the previous week, because the network has more participants Enter, the proportion of large miners declines
    • The average number of messages last week was about 13.5, a sharp drop compared to the previous week
    • The size of the message last week exceeded 998 bytes, which was basically the same as the previous week. It was mainly to prove the message.
  • The Butterfly network is launched, which contains some new codes. The test network is expected to restart in a few days to two weeks
    • In fact, this is what was called Devnet before, now it has a specific name
    • Some changes of Butterfly will enter the new testnet

2) Main issues:

  • Consensus error report does not take effect
  • System stability problems: crashes and panicks still occur from time to time
  • PaymentChannel is unstable

 

[Development progress last week]

  • Code additions and bug fixes:
    • Some bug fixes: one of the important recent work, including improving error handling, improving prompts, command line error correction, better log structured output, etc.
    • The selection process of news based on Gas fee: Allow miners to get higher transaction fees
    • Quick search option support
    • A single sector supports multiple deals
    • Journal support for Lotus operations
    • Code improvement: support for multiple blockstores,
      better PoRep scheduling
      , improvement of deal processing,
      search market support, improvement of
      Sector lifecycle implementation,
      message pool improvement: organization according to gas price
    • Block reward improvement: no reward for founding blocks; correction of total network computing power (not including underwater computing power)
    • Some Actors code refactoring
  • Design and certification update:
    • Design documentation updated to reflect recent code improvements
    • Proof of code cleanup (no harm): add change information, clear useless code, etc.
    • Support ARM (in progress)
    • Security audit and problem repair

Guess you like

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