Add Stable chain and logo

[0xh3rman]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @0xh3rman, 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 introduces comprehensive support for the new 'Stable' blockchain. It updates core chain enumerations, integrates its visual assets, and ensures proper compatibility with the WalletCore framework, allowing the application to recognize and interact with the 'Stable' chain.

Highlights

• New Chain Integration: The 'Stable' blockchain has been added to the system's chain definitions, including its Chain and EVMChain enumerations.
• Image Asset Inclusion: A new SVG logo for the 'Stable' chain has been introduced and configured within the asset catalog, ensuring its visual representation in the UI.
• WalletCore Mapping Update: The Stable chain is now correctly mapped to the .ethereum coin type within the WalletCore primitives, enabling proper address handling.
• Subproject Update: The core subproject's commit hash has been updated, indicating a dependency change or update.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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 by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

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 pull request 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 adds support for the 'Stable' chain, including its logo and necessary enum cases and mappings across different packages. The changes are generally well-implemented and follow the existing project structure.

However, there is a critical issue that needs to be addressed: the tests will likely fail because of the new chain. The test testChainToCoinType in Packages/WalletCore/Tests/WalletCorePrimitivesTests/Chain+WalletCorePrimitiveTests.swift iterates through all Chain.allCases but hasn't been updated to handle the new .stable case, which will cause a crash. Please update the tests to cover the new chain.

Additionally, for improved maintainability, I've left a suggestion to sort the list of EVM-compatible chains alphabetically. It would be beneficial to apply similar sorting to other large enum/switch blocks in the future.