feat:update peer-id dep

[GrapeBaBa]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @GrapeBaBa, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on a critical maintenance update by refreshing a core dependency. The primary goal is to ensure the project utilizes the correct and most up-to-date version of the peer-id library, which is essential for its functionality. This update involves adjusting the source of the dependency and its associated cryptographic fingerprint within the build configuration.

Highlights

• Dependency Update: The peer-id dependency has been updated to point to a new Git repository URL and a different commit hash. Previously, it was sourced from zen-eth/peer-id, and now it points to blockblaz/peer-id.
• Fingerprint Change: The fingerprint for the zmultiformats package within build.zig.zon has been updated. This change is likely a direct consequence of the peer-id dependency update, ensuring consistency in the build system.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in issue comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates the peer-id dependency. While the URL has been correctly updated to a new source and commit, the associated content hash has not been updated. This will cause a hash mismatch and break the build. The hash needs to be re-calculated and updated in build.zig.zon.

[gemini-code-assist]

The URL for the peer_id dependency has been updated, but the content hash (.hash) has not. This will likely cause a build failure due to a hash mismatch. Please update the hash to correspond to the new dependency URL. You can usually get the correct hash by running a build command like zig build and letting the package manager report the expected hash.