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

Option to configure Wallet time to response #1304

Open
coldhardware opened this issue Sep 21, 2022 · 1 comment
Open

Option to configure Wallet time to response #1304

coldhardware opened this issue Sep 21, 2022 · 1 comment
Labels
anchor enhancement New feature or request

Comments

@coldhardware
Copy link

Platform

Desktop (Windows)

Description

I personally use my Ledger Nano S Hardware Wallet within Anchor Desktop.
When i sign big transactions with maybe 100 different Actions in it takes more time then i have before the timeout is reached.
Expiration duration of a transaction is 1 hour, but the time i have to sign the transaction with my hardware wallet is not above 2 minuits, so i always get the error "Wallet did not response in time" after approve and sign all 100 different actions of the transaction. I would like a future option to increase or disable this 2 minuit response time i have to sign a transaction with a hardware wallet. It's really needed for signing bundled transactions with a hardware wallet.

Contact Details

[email protected]

Anything else?

No response

@coldhardware coldhardware added anchor enhancement New feature or request labels Sep 21, 2022
@aaroncox
Copy link
Member

Which app is it that's creating transactions with hundreds of actions?

I ask because it's actually the app that determines the expiration, and the app developer could increase that without intervention from us. We actually don't set the expiration in Anchor, but our SDKs do default to 2 minutes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
anchor enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants