When working on Freeze Accounts in the Registry App, I noticed an unexpected Daml Finance behaviour when you unlock a Semaphore type lock using a different context than you used when you originally locked the account:
https://github.com/digital-asset/daml-finance/pull/1190
In short, the account is unlocked, but the account reference is not updated.
So when you try to accept a transfer into the account, you get an error message regarding a consumed contract.
When working on Freeze Accounts in the Registry App, I noticed an unexpected Daml Finance behaviour when you unlock a Semaphore type lock using a different context than you used when you originally locked the account: https://github.com/digital-asset/daml-finance/pull/1190
In short, the account is unlocked, but the account reference is not updated.
So when you try to accept a transfer into the account, you get an error message regarding a consumed contract.