| fip | title | author | description | discussions-to | status | type | created | requires | Withdrawal-reason |
|---|---|---|---|---|---|---|---|---|---|
2 |
FIP’s title |
Firstname1 Lastname1 (fname.lname@email.com), Firstname2 Lastname2 (@GHHandle) |
Short description for this FIP |
<link-to-discussion>, <link-to-vote> |
draft |
Ecosystem |
2022-01-01 |
A short (~200 word) description of the problem being addressed and the solution being proposed.
Critical for FIPs that want to change the Fetch.ai protocol. The motivation should clearly explain why the existing systems, processes, or protocols are inadequate to address the problem that this FIP solves. FIP submissions without sufficient motivation may be rejected outright.
The main in-depth specification of the solution being proposed. The specification should describe the syntax and semantics of any new feature being proposed.
Describe what motivated the design, why particular design decisions were made. Present alternate designs that were considered and related work, e.g. how the feature is supported in other systems. The rationale may also provide evidence of consensus within the community, and should discuss important objections or concerns raised during discussion.