Sweeping an account's default voucher results in an error #91
Labels
No Label
ussd/user-reported
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: grassrootseconomics/sarafu-vise#91
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
activeSym not found in vouchers
If the active voucher balance is 0 or not found in the holdings, it should still show up and USSB be accessible. There are several scenarios that can lead to the voucher not appearing on the holdings endpoint.
As it is, the system reads the holdings endpoint and gets the current active symbol. This is then used to update the current balance.
The
ManageVouchers
handler is set to error as the assumption was a user's holdings will remain intact despite the balance being 0If a voucher can fail to appear on the holdings response, an approach we can use is set the first voucher in the response as the active voucher. Would this be a fix?
The other option is clearing the active voucher data and this will prevent the user from using the send node and swap.
Yes this can work.