---
tdp: <to be assigned>
title: <TDP title>
status: WIP
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 <foo@bar.com>, FirstName (@GitHubUsername) and GitHubUsername (@GitHubUsername)>
discussions-to: <Create a new thread on https://forum.mstable.org and drop the link here>
created: <date created on, in ISO 8601 (yyyy-mm-dd) format>
requires (*optional): <Proposal number(s)>
---
This is the suggested template for new TDPs. Note that an TDP number will be assigned by an editor. When opening a pull request to submit your TDP, please use an abbreviated title in the filename, tdp-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." Simply describe the outcome the proposed change intends to achieve. This should be non-technical and accessible to a casual community member.
A short (~200 word) description of the proposed change, the abstract should clearly describe the proposed change. This is what will be done if the MIP is implemented, not why it should be done or how it will be done. If the MIP proposes deploying a new contract, write, "we propose to deploy a new contract that will do x".
This is the problem statement. This is the why of the TDP. It should clearly explain why the current state of the protocol is inadequate. It is critical that you explain why the change is needed, if the TDP proposes changing how something is calculated, you must address why the current calculation is innaccurate or wrong. This is not the place to describe how the TDP will address the issue!
The specification should include how and what will change with this proposal.
Copyright and related rights waived via CC0.