computable-finance / cips Goto Github PK

• Need to submit PR to https://github.com/snapshot-labs/snapshot-spaces
• Use the standard forma (like https://snapshot.page/#/yearn)

Author: [email protected]

Something happened and now 1inch.exchange can't conduct routing of the price and liquidity from CoFix. I've tried it today for ETH-USDT and ETH-HBTC.
Please forward this to dev team, I think this is important to resolve

What is the COFI team currently working on and what can we expect in the near future? More trading pairs? Some metrics on token balances in pool? Deploy some of the ETH savings fund to buy/burn COFI?

I guess every community member will be very grateful if CoFix team shares the roadmap.

Thanks in advance!

cip:
title:取消分红机制的提案(Proposal to cancel the dividend mechanism)
author:cofixfans([email protected])
vote:
discussion: https://github.com/Computable-Finance/CIPs/issues
status:Drafted
created:2021-01-15
取消分红机制的提案
由于系统价值一直在流失，导致代币价格下跌，建议取消现有的分红机制。
Abstract(摘要）
取消20%的分红，将手续费收入全部用于回购。

Proposal to cancel the dividend mechanism
As the system has been losing value and causing token prices to fall, it is recommended that the existing dividend mechanism be eliminated.
Abstract
Eliminate the 20% dividend and use all fee income for repurchase.

cip:
title:CoFiX Fee Revenue Allocation Program（CoFiX手续费收入分配方案）
author:cofixfans([email protected])
vote:
discussion: https://github.com/Computable-Finance/CIPs/issues
status:PROPOSED
created:2020-11-21
CoFiX手续费收入分配方案
发起背景
当前手续费收入资金的分配方案，导致储蓄池的沉淀资金过多，每一笔手续费收入，都应该发挥他应有的作用，保障CoFi持有者的权益，所以发起此提案。
Abstract(摘要）
将手续费收入的资金分成三部分：1，锁仓分红。2，回购销毁。3，基金会。在回购销毁启动之前，将回购销毁资金用于锁仓分红。
Motivation(动机）
当前分配方案，未充分发挥手续费收入的作用。1，由于分红比例过低，并未充分体现CoFi代币应有的价值，导致做市商及现有持币者的信心不足。2，由于CoFi无限增发的特性，可以使用回购销毁来抵御通胀，保障现在及未来持币者的权益。3，分配部分资金给予CoFiX基金会，进行合约多方审计，社区推广，CoFiX做市插件，保险等等项目，为CoFiX的发展，保驾护航。
分配方案
方案1：分红50%,回购销毁(30%),基金会(20%)。
方案2：分红40%,回购销毁(40%),基金会(20%)。
为了充分利用好每一笔资金，在回购销毁启动之前，回购销毁的资金全部用于分红。
未来展望
以上分配方案的应用，可以使手续费收入的资金利用率，大幅提升，发挥他应有的作用。分红及回购，对稳定CoFi价格，能起到非常积极的作用。CoFi的价格稳定，对交易量及做市商，都是一种激励。基金会的运营，可以为CoFiX未来的发展，添砖加瓦，增加CoFi持有者的信心。

CoFiX Fee Revenue Allocation Program
Simple Summary
The current allocation of fee revenue funds leads to excessive deposits in savings pools.Every fee revenue should play its proper role in protecting the rights of CoFi owners，so this proposal is initiated.
Abstract
Divide the funds from the fee revenue into three parts: 1) Lock-up dividends, 2) Repo Destroy, and 3) Foundation. Use the repo destroy funds for lock-up dividends before the repo and destroy are initiated.
Motivation
The current allocation plan does not fully utilize the fee revenue.1 The low dividend payout ratio does not fully reflect the value of CoFi tokens, resulting in a lack of confidence among market makers and existing coin holders.2 Due to CoFi's unlimited issuance, repo destroys can be used to counter inflation and protect the interests of current and future coin holders.3 Part of the funds should be allocated to the CoFiX Foundation. We conduct contract audits, community outreach, CoFiX market making plug-ins, insurance, and other programs to protect the development of CoFiX.
Allocation Scheme
Scenario 1: 50% dividend, repo and destroy (30%), foundation (20%).
Scenario 2: 40% dividend, repo and destroy (40%), foundation (20%).
In order to make the best use of each of these funds, all of the funds from the repo destroy were used to pay dividends before the repo destroy was initiated.
Future Outlook
The application of the above allocation scheme can greatly improve the utilization rate of fee revenue and play its proper role. Dividends and repos can play a very positive role in stabilizing the price of CoFi, which is an incentive for trading volume and market makers. The operation of the foundation can help the future development of CoFiX and increase the confidence of CoFi holders.

cip:
title:CoFiX手续费收入分配方案1号修正案
author:cofixfans([email protected])
vote:
discussion: https://github.com/Computable-Finance/CIPs/issues
status:Drafted
created:2020-11-19
CoFiX手续费收入分配方案
发起背景
当前手续费收入资金的分配方案，导致储蓄池的沉淀资金过多，每一笔手续费收入，都应该发挥他应有的作用，保障CoFi持有者的权益，所以发起此提案。
Abstract(摘要）
将手续费收入的资金分成三部分：1，锁仓分红。2，回购销毁。3，储备资金。在回购销毁启动之前，将回购销毁资金用于锁仓分红。
Motivation(动机）
当前分配方案，未充分发挥手续费收入的作用。1，提高分红比例，将CoFiX系统产生的价值及时赋予CoFi，让CoFi代币的价值得到充分体现。同时也能提振做市的信心。2，由于CoFi无限增发的特性，可以使用回购销毁来抵御通胀，保障现在及未来持币者的权益。3，储备20%的资金以供未来使用，具体如何使用，由持币者决定。
分配方案
方案1：分红50%,回购销毁(30%),储备资金(20%)。
方案2：分红40%,回购销毁(40%),储备资金(20%)。
为了充分利用好每一笔资金，在回购销毁启动之前，回购销毁的资金全部用于分红。
为什么要将回购销毁的资金暂时用于分红，而不储备起来以供未来回购销毁之用？
1，回购销毁的时间及方案暂未确定。（这需要花费大量的时间来讨论与实施）
2，现时CoFi流动性不足，价格失真，若此时启动回购，资金浪费会非常严重。
3，如果将资金储备起来，那么这笔资金将失去流动性，不能为CoFi持有者带来利益。
4，当储备的资金量越来越大的时候，不排除未来出现大户联盟，左右这笔资金的使用。
5，名义上，现在储备池的资金是属于CoFi持币者，但是，这笔资金如果一直未被使用，那么这实际上只是一张空头支票。
未来展望
以上分配方案的应用，可以使手续费收入的资金利用率，大幅提升，发挥他应有的作用。分红及回购，对稳定CoFi价格，能起到非常积极的作用。CoFi的价格稳定，对交易量及做市商，都是一种激励。储备资金，可以为CoFiX未来的发展，添砖加瓦，增加CoFi持有者的信心。

CoFiX Fee Revenue Allocation Program Amendment 1
Simple Summary
The current allocation of fee revenue funds leads to excessive deposits in savings pools.Every fee revenue should play its proper role in protecting the rights of CoFi owners，so this proposal is initiated.
Abstract
Divide the funds from the fee revenue into three parts: 1) Lock-up dividends, 2) Repo Destroy, and 3) Reserve Funds. Use the repo destroy funds for lock-up dividends before the repo and destroy are initiated.
Motivation
The current allocation plan does not fully play the role of fee revenue.1, increase the dividend ratio, give the value generated by the CoFiX system to CoFi in time, so that the value of CoFi tokens can be fully reflected. 2, Due to the unlimited issuance of CoFi, buyback and destruction can be used to resist inflation and protect the rights and interests of current and future coin holders.3, 20% of the funds can be reserved for future use, the specific use of which is decided by the coin holders.
Allocation Scheme
Scenario 1: 50% dividend, repo and destroy (30%), Reserve Funds(20%).
Scenario 2: 40% dividend, repo and destroy (40%), Reserve Funds (20%).
In order to make the best use of each of these funds, all of the funds from the repo destroy were used to pay dividends before the repo destroy was initiated.
Why use the funds from the repo and destroy to pay dividends temporarily, rather than reserving them for future repo and destroy?

1. The timing of the repo and destroy program has not been determined yet. (This will take a lot of time to discuss and implement)
   2, CoFi is illiquid and the price is distorted at the moment, and if a repo is initiated at this time, it will be a serious waste of funds.
   3, if the funds are stored up, the funds will be illiquid and will not benefit the CoFi holders.
   4, When the amount of funds in reserve becomes larger and larger, we can't rule out the possibility of a coalition of large investors influencing the use of the funds in the future.
2. Nominally, the funds in the reserve pool now belong to the CoFi holders, but if the funds remain unused, then it is actually just a empty promise.
   Future Outlook
   The application of the above allocation scheme can greatly improve the utilization rate of fee revenue and play its proper role. Dividends and repos can play a very positive role in stabilizing the price of CoFi, which is an incentive for trading volume and market makers. The operation of the Reserve Funds can help the future development of CoFiX and increase the confidence of CoFi holders.

Snapshot link

What is an CIP?

CIP stands for CoFix Improvement Proposal, it has been adapted from the SIP (Synthetix Improvement Proposal). The purpose of this process is to ensure changes to CoFix are transparent and well governed. An CIP is a design document providing information to the CoFix community about a proposed change to the system. The author is responsible for building consensus within the community and documenting dissenting opinions.

CIP Rationale

We intend CIPs to be the primary mechanisms for proposing new features, collecting community input on an issue, and for documenting the design decisions for changes to CoFix. Because they are maintained as text files in a versioned repository, their revision history is the historical record of the feature proposal.

It is highly recommended that a single CIP contain a single key proposal or new idea. The more focused the CIP, the more successful it is likely to be.

An CIP must meet certain minimum criteria. It must be a clear and complete description of the proposed enhancement. The enhancement must represent a net improvement.

CIP Work Flow

Parties involved in the process are the author, the CIP editors, and the CoFix community.

⚠️ Before you begin, vet your idea, this will save you time. Ask the CoFix community first if an idea is original to avoid wasting time on something that will be rejected based on prior research (searching the Internet does not always do the trick). It also helps to make sure the idea is applicable to the entire community and not just the author. Just because an idea sounds good to the author does not mean it will have the intend effect. The appropriate public forum to gauge interest around your CIP is [the unofficial CoFix Discord] or [the unofficial CoFix Telegram].

Your role as the champion is to write the CIP using the style and format described below, shepherd the discussions in the appropriate forums, and build community consensus around the idea. Following is the process that a successful CIP will move along:

Drafted -> Proposed -> Approved -> Implemented
         ^                     
         +----> Rejected       
         |         
         v
       Deferred

Each status change is requested by the CIP author and reviewed by the CIP editors. Use a pull request to update the status. Please include a link to where people should continue discussing your CIP. The CIP editors will process these requests as per the conditions below.

• Drafted -- Once the champion has asked the CoFix community whether an idea has any chance of support, they will write a draft CIP as a pull request and github issue. Consider including an implementation if this will aid people in studying the CIP.

• Proposed If agreeable, CIP editor will assign the CIP a number (generally the issue or PR number related to the CIP) and merge your pull request. The CIP editor will not unreasonably deny an CIP. Proposed CIPs will be discussed on snapshots. If there is a reasonable level of consensus around the change on the governance call the change will be moved to approved. If the change is contentious a vote of token holders may be held to resolve the issue or approval may be delayed until consensus is reached.

• Approved -- This CIP has passed community governance and is now being prioritised for development.

• Implemented -- This CIP has been implemented and deployed to mainnet.

• Rejected -- This CIP has failed to reach community consensus.

• Deferred -- This CIP is pending another CIP/some other change that should be bundled with it together.

What belongs in a successful CIP?

Each CIP should have the following parts:

• Preamble - RFC 822 style headers containing metadata about the CIP, including the CIP number, a short descriptive title (limited to a maximum of 44 characters), and the author details.
• Simple Summary - “If you can’t explain it simply, you don’t understand it well enough.” Provide a simplified and layman-accessible explanation of the CIP.
• Abstract - a short (~200 word) description of the technical issue being addressed.
• Motivation (*optional) - The motivation is critical for CIPs that want to change CoFix. It should clearly explain why the existing specification is inadequate to address the problem that the CIP solves. CIP submissions without sufficient motivation may be rejected outright.
• Specification - The technical specification should describe the syntax and semantics of any new feature.
• Rationale - The rationale fleshes out the specification by describing what motivated the design and why particular design decisions were made. It should describe alternate designs that were considered and related work, e.g. how the feature is supported in other languages. The rationale may also provide evidence of consensus within the community, and should discuss important objections or concerns raised during discussion.
• Test Cases - Test cases may be added during the implementation phase but are required before implementation.
• Copyright Waiver - All CIPs must be in the public domain. See the bottom of this CIP for an example copyright waiver.

CIP Formats and Templates

CIPs should be written in markdown format.
Image files should be included in a subdirectory of the assets folder for that CIP as follows: assets/cip-X (for cip X). When linking to an image in the CIP, use relative links such as ../assets/cip-X/image.png.

CIP Header Preamble

Each CIP must begin with an RFC 822 style header preamble, preceded and followed by three hyphens (---). This header is also termed "front matter" by Jekyll. The headers must appear in the following order. Headers marked with "*" are optional and are described below. All other headers are required.

cip: (this is determined by the CIP editor)

title:

author: <a list of the author's or authors' name(s) and/or username(s), or name(s) and email(s). Details are below.>

vote: <a url pointing to the voting at https://snapshot.page/#/cofix/>

* discussion: <a url pointing to the official discussion thread at https://github.com/Computable-Finance/CIPs/issues >

status: < Drafted | PROPOSED | APPROVED | IMPLEMENTED | Rejected | Defered >

created:

* updated:

* requires: <CIP number(s)>

* resolution: <a url pointing to the resolution of this CIP>

Headers that permit lists must separate elements with commas.

Headers requiring dates will always do so in the format of ISO 8601 (yyyy-mm-dd).

author header

The author header optionally lists the names, email addresses or usernames of the authors/owners of the CIP. Those who prefer anonymity may use a username only, or a first name and a username. The format of the author header value must be:

Random J. User <[email protected]>

or

Random J. User (@username)

if the email address or GitHub username is included, and

Random J. User

if the email address is not given.

discussion header

While an CIP is in Drafted or Proposed status, a discussion header will indicate the URL at CoFix github where the CIP is being discussed.

vote header

While an CIP is in Drafted or Proposed status, a vote header will indicate the URL at CoFix snapshot where the CIP is being voted.

created header

The created header records the date that the CIP was assigned a number. Both headers should be in yyyy-mm-dd format, e.g. 2001-08-14.

updated header

The updated header records the date(s) when the CIP was updated with "substantial" changes. This header is only valid for CIPs of Draft and Active status.

requires header

CIPs may have a requires header, indicating the CIP numbers that this CIP depends on.

Auxiliary Files

CIPs may include auxiliary files such as diagrams. Such files must be named CIP-XXXX-Y.ext, where “XXXX” is the CIP number, “Y” is a serial number (starting at 1), and “ext” is replaced by the actual file extension (e.g. “png”).

CIP Editors

The current CIP editors are:

* Victor Zhang (@zhangzhongnan928)

CIP Editor Responsibilities

For each new CIP that comes in, an editor does the following:

• Read the CIP to check if it is ready: sound and complete. The ideas must make technical sense, even if they don't seem likely to get to final status.
• The title should accurately describe the content.
• Check the CIP for language (spelling, grammar, sentence structure, etc.), markup (Github flavored Markdown), code style

If the CIP isn't ready, the editor will send it back to the author for revision, with specific instructions.

Once the CIP is ready for the repository, the CIP editor will:

• Assign an CIP number (generally the PR number or, if preferred by the author, the Issue # if there was discussion in the Issues section of this repository about this CIP)

• Merge the corresponding pull request

• Send a message back to the CIP author with the next step.

The CIP editors monitor CIP changes, and correct any structure, grammar, spelling, or markup mistakes we see.

The editors don't pass judgment on CIPs. We merely do the administrative & editorial part.

History

The CIP document was derived heavily from the SIP Synthetix Improvement Proposal document in many places text was simply copied and modified. Any comments about the CIP document should be directed to the CIP editors.

Bibliography

Copyright

Copyright and related rights waived via CC0.