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
We are not excluding terminated wallets when searching by the SDK for the wallets that could process the redemption request. Terminated wallets are removed from the contract registry, but on the current code they could still be chosen for redemption, resulting in the following error: Wallet with the given ID has not been registered.
The text was updated successfully, but these errors were encountered:
Closes: #812
The current logic used to fetch wallet public keys was throwing errors
while used for `Closed` or `Terminated` wallets. This is because the
`WalletRegistry` contract does no longer hold the public key for such
wallets. In effect, the exception was propagated upstream and caused
problems while searching wallets for redemption.
Here we fix that problem by making the public key field optional and
keeping it undefined for closed/terminated wallets. That way, the client
code can detect this fact and omit closed/terminated wallets during
processing.
We are not excluding terminated wallets when searching by the SDK for the wallets that could process the redemption request. Terminated wallets are removed from the contract registry, but on the current code they could still be chosen for redemption, resulting in the following error:
Wallet with the given ID has not been registered
.The text was updated successfully, but these errors were encountered: