lotus/curiosrc/seal
2024-04-04 11:17:04 -05:00
..
finalize_pieces.go Merge remote-tracking branch 'origin/master' into feat/lpdeal-cache 2024-03-17 17:31:26 +01:00
poller_commit_msg.go feat: Curio - Easy Migration (#11617) 2024-03-15 16:38:13 -05:00
poller_precommit_msg.go feat: Curio - Easy Migration (#11617) 2024-03-15 16:38:13 -05:00
poller.go feat: Curio - Easy Migration (#11617) 2024-03-15 16:38:13 -05:00
README.md rename lotus-provider 2024-04-04 14:32:06 +02:00
sector_num_alloc.go feat: Curio - Easy Migration (#11617) 2024-03-15 16:38:13 -05:00
task_finalize.go Merge remote-tracking branch 'origin/master' into feat/lpdeal-cache 2024-03-17 17:31:26 +01:00
task_movestorage.go feat: curio: Storage reservations in MoveStorage 2024-04-03 21:40:06 +02:00
task_porep.go feat: Curio - Easy Migration (#11617) 2024-03-15 16:38:13 -05:00
task_sdr.go Merge remote-tracking branch 'origin/master' into feat/lpdeal-cache 2024-03-17 17:31:26 +01:00
task_submit_commit.go feat: Curio - Easy Migration (#11617) 2024-03-15 16:38:13 -05:00
task_submit_precommit.go fix: curio seal: Check ticket age before sending PreCommit message 2024-03-26 20:33:23 +01:00
task_trees_test.go feat: Curio - Easy Migration (#11617) 2024-03-15 16:38:13 -05:00
task_trees.go fix: paths/local: Fix on-disk storage accounting in new reservations (#11825) 2024-04-04 11:17:04 -05:00

Curio Sealer

Overview

The Curio sealer is a collection of harmony tasks and a common poller which implement the sealing functionality of the Filecoin protocol.

Pipeline Tasks

  • SDR pipeline
    • SDR - Generate SDR layers
    • SDRTrees - Generate tree files (TreeD, TreeR, TreeC)
    • PreCommitSubmit - Submit precommit message to the network
    • PoRep - Generate PoRep proof
    • CommitSubmit - Submit commit message to the network

Poller

The poller is a background process running on every node which runs any of the SDR pipeline tasks. It periodically checks the state of sectors in the SDR pipeline and schedules any tasks to run which will move the sector along the pipeline.

Error Handling

  • Pipeline tasks are expected to always finish successfully as harmonytask tasks. If a sealing task encounters an error, it should mark the sector pipeline entry as failed and exit without erroring. The poller will then figure out a recovery strategy for the sector.