You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you want to blacklist all runes for some reason you might decide to run the command
lightning-cli blacklistrune 0 99
Or even worse: 0 99999
At first you might exepct that this will blacklist all existing runes between 0 and 99999
When you generate a new rune, this new rune will be on the blacklist. I'm not sure how to resolve this other then creating 99999 blacklisted runes.
What I might have expected is that lightning-cli blacklistrune 0 99 would blacklist all runes from 0 to 11 and then maybe given an error message about being unable to blacklist rune 12.
Creating this issue to propose that blacklistrune should not blacklist a non-existing rune.
An alternative approach to destroying all runes would be to have blacklistrune be able to take the parameter all to destroy all runes.
lightning-cli blacklistrune
The text was updated successfully, but these errors were encountered:
If you want to blacklist all runes for some reason you might decide to run the command
Or even worse: 0 99999
At first you might exepct that this will blacklist all existing runes between 0 and 99999
When you generate a new rune, this new rune will be on the blacklist. I'm not sure how to resolve this other then creating 99999 blacklisted runes.
What I might have expected is that lightning-cli blacklistrune 0 99 would blacklist all runes from 0 to 11 and then maybe given an error message about being unable to blacklist rune 12.
Creating this issue to propose that blacklistrune should not blacklist a non-existing rune.
An alternative approach to destroying all runes would be to have blacklistrune be able to take the parameter all to destroy all runes.
The text was updated successfully, but these errors were encountered: