Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide cancel txn via api #123

Open
baymac opened this issue Dec 6, 2021 · 3 comments
Open

Provide cancel txn via api #123

baymac opened this issue Dec 6, 2021 · 3 comments

Comments

@baymac
Copy link

baymac commented Dec 6, 2021

If user initiates txn signing and returns to the DApp and navigates to a different location DApp would want to cancel the txn via api. Is there a challenge exposing cancel api?

@baymac baymac changed the title Provide cancel via api Provide cancel txn via api Dec 6, 2021
@alessandrokonrad
Copy link
Contributor

You mean cancelling a submitted transaction to the network? That is not possible.

@baymac
Copy link
Author

baymac commented Dec 7, 2021

@alessandrokonrad I mean cancelling transaction before it is signed and submitted. For ref:
Screenshot 2021-12-07 at 1 29 50 PM
Is it possible to cancel the transaction at this stage from the dapp itself?

@rooooooooob
Copy link

@baymac

Is it possible to cancel the transaction at this stage from the dapp itself?

Do you mean like the dApp sends, say, cardano.cancelTx(txIdhere) and then if the tx sign box is open it auto-closes the pop-up? If so, then it's not possible under the CIP-0030 bridge spec.

The dApp would have to just ignore the signed tx returned (or the user cancelled error) returned when the user closes the tx sign box or presses Cancel/Sign in it.

Can you elaborate on your exact use case? Why is the dApp asking the user to sign a TX and then changing its mind before the user can sign it or refuse it?

If you think this is an important use-case then feel free to leave a comment on CIP-0030's initial merge PR to get a discussion started. It didn't come up in any of the discussion before in the spec. Otherwise you'll just have to tell the user they should cancel it or simply ignore whatever output is in it if you no longer want the user to sign it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants