Skip to content
This repository has been archived by the owner on Jun 6, 2023. It is now read-only.

Sectors sealed with V1 seal proof type cannot be extended #1309

Closed
ethan-xiao opened this issue Nov 26, 2020 · 6 comments
Closed

Sectors sealed with V1 seal proof type cannot be extended #1309

ethan-xiao opened this issue Nov 26, 2020 · 6 comments
Labels
discussion wontfix This will not be worked on

Comments

@ethan-xiao
Copy link

ethan-xiao commented Nov 26, 2020

ERROR: GasEstimateMessageGas error: estimating gas used: message execution failed: exit 18, reason: cannot extend expiration for sector 1049 with unsupported seal type 3 (RetCode=18)

@anorth
Copy link
Member

anorth commented Nov 26, 2020

This is by design, motivated by security considerations for the V1 proof. @nicola can you add any more clarity?

@anorth anorth changed the title sector extension error Sectors sealed with V1 seal proof type cannot be extended Nov 26, 2020
@anorth anorth closed this as completed Dec 16, 2020
@anorth anorth added the wontfix This will not be worked on label Dec 16, 2020
@deltazxm
Copy link

V1 proof do windowPOST have no security problem.I think V1 proof should be allowed extension to maxLifetime.Otherwise it is unfair to the miners of V1 proof sectors.

@fmtmbs
Copy link

fmtmbs commented Dec 23, 2020

Just extend the lifetime of sectors to maintain the power, I think it has noting to do with security.

@coder-lb
Copy link

I also think V1 proof doesn't have security problems. If these sectors can't be extended, so much sealing machine resources will be wasted to seal sectors again. Filecoin should be a project with less energy consumed, then it will be more competitive in storage markets.
If the huge number of sectors can't be extended, there will be several side effects. If the miners seal sectors again, it will take much more time, and much more gas. More messages will make the chain congested, and other miners will pay more high gas fees, too.

@steven004
Copy link
Contributor

This is by design, motivated by security considerations for the V1 proof. @nicola can you add any more clarity?

@anorth @nicola Would you please elaborate what kind of security concerns being considered?

@nicola
Copy link
Contributor

nicola commented Jan 12, 2021

There is a risk that a year+ from now, with highly pipelined custom hardware (less likely to be software - but not impossible), one may able to avoid storing 100% of the sector and still succeed at WindowPoSt.

As we come closer to these sectors' expiration (most are a ~year from now), depending on (1) what percentage of power these sectors sum up to, (2) what is the state of the art of ASICs and Proof of Space software, the community should decide what to do with those sectors.

I would not recommend to allow for sector extension right now.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
discussion wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

7 participants