Closed buhtignew closed 5 months ago
I have already added a check to that as part of the fix for the deck set
command, so only addresses which could be valid (due to the string they use) are accepted by address set
.
Checking the "existence" of addresses is not possible realistically. All blocks would have been checked :) What could be checked is of course if the address is part of the wallet, but that would exclude non-wallet addresses from being labeled, and for example it may make sense to label a gateway address of an AT token, or an exchange partner in the DEX.
I think I'll check if I can fix/catch the error in the address list
command instead in this case.
Edit: I've found out that my validity test was too weak, the "...N2" address was actually invalid. Fixed in commit 117b9ed. Anyway address list
will not anymore throw an error if an invalid address was stored, e.g. by "misusing" config set
.
Can be closed if everything works.
(just a short comment: I'll comment on the issues related to the block locators once I fixed the issue mentioned in issue #86 ).
This works I'm closing.
While I was making tests for the issue #112 I've discovered that it was possible to create a label for a non existent address. Specifically I've run
address set blabla mqnBdCH2cuoSiQWjKoEZHfov77bzrpmtN2
and everything went smoothly except at the next run ofaddress list
I've got an error message:The
address list -d
output was:I was able to solve with
address set blabla -d -n
command.I'd suggest us to perform a check against the existing addresses before the
address set LABEL ADDRESS
command is performed, although it will increase considerable the time needed to run that command.