From f78e96c881972b5061135fd9fffbd875604712fb Mon Sep 17 00:00:00 2001
From: IPFSUnion <tech@ipfsunion.cn>
Date: Fri, 1 Oct 2021 21:39:54 +0800
Subject: [PATCH 01/12] Add files via upload

extend the cc sector fault period
---
 FIPS/fip-0025.md | 80 ++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 80 insertions(+)
 create mode 100644 FIPS/fip-0025.md

diff --git a/FIPS/fip-0025.md b/FIPS/fip-0025.md
new file mode 100644
index 000000000..9c2cf0ccc
--- /dev/null
+++ b/FIPS/fip-0025.md
@@ -0,0 +1,80 @@
+---
+fip: "0025"
+title: Extend the fault period of cc sector from 2 weeks to 6 weeks
+author: IPFSUnion(@IPFSUnion)
+discussions-to: https://github.com/filecoin-project/FIPs/issues/189
+status: Draft
+type: Technical (Core)
+created: 2021-10-01
+---
+
+<!--You can leave these HTML comments in your merged FIP and delete the visible duplicate text guides, they will not appear and may be helpful to refer to if you edit it again. This is the suggested template for new FIPs. Note that a FIP number will be assigned by an editor. When opening a pull request to submit your FIP, please use an abbreviated title in the filename, `fip-draft_title_abbrev.md`. The title should be 44 characters or less.-->
+
+
+## Simple Summary
+<!--"If you can't explain it simply, you don't understand it well enough." Provide a simplified and layman-accessible explanation of the FIP.-->
+
+Due to force majeure factors such as major natural disasters, storage providers may not be able to restore services in a short period. According to the current implementation of the protocal, the sector will be forcibly terminated after two consecutive weeks of faults. Two weeks is not enough to complete the EiB-level data migration and recovery, so we hereby propose this FIP.
+
+## Abstract
+<!--A short (~200 word) description of the technical issue being addressed.-->
+
+Filecoin needs to extend the fault period so that large storage providers have enough time to complete the data migration.  Six weeks is generally enough for overseas migration, including overall planning, customs application, sea or air transport, etc.  
+
+## Change Motivation
+<!--The motivation is critical for FIPs that want to change the Filecoin protocol. It should clearly explain why the existing protocol specification is inadequate to address the problem that the FIP solves. FIP submissions without sufficient motivation may be rejected outright.-->
+
+Any country in the world is likely to face force majeure factors such as major natural disasters or social abnormal events, causing storage providers to be unable to provide services normally for a long period of time. To this end, we must plan ahead.
+In the current implementation of the protocol, the sector will be forcibly terminated if there are two consecutive weeks of faults. However, two weeks is not enough for a large storage provider to complete the data migration and restart the service. If appropriate measures are not taken, it will not only cause huge economic losses to the storage provider, but also cause large fluctuations in the storage power of the entire Filecoin network.
+Therefore, it is necessary to make some adjustments to the sector fault period. Regarding the deal sector, the current data of all transactions is about 32 PiB. It is not a big problem to complete the real data migration within two weeks, but it is far from enough for the EiB level of cc sector to complete the migration within two weeks, so we propose to extend the cc sector fault period from 2 weeks to 6 weeks.
+
+## Specification
+<!--The technical specification should describe the syntax and semantics of any new feature. The specification should be detailed enough to allow competing, interoperable implementations for any of the current Filecoin implementations. -->
+
+Extend fault period of cc sector from 2 weeks to 6 weeks, and calculate the right fee structure.
+
+## Design Rationale
+<!--The rationale fleshes out the specification by describing what motivated the design and why particular design decisions were made. It should describe alternate designs that were considered and related work, e.g. how the feature is supported in other languages. The rationale may also provide evidence of consensus within the community, and should discuss important objections or concerns raised during discussion.-->
+
+Extend the cc sector fault period to buy time for storage providers to migrate data
+
+## Backwards Compatibility
+<!--All FIPs that introduce backwards incompatibilities must include a section describing these incompatibilities and their severity. The FIP must explain how the author proposes to deal with these incompatibilities. FIP submissions without a sufficient backwards compatibility treatise may be rejected outright.-->
+
+The proposal extends the fault period of the cc sector and adjusts the related economic model, so such changes must be completed through version upgrades.
+
+## Test Cases
+<!--Test cases for an implementation are mandatory for FIPs that are affecting consensus changes. Other FIPs can choose to include links to test cases if applicable.-->
+
+The following test cases should be covered:
+
+- Calculate whether the penalty amount for different fault durations is consistent with expectations
+- Test whether there is a conflict with the sector expiration
+
+
+## Security Considerations
+<!--All FIPs must contain a section that discusses the security implications/considerations relevant to the proposed change. Include information that might be important for security discussions, surfaces risks and can be used throughout the life cycle of the proposal. E.g. include security-relevant design decisions, concerns, important discussions, implementation-specific guidance and pitfalls, an outline of threats and risks and how they are being addressed. FIP submissions missing the "Security Considerations" section will be rejected. A FIP cannot proceed to status "Final" without a Security Considerations discussion deemed sufficient by the reviewers.-->
+
+No obvious impact on protocol security.  
+
+By the way, If the six-week windowpost faults deducts too much pledge, the proposal may not be accepted by some storage providers.
+If the penalty strategy is to be adjusted, reducing the daily fault penalty will reduce the intensity of the windowpost penalty, and increasing the initial penalty will reduce the storage provider's rate of return.
+
+## Incentive Considerations
+<!--All FIPs must contain a section that discusses the incentive implications/considerations relative to the proposed change. Include information that might be important for incentive discussion. A discussion on how the proposed change will incentivize reliable and useful storage is required. FIP submissions missing the "Incentive Considerations" section will be rejected. An FIP cannot proceed to status "Final" without a Incentive Considerations discussion deemed sufficient by the reviewers.-->
+
+The incentive mechanism has not changed
+
+## Product Considerations
+<!--All FIPs must contain a section that discusses the product implications/considerations relative to the proposed change. Include information that might be important for product discussion. A discussion on how the proposed change will enable better storage-related goods and services to be developed on Filecoin. FIP submissions missing the "Product Considerations" section will be rejected. An FIP cannot proceed to status "Final" without a Product Considerations discussion deemed sufficient by the reviewers.-->
+
+For related products, there is no impact.
+
+
+## Implementation
+<!--The implementations must be completed before any core FIP is given status "Final", but it need not be completed before the FIP is accepted. While there is merit to the approach of reaching consensus on the specification and rationale before writing code, the principle of "rough consensus and running code" is still useful when it comes to resolving many discussions of API details.-->
+
+TODO in all related Filecoin implementations.
+
+## Copyright
+Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).

From b4a2c362ce1cb6bfc232a1418aea77d28c962964 Mon Sep 17 00:00:00 2001
From: IPFSUnion <tech@ipfsunion.cn>
Date: Fri, 1 Oct 2021 21:41:53 +0800
Subject: [PATCH 02/12] extend the cc sector fault period

---
 FIPS/fip-0025.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/FIPS/fip-0025.md b/FIPS/fip-0025.md
index 9c2cf0ccc..2758d2e12 100644
--- a/FIPS/fip-0025.md
+++ b/FIPS/fip-0025.md
@@ -57,7 +57,7 @@ The following test cases should be covered:
 
 No obvious impact on protocol security.  
 
-By the way, If the six-week windowpost faults deducts too much pledge, the proposal may not be accepted by some storage providers.
+By the way, If the six-week windowpost faults deducts too much pledge, the proposal may not be accepted by some storage providers.  
 If the penalty strategy is to be adjusted, reducing the daily fault penalty will reduce the intensity of the windowpost penalty, and increasing the initial penalty will reduce the storage provider's rate of return.
 
 ## Incentive Considerations

From 99c7189ba72a059522f7b7b953664521c3cf9d42 Mon Sep 17 00:00:00 2001
From: IPFSUnion <tech@ipfsunion.cn>
Date: Wed, 6 Oct 2021 11:00:22 +0800
Subject: [PATCH 03/12] Remove adjustments to the fee structure

Co-authored-by: MollyM <momack2@users.noreply.github.com>
---
 FIPS/fip-0025.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/FIPS/fip-0025.md b/FIPS/fip-0025.md
index 2758d2e12..e1c7ade56 100644
--- a/FIPS/fip-0025.md
+++ b/FIPS/fip-0025.md
@@ -31,7 +31,7 @@ Therefore, it is necessary to make some adjustments to the sector fault period.
 ## Specification
 <!--The technical specification should describe the syntax and semantics of any new feature. The specification should be detailed enough to allow competing, interoperable implementations for any of the current Filecoin implementations. -->
 
-Extend fault period of cc sector from 2 weeks to 6 weeks, and calculate the right fee structure.
+Extend fault period of cc sector from 2 weeks to 6 weeks.
 
 ## Design Rationale
 <!--The rationale fleshes out the specification by describing what motivated the design and why particular design decisions were made. It should describe alternate designs that were considered and related work, e.g. how the feature is supported in other languages. The rationale may also provide evidence of consensus within the community, and should discuss important objections or concerns raised during discussion.-->

From 8ffd84b486c772f2e042d6d47faec8d8811eee33 Mon Sep 17 00:00:00 2001
From: IPFSUnion <tech@ipfsunion.cn>
Date: Wed, 6 Oct 2021 11:01:36 +0800
Subject: [PATCH 04/12] Update FIPS/fip-0025.md

Co-authored-by: Jiaying Wang <42981373+jennijuju@users.noreply.github.com>
---
 FIPS/fip-0025.md | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

diff --git a/FIPS/fip-0025.md b/FIPS/fip-0025.md
index e1c7ade56..2ef591f78 100644
--- a/FIPS/fip-0025.md
+++ b/FIPS/fip-0025.md
@@ -55,10 +55,7 @@ The following test cases should be covered:
 ## Security Considerations
 <!--All FIPs must contain a section that discusses the security implications/considerations relevant to the proposed change. Include information that might be important for security discussions, surfaces risks and can be used throughout the life cycle of the proposal. E.g. include security-relevant design decisions, concerns, important discussions, implementation-specific guidance and pitfalls, an outline of threats and risks and how they are being addressed. FIP submissions missing the "Security Considerations" section will be rejected. A FIP cannot proceed to status "Final" without a Security Considerations discussion deemed sufficient by the reviewers.-->
 
-No obvious impact on protocol security.  
-
-By the way, If the six-week windowpost faults deducts too much pledge, the proposal may not be accepted by some storage providers.  
-If the penalty strategy is to be adjusted, reducing the daily fault penalty will reduce the intensity of the windowpost penalty, and increasing the initial penalty will reduce the storage provider's rate of return.
+Strong incentives remain for Storage Providers to keep proving all their sectors reliably, which should prevent any increased variability / unreliability in network storage power.
 
 ## Incentive Considerations
 <!--All FIPs must contain a section that discusses the incentive implications/considerations relative to the proposed change. Include information that might be important for incentive discussion. A discussion on how the proposed change will incentivize reliable and useful storage is required. FIP submissions missing the "Incentive Considerations" section will be rejected. An FIP cannot proceed to status "Final" without a Incentive Considerations discussion deemed sufficient by the reviewers.-->

From a055717ee20ac36aae1c735581a405bdbd37ad5b Mon Sep 17 00:00:00 2001
From: IPFSUnion <tech@ipfsunion.cn>
Date: Wed, 6 Oct 2021 11:03:09 +0800
Subject: [PATCH 05/12] Update FIPS/fip-0025.md

Co-authored-by: MollyM <momack2@users.noreply.github.com>
---
 FIPS/fip-0025.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/FIPS/fip-0025.md b/FIPS/fip-0025.md
index 2ef591f78..76e2bec62 100644
--- a/FIPS/fip-0025.md
+++ b/FIPS/fip-0025.md
@@ -65,7 +65,8 @@ The incentive mechanism has not changed
 ## Product Considerations
 <!--All FIPs must contain a section that discusses the product implications/considerations relative to the proposed change. Include information that might be important for product discussion. A discussion on how the proposed change will enable better storage-related goods and services to be developed on Filecoin. FIP submissions missing the "Product Considerations" section will be rejected. An FIP cannot proceed to status "Final" without a Product Considerations discussion deemed sufficient by the reviewers.-->
 
-For related products, there is no impact.
+Increasing the sector forced termination window increases the potential time between when a storage provider could stop storing/proving data to the network, and when storage clients would have their payment refunded. This could be annoying/frustrating from a sector repair perspective, since there is a longer window before it is clear whether a storage provider is coming back online, which the client isn't compensated for.
+
 
 
 ## Implementation

From 182003ed0373dfb4bffaaf25c7062537f27bdff9 Mon Sep 17 00:00:00 2001
From: IPFSUnion <tech@ipfsunion.cn>
Date: Wed, 6 Oct 2021 11:07:02 +0800
Subject: [PATCH 06/12] Update FIPS/fip-0025.md

Co-authored-by: MollyM <momack2@users.noreply.github.com>
---
 FIPS/fip-0025.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/FIPS/fip-0025.md b/FIPS/fip-0025.md
index 76e2bec62..44e35d0d4 100644
--- a/FIPS/fip-0025.md
+++ b/FIPS/fip-0025.md
@@ -41,7 +41,8 @@ Extend the cc sector fault period to buy time for storage providers to migrate d
 ## Backwards Compatibility
 <!--All FIPs that introduce backwards incompatibilities must include a section describing these incompatibilities and their severity. The FIP must explain how the author proposes to deal with these incompatibilities. FIP submissions without a sufficient backwards compatibility treatise may be rejected outright.-->
 
-The proposal extends the fault period of the cc sector and adjusts the related economic model, so such changes must be completed through version upgrades.
+The proposal extends the fault period of the cc sector, so such changes must be completed through version upgrades.
+
 
 ## Test Cases
 <!--Test cases for an implementation are mandatory for FIPs that are affecting consensus changes. Other FIPs can choose to include links to test cases if applicable.-->

From ba1b97e682a1ea693cb7033c44fd14e996f81d0c Mon Sep 17 00:00:00 2001
From: IPFSUnion <tech@ipfsunion.cn>
Date: Wed, 6 Oct 2021 11:07:54 +0800
Subject: [PATCH 07/12] Update FIPS/fip-0025.md

Co-authored-by: MollyM <momack2@users.noreply.github.com>
---
 FIPS/fip-0025.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/FIPS/fip-0025.md b/FIPS/fip-0025.md
index 44e35d0d4..7b344bcdb 100644
--- a/FIPS/fip-0025.md
+++ b/FIPS/fip-0025.md
@@ -61,7 +61,8 @@ Strong incentives remain for Storage Providers to keep proving all their sectors
 ## Incentive Considerations
 <!--All FIPs must contain a section that discusses the incentive implications/considerations relative to the proposed change. Include information that might be important for incentive discussion. A discussion on how the proposed change will incentivize reliable and useful storage is required. FIP submissions missing the "Incentive Considerations" section will be rejected. An FIP cannot proceed to status "Final" without a Incentive Considerations discussion deemed sufficient by the reviewers.-->
 
-The incentive mechanism has not changed
+The maintained FaultFee structure provides strong incentives for storage providers to maintain great quality of service and keep any downtime to a bare minimum.
+
 
 ## Product Considerations
 <!--All FIPs must contain a section that discusses the product implications/considerations relative to the proposed change. Include information that might be important for product discussion. A discussion on how the proposed change will enable better storage-related goods and services to be developed on Filecoin. FIP submissions missing the "Product Considerations" section will be rejected. An FIP cannot proceed to status "Final" without a Product Considerations discussion deemed sufficient by the reviewers.-->

From 1aff8d5b1ab2e84a84d35caadf08d5021b07b82a Mon Sep 17 00:00:00 2001
From: IPFSUnion <tech@ipfsunion.cn>
Date: Wed, 6 Oct 2021 14:31:27 +0800
Subject: [PATCH 08/12] remove cc

---
 FIPS/fip-0025.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/FIPS/fip-0025.md b/FIPS/fip-0025.md
index 7b344bcdb..a6f1b264a 100644
--- a/FIPS/fip-0025.md
+++ b/FIPS/fip-0025.md
@@ -1,6 +1,6 @@
 ---
 fip: "0025"
-title: Extend the fault period of cc sector from 2 weeks to 6 weeks
+title: Extend the fault period of sector from 2 weeks to 6 weeks
 author: IPFSUnion(@IPFSUnion)
 discussions-to: https://github.com/filecoin-project/FIPs/issues/189
 status: Draft
@@ -26,22 +26,22 @@ Filecoin needs to extend the fault period so that large storage providers have e
 
 Any country in the world is likely to face force majeure factors such as major natural disasters or social abnormal events, causing storage providers to be unable to provide services normally for a long period of time. To this end, we must plan ahead.
 In the current implementation of the protocol, the sector will be forcibly terminated if there are two consecutive weeks of faults. However, two weeks is not enough for a large storage provider to complete the data migration and restart the service. If appropriate measures are not taken, it will not only cause huge economic losses to the storage provider, but also cause large fluctuations in the storage power of the entire Filecoin network.
-Therefore, it is necessary to make some adjustments to the sector fault period. Regarding the deal sector, the current data of all transactions is about 32 PiB. It is not a big problem to complete the real data migration within two weeks, but it is far from enough for the EiB level of cc sector to complete the migration within two weeks, so we propose to extend the cc sector fault period from 2 weeks to 6 weeks.
+Therefore, it is necessary to make some adjustments to the sector fault period. Regarding the deal sector, the current data of all transactions is about 32 PiB. It is not a big problem to complete the real data migration within two weeks, but it is far from enough for the EiB level of cc sector to complete the migration within two weeks, so we propose to extend the sector fault period from 2 weeks to 6 weeks.
 
 ## Specification
 <!--The technical specification should describe the syntax and semantics of any new feature. The specification should be detailed enough to allow competing, interoperable implementations for any of the current Filecoin implementations. -->
 
-Extend fault period of cc sector from 2 weeks to 6 weeks.
+Extend fault period of sector from 2 weeks to 6 weeks.
 
 ## Design Rationale
 <!--The rationale fleshes out the specification by describing what motivated the design and why particular design decisions were made. It should describe alternate designs that were considered and related work, e.g. how the feature is supported in other languages. The rationale may also provide evidence of consensus within the community, and should discuss important objections or concerns raised during discussion.-->
 
-Extend the cc sector fault period to buy time for storage providers to migrate data
+Extend the sector fault period to buy time for storage providers to migrate data
 
 ## Backwards Compatibility
 <!--All FIPs that introduce backwards incompatibilities must include a section describing these incompatibilities and their severity. The FIP must explain how the author proposes to deal with these incompatibilities. FIP submissions without a sufficient backwards compatibility treatise may be rejected outright.-->
 
-The proposal extends the fault period of the cc sector, so such changes must be completed through version upgrades.
+The proposal extends the fault period of the sector, so such changes must be completed through version upgrades.
 
 
 ## Test Cases

From 77f7e5a1e1c3a30fceab49f9de522734d0b5330e Mon Sep 17 00:00:00 2001
From: IPFSUnion <tech@ipfsunion.cn>
Date: Wed, 6 Oct 2021 14:38:35 +0800
Subject: [PATCH 09/12] Update and rename fip-0025.md to fip-0026.md

---
 FIPS/{fip-0025.md => fip-0026.md} | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
 rename FIPS/{fip-0025.md => fip-0026.md} (97%)

diff --git a/FIPS/fip-0025.md b/FIPS/fip-0026.md
similarity index 97%
rename from FIPS/fip-0025.md
rename to FIPS/fip-0026.md
index a6f1b264a..95dddccc9 100644
--- a/FIPS/fip-0025.md
+++ b/FIPS/fip-0026.md
@@ -1,5 +1,5 @@
 ---
-fip: "0025"
+fip: "0026"
 title: Extend the fault period of sector from 2 weeks to 6 weeks
 author: IPFSUnion(@IPFSUnion)
 discussions-to: https://github.com/filecoin-project/FIPs/issues/189
@@ -24,8 +24,8 @@ Filecoin needs to extend the fault period so that large storage providers have e
 ## Change Motivation
 <!--The motivation is critical for FIPs that want to change the Filecoin protocol. It should clearly explain why the existing protocol specification is inadequate to address the problem that the FIP solves. FIP submissions without sufficient motivation may be rejected outright.-->
 
-Any country in the world is likely to face force majeure factors such as major natural disasters or social abnormal events, causing storage providers to be unable to provide services normally for a long period of time. To this end, we must plan ahead.
-In the current implementation of the protocol, the sector will be forcibly terminated if there are two consecutive weeks of faults. However, two weeks is not enough for a large storage provider to complete the data migration and restart the service. If appropriate measures are not taken, it will not only cause huge economic losses to the storage provider, but also cause large fluctuations in the storage power of the entire Filecoin network.
+Any country in the world is likely to face force majeure factors such as major natural disasters or social abnormal events, causing storage providers to be unable to provide services normally for a long period of time. To this end, we must plan ahead.  
+In the current implementation of the protocol, the sector will be forcibly terminated if there are two consecutive weeks of faults. However, two weeks is not enough for a large storage provider to complete the data migration and restart the service. If appropriate measures are not taken, it will not only cause huge economic losses to the storage provider, but also cause large fluctuations in the storage power of the entire Filecoin network.  
 Therefore, it is necessary to make some adjustments to the sector fault period. Regarding the deal sector, the current data of all transactions is about 32 PiB. It is not a big problem to complete the real data migration within two weeks, but it is far from enough for the EiB level of cc sector to complete the migration within two weeks, so we propose to extend the sector fault period from 2 weeks to 6 weeks.
 
 ## Specification

From d115bce393588844816026ed8d702d95abfb19c9 Mon Sep 17 00:00:00 2001
From: IPFSUnion <tech@ipfsunion.cn>
Date: Fri, 8 Oct 2021 13:58:10 +0800
Subject: [PATCH 10/12] Update fip-0026.md

---
 FIPS/fip-0026.md | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)

diff --git a/FIPS/fip-0026.md b/FIPS/fip-0026.md
index 95dddccc9..532c858c8 100644
--- a/FIPS/fip-0026.md
+++ b/FIPS/fip-0026.md
@@ -61,7 +61,8 @@ Strong incentives remain for Storage Providers to keep proving all their sectors
 ## Incentive Considerations
 <!--All FIPs must contain a section that discusses the incentive implications/considerations relative to the proposed change. Include information that might be important for incentive discussion. A discussion on how the proposed change will incentivize reliable and useful storage is required. FIP submissions missing the "Incentive Considerations" section will be rejected. An FIP cannot proceed to status "Final" without a Incentive Considerations discussion deemed sufficient by the reviewers.-->
 
-The maintained FaultFee structure provides strong incentives for storage providers to maintain great quality of service and keep any downtime to a bare minimum.
+The maintained FaultFee structure provides strong incentives for storage providers to maintain great quality of service and keep any downtime to a bare minimum.  
+So this proposal seeks to extend the fault window without recalculating the fault fees schedule. it is thus fundamentally irrational for storage providers to choose to fault on sectors for an extended period of time. This reinforces the idea that this extended fault period ought to be viewed as a worst-case-scenario provision, rather than a benchmark for how long someone could reasonably take data offline. The current punishment is quite exspensive so that it is unlikely to incentive unreliable storage behavior.
 
 
 ## Product Considerations
@@ -74,7 +75,11 @@ Increasing the sector forced termination window increases the potential time bet
 ## Implementation
 <!--The implementations must be completed before any core FIP is given status "Final", but it need not be completed before the FIP is accepted. While there is merit to the approach of reaching consensus on the specification and rationale before writing code, the principle of "rough consensus and running code" is still useful when it comes to resolving many discussions of API details.-->
 
-TODO in all related Filecoin implementations.
+Specs-actors PR: https://github.com/filecoin-project/specs-actors/pull/1504  
+
+Note:  
+This proposal will not go into effect until v14 Chocolate network upgrade.  
+If a storage provider were to fault on their Window PoSt submission before the upgrade (scheduled for the end of October), they would still be bound to the 14 day fault sector period. On day 15, for example, they could experience sector termination even if this FIP had been approved.
 
 ## Copyright
 Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).

From e879fa854855081832642f861c74f816912c684f Mon Sep 17 00:00:00 2001
From: IPFSUnion <tech@ipfsunion.cn>
Date: Sat, 9 Oct 2021 10:44:58 +0800
Subject: [PATCH 11/12] Update fip-0026.md

---
 FIPS/fip-0026.md | 14 +++++---------
 1 file changed, 5 insertions(+), 9 deletions(-)

diff --git a/FIPS/fip-0026.md b/FIPS/fip-0026.md
index 532c858c8..227855869 100644
--- a/FIPS/fip-0026.md
+++ b/FIPS/fip-0026.md
@@ -1,6 +1,6 @@
 ---
 fip: "0026"
-title: Extend the fault period of sector from 2 weeks to 6 weeks
+title: Extend sector fault cutoff period from 2 weeks to 6 weeks
 author: IPFSUnion(@IPFSUnion)
 discussions-to: https://github.com/filecoin-project/FIPs/issues/189
 status: Draft
@@ -25,13 +25,13 @@ Filecoin needs to extend the fault period so that large storage providers have e
 <!--The motivation is critical for FIPs that want to change the Filecoin protocol. It should clearly explain why the existing protocol specification is inadequate to address the problem that the FIP solves. FIP submissions without sufficient motivation may be rejected outright.-->
 
 Any country in the world is likely to face force majeure factors such as major natural disasters or social abnormal events, causing storage providers to be unable to provide services normally for a long period of time. To this end, we must plan ahead.  
-In the current implementation of the protocol, the sector will be forcibly terminated if there are two consecutive weeks of faults. However, two weeks is not enough for a large storage provider to complete the data migration and restart the service. If appropriate measures are not taken, it will not only cause huge economic losses to the storage provider, but also cause large fluctuations in the storage power of the entire Filecoin network.  
-Therefore, it is necessary to make some adjustments to the sector fault period. Regarding the deal sector, the current data of all transactions is about 32 PiB. It is not a big problem to complete the real data migration within two weeks, but it is far from enough for the EiB level of cc sector to complete the migration within two weeks, so we propose to extend the sector fault period from 2 weeks to 6 weeks.
+Up to the current V13 network, the sector will be forcibly terminated if there are two consecutive weeks of faults. However, two weeks is not enough for a large storage provider to complete the data migration and restart the service. If appropriate measures are not taken, it will not only cause huge economic losses to the storage provider, but also cause large fluctuations in the storage power of the entire Filecoin network.  
+Therefore, it is necessary to make some adjustments to the sector fault period. Regarding the deal sector, the total data of deals is about 33 PiB by 2021/10/09. It is not a big problem to complete the real data migration within two weeks, but it is far from enough for the EiB level of cc sector to complete the migration within two weeks, so we propose to extend the sector fault period from 2 weeks to 6 weeks.
 
 ## Specification
 <!--The technical specification should describe the syntax and semantics of any new feature. The specification should be detailed enough to allow competing, interoperable implementations for any of the current Filecoin implementations. -->
 
-Extend fault period of sector from 2 weeks to 6 weeks.
+Extend fault period of the sector before sector termination from 2 consecutive weeks to 6 consecutive weeks.  
 
 ## Design Rationale
 <!--The rationale fleshes out the specification by describing what motivated the design and why particular design decisions were made. It should describe alternate designs that were considered and related work, e.g. how the feature is supported in other languages. The rationale may also provide evidence of consensus within the community, and should discuss important objections or concerns raised during discussion.-->
@@ -47,11 +47,7 @@ The proposal extends the fault period of the sector, so such changes must be com
 ## Test Cases
 <!--Test cases for an implementation are mandatory for FIPs that are affecting consensus changes. Other FIPs can choose to include links to test cases if applicable.-->
 
-The following test cases should be covered:
-
-- Calculate whether the penalty amount for different fault durations is consistent with expectations
-- Test whether there is a conflict with the sector expiration
-
+Test PR: https://github.com/filecoin-project/specs-actors/pull/1506
 
 ## Security Considerations
 <!--All FIPs must contain a section that discusses the security implications/considerations relevant to the proposed change. Include information that might be important for security discussions, surfaces risks and can be used throughout the life cycle of the proposal. E.g. include security-relevant design decisions, concerns, important discussions, implementation-specific guidance and pitfalls, an outline of threats and risks and how they are being addressed. FIP submissions missing the "Security Considerations" section will be rejected. A FIP cannot proceed to status "Final" without a Security Considerations discussion deemed sufficient by the reviewers.-->

From fd2274f159ad6334af712b944747911e3845d3ec Mon Sep 17 00:00:00 2001
From: Jiaying Wang <42981373+jennijuju@users.noreply.github.com>
Date: Tue, 12 Oct 2021 12:38:53 -0400
Subject: [PATCH 12/12] Update FIPS/fip-0026.md

Co-authored-by: Aayush Rajasekaran <arajasek94@gmail.com>
---
 FIPS/fip-0026.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/FIPS/fip-0026.md b/FIPS/fip-0026.md
index 227855869..1776c4d14 100644
--- a/FIPS/fip-0026.md
+++ b/FIPS/fip-0026.md
@@ -26,7 +26,7 @@ Filecoin needs to extend the fault period so that large storage providers have e
 
 Any country in the world is likely to face force majeure factors such as major natural disasters or social abnormal events, causing storage providers to be unable to provide services normally for a long period of time. To this end, we must plan ahead.  
 Up to the current V13 network, the sector will be forcibly terminated if there are two consecutive weeks of faults. However, two weeks is not enough for a large storage provider to complete the data migration and restart the service. If appropriate measures are not taken, it will not only cause huge economic losses to the storage provider, but also cause large fluctuations in the storage power of the entire Filecoin network.  
-Therefore, it is necessary to make some adjustments to the sector fault period. Regarding the deal sector, the total data of deals is about 33 PiB by 2021/10/09. It is not a big problem to complete the real data migration within two weeks, but it is far from enough for the EiB level of cc sector to complete the migration within two weeks, so we propose to extend the sector fault period from 2 weeks to 6 weeks.
+Therefore, it is necessary to make some adjustments to the sector fault period.
 
 ## Specification
 <!--The technical specification should describe the syntax and semantics of any new feature. The specification should be detailed enough to allow competing, interoperable implementations for any of the current Filecoin implementations. -->