# 0zk Address Support / Kohaku **URL:** \ **Category:** Feature Requests\ **Created:** [June 3, 2026, 2:50am UTC](https://community.metamask.com/t/0zk-address-support-kohaku/31491 "2026-06-03T02:50:41Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![danlipert](https://dub1.discourse-cdn.com/metamask/user_avatar/community.metamask.com/danlipert/32/39632_2.png) [@danlipert](https://community.metamask.com/u/danlipert)\ **Post date:** [June 3, 2026, 2:50am UTC](https://community.metamask.com/t/0zk-address-support-kohaku/31491/1 "2026-06-03T02:50:41Z")
**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 ---
**Author:** ![theweb3dave](https://dub1.discourse-cdn.com/metamask/user_avatar/community.metamask.com/theweb3dave/32/39163_2.png) [@theweb3dave](https://community.metamask.com/u/theweb3dave)\ **Post date:** [June 3, 2026, 3:45am UTC](https://community.metamask.com/t/0zk-address-support-kohaku/31491/2 "2026-06-03T03:45:08Z")
Hi! Thanks for creating the feature request. ---
**Author:** ![danlipert](https://dub1.discourse-cdn.com/metamask/user_avatar/community.metamask.com/danlipert/32/39632_2.png) [@danlipert](https://community.metamask.com/u/danlipert)\ **Post date:** [June 9, 2026, 12:09am UTC](https://community.metamask.com/t/0zk-address-support-kohaku/31491/3 "2026-06-09T00:09:27Z")
Any updates on this? Would love to have a discussion, especially with everything thats been happening with ZEC and the wider ZK space. ---
**Author:** ![holy](https://dub1.discourse-cdn.com/metamask/user_avatar/community.metamask.com/holy/32/38706_2.png) [@holy](https://community.metamask.com/u/holy)\ **Post date:** [June 9, 2026, 4:09am UTC](https://community.metamask.com/t/0zk-address-support-kohaku/31491/4 "2026-06-09T04:09:23Z")
Hey @danlipert ! Thanks for checking in! Feature requests are a long-term game. After a post is made, it gets logged internally for our teams to review during their planning cycles. Because of this, there won’t be a specific update after just a few days. However, please be assured that we have seen your suggestion and it’s been added to the list for consideration. We really appreciate you taking the time to share your ideas with us! ---
**Author:** ![HiroProtagonist](https://dub1.discourse-cdn.com/metamask/user_avatar/community.metamask.com/hiroprotagonist/32/9884_2.png) [@HiroProtagonist](https://community.metamask.com/u/HiroProtagonist)\ **Post date:** [June 9, 2026, 2:09pm UTC](https://community.metamask.com/t/0zk-address-support-kohaku/31491/5 "2026-06-09T14:09:18Z")
Snaps would be a perfect fit. Snaps are mostly developed by external teams. They’re currently only supported on Extension, but we’re working to bring them to mobile as well. Docs are here: [Snaps introduction | MetaMask developer documentation](https://docs.metamask.io/snaps) But the TL;DR: If it interacts with keystore, the Snap needs to be reviewed by one of the [approved external security auditors](https://docs.metamask.io/snaps/how-to/get-allowlisted), then submitted for allowlisting, then it’ll be shown on the Snaps directory and users can install it. ---
**Author:** ![danlipert](https://dub1.discourse-cdn.com/metamask/user_avatar/community.metamask.com/danlipert/32/39632_2.png) [@danlipert](https://community.metamask.com/u/danlipert)\ **Post date:** [June 17, 2026, 1:20am UTC](https://community.metamask.com/t/0zk-address-support-kohaku/31491/6 "2026-06-17T01:20:48Z")
Thanks Hiro for your reply. I spent some time looking into this last week, and it seems it would require support for custom curves and derivation paths. Maybe it could be a external-hardware only system, where key generation and signing could be done on a ledger, etc., but also I think there would be some problems with proving, specifically the keyfiles used I believe are larger than the snaps sandbox would allow. What do you think? ---
**Author:** ![danlipert](https://dub1.discourse-cdn.com/metamask/user_avatar/community.metamask.com/danlipert/32/39632_2.png) [@danlipert](https://community.metamask.com/u/danlipert)\ **Post date:** [June 30, 2026, 1:28am UTC](https://community.metamask.com/t/0zk-address-support-kohaku/31491/7 "2026-06-30T01:28:10Z")
Anyone have any thoughts on this? I’m starting to think the only way forward is by using a ledger etc., without some deeper integration with MM…