You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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
The text was updated successfully, but these errors were encountered: