Currently the behaviour is the txHash just stays in recoil and gets replaced when a new tx happens. We may benefit from having txHash reset back to an empty string after a toast pops up. This way we can trigger the loader in the stepper form for creating a proposal based off the hash going from empty an empty state to a non-empty state. Right now if you make a tx (i.e. swapping yfd into fyfd) a txHash would populate into recoil and the loader wouldn't work based of txHash. This behaviour may be useful for other reasons and would probably be good practice to just reset the txHash so by default it's empty and only populates long enough to create the confrimation toast for the user before going back to blank again.
Currently the behaviour is the txHash just stays in recoil and gets replaced when a new tx happens. We may benefit from having txHash reset back to an empty string after a toast pops up. This way we can trigger the loader in the stepper form for creating a proposal based off the hash going from empty an empty state to a non-empty state. Right now if you make a tx (i.e. swapping yfd into fyfd) a txHash would populate into recoil and the loader wouldn't work based of txHash. This behaviour may be useful for other reasons and would probably be good practice to just reset the txHash so by default it's empty and only populates long enough to create the confrimation toast for the user before going back to blank again.