TLDR:
Privacy should be the default in wallets: Users shouldn’t need extra steps/accounts to get privacy.
Self-custody includes data custody: Owning assets is not enough if your behavior is fully traceable.
@RAILGUN_Project approach:
• Private address from the same seed. Uses a separate derivation path (ZK address) for private activity.
• Goal: private address can do everything public address can. Not limited to one token or one narrow use case.
• No dependency on a privacy token. Privacy is infrastructure-level, not tied to a special asset.
Kohaku = EF-backed privacy wallet initiative. Built as a privacy-focused fork based on the Ambire codebase.
Why was Ambire selected as base?
• Low external dependency, strong open-source base, account abstraction maturity.
• Ambire data layer minimizes third-party API reliance. More privacy today; easier future move toward light-client architecture etc
Kohaku is intended to feed back into broader wallet ecosystem. End goal is SDK-level integration across many wallets, not one app: notes.ethereum.org@niard/KohakuRoadmap…
Blockers:
• dApps bypass wallet and query RPC directly. Frontends often ignore wallet-reported state.
• Direct RPC calls create both UX and privacy tradeoffs. Better reliability for apps, but more user data leakage/tracking risk.
@Ivshti @tsu_kareta @cinesiusss agree private transfers are landing in major EVM wallets before GTA6 :D
Someone spawn Polymarket for this please :D
