If the user wants to stop their baker registration, they can do so with the Stop baker flow. This flow can be found in the drop down on the baker status page, if the baker isn't currently in a cool down due to decreased stake amount, or an already finalized Stop baker submission.
The flow can be found in Figma in the box called Stop baker. The flow in itself is relatively simple:
It starts with a carousel explaining the cool down and that the node doesn't stop, it just stops baking when the Stop baker submission takes effect.
The user doesn't have to input anything for this transaction, so they will just be taken straight to the pre-submission overview, that states which account will stop being a baker.
After submitting the transaction, the transaction ticket will of course display the transaction hash. After pressing "Finish", the user will be notified that the cool down will start after the transaction has finalized. Pressing "Okay" on the notification will take the user to the baker status page.
Notes:
From a technical standpoint the "Stop baker" transaction is still just the ConfigureBaker transaction. The way to close the baker is to just submit 0 as the value, but from the users perspective that might not make sense, so we just state that the baker will be stopped in the transaction ticket.
Task description
If the user wants to stop their baker registration, they can do so with the Stop baker flow. This flow can be found in the drop down on the baker status page, if the baker isn't currently in a cool down due to decreased stake amount, or an already finalized Stop baker submission.
The flow can be found in Figma in the box called Stop baker. The flow in itself is relatively simple:
Notes: