feat: cross chain swaps gateway client

[Orland0x]

No description provided.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
bob-docs	Ready	Preview	Comment	Dec 8, 2025 5:21pm

[gemini-code-assist]

Summary of Changes

Hello @Orland0x, 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 significantly enhances the SDK's cross-chain capabilities by introducing a dedicated client for cross-chain swaps. It integrates with an external Swaps API to allow for more flexible asset transfers between Bitcoin and EVM chains, including scenarios where assets need to be swapped during the onramp or offramp process. The changes also involve a clear refactoring of LayerZero-specific functionalities to distinguish them from the broader cross-chain swap mechanisms, ensuring a more organized and extensible codebase.

Highlights

• New Cross-Chain Swap Gateway Client: Introduced a new CrossChainSwapGatewayClient class that extends LayerZeroGatewayClient to handle complex cross-chain operations involving swaps, particularly for Bitcoin onramp and offramp scenarios.
• Swaps API Integration: Integrated a new SwapsClient to interact with a dedicated Swaps API, enabling the execution of swap actions as part of cross-chain transactions.
• Refactored LayerZero Functionality: Renamed existing CrossChainSwap related types and functions to EVMToEVMWithLayerZero to more accurately reflect their scope, focusing on EVM-to-EVM transfers via LayerZero.
• New Order Types: Added new GatewayOrderType enumerations: OnrampWithSwaps, OfframpWithSwaps, OnrampWithLayerZero, OfframpWithLayerZero, and EVMToEVMWithLayerZero to categorize the different types of cross-chain transactions.
• Bitcoin Signer Utility: A new ScureBitcoinSigner utility class has been added to facilitate Bitcoin transaction signing from a seed phrase using scure-btc-signer.

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 introduces a CrossChainSwapGatewayClient to handle cross-chain swaps, integrating with both LayerZero and a new Swaps API. The changes include significant refactoring of types for clarity, the addition of a SwapsClient, and a ScureBitcoinSigner for Bitcoin transactions. The overall structure is well-thought-out, but there are a few critical issues to address, particularly concerning hardcoded values in production-sensitive code and incorrect type definitions. My review includes suggestions to improve configurability for different environments and fix incorrect type definitions.