Summary of Bug
An address can be passported and tagged by more than one bank member. Coin at the one address cannot be delineated correctly among where the fiat should be held by multiple banks.
Preventing tagging an address that has another kyc tag on it simplifies coin ownership.
Doing so when tagging is asynchronous can result in some error handling that needs to be implemented:
e.g. bank middleware requests the service to tag an address. It validates that no other attributes exist on this address. But by the time it tries to tag this address with this service's attribute or concurrently with another service, multiple tags can be written on the same address.
Need to discuss how to handle this from a bank fiat ledgering perspective.
Version
Always existed
Steps to Reproduce
Multiple instances handling different bank coins and different attribute tagging names can tag the same address.
For Admin Use
Summary of Bug
An address can be passported and tagged by more than one bank member. Coin at the one address cannot be delineated correctly among where the fiat should be held by multiple banks.
Preventing tagging an address that has another kyc tag on it simplifies coin ownership.
Doing so when tagging is asynchronous can result in some error handling that needs to be implemented:
e.g. bank middleware requests the service to tag an address. It validates that no other attributes exist on this address. But by the time it tries to tag this address with this service's attribute or concurrently with another service, multiple tags can be written on the same address.
Need to discuss how to handle this from a bank fiat ledgering perspective.
Version
Always existed
Steps to Reproduce
Multiple instances handling different bank coins and different attribute tagging names can tag the same address.
For Admin Use