feat(tss): bump go-tss

[swift1337]

zeta-chain/go-tss#54

Summary by CodeRabbit

• Chores
  • Updated a core underlying component to leverage the latest improvements for enhanced stability and performance. This maintenance update ensures a robust and reliable experience without impacting visible functionality.

[coderabbitai]

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

📝 Walkthrough

Walkthrough

The pull request updates the dependency version for github.com/zeta-chain/go-tss in the go.mod file. The version is changed from the stable release v0.4.0 to a pseudo-version v0.4.1-0.20250326144024-94b1d39b9c2d, which includes a timestamp and a commit hash. This suggests the dependency now points to a specific commit with potential modifications or fixes that have not yet been formally released.

Changes

File	Change Summary
go.mod	Updated dependency github.com/zeta-chain/go-tss from v0.4.0 to v0.4.1-0.20250326144024-94b1d39b9c2d, shifting from a stable version to a commit-based pseudo-version.

Possibly related PRs

• feat(tss): bump go-tss #3743: Updates the github.com/zeta-chain/go-tss dependency version, showcasing a related dependency management update.
• chore: use rebased go-tss library #2514: Modifies the import paths for the same go-tss library, indicating a direct connection at the code level.
• chore: bump go tss #2462: Also involves an update to the dependency version in the go.mod file, reflecting a similar dependency management focus.

Suggested Reviewers

• lumtis
• gartnera
• kingpinXD
• ws4charlie

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[gartnera]

Would be great to get #3628 in before we start making serious TSS changes to validate there are no performance regressions with large amounts of withdrawals.