lightninglabs / lightninglabs/pool

reset/cleanup lnd state when canceled Pool actions occur (open channel etc)

Open
#456 0 comments 0 reactions 0 assignees View on GitHub
batch batch execution optimization
Dominant language
Go
Stars
259
Forks
51
PR merge metrics
No merged PRs in 30d

Description

**Expected behavior**
If Pool backend cancels a batch (one of the set of trader doesn't perform the batch's instructions), Pool should instruct lnd to return to a state where the node is reset to be able to create a new transaction with their pool funds (say, open a Pool channel immediately).

**Actual behavior**
Pool doesn't instruct lnd to reset state/channels when batches are canceled. Channel opens, and spends will persist in their unexecutable form (Due to a cancel batche) until Pool client receives the next batch-creation instructions from Pool server.

Waiting to reset lnd's state until Pool server instructs the client to perform and time critical action (batch creation) is subpary and likely causes delay and dysfunction in subsequent batch creation

**Remediation:**
Reset/cleanup lnd state when canceled Pool actions occur (open channel etc)

Contributor guide

No contributing guide indexed for this repository

Research direction

No files or tests are named. Start by tracing how Pool handles canceled batch actions and communicates with lnd; done means canceled channel opens and spends leave lnd reset so a new Pool transaction can be created immediately.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.