lightninglabs / lightninglabs/pool
batch: rejected batches due to funding shims already being registered
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 259
- Forks
- 51
- PR merge metrics
- No merged PRs in 30d
Description
Reported by a user:
```
2020-11-10 04:42:24.230 [INF] FNDG: Registering funding shim for Order(type=Bid, amt=N BTC, nonce=X
2020-11-10 04:42:24.237 [WRN] RPCS: Error preparing channel funding: unable to register funding shim: unable to register funding shim: rpc error: code = Unknown desc = pendingChanID(X) already has intent registered
2020-11-10 04:42:24.238 [INF] RPCS: Sending batch rejection message for batch X with code UNKNOWN and message: unable to register funding shim: unable to register funding shim: rpc error: code = Unknown desc = pendingChanID(X) already has intent registered
```
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 tracing the FNDG funding-shim registration and RPCS batch-rejection paths represented in the log, focusing on the pendingChanID(X) duplicate-intent error. Determine the intended behavior when a funding shim is already registered; done means the reported condition no longer causes an incorrect batch rejection and is covered by a regression check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100