原生 IBC 安全模型

Eureka 实现了完整的 IBC 轻客户端安全模型,为跨链交易提供信任最小化的验证:
  • 轻客户端验证:每条链都会运行对方链的轻客户端,从而能够对状态转换进行密码学验证。在以太坊侧,我们使用 Succinct 的 SP1 零知识证明来实现高效验证
  • 无多签依赖:不同于许多桥接方案,Eureka 的安全性不依赖受信任的验证者集合或多签
  • 无许可访问:任何人都可以连接到 IBC 网络和以太坊,只要你的链实现了 IBC,无论是经典版还是 v2
  • 基础设施开销极低,且无持续成本:从 Cosmos Hub 与以太坊到你的链之间的中继、证明和路由由智能中继器处理,费用由终端用户承担。你只需维护一条到 Cosmos Hub 的 IBC 经典连接

性能与成本效率

  • Gas 消耗已优化:通过 Cosmos Hub 从以太坊转账到你的链,快速模式约为 $5,标准转账低于 $1
  • 快速终局性:无论源链的终局时间如何,资产都可以在数秒内到达目标链

原生资产表示

  • Bank 模块集成:收到的资产会直接以原生代币的形式存在于 bank 模块中
  • 无包装代币:资产不会被包装,也不会附加桥专属标识符后缀(例如,不会出现 ETH.axl)
  • ERC20 兼容性:未来这些资产可以轻松表示为 ERC20,而无需承担复杂的转换成本

Eureka 的工作原理

Eureka 通过以下组合连接各条区块链:
  1. IBC Protocol v2:定义数据包格式和验证逻辑的标准化通信层
  2. Solidity 实现:部署在以太坊和 EVM 链上的智能合约,用于实现 IBC 协议(其他智能合约链即将支持)
  3. 轻客户端:每条链都会运行对方链的轻客户端以验证状态转换。在以太坊上,这通过 SP1 零知识证明实现高 Gas 效率的验证
  4. 中继器:IBC v2 使用中继器在链之间发送消息。我们会为你提供支持并运营 Eureka 的中继基础设施。
IBC 协议通过密码学验证而非受信任的第三方,保证目标链上接收到的数据包 必然来自源链。

许可型中继

IBC Eureka 的初始发布将使用许可型中继器,以提供额外的安全与保障。 IBC 轻客户端的使用方式与 IBC 无许可模式下完全相同;这里的许可机制仅意味着系统活性 依赖于这组被许可的中继器。许可限制将在近期移除。

架构概览


Native IBC Security Model

Eureka implements the full IBC light client security model, providing trust-minimized verification of cross-chain transactions:
  • Light Client Verification: Each chain runs a light client of the other chain, enabling cryptographic verification of state transitions. On the Ethereum side we use Succinct’s SP1 zero-knowledge proofs for efficient verification
  • No Multisig Dependencies: Unlike many bridge solutions, Eureka doesn’t rely on trusted validator sets or multisigs for security
  • Permissionless Access: Anyone can connect to the IBC network and Ethereum, as long as your chain has an IBC implementation, classic or v2
  • Minimal Infrastructure Overhead, no ongoing costs: Relaying, proving and routing between the Cosmos Hub and Ethereum onto your chain is handled by the smart relayer, paid for by end users. Simply maintain an IBC classic connection to the Cosmos Hub

Performance and Cost Efficiency

  • Optimized Gas Consumption: Transfer from Ethereum to your chain, via Cosmos Hub for approximately $5 using fast mode and less than $1 for standard transfers
  • Fast Finality: Assets arrive on destination chains in seconds, regardless of source chain finality times

Native Asset Representation

  • Bank Module Integration: Received assets live directly in the bank module as native tokens
  • No Wrapped Tokens: Assets are not wrapped or suffixed with bridge-specific identifiers (e.g., no ETH.axl)
  • ERC20 Compatibility: Assets can be easily represented as ERC20s in the future without conversion complexity

How Eureka Works

Eureka connects blockchains through a combination of:
  1. IBC Protocol v2: The standardized communication layer that defines packet formats and verification logic
  2. Solidity Implementation: Smart contracts deployed on Ethereum and EVM chains that implement the IBC protocol (Other smart contract chains to come)
  3. Light Clients: Each chain runs a light client of the other chain to verify state transitions. On Ethereum, this uses SP1 zero-knowledge proofs for gas-efficient verification
  4. Relayers: IBC v2 uses relayers to send messages between chains. We facilitate and operate the relaying infrastructure for Eureka for you.
The IBC protocol guarantees that a packet delivered on the destination chain was definitely sent from the source chain, using cryptographic verification rather than trusted third parties.

Permissioned Relay

The initial rollout of IBC Eureka will use permissioned relayers for additional safety and security guarantees. The IBC light clients will be used in the same way as when IBC is permissionless, the permissioning only means that liveness is dependent on the permissioned relay set. Permissioning will be removed in the near future.

Architecture Overview