Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to unblacklist runes #8037

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

rustyrussell
Copy link
Contributor

Fixes: #7017

This migration was introduced in dccbccf (pre 23.08), so the only way they
would need this is if they migration straight from 23.05 to 25.02.  And then
the solution is to migration to a prior one first, but I'll bet good money
we never, ever see this message:

   Commando runes still present?  Migration removed in v25.02: call Rusty!

Signed-off-by: Rusty Russell <[email protected]>
Sure, we have to convert to and from the db set-of-pairs, but that's far simpler
than dealing with the current structure now we want to add code to *remove* from
the blacklist.

Changelog-Changed: JSON-RPC: `blacklistrune` no longer supports of runes over id 100,000,000.
Signed-off-by: Rusty Russell <[email protected]>
@rustyrussell rustyrussell added this to the v25.02 milestone Jan 28, 2025
@rustyrussell rustyrussell requested a review from cdecker as a code owner January 28, 2025 00:27
Signed-off-by: Rusty Russell <[email protected]>
Changelog-Added: JSON-RPC: `blacklistrune` now has an option to un-blacklist (`relist`).
@rustyrussell rustyrussell force-pushed the guilt/unblacklist-runes branch from 1cf9588 to d50aa0d Compare January 28, 2025 03:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

lightning-blacklistrune future (not yet existing) runes
1 participant