lightninglabs / lightninglabs/pool
rpc: add expired field or filter flag for the Leases command
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 259
- Forks
- 51
- PR merge metrics
- No merged PRs in 30d
Description
Today `pool auction leases` lets a use see the set of channel leases they bought or sold. However since we don't yet auto-close leased channels after expiry (if we were the maker) users need to eye ball the expiry height and compared that against their known best height to determine if the lease is expired or not. To make things a bit easier in the CLI days, we should add either an `expired` field, or a new flag on the CLI that user can use to make it print out only expired leases.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the implementation of `pool auction leases` and trace how lease expiry height and the user's best height are obtained. Confirm with maintainers whether completion means an `expired` field or an expired-only CLI flag, then verify the chosen behavior with coverage for the lease listing output or filter.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100