TOKI Finance, a cross-chain bridge project incubated by Datachain Inc., a subsidiary of Tokyo-listed Speee Inc., connected Unichain to the Inter-Blockchain Communication (IBC) protocol in early December 2025. The deployment made Unichain the fourth EVM-compatible network in TOKI's live roster, joining Ethereum mainnet, BNB Chain, and OP Mainnet. On January 29, 2026, TOKI shut down its bridge entirely, citing a compliance ruling by Speee Inc.'s financial auditor that forced the company to sever ties with the project.

The episode illustrates both the momentum behind IBC's expansion into Ethereum's ecosystem and the fragility of the startups carrying that expansion forward.

What TOKI Built

IBC is a standardised messaging protocol launched by the Cosmos ecosystem in April 2021. It allows separate blockchains to exchange verified data using light clients, which are software components that confirm transaction validity without downloading entire chain histories. The protocol now connects more than 115 chains and processes roughly 35 million cross-chain transactions per year, with 2 million monthly active users and approximately $2.7 billion in 30-day transfer volume. It has recorded zero exploits since launch, a record its developers cite regularly against competitors built on custodial or multisig bridge designs.

The challenge for IBC on Ethereum-based networks is cost. Running light-client verification directly on an EVM chain requires expensive on-chain computation. TOKI addressed this with a component called a Light Client Proxy, or LCP. The LCP runs inside Intel SGX trusted execution environments, which are hardware-secured computing enclaves that can process verification logic off-chain and post attested results on-chain at a fraction of the gas cost.

To reduce the security risk of depending on a single proof system, TOKI layered in multi-party computation across multiple operators, eliminating any single point of failure. Zero-knowledge proofs were planned as a third layer for high-value transfers. The team was explicit about the tradeoffs involved. In published documentation, they acknowledged that SGX has faced documented vulnerabilities in the past (including the ÆPIC Leak, a named exploit targeting Intel's trusted execution environment) and described the multi-prover design as a structural response: "Even if an attacker successfully hacks one proof system, they would need to compromise the other proof systems at the same time."

Why Unichain

Uniswap Labs launched Unichain on February 10, 2025, as an Optimism Superchain Layer 2 built around DeFi liquidity. The network processes about 50 percent of all Uniswap v4 transaction volume, charges fees up to 95 percent lower than Ethereum mainnet, and had accumulated roughly $800 million in total value locked by mid-2025, up from $9 million before a liquidity incentive campaign launched in April of that year. More than 100 DeFi protocols, including Euler and Morpho, have deployed on the network.

TOKI's roadmap described Unichain as a potential settlement layer for cross-chain swaps, where Cosmos-native assets and EVM-native tokens could be exchanged using Uniswap's liquidity pools directly across chains. That use case had not reached production before the service shut down.

The Shutdown

On January 22, 2026, TOKI announced it would cease operations. The transfer and deposit functions were disabled on January 29. The stated cause was a compliance ruling by Speee Inc.'s financial auditor. The auditor concluded that TOKI's offshore entities in Dubai, the Cayman Islands, and the British Virgin Islands could be treated as consolidated subsidiaries under Japanese accounting standards. Auditing those entities was described as unworkable because no established auditing standards for Web3 entities exist under Japanese GAAP. Speee's response was to cut all ties with TOKI rather than absorb the compliance burden.

TOKI's farewell notice stated: "Although the TOKI cross-chain bridge is coming to an end, Datachain will continue to build core interoperability infrastructure for institutions in pursuit of the original vision shared with TOKI."

The smart contracts remain deployed on-chain. Users can still withdraw liquidity directly from the contracts. Developers can access the open-source code, including the ibc-solidity library and the LCP middleware. But the live transfer product is gone.

Regional Stakes

The TOKI shutdown removed what had been a potentially meaningful infrastructure development for users and developers in South Asia and Sub-Saharan Africa. India ranked first globally in crypto adoption in the Chainalysis 2025 index, with Pakistan third and Bangladesh fourteenth. South Asia recorded $300 billion in on-chain transaction volume in 2025, an 80 percent year-over-year increase. Sub-Saharan Africa grew adoption by 52 percent, driven largely by stablecoin remittances and cross-border trade.

In both regions, cost-sensitive retail users stand to benefit from IBC connectivity on low-fee L2 networks as the IBC-on-EVM category continues to develop, though TOKI's specific implementation is no longer available. A route linking Cosmos-native stablecoins to EVM liquidity pools, using a trust-minimised rather than custodial bridge model, is directly relevant to remittance corridors across the India-Gulf-Africa axis, including the broader India-Pakistan-Bangladesh-Gulf corridor that represents one of the world's largest cross-border payment flows. Datachain had previously partnered with Mitsubishi UFJ Trust Bank on cross-chain stablecoin infrastructure using IBC, signalling that institutional appetite for this technology exists in Japan and potentially beyond.

What Continues

The IBC-on-EVM movement did not stop with TOKI. IBC v2, released in March 2025, reduced Ethereum token transfer costs to roughly $0.97 per transaction using zero-knowledge verification. Other projects are pursuing similar IBC-to-EVM connectivity. Datachain has said it will continue building the underlying infrastructure stack for institutional clients, separate from the consumer product it retired.

The Unichain deployment was real, and the technical problem it tackled remains unsolved at scale. The question now is which project picks up where TOKI left off.