Revised FIP-0036 Draft for Community Consideration #451
Conversation
## Simple Summary - A Sector Duration Multiplier is introduced for all sectors, including Committed Capacity (CC) sectors and sectors containing storage deals. - A longer sector will have a higher Quality Adjusted Power than a shorter sector, all things equal. - The Duration Multiplier is multiplicative on the existing Quality Multiplier incentive (Filecoin Plus incentive). Filecoin Plus already offers up to a 10x multiplier for proving storage of data from verified clients. FIP-0036 introduces an independent Duration Multiplier up to 3.5x. Thus, the *maximum* multiplier available to any sector will increase from 10x to 35x. - Sectors with higher Quality Adjusted Power as a result of the Sector Duration Multiplier and Quality Multiplier will require higher initial pledge collateral. - The minimum sector duration time will increase from 6 months to 1 year and the maximum sector duration will increase from 1.5 years to 3.5 years. This change to maximum sector duration **will be implemented gradually**: we propose increasing the maximum duration by 6 months every week for 4 weeks, until the maximum duration of 3.5 years is available. - CEL and the community will monitor the network and look to increase the maximum sector duration in a future FIP if network conditions merit, pending community-driven support for such measures. - The SectorInitialConsensusPledge multiplier will increase from 30% to 50%. - This policy will apply at Sector Upgrade and Extension.
vkalghatgi
requested review from
momack2,
arajasek,
jennijuju,
kaitlin-beegle and
anorth
as code owners
|
Hello everyone, Glad to see you have made an overhaul after the feedback on the original FIP over the last period. Well I read in the previous chat a lot of points of improvement by very important developers and core storage providers. Is the only thing this new FIP changes the sector lifetime from 5 to 3.5 years? If so, I am stunned. |
|
Importantly a gradual ramp up of the max sector commitment is introduced, this solves many of edge cases that were surfaced in the previous FIP draft. I personally think that the max lock up period should be higher as the risk increases accordingly. The objective of a protocol changes should be to provide the ecosystem with the ability to choose, so the range should be wide, potentially with the expectation to see a normal distribution. My suggestion would be to closely monitor the distribution of the lock up period and accordingly adjust the range. |
|
Feels better than the last FIP. Proceed with caution. Keep the dialog open at all times. |
|
Here is a list of changes: |
|
Without a better or more thoroughly vetted option, I support FIP0036 being implemented in a timely manner and the proposed phased rollout is prudent. After assessing the effects of the initial phase of the rollout, if there is a detrimental effect on our network, then there should be a contingency plan in place to address it IMO. Has there been discussion about what will be done if FIP0036 fails to achieve it's goals? |
| - Two SPs, A and B, each have 1PiB QAP today, 100TiB/day sealing throughput, and 10PiB worth of collateral. | ||
| - SP A can extend CC sectors, and take 3y extension with 3x multiplier. They can quickly gain 3PiB QAP through extension, and a further 7PiB through onboarding over 70days. | ||
| - SP B has FIL+ deals. They can’t extend. But they can onboard new 3y deals at a rate of up to 3 * 10 * 100TiB/day = 3PiB of QAP/day. | ||
| - FIL+ ability to gain a multiplier on extending is not the limiting factor. |
There was a problem hiding this comment.
| - FIL+ ability to gain a multiplier on extending is not the limiting factor. | |
| - Fil+ ability to gain a multiplier on extending is not the limiting factor. |
|
Added review as an FIP editor. Note to the community, technical feedback is preferred to be provided in the FIP discussion |
|
From 5 years to 3.5 years, which is very considerate considering the operating cycle of the machine. |
Notable Changes/Adjustments