---
icip: <to be assigned>
title: <ICIP title>
author: <a list of the author's or authors' name(s) and/or username(s), or name(s) and email(s), e.g. (use with the parentheses or triangular brackets): FirstName LastName (@GitHubUsername), FirstName LastName <[email protected]>, FirstName (@GitHubUsername) and GitHubUsername (@GitHubUsername)>
discussions-to: <email address or github issue address or other discussion channels>
status: Draft
type: <Community>
category <Translation>
created: <date created on (yyyy-mm-dd) format>
requires (*optional): <ICIP number(s)>
replaces (*optional): <ICIP number(s)>
---
This is the suggested template for new ICIPs.
Note that an ICIP number will be assigned by an editor. When opening a pull request to submit your ICIP, please use an abbreviated title in the filename, ICIP-draft_title_abbrev.md.
The title should be 44 characters or less.
"If you can't explain it simply, you don't understand it well enough." Provide a simplified and layman-accessible explanation of the ICIP.
The motivation is critical for ICIPs that want to change the ICON protocol. It should clearly explain why the existing protocol specification is inadequate to address the problem that the ICIP solves. ICIP submissions without sufficient motivation may be rejected outright.
The action plans are critical for ICIPs to be taken seriously and potentially implemented. List out the to-dos without being vague, especially if you need additional resources from the community or the team. Be precise about how you plan to achieve the goal.
Explain the resources required for this proposal, preferably including a timeline projection. Remember we're dedicating our time to your plan, we will need to know your expectations from us.
Copyright and related rights waived via CC0.