FIP template
description
description
author
FirstName LastName (GitHub)
discussion
status
Idea
category
template
created
yyyy-mm-dd
requires
optional field for dependencies on not finalized FIPs
Please use this template to get started and delete comments before submitting yout PR.
PR naming convention is: fip-title_of_this_fip.mdx
To read more about how to write a FIP, see https://fips.ironfish.network
Abstract
Technical summary. This is meant for others to quickly understand the gist of this proposal
Motivation
Why this proposal is being made. What problem is it solving?
Specification
This should be the bulk of your FIP. What exactly are you proposing, and how can your proposal be implemented?
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 and RFC 8174.
Rationale
This is for explaining why this approach solves the problem and why this is the best approach versus other alternatives.
Backwards Compatibility
This section is only relevant for FIPs that are not backwards compatible. If your FIP is backwards incompatible, you must clearly outline all incompatibilities, their consequences and mitigations
Security and Privacy Considerations
Please describe all security and privacy considerations for your FIP including implementation specific guidance, possible pitfalls, and any relevant discussions around privacy guarantees.
Reference Implementation
An optional section that contains a reference/example implementation, or WIP code.
Copyright
Copyright and related rights waived via CC0.