LIP # Title Author(s) Created Requires Replaces <TBA> <LIP title> <list of the author’s/authors’ name(s) and/or username(s)>, e.g. Sean (@Seanm99, Sean#4006), Lixir (@Lixiir, Lixir#5587), etc. <date created on, dd-mm-yyyy format> <LIP #> <LIP #> 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 LIP. Technical Abstract A compact description of the technical issue being addressed. This should be a very terse and human-readable version of the specification section. Someone should be able to read only the technical abstract to get the gist of what this specification does. Motivation The motivation section should describe the ’why’ of this LIP. What problem does it solve? Why should we want to implement this proposal? How does the protocol and/or the community benefit from it? What does the pros and cons analysis look like? 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 protocols. Considerations A section that discusses the implications and considerations relevant to the proposed change. This is a place where you can further delve into the (possible) cons, risks and implications of your proposal, and add any additional comments you feel are relevant to the discussion.