filecoin-project / filecoin-project/boost

Easily cancel / clear storage deals from queue (for fvm contract deals) if it has been claimed already

Open
#1,272 2 comments 0 reactions 0 assignees View on GitHub
kind/feature need/triage
Dominant language
Go
Stars
121
Forks
79
Avg merge
10d 14h
Merged PRs (30d)
1

Description

### Checklist

- [X] This is **not** a new feature or an enhancement to the Filecoin protocol. If it is, please open an [FIP issue](https://github.com/filecoin-project/FIPs/blob/master/FIPS/fip-0001.md).
- [X] This is **not** brainstorming ideas. If you have an idea you'd like to discuss, please open a new discussion on [the Boost forum](https://github.com/filecoin-project/boost/discussions/categories/ideas) and select the category as `Ideas`.
- [X] I **have** a specific, actionable, and well motivated feature request to propose.

### Boost component

- [X] boost daemon - storage providers
- [ ] boost client
- [X] boost UI
- [ ] boost data-transfer
- [ ] boost index-provider
- [ ] Other

### What is the motivation behind this feature request? Is your feature request related to a problem? Please describe.

Have an easier way to cancel deals / stop trying to make a storage deal if an fvm contract deal has already been claimed by another SP.

### Describe the solution you'd like

SP suggestion (from early fvm testing) : It would be nice for boost to make cancel deals & clear the deal from the queue if the deal has been claimed by others

### Describe alternatives you've considered

_No response_

### Additional context

_No response_

Contributor guide

Open the contributing guide

Research direction

No files or tests are named. Start by tracing the boost daemon's storage-deal queue and its FVM contract-deal handling, then check how the boost UI exposes queued deals. Done means an already-claimed deal can be cancelled and removed from the queue without further storage-deal attempts.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
backend, blockchain
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.