- Feature name: (fill me in with a unique ident,
my_awesome_feature) - Start date: (fill me in with today's date, YYYY-MM-DD)
- RFC PR: iotaledger/bee-rfcs#0000
- Bee issue: iotaledger/bee#0000
One paragraph explanation of the feature.
Why are we doing this? What use cases does it support? What is the expected outcome?
- Write a summary of the motivation.
- List all the specific use cases that your proposal is trying to address.
- Where applicable, write from the perspective of the person who will be using the software, for example using the "Job story" format:
When ＿＿＿ , I want to ＿＿＿, so I can ＿＿＿.
- Example 1: When I query a node for a list of transactions, I want to be able to sort them by date, so I can work with the most relevant ones.
- Example 2: When I configure a node, I want to be able to control how much transaction history the node stores, so I can make sure I only store the data I need without incurring additional operational costs.
This is the bulk of the RFC. Explain the design in enough detail for somebody familiar with the IOTA and to understand, and for somebody familiar with Rust to implement. This should get into specifics and corner-cases, and include example of how the feature is used.
Why should we not do this?
- Why is this design the best in the space of possible designs?
- What other designs have been considered and what is the rationale for not choosing them?
- What is the impact of not doing this?
- What parts of the design do you expect to resolve through the RFC process before this gets merged?
- What parts of the design do you expect to resolve through the implementation of this feature before stabilization?
- What related issues do you consider out of scope for this RFC that could be addressed in the future independently of the solution that comes out of this RFC?