Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BAIP 1: Decouple BitAssets from Bitshares BSIPS Repository #1

Open
bangzi1001 opened this issue Oct 19, 2019 · 9 comments
Open

BAIP 1: Decouple BitAssets from Bitshares BSIPS Repository #1

bangzi1001 opened this issue Oct 19, 2019 · 9 comments

Comments

@bangzi1001
Copy link
Contributor

BitAssets are owned by committee and price feed are provided by witnesses (New role call Oracles/Price Feeders in future). The main purpose of Bitshares BSIPS Repository allow community propose any changes related to CORE level. But there are some BSIP related to changes of BitAssets parameters and price feed formula which is totally irrelevant to core team, it give unnecessary pressure and workload to core team developers which slow down development work. They are the best C++ programmers in the world but community should not expect them good in economy as well, is totally different field.

Solution:
Any proposal that change BitAssets' parameters or price feed formula should use committee-tools
Repository. If need to assign any number, then can use BAIP (BitAssets Improvement Proposal).

@ryanRfox
Copy link

The purpose of the BSIP repository is to provide the single source for project-wide improvements proposals and discussions, including informational and protocol proposals. The BSIP Review Team is comprised of members from multiple development teams and individuals with the Community and is not limited solely to Core Team members. SmartCoins are a protocol feature and are not controlled by the Committee (other than related fees). BitAssets are a special case SmartCoin owned by the Committee. How the Committee operates those BitAssets is at their discretion alone. In the case of BSIP83, the authors are focused on a protocol change to separate the feed provision of BitAsssets (product) from the block producer role (protocol).

@pmconrad
Copy link

I would suggest to create a separate repository for BSSCIP (or whatever it will be called), instead of using the committee repo.

Also I agree with @ryanRfox that the wording should make it clear that the repo is meant for (committee-owned) BitAssets, not for all SmartCoins.

Changes to SmartCoin logic that must be implemented in the core should still go into the BSIPS repository.

@bangzi1001
Copy link
Contributor Author

The purpose of the BSIP repository is to provide the single source for project-wide improvements proposals and discussions, including informational and protocol proposals. The BSIP Review Team is comprised of members from multiple development teams and individuals with the Community and is not limited solely to Core Team members.

  1. If everything go to single source, how to "Becoming Sufficiently Decentralized"?

SmartCoins are a protocol feature and are not controlled by the Committee (other than related fees). BitAssets are a special case SmartCoin owned by the Committee.

  1. True. The title mention BitAsset. Bascially mean SmartCoin Owned by Committee.

In the case of BSIP83, the authors are focused on a protocol change to separate the feed provision of BitAsssets (product) from the block producer role (protocol).

  1. BSIP83 is irrelevant. Abit found an easier way to do this without hard fork.
    https://bitsharestalk.org/index.php?topic=29702.0

@bangzi1001 bangzi1001 changed the title BSSCIP 1: Decouple BitAssets from Bitshares BSIPS Repository BCSSCIP 1: Decouple BitAssets from Bitshares BSIPS Repository Oct 19, 2019
@bangzi1001
Copy link
Contributor Author

I would suggest to create a separate repository for BSSCIP (or whatever it will be called), instead of using the committee repo.

This repo is good enough unless committee want to create different repo.

Also I agree with @ryanRfox that the wording should make it clear that the repo is meant for (committee-owned) BitAssets, not for all SmartCoins.

Change to BCSSCIP (BitShares Committee's SmartCoins Improvement Proposal)

Changes to SmartCoin logic that must be implemented in the core should still go into the BSIPS repository.

True. Changes in core code is relevant to core team.

@bangzi1001
Copy link
Contributor Author

BitShares may have a brand owner in future which may have conflict with committee and "BCSSCIP" is too long. I suggest change to BAIP (BitAssets Improvement Proposal).

@bangzi1001 bangzi1001 changed the title BCSSCIP 1: Decouple BitAssets from Bitshares BSIPS Repository BAIP 1: Decouple BitAssets from Bitshares BSIPS Repository Oct 21, 2019
@abitmore
Copy link
Member

Created https://github.com/bitshares/baips, moving this issue there.

@abitmore abitmore transferred this issue from bitshares/committee-tools Oct 21, 2019
@abitmore
Copy link
Member

@bangzi1001 please continue here.

@bangzi1001
Copy link
Contributor Author

I am preparing BAIP Purpose and Guidelines which is similar to BSIP-0001. Some wording will change for BitAssets and will add criterias about how BAIP proposals consider approved by BTS Holders.

@bangzi1001
Copy link
Contributor Author

Pull Request Created for:
BAIP 1: BAIP Purpose and Guidelines #2
Update README.md #3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants