title: <BIP 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 <firstname.lastname@example.org>, FirstName (@GitHubUsername) and GitHubUsername (@GitHubUsername)> status: Draft created: <date created on, in ISO 8601 (yyyy-mm-dd) format> requires (*optional): <BIP number(s)> replaces (*optional): <BIP number(s)>
This is the suggested template for new BIPs.
When creating a topic to submit your BIP, please name accordingly, BIP #X draft: title .
This proposal is posted in the #ideas-discussions category for feedback and comments from the community for the coming 5 days. After 5 days of posting this under #ideas-discussions for discussion, it will be posted under #Proposals with whatever comments that will be taken from the discussion, for a minimum of 48 hours and then posted as a formal BIP with a Snapshot to be voted on by the DAO.
Short sum up of contents of BIP
If you explain it simply, you understand it well enough. Provide a simplified and layman-accessible explanation of the BIP.
The motivation is critical for gathering support within the community. Please explain how your BIP is intended to advance B.Protocol DAO and / or B.Protocol, and how it’s aligned with B.Protocol’s values.
The technical specification should describe the syntax and semantics of any new feature. The specification should be detailed enough to allow for it to be reasoned about by participants in the B.Protocol DAO.
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. The rationale may also provide evidence of consensus within the community, and should discuss important objections or concerns raised during discussion.