This repository is used to propose and track smart contract standards for the Koinos Blockchian. It's maintained by members of the Koinos community and the processes set forth attempt to be as decentralized as possible. Since this is an ongoing effort, the processes may change over time.
For the case of tokens on Koinos we believe that it's important to give developers an expectation for what format of token contracts would and would not be included on exchanges or NFT marketplaces. If a developer wishes to launch a token contract that is in line with others listed, they would want to follow a standard to be sure that it's compatible with both interfaces and aggregators that use these standards.
It's important to note that some token contracts can and will have extended utility and functionality beyond a standard, but, the standard exists so that all of these types of tokens will have a base layer of expectations for software interacting with them. If there is additional utility that's intended to be duplicated by other tokens then it may be appropriate to propose a new standard that includes this additional functionality.
This is not a place to submit governance proposals for the Koinos Blockchain. While Ethereum uses the EIP process for both chain changes and smart contract standards, KCS is specifically for contract standards. Governance proposals can be a separate process that may require a different type of decentralization. Because of this, this process does not need to be the same as EIP and can even be less extensive. Remember, the point here is to help developers and not hinder them - we want to help provide the information they need and this process is not intended to block them.
Developers can launch any smart contract on the Koinos blockchain whether they follow standards or not. The world (and the blockchain) is your oyster.
Before submitting a standard you should thoroughly discuss it with other Koinos developers either on the Koinos discord or on the Koinos forum.
Once you believe that your idea for a standard is sound and should be proposed, next you should write a draft describing the standard using markdown. Open an issue in this repo with simply the title of the standard. The number issued should be in order of proposals merged. The file name should be in a format like: kcs-1.md which includes the next available number for a standard. Open a pull request that will close your open issue. Public discussions can continue on the GitHub issue whether it's open, merged as Draft or in Final status.
If a standard submitted is filled out in the proper format, it should be merged as a Draft standard.
In order to move to Final status the proposer should be able to point to an actual live implementation of their contract standard in place on Koinos mainnet.
You can find a template here
At a minimum, your standard should include these things:
A header with a Title, the KCS number, Short Description, Author(s), and Status (initially Draft)
Authors can of course be anonymous if they wish.
The body should contain these sections:
This description should be a human readable technical summary of the standard you are proposing.
You should elaborate on what problem you're trying to solve here. Tell the world why you believe it makes sense for your idea to be a standard. What are your use cases?
Provide a complete technical specification for your smart contract standard that includes the minimum criteria for a token contract to be considered using this standard.
You are welcome to include any additional information describing your proposed standard. Some of these could include information about backwards compatibility with previous standards, security considerations, links to reference implementation, and anything else you deem necessary.
Include any references or links to resources you used that your specification may be based on (if any).