lightninglabs / lightninglabs/pool
batch: add information about noop near miss orders in NextBatchInfo
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 259
- Forks
- 51
- PR merge metrics
- No merged PRs in 30d
Description
Requested from a user on slack. They want to be able to know what the near misses were when an interval passes without a match. This may help some traders know if they're very far off, or if it's only just them on the book. This is effectively equivalent to us giving a periodic price quote every 10 minutes if no batch happens. Giving this extra information to participants effectively "leaks" the "tip" of the order book, but may end up leading to a thicker market as participants are able to make adjustments more easily.
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 by locating NextBatchInfo and the batch interval handling for cases where no match occurs. Determine what near-miss order information is available there and define how it should be exposed to participants without exceeding the requested scope. Done means callers can identify near misses after an unmatched interval.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100