lightninglabs / lightninglabs/lightning-terminal

root_key_ids keep getting added to lnd even when I delete an LND Account

Open
#577 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug macaroons
Dominant language
Go
Stars
595
Forks
135
Avg merge
2d 7h
Merged PRs (30d)
10

Description

root_key_ids keep getting added to lnd even when I delete an LND Account

**Expected behavior**

When deleting an LND Account, lnd should forget about the root_key_id.

**Actual behavior**

After deleting an account with litcli, lnd stills has a root_key_id for it.

**To reproduce**

1. Run `lncli listmacaroonids` and see the initial list of `root_key_ids`.
2. Run `litcli accounts create 150` to create a new LND Account.
3. Run `lncli listmacaroonids` again to see the new list of `root_key_ids`.
4. Run `litcli accounts remove id` to remove the account that was just created.
5. Run `lncli listmacaroonids` again to see the list of `root_key_ids` has not shrunk.

**System information**

Standalone install on ubuntu

Remote lnd

v0.10.1-alpha, self compiled

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the behavior with `litcli accounts create`, `litcli accounts remove`, and `lncli listmacaroonids`, then trace the account-removal entry point and its interaction with lnd. Done means removing an LND Account also removes its root_key_id from the list returned by `lncli listmacaroonids`.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
authentication
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.