← All intelligence

web · May 8, 2026

Canton, Meet Ethereum: ERC-20/CIP-56 Middleware is here

blog.chainsafe.io · Read at source ↗

ChainSafe's ERC-20/CIP-56 Middleware is a high-fidelity translation layer that lets you deploy to Canton using your existing EVM workflows, MetaMask signatures, and infrastructure.

ChainSafe has introduced ERC-20 / CIP-56 Middleware, a translation layer designed to let Ethereum teams deploy assets on Canton Network while retaining existing EVM workflows, MetaMask signatures and infrastructure.

Connecting Ethereum and Canton

The middleware connects Ethereum’s EVM environment with Canton’s privacy-focused architecture. ChainSafe says it addresses a development barrier that previously required Ethereum teams to rewrite their smart contracts entirely in Daml, learn a new virtual machine and spend months preparing to launch.

ChainSafe positions Canton as a privacy ledger for the world’s largest financial institutions, including G-SIBs. It frames the integration as a way to access a $10 trillion tokenization opportunity and settlement against JPM Coin without abandoning an existing EVM stack.

How the middleware works

The system has two main components:

  • API translation layer: Generates the data needed for wallets such as MetaMask to interact as though they were connected to a standard Ethereum node. When a user signs a transaction, it translates the EVM command into a native Canton call in real time.
  • Dedicated relayer server: Provides a custom, white-label bridge for each partner. The server serves as the central authority for that partner’s token, locking assets on Ethereum and mirroring them on Canton as CIP-56 tokens at a 1:1 ratio.

The middleware maps Ethereum’s ERC-20 standard to Canton’s CIP-56 token standard. According to ChainSafe, users can sign Canton transactions in MetaMask without changing wallets and manage Canton-based assets through existing internal signing tools.

Asset onboarding and settlement access

Institutions can use the middleware to lock ERC-20 assets on Ethereum and issue corresponding CIP-56 assets on Canton. Examples cited by ChainSafe include USDC, EURC and tokenized treasuries.

The company also says the middleware enables immediate, native interaction with Canton-based liquidity, including JPMD and DTCC settlement rails.

ChainSafe presents the system as a way to bring assets to Canton using existing EVM logic and expertise, avoiding months of development work and technical debt. It says teams can move assets without changing internal security rules or retraining staff.

Custom integration and infrastructure

ChainSafe is offering the middleware through a bespoke co-development partnership rather than as a standalone software handoff or sign-in dashboard. The company says it has spent eight years building custom decentralized applications and complex Ethereum smart contracts.

As a Canton Network supervalidator, ChainSafe provides a dedicated infrastructure team to support deployment and help partners address the network’s privacy and security requirements. Its stated focus is on technically complex partnerships, with ChainSafe taking responsibility for integration work so partners can concentrate on their products.

Middleware alongside Daml Autopilot

The middleware is also part of a broader development stack that includes Daml Autopilot and specialized AI context supplied through an MCP Server.

Rather than eliminating Daml entirely, ChainSafe says the combined tools help teams write, validate and translate complex Daml logic that conventional EVM wrappers cannot reproduce. The company claims the approach can help developers master Daml at 10 times the speed.

Daml Autopilot includes more than 3,600 compiler-validated patterns, built-in safety checks and continuous integration automation. In the combined workflow, Autopilot supports the creation and validation of custom Daml logic, while the middleware supplies the production connectivity between that logic and external markets.

TopicProduct
ProvenanceLive web scan, matched against the project registry
Scope
Canton Network

Sources & attribution

Published
May 8, 2026 · 11:17 PM UTC
Source
blog.chainsafe.io

Full attribution under the Digital Millennium Copyright Act (DMCA), 17 U.S.C. § 512: this article is an original report by Canton Intelligence that summarizes the reporting of the publishers named above, links to their original work, and reproduces no protected expression beyond brief factual reference and in-line attribution (“according to blog.chainsafe.io”). All rights in the underlying reporting remain with the publishers listed; nothing here implies endorsement by or affiliation with them. Rights holders may request correction, update or removal through the contact address published at infiniti.w3ai.io.