​
集成方类型

Eureka 的集成方分为三类：
  1. 链开发者 - 确保你的链与 Eureka 兼容，并能够支持资产在 Eureka 生态中的其他链之间双向桥接。
  2. 资产发行方 - 确保你关心的、通过 Eureka 桥接的资产已在协议中以及 Skip Go API 中完成正确配置，便于应用开发者轻松支持。
  3. 应用开发者 - 确保你的终端用户能够通过 Skip Go API 访问 Eureka 资产和桥接能力。

​
链开发者

如果你正在开发基于 Cosmos 的区块链，解锁 Eureka 资产和桥接能力的最简单方式，就是与 Cosmos Hub 建立 IBC 连接：
  • 需要与 Cosmos Hub 建立 IBC（classic）连接
  • 如果你已经在使用 IBC，则无需链升级
  • 通过批处理机制，用户在 Eureka 已启用域之间进行资产转移时可享受更低成本
  • 链只需维护一个连接到 Cosmos Hub 的 relayer，即可触达整个 Eureka 和 IBC 网络
如果你希望在今年晚些时候直接连接 Eureka 到 Ethereum 或 L2s/Solana，请直接联系 Jeremy 或 Susannah，因为这需要额外的集成工作。

​
资产发行方：将你的代币引入 Ethereum

要通过 Eureka 将资产桥接到 Ethereum，同时保持对代币表示形式的完全控制，你必须部署一个自定义 ERC20 合约。这样可以确保你保留对代币元数据和链上行为的所有权与控制权。 要求：
  1. 自定义 ERC20 实现 部署一个实现我们所需接口标准的 ERC20 合约
  2. CoinGecko 上线 保持 CoinGecko 上线状态，以确保我们的界面中价格和元数据准确无误
为什么要部署自定义 ERC20？
  • 完全的元数据控制权 - 你可以在部署时设置代币名称、符号及其他细节
  • 可验证的所有权 - 可在 Etherscan 上将合约登记到你项目的域名下
  • 永久治理权 - 持续保有对代币核心逻辑不可撤销的控制权
准备开始了吗？ 按照我们的分步自定义 ERC20 集成指南部署你的合约。

​
应用开发者

如果你是应用开发者，希望在自己的 UI 中为用户提供 Eureka 资产访问能力，或在你的协议中使用这些资产，那么通过 Skip Go 集成到 Eureka 生态会非常简单。

​
申请新增资产

如果你希望启用某个新资产（例如 Ethereum 资产）桥接到 Cosmos 或已连接 Eureka 的链，可以加入我们的 Discord并提交支持工单。我们的团队会审核你的请求，并为你提供后续步骤建议。

​
新的 Skip Go 集成方

如果你刚开始接触 Skip Go，最适合快速了解 Skip Go 能力及各种集成方式的资源，是阅读入门指南页面上的跨链开发者平台介绍。
  • 如果你希望以最快、最简单的方式完成集成，可以在几分钟内接入 Widget。如果你希望对提供给用户的 UI 拥有更多控制权，那么 Client Library 会是更合适的选择。
  • 该集成可为用户提供一键式体验，通过一次集成即可在 Eureka 生态及更广泛的网络之间转移资产（依托 Skip Go 的聚合与可组合性引擎）。

​
现有 Skip Go 集成方

确保 Eureka 能在你的 Skip Go 集成中生效，流程与接入其他桥完全一样简单。
要获取包含 Eureka 资产的路由，你必须在 /route 和 /msgs_direct 的 payload 中，将 "eureka" 添加到 experimental_features 数组。例如：如果你没有启用其他实验性功能，则使用 "experimental_features": ["eureka"]；如果你已经启用了其他功能，则使用 "experimental_features": ["cctp", "eureka"]。这一要求适用于所有涉及 Eureka 资产的路由，包括同链交换。如果没有这个标记，路由响应中将不会包含 Eureka 资产。
变更如下：
  1. 预期 /route 和 /msgs_direct 端点会返回 eureka_transfer Operation 类型
  2. 预期 /status 端点会在传输序列中返回 eureka_transfer Transfer 类型
  3. /bridges 端点会返回 eureka bridge 类型
  4. 为了让 Eureka 保持为可选启用项，集成方必须在调用 /route 和 /msgs_direct 时，将 eureka 传入 experimental_features 数组以启用 Eureka 路由
对于不同类型的 Skip Go 集成，这具体意味着：
  1. 如果你使用的是 Widget，请确保版本已升级到 3.5.0 或更高，并在 experimentalFeatures prop 中传入 eureka。
  2. 如果你使用的是 Client Library，请确保版本已升级到 0.16.22 或更高，并在 experimentalFeatures 参数中传入 eureka。
  3. 如果你是直接集成 REST 端点，可以在 API 参考中查看相关类型：Route Operation 和 Lifecycle Tracking Transfer。

​
Types of Integrators

There are three types of integrators of Eureka:
  1. Chain Developers - ensuring that your chain is compatible with Eureka and can facilitate the bridging of assets to and from other chains in the Eureka ecosystem.
  2. Asset Issuers - ensuring the assets you care about being bridged over Eureka are properly set up in the protocol and in the Skip Go API for application developers to support easily.
  3. Application Developers - ensuring your end users have access to Eureka assets and bridging capabilities via the Skip Go API.

​
Chain Developers

If you’re developing a Cosmos-based blockchain, the easiest way to unlock Eureka assets and bridging capabilities is by opening up an IBC connection to the Cosmos Hub:
  • Requires an IBC (classic) connection to the Cosmos Hub
  • No chain upgrade is needed if you’re already using IBC
  • Users benefit from reduced cost of asset transfers between Eureka-enabled domains through batching
  • Chains only need to maintain a single relayer to the Cosmos Hub to reach the entire Eureka and IBC network
If you are interested in a direct Eureka connection to Ethereum or L2s/Solana coming later this year, please reach out to Jeremy or Susannah directly as additional integration work is required.

​
Asset Issuers: Bringing Your Token to Ethereum

To bridge assets to Ethereum through Eureka while maintaining full control over your token’s representation, you must deploy a custom ERC20 contract. This approach ensures you retain ownership of the token’s metadata and on-chain behavior. Requirements:
  1. Custom ERC20 Implementation Deploy an ERC20 contract that implements our required interface standards
  2. CoinGecko Listing Maintain a CoinGecko listing to ensure accurate pricing and metadata in our interfaces
Why deploy a custom ERC20?
  • Full Metadata Control - Set your token’s name, symbol, and other details during deployment
  • Verified Ownership - Register the contract under your project’s domain on Etherscan
  • Permanent Governance - Maintain irrevocable control over the token’s core logic
Ready to get started? Follow our step-by-step Custom ERC20 Integration Guide to deploy your contract.

​
Application Developers

If you’re an application developer looking to give your users access to Eureka assets in your UI or to leverage them within your protocol, integrating into the Eureka ecosystem via Skip Go is super simple!

​
Requesting New Assets

If you want to enable bridging of a new asset (e.g., an Ethereum asset) to Cosmos or Eureka-connected chains, you can submit a request by joining our Discord and opening a support ticket. Our team will review your request and provide guidance on the next steps.

​
New Skip Go Integrator

If you’re brand new to Skip Go, read about our cross-chain developer platform on the Getting Started page will be the best resource for you to get up to speed on the capabilities of Skip Go and the various integration options.
  • For the quickest and easiest integration, you can integrate the Widget in minutes! For more control over the UI you provide your users, the Client Library is the way to go.
  • The integration provides a one-click experience for users to transfer assets across the Eureka ecosystem and beyond in a single integration (via Skip Go’s aggregation and composability engine).

​
Current Skip Go Integrator

Ensuring Eureka works with your Skip Go integration is the same easy process as any other bridge!
To get routes involving Eureka assets, you must add "eureka" to the experimental_features array in your /route and /msgs_direct payload. For example: "experimental_features": ["eureka"] if you have no other experimental features enabled, or "experimental_features": ["cctp", "eureka"] if you already have other features enabled. This requirement applies to all routes involving Eureka assets, including same-chain swaps. Without this flag, Eureka assets will not be included in routing responses.
Changes are as follows:
  1. eureka_transfer Operation type to be expected to be returned from the /route and /msgs_direct endpoints
  2. eureka_transfer Transfer type to be expected to be returned from the /status endpoint in the transfer sequence
  3. eureka bridge type returned from the /bridges endpoint
  4. To keep Eureka opt-in, integrators must pass eureka into the experimental_features array in the /route and /msgs_direct calls to enable Eureka routing
What this looks like for each type of Skip Go integration:
  1. If you’re using the Widget, make sure you’re updated to version 3.5.0 or above and pass in eureka to the experimentalFeatures prop.
  2. If you’re using the Client Library, make sure you’re updated to version 0.16.22 or above and pass in eureka to the experimentalFeatures param.
  3. If you’re integrated directly with the REST endpoints, you can find the relevant types in the API reference for the Route Operation and for the Lifecycle Tracking Transfer.