Description:
Add support for 0zk addresses: the shielded address format used by the RAILGUN protocol. At minimum, this could mean recognizing 0zk balances, 0zk addresses as valid send targets (similar to ENS resolution) and routing the transaction through RAILGUN’s relay infrastructure or even “self-broadcasting” or a paymaster solution. A deeper integration could include a “shield” flow directly within the send UI from the standard 0x address to the user’s own 0zk address.
Purpose:
Privacy is a legitimate and increasingly mainstream need for Ethereum users. RAILGUN is a non-custodial, fully audited ZK privacy layer deployed on Ethereum, Arbitrum, BSC, and Polygon, and unlike older approaches, it ships with built-in compliance tooling (PPOI) that lets users cryptographically prove funds don’t come from sanctioned sources.
Kohaku recently added native RAILGUN + PPOI support, and MetaMask supporting 0zk addresses would be a meaningful signal that privacy is a first-class concern.
If a full native integration isn’t feasible short-term, a MetaMask Snap could potentially cover this. I’m curious whether that path has been explored or what the team’s thoughts are on developing this internally or being open to review a community contribution for either Kohaku integration or just integrating the Railgun SDK.
Extension/Mobile/Both:
Extension
Images/Attachments:
N/A