Added alternate resolution for dependent MPAs
This commit is contained in:
parent
ba68bdbc35
commit
207a44bda1
1 changed files with 12 additions and 1 deletions
13
bsip-0017.md
13
bsip-0017.md
|
@ -124,9 +124,20 @@ revival none of these exist.
|
||||||
However, calls may exist with SWAN as collateral. Suppose that DUCK is an asset
|
However, calls may exist with SWAN as collateral. Suppose that DUCK is an asset
|
||||||
that is backed by SWAN. Calls on DUCK cannot be cancelled.
|
that is backed by SWAN. Calls on DUCK cannot be cancelled.
|
||||||
|
|
||||||
Resolution: Modify DUCK to be backed by BACK instead of SWAN. Modify all DUCK
|
Resolution 1: Modify DUCK to be backed by BACK instead of SWAN. Modify all DUCK
|
||||||
calls accordingly. Remove price feeds from DUCK.
|
calls accordingly. Remove price feeds from DUCK.
|
||||||
|
|
||||||
|
Resolution 2: Force-settle DUCK. This will free up all SWAN used as collateral
|
||||||
|
for DUCK, i. e. the SWAN will be returned into account_balance objects and
|
||||||
|
resolved as described below.
|
||||||
|
|
||||||
|
Note that Resolution 2 is only available for MPAs, not for PMs, because PMs
|
||||||
|
don't have a price feed that can be used to determine the fair value of DUCK vs
|
||||||
|
SWAN in settlements.
|
||||||
|
|
||||||
|
Also note that Resolution 2 is recursive - if an asset SLUG exists that is
|
||||||
|
backed by SWAN, SLUG will have to be settled as well.
|
||||||
|
|
||||||
This solution requires further discussion.
|
This solution requires further discussion.
|
||||||
|
|
||||||
### vesting_balance_object
|
### vesting_balance_object
|
||||||
|
|
Loading…
Reference in a new issue