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

consider caching TSS signatures to avoid unnecessary TSS keysign sessions #3675

Open
ws4charlie opened this issue Mar 7, 2025 · 0 comments
Assignees
Labels
performance zetaclient Issues related to ZetaClient

Comments

@ws4charlie
Copy link
Contributor

Describe the Issue
Caching TSS signatures can reduce the unnecessary TSS keysign requests. With cached signatures, the signer can bypass the time-consuming TSS keysign to accelerates the outbound processing; it also reduces the burden of concurrent TSS keysign in high traffic hours.

Expected Outcome

Redundant TSS keysign requests should be avoided. For given EVM/Bitcoin CCTX (maybe other chains also applicable, Solana is not applicable), the outbound signature can be cached and reused for transaction broadcasting, as far as the outbound transaction body stays same (e.g., no change in GasPrice, GasLimit).

@ws4charlie ws4charlie self-assigned this Mar 7, 2025
@ws4charlie ws4charlie added performance zetaclient Issues related to ZetaClient labels Mar 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
performance zetaclient Issues related to ZetaClient
Projects
None yet
Development

No branches or pull requests

1 participant