Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

sealing pipeline: Support importing (partially) sealed sectors #9012

Closed
magik6k opened this issue Jul 11, 2022 · 4 comments
Closed

sealing pipeline: Support importing (partially) sealed sectors #9012

magik6k opened this issue Jul 11, 2022 · 4 comments
Assignees
@magik6k
Labels
area/api area/sealing dif/hard Suggests that having worked on the specific component affected by this issue is important effort/days Effort: Multiple Days impact/new-api kind/feature Kind: Feature P1 P1: Must be resolved

Comments

@magik6k
Copy link
Contributor

magik6k commented Jul 11, 2022

This is a feature needed by things like external sealing services.

We should add some new APIs to lotus-miner which would make it possible to import sector data and metadata in any state.

This would enable a lot of new alternative sealing architectures - for example making it possible to offload PC1/2 compute to an external service, ship sector data to the miner before any (Commit/PreCommit) messages are sent to the chain, and let the miner handle the remaining sealing steps (sending chain messages, running Commit1/2 (possibly using external snarking service for PoRep))

Example architecture:
sealing-service
@magik6k magik6k added kind/feature Kind: Feature P2 P2: Should be resolved effort/days Effort: Multiple Days dif/hard Suggests that having worked on the specific component affected by this issue is important area/sealing area/api impact/new-api labels Jul 11, 2022
@magik6k magik6k self-assigned this Jul 11, 2022
@f8-ptrk
Copy link
Contributor

f8-ptrk commented Jul 11, 2022

much love for this!

@ImmanuelSegol
Copy link

ImmanuelSegol commented Jul 17, 2022 •
edited
Loading

@magik6k magik6k Is this new architecture being worked on now?
Also thanks for sharing this!

@jennijuju
Copy link
Member

jennijuju commented Jul 19, 2022 •
edited
Loading

@ImmanuelSegol

not atm. We will pick this up maybe, later in Q3

@magik6k magik6k mentioned this issue Aug 9, 2022
Merged
5 tasks
@jennijuju jennijuju added P1 P1: Must be resolved and removed P2 P2: Should be resolved labels Aug 11, 2022
@magik6k magik6k mentioned this issue Aug 24, 2022
Merged
5 tasks
@jennijuju
Copy link
Member

can close now?

@magik6k magik6k closed this as completed Sep 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@magik6k magik6k

Labels
area/api area/sealing dif/hard Suggests that having worked on the specific component affected by this issue is important effort/days Effort: Multiple Days impact/new-api kind/feature Kind: Feature P1 P1: Must be resolved
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@magik6k @ImmanuelSegol @jennijuju @f8-ptrk