Great. Thank you for the reply. That sounds promising.
To elaborate a little further…
In the event illustrated above it surprised me because I wanted to withdrawal while I was under timepressure.
- How quick would this bypassed withdrawal process be ?
I understand in an event like this I should go true a third party providing a tool to execute the withdrawal. (because I’m not a developer and would need a UI)
The question then raises wether I can trust this party providing the withdrawal service.
Is there a motivation for malicious people to setup a fake withdrawal service ? (to capture PKs for example) Any way Nash could prevent that from happening ? What user input would be minimum required to execute such bypassed withdrawal ?