Yen Transfers That Hide "Who Paid Whom": zJPYC and the Design of "Compliance-Friendly Privacy"

[Date] June 11, 2026

[Title] Yen Transfers That Hide "Who Paid Whom": zJPYC and the Design of "Compliance-Friendly Privacy"

[Summary] The privacy-transfer protocol "zERC20" has launched "zJPYC," a confidential-transfer token for the Japanese-yen stablecoin "JPYC," on Polygon. It addresses a key weakness of public blockchains—where every transaction is visible to anyone—by hiding the link between sender and recipient. Yet the transfer amount remains verifiable, a design that seeks to balance regulatory compliance with practical usability.

[Main Body]

What Was Announced

zERC20 is a protocol that aims to add privacy features to Ethereum's "ERC20" token standard, built by core developers of the L2 project "INTMAX." On June 11, it launched "zJPYC," exchangeable 1:1 with JPYC, on Polygon. JPYC supports four chains—Ethereum, Polygon, Avalanche, and Kaia—but circulation is largest on Polygon (about 324 million JPYC as of June 11), and zJPYC is offered there. Notably, it requires no dedicated wallet or app and works with common wallets such as MetaMask.

How It Works: Why "Who Paid Whom" Can Be Hidden

The flow is simple. First, you "wrap" Polygon JPYC into an equal amount of zJPYC. Then you send it via zERC20, and the recipient converts zJPYC back to JPYC ("unwrap"). The privacy arises in that transfer process.

Technically, the sender first sends tokens to a "burn address," and the recipient withdraws the same amount using a Zero-Knowledge Proof (ZKP—a technique that proves "correctness" without revealing the contents). Because the receiving addresses are generated as single-use, one-time addresses, the on-chain link between the sender's and recipient's addresses is severed. Crucially, the transfer and withdrawal amounts themselves remain verifiable. In other words, it creates a state where "the amount is visible, but who transacted with whom is not."

Why Private Transfers Are Needed

The fundamental weakness of public blockchains is that every transaction is visible to anyone. A third party can trace an address's balance, full transaction history, and even its counterparties. For real-world uses—payments, payroll, supplier payments, corporate treasury—this is a serious obstacle. If salaries or payments to suppliers were laid bare to competitors and the public, businesses simply could not use it. zERC20 lists use cases such as payments, recurring payments, salaries, creator rewards, and corporate fund management precisely to solve this "everything-is-visible" problem.

The Philosophy of "Compliance-Friendly Privacy"

This is the most important point. Traditional privacy coins like Monero hide the sender, recipient, and amount entirely, and have effectively been excluded from the Japanese market over money-laundering concerns. By contrast, zJPYC is built on a regulated asset—JPYC (registered in August 2025 as Japan's first funds-transfer-type stablecoin, with identity verification at issuance and redemption)—and keeps amounts traceable on-chain, limiting concealment to "the link between who and whom."

This is not "anonymity that hides everything" but "confidentiality that protects only what is necessary." It resembles how a bank transfer is private to the general public yet known to the authorities—a middle-ground design aiming to reconcile regulation and usability. As stablecoin payments spread in Japan, it could become a way to fill the adoption barrier posed by the lack of privacy on public ledgers.

[Business Development Insights]

1. On "transparency-by-default" infrastructure, privacy becomes the final bottleneck to adoption. Transparency is a strength of public blockchains, but for practical uses like payroll, supplier payments, and treasury management, it turns into a fatal obstacle. A platform's strength can become its greatest weakness in specific use cases. The complementary feature that removes that "last friction" is often the key to mainstream adoption. In new ventures, it is vital to identify the scenarios where a technology's strength backfires and design value propositions that fill exactly that gap.
2. A "layer strategy"—adding functions on top of a regulated asset—is lower-risk and faster. zERC20 issues no currency of its own; it "retrofits" privacy onto an already-compliant stablecoin. Placing a complementary layer atop an established base (a regulated asset, existing infrastructure, a standard spec) tends to be advantageous over building a full stack in-house, in terms of entry barriers, compliance burden, and development speed.
3. Designing to "protect only what is necessary," rather than "all or nothing," reconciles regulation and usability. Anonymity that hides everything collides with regulation, but selective confidentiality—disclosing amounts while severing only the linkage—can deliver practical value while preserving supervisability for authorities. The more heavily regulated the domain, the more a calibrated design of "minimal concealment and selective disclosure," rather than maximalism, becomes the meeting point of acceptance and adoption.

[Sources]

• NADA NEWS, "zERC20 launches privacy-transfer token 'zJPYC' supporting JPYC" (June 11, 2026)
• Atarashii Keizai, "zERC20 releases privacy token 'zJPYC' for JPYC" (INTMAX core developers; wrapped design; EVM-compatible)
• osumiakari.jp, "'zJPYC' now generally available on Polygon" (one-time burn receiving addresses; wrap/unwrap mechanics)
• JPYC Inc. press release, "Japan's first yen-denominated stablecoin issuance—funds-transfer-operator registration obtained" (August 18, 2025)
• Kaisha-Setsuritsu no Michishirube, "What is JPYC? A complete guide to Japan's stablecoins (2026)" (migration to the funds-transfer-type; status as an electronic payment instrument)
• IIMA, Makoto Shibata lecture materials (November 2025); Nikkei, "FSA registers JPYC as a funds-transfer operator" (August 18, 2025)
• JPYC info (circulation by chain; Polygon the largest)