boost
boost copied to clipboard
Boost is a tool for Filecoin storage providers to manage data storage and retrievals on Filecoin.
From a monitoring perspective it appears we no longer have working code to follow easily a single graphsync request with all its concurrency span-out traces, so it is hard to...
Graphsync requests an entire graph of blocks in one request. Currently LID makes a new request to the database for each block (to get the block offset) in real time....
### Checklist - [X] This is **not** a question or a support request. If you have any boost related questions, please ask in the [discussion forum](https://github.com/filecoin-project/boost/discussions). - [X] This is...
# What We want Lassie to download over HTTP from booster-http. This issue tracks what is needed for this to happen. # Components Updated 6/12/23 to reflect current state and...
At the moment `resolver_piece.go` is calculating itself whether a piece is unsealed or not, via its `sealStatus` function. It should be refactored to rely on SSM, and SSM should be...
1. Expired deals should be cleaned up - Should be user defined not automatic in case SP wants to keep serving from expired deals. 2. Slashed deals should be cleaned...
### Checklist - [X] This is **not** a question or a support request. If you have any boost related questions, please ask in the [discussion forum](https://github.com/filecoin-project/boost/discussions). - [X] This is...
we need a health page hosted on boostd, so that SPs know quickly if all their sub-process are working
Currently, index-provider uses the local batching datastore backed by leveldb to store advertisement and other mapping data. Once we have LID in place, we should find a way to migrate...
Current Boost deal flow: Deal -> Publish -> AP -> IndexandAnnounce (Add Piece Store -> Register with Dagstore -> Announce) -> Watch the sealing pipeline Retry Deal flow(After AP): Add...