From c3588c8984b5f06ef98858b313ff516bf1dfa7c4 Mon Sep 17 00:00:00 2001 From: Abit Date: Fri, 24 Aug 2018 00:03:26 +0200 Subject: [PATCH 01/11] Update workers --- bsip-0042.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/bsip-0042.md b/bsip-0042.md index a33c5db..1f87f7c 100644 --- a/bsip-0042.md +++ b/bsip-0042.md @@ -6,7 +6,7 @@ Created: 2018-08-22 Discussions: https://bitsharestalk.org/index.php?topic=26948.0 https://bitsharestalk.org/index.php?topic=26315.0 - Worker: TBD + Worker: 1.14.118, 1.14.119 # Abstract From e2649be31d1fe6f77d59fe97227a15edb5dd26f8 Mon Sep 17 00:00:00 2001 From: Abit Date: Mon, 27 Aug 2018 19:10:58 +0200 Subject: [PATCH 02/11] Added which worker is pro and which is con --- bsip-0042.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/bsip-0042.md b/bsip-0042.md index 1f87f7c..f9935e5 100644 --- a/bsip-0042.md +++ b/bsip-0042.md @@ -6,7 +6,7 @@ Created: 2018-08-22 Discussions: https://bitsharestalk.org/index.php?topic=26948.0 https://bitsharestalk.org/index.php?topic=26315.0 - Worker: 1.14.118, 1.14.119 + Worker: 1.14.118 (pro), 1.14.119 (con) # Abstract From 377cac0d8d695ee191819cccf89469fa0803ff4a Mon Sep 17 00:00:00 2001 From: Abit Date: Mon, 27 Aug 2018 19:12:14 +0200 Subject: [PATCH 03/11] BSIP 42: added one more discussion link --- bsip-0042.md | 1 + 1 file changed, 1 insertion(+) diff --git a/bsip-0042.md b/bsip-0042.md index f9935e5..6e7369e 100644 --- a/bsip-0042.md +++ b/bsip-0042.md @@ -6,6 +6,7 @@ Created: 2018-08-22 Discussions: https://bitsharestalk.org/index.php?topic=26948.0 https://bitsharestalk.org/index.php?topic=26315.0 + https://bitsharestalk.org/index.php?topic=26966.0 Worker: 1.14.118 (pro), 1.14.119 (con) # Abstract From a650325c85af2456276b941969048d43726aadeb Mon Sep 17 00:00:00 2001 From: Abit Date: Mon, 27 Aug 2018 19:15:07 +0200 Subject: [PATCH 04/11] BSIP 42: updated worker to workers --- bsip-0042.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/bsip-0042.md b/bsip-0042.md index 6e7369e..2b5c2b0 100644 --- a/bsip-0042.md +++ b/bsip-0042.md @@ -7,7 +7,7 @@ Discussions: https://bitsharestalk.org/index.php?topic=26948.0 https://bitsharestalk.org/index.php?topic=26315.0 https://bitsharestalk.org/index.php?topic=26966.0 - Worker: 1.14.118 (pro), 1.14.119 (con) + Workers: 1.14.118 (pro), 1.14.119 (con) # Abstract From c2971903a3b184cf9bf32d8f1d0509be3fa38c0c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Stefan=20Schie=C3=9Fl?= Date: Wed, 29 Aug 2018 08:34:00 +0200 Subject: [PATCH 05/11] Completion of this BSIP from a formal standpoint and inclustion of a clear accepted/rejected state --- bsip-0042.md | 27 +++++++++++++++++++++------ 1 file changed, 21 insertions(+), 6 deletions(-) diff --git a/bsip-0042.md b/bsip-0042.md index 2b5c2b0..8daae1e 100644 --- a/bsip-0042.md +++ b/bsip-0042.md @@ -1,12 +1,9 @@ BSIP: 0042 Title: Adjust price feed to influence trading price of SmartCoins Author: Abit More - Status: Draft + Status: Up for voting Type: Protocol Created: 2018-08-22 - Discussions: https://bitsharestalk.org/index.php?topic=26948.0 - https://bitsharestalk.org/index.php?topic=26315.0 - https://bitsharestalk.org/index.php?topic=26966.0 Workers: 1.14.118 (pro), 1.14.119 (con) # Abstract @@ -14,6 +11,8 @@ We here propose to dynamically adjust price feed in order to influence trading price of smart coins to achieve tighter peg. +This BSIP is constantly evaluated in terms of being accepted or rejected,see the last section *Constant voting evaluation* for details. + # Motivation To get mass adoption, it's better that the SmartCoins can peg to targets more @@ -156,11 +155,27 @@ by bugs. # Discussion -[To be added] +- https://bitsharestalk.org/index.php?topic=26948.0 +- https://bitsharestalk.org/index.php?topic=26315.0 +- https://bitsharestalk.org/index.php?topic=26966.0 # Summary for Shareholders -[To be added] +The peg of SmartCoin to the underlying asset is crucial to create trust for SmartCoin holders, in combination with a force settlement offset that is considered fair. This BSIP seeks to adress the issue of volatility with respect to the peg by allowing the witnesses to implement (within boundaries) their own price feed strategy that is targeted to uphold the peg and provide a fair force settlement offset. + +This is a crucial intrusion into the open market mechanics and is thus not a strict directive to the witnesses, furthermore this BSIP is constantly evaluated, and if it becomes rejected (see the next section), witnesses are bound to return to the former price feed mechanisms. + +# Constant voting evaluation + +This BSIP has a pro and a con worker and has an ever evaluated state of accepted and rejected. + +- **Accepted**: +The pro worker is active in terms of receiving payout from the reserve pool AND its votes surpass the con worker. + +- **Rejected**: +The pro worker is NOT active (is not receiving funds from reserve pool) OR the votes of the con worker surpass the pro worker. If the pro worker expires, this BSIP is also considered rejected. + +The earliest that this worker can become active is 7th September 2018. # Copyright From b2dca448421d5f59df8baa8e0189322814ee0594 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Stefan=20Schie=C3=9Fl?= Date: Wed, 29 Aug 2018 13:09:34 +0200 Subject: [PATCH 06/11] add bitcrabs comment --- bsip-0042.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/bsip-0042.md b/bsip-0042.md index 8daae1e..3852a7a 100644 --- a/bsip-0042.md +++ b/bsip-0042.md @@ -153,6 +153,10 @@ Witnesses should make their own decisions on whether to set a hard limit and how much should it be if need to set one, generally, to reduce impacts caused by bugs. +It will be good to apply the change to bitCNY first, which has much better liquidity +than other smartcoins. After witnesses and community learned enough in the process +it can be also applied to bitUSD. + # Discussion - https://bitsharestalk.org/index.php?topic=26948.0 From 6aa3df5ff19d639271d581725e0c6a4b8fff3d45 Mon Sep 17 00:00:00 2001 From: CM Date: Sun, 7 Oct 2018 14:52:55 +0100 Subject: [PATCH 07/11] Create bsip 45 --- bsip-0045.md | 85 ++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 85 insertions(+) create mode 100644 bsip-0045.md diff --git a/bsip-0045.md b/bsip-0045.md new file mode 100644 index 0000000..b9f6b0d --- /dev/null +++ b/bsip-0045.md @@ -0,0 +1,85 @@ +BSIP: 45 +Title: Introduce 'allow use as bitasset backing collateral' flag/permission to assets +Authors: @grctest +Status: Draft +Type: Protocol +Created: 07/10/2018 +Discussion: https://github.com/bitshares/bsips/issues/80 +Replaces: N/A +Superseded-By: N/A +Worker: N/A + +--- + +# Abstract + +It's currently possible to impose new asset settings through MPA encapsulation without the permission of the backing asset's 'asset owner'. + +This BSIP proposes to introduce a new asset permission/flag which enables the asset owner to enable|prevent MPA encapsulation. + +# Motivation + +By encapsulating an asset (UIA/EBA|MPA) within a new MPA, you can impose new asset settings upon the underlying asset, to the possible detriment of the backing asset's 'asset owner'. + +# Rational + +By providing asset owners this functionality, we can improve asset owner confidence in the finality of their configured asset settings. + +# Specifications + +## Create new 'allow use as backing collateral' flag/permission + +Rather than create a system of inheriting permissions from backing collateral, a new flag/permission for 'allow use as MPA backing collateral' could simply prevent MPA encapsulation entirely at the discretion of the asset owner. + +Existing assets which are currently configured as an bitasset's backing collateral would require this flag to be set default enabled (allowed). This couldn't be changed unless the bitasset reconfigured to an alternative backing collateral - impossible if supply is greater than 0. + +Non applicable assets (PM & twice nested MPA) would prevent the flag from being enabled. + +Existing assets currently not used as backing collateral could be set to disabled by default. + +# Discussion + +## Consequences of MPA encapsulation + +* Removal/Bypassing of market fees (if enabled) +* Re-implementation of confidential transfers (if disabled) +* Evasion of whitelist/blacklist (both user & market lists) +* Preventing the issuer from transfering the asset back to themselves (Can't transfer backing collateral back to yourself) +* Remove backing asset issuer from transfer approval provess. + +## Committee configuration + +Should all smartcoins be allowed as bitasset backing collateral? Given that XCD already does this with bitUSD, I think it's appropriate. That said, not all committee owned bitassets are in a stable state (bitGOLD for example is in global settlement state right now). + +## Enabling the flag grants permisson for all + +Currently you can perform MPA encapsulation without involving the asset owner, this could introduce conflict between the two asset owners. + +If the flag is enabled, that's an indication that the asset owner accepts any bitasset use case - you wouldn't need to seek explicit permission prior to creating experimental bitassets on the BTS DEX. + +If it's disabled, that's a clear indication that the asset owner doesn't want it used as backing collateral. + +## How to configure assets held by null-account? + +It's possible that bitassets may be owned by null-account but remain operational, configuring default disabled would burn the possibility of encapsulation - if these assets exist then if possible should be set to enabled? + +## Proposed UI changes + +This flag could only work as long as no MPA has already selected the asset as its backing collateral; setting this as default disabled (not allowed) for newly created assets in the asset creation form could help prevent the asset being used as backing collateral without the user's knowledge. + +--- + +# Summary for Shareholders + +* Would likely require a hard fork. +* Introduces new asset owner permissions. +* Helps mitigate negative MPA encapsulation consequences, improving gateway regulatory compliance capability? +* Given enabled flags could constitute advanced permission for MPA use case, there may be UIA backed MPA created which would contribute BTS fees to the reserve pool. + +# Copyright + +This document is placed in the public domain, 100% open source & should be considered MIT licensed. + +# See Also + +N/A From c454764eb0579781cca2171818a662ad8c4f4bfb Mon Sep 17 00:00:00 2001 From: CM Date: Sun, 7 Oct 2018 14:53:48 +0100 Subject: [PATCH 08/11] bsip 45 added to readme --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index 2d23357..9ed4b19 100644 --- a/README.md +++ b/README.md @@ -49,3 +49,4 @@ Number | Title | [39](bsip-0039.md) | Automatically approve proposals by the proposer | Fabian Schuh | Protocol | Draft [40](bsip-0040.md) | Custom active permission | Stefan Schießl | Protocol | Draft [42](bsip-0042.md) | Adjust price feed to influence trading price of SmartCoins | Abit More | Protocol | Draft +[45](bsip-0045.md) | Introduce 'allow use as bitasset backing collateral' flag/permission to assets | Customminer | Protocol | Draft From 2a4c2b7e9ab3122e9b0ed008b8ae74cc5f784ace Mon Sep 17 00:00:00 2001 From: CM Date: Sun, 7 Oct 2018 14:54:21 +0100 Subject: [PATCH 09/11] Fixed formatting --- bsip-0045.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/bsip-0045.md b/bsip-0045.md index b9f6b0d..2e3c530 100644 --- a/bsip-0045.md +++ b/bsip-0045.md @@ -1,3 +1,4 @@ +``` BSIP: 45 Title: Introduce 'allow use as bitasset backing collateral' flag/permission to assets Authors: @grctest @@ -8,7 +9,7 @@ Discussion: https://github.com/bitshares/bsips/issues/80 Replaces: N/A Superseded-By: N/A Worker: N/A - +``` --- # Abstract From f03f4ce7ab1d66c6aecd4157aa3fcf25c513d222 Mon Sep 17 00:00:00 2001 From: CM Date: Mon, 8 Oct 2018 16:41:32 +0100 Subject: [PATCH 10/11] Update bsip-0045.md --- bsip-0045.md | 1 - 1 file changed, 1 deletion(-) diff --git a/bsip-0045.md b/bsip-0045.md index 2e3c530..46d76d6 100644 --- a/bsip-0045.md +++ b/bsip-0045.md @@ -72,7 +72,6 @@ This flag could only work as long as no MPA has already selected the asset as it # Summary for Shareholders -* Would likely require a hard fork. * Introduces new asset owner permissions. * Helps mitigate negative MPA encapsulation consequences, improving gateway regulatory compliance capability? * Given enabled flags could constitute advanced permission for MPA use case, there may be UIA backed MPA created which would contribute BTS fees to the reserve pool. From ee9ec4cd45b1294e72fad5424495861a2cbbbc8c Mon Sep 17 00:00:00 2001 From: grcgrc Date: Wed, 10 Oct 2018 13:57:51 +0100 Subject: [PATCH 11/11] License change MIT -> PD --- bsip-0021.md | 2 +- bsip-0022.md | 2 +- bsip-0023.md | 2 +- bsip-0024.md | 2 +- bsip-0045.md | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/bsip-0021.md b/bsip-0021.md index ee77bdf..703f9fb 100644 --- a/bsip-0021.md +++ b/bsip-0021.md @@ -107,7 +107,7 @@ for each asset_holder in coin_age_hashmap { # Copyright -N/A - Consider this BSIP entirely open-source/MIT-licensed, I am not the originator of the concept of 'coin-age' (several proof-of-stake cryptocurrencies make use of coin-age for finding stakable coins). +This document is placed in the public domain. # See Also * [List account balances - Graphene documentation](http://docs.bitshares.org/api/database.html#id8) diff --git a/bsip-0022.md b/bsip-0022.md index 9cfa195..7b149ce 100644 --- a/bsip-0022.md +++ b/bsip-0022.md @@ -119,7 +119,7 @@ Please do raise your concerns, propose improvements and engage in the BSIP creat # Copyright -This document is placed in the public domain, 100% open source & should be considered MIT licensed. +This document is placed in the public domain. # See Also diff --git a/bsip-0023.md b/bsip-0023.md index f71ad1e..5209283 100644 --- a/bsip-0023.md +++ b/bsip-0023.md @@ -651,7 +651,7 @@ The Bitshares starship drops out of hyperspace in planet Bitcoin's orbit, the cr # Copyright -This document is placed in the public domain, 100% open source & should be considered MIT licensed. +This document is placed in the public domain. # See Also diff --git a/bsip-0024.md b/bsip-0024.md index 3169c6c..cd6b76e 100644 --- a/bsip-0024.md +++ b/bsip-0024.md @@ -62,7 +62,7 @@ Would there even be a difference in voting behaviour betwen the two? Perhaps it # Copyright -This document is placed in the public domain, 100% open source & should be considered MIT licensed. +This document is placed in the public domain. # See Also diff --git a/bsip-0045.md b/bsip-0045.md index 46d76d6..b6ffd77 100644 --- a/bsip-0045.md +++ b/bsip-0045.md @@ -78,7 +78,7 @@ This flag could only work as long as no MPA has already selected the asset as it # Copyright -This document is placed in the public domain, 100% open source & should be considered MIT licensed. +This document is placed in the public domain. # See Also