- TEP: 0 (don't change)
- title: TEP Template (write title of TEP here)
- status: Draft
- type: Meta / Core / Contract Interface (choose one)
- authors: Vladimir Lebedev (replace)
- created: DD.MM.YYYY (fill with current date)
- replaces: TEP-0
- replaced by: -
Which feature this document introduces? Describe it in one paragraph.
Which problem we address? Why it is important to make a new TEP?
Explain this document in simple language, as if you were teaching it to another developers. Give examples how your feature will work in real life.
This section describes your feature formally. It contains requirements, which must be followed in order to implement your TEP. To keep things formal, it is convenient to follow RFC 2119. You should include following text at the beginning of this section:
The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC 2119.
Why should we not do this?
- Why is this design the best in the space of possible designs?
- What other designs have been considered and what is the rationale for not choosing them?
- What is the impact of not doing this?
Discuss prior art, both the good and the bad, in relation to this proposal. How the problem stated in "Motivation" section was solved in another blockchains? This section encourages you as an author to learn from others' mistakes. Feel free to include links to blogs, books, Durov's whitepapers, etc.
If there are some questions that have to be discussed during review process or to be solved during implementation of this TEP, write it here.
Do you have ideas, which things can be implemented on top of this TEP later? Write possible ideas of new TEPs, which are related to this TEP.