ContextDescribe / explain why we should do this: motivations, context or other info. Keep it brief and simple - PM
Massa network will have a new feature of minimal operation fees.
User flowDescribe the user flow using user stories so the end result is super clear - PM
User will see in massa station wallet the fees that will allow the operation to get accepted by the node and included in a block.
Concerns:
the dapp may show to user that there no fee, but the sign prompt will show fees. Maybe we can add a tooltip saying that user is connected to a node that accept only operations with at leat 0.01 MAS fee?
the fee field is editable in the sign prompt, should we allow user to set a value bellow the minimal fee of the node?
How toList the step-by-step to get it do if needed - PM
[ ] Massa station, when connecting to a node, fetch the amount of minimal fees
[ ] Massa station, when receiving an execute function request, will modify the operation to put at least the minimal of the connected node
[ ] UX: cc @SlnPons @LucasF243 see the too concerns above ;)
Technical detailsGive the technical insights so anyone in the team can tackle the tasks - Dev
the logic will be in sendoperation::Call
QA testingDoes this task require some QA tests ?If yes, explain how to validate it
Context Describe / explain why we should do this: motivations, context or other info. Keep it brief and simple - PM
Massa network will have a new feature of minimal operation fees.
User flow Describe the user flow using user stories so the end result is super clear - PM
User will see in massa station wallet the fees that will allow the operation to get accepted by the node and included in a block.
Concerns:
How to List the step-by-step to get it do if needed - PM
Technical details Give the technical insights so anyone in the team can tackle the tasks - Dev
the logic will be in sendoperation::Call
QA testing Does this task require some QA tests ? If yes, explain how to validate it