Kohaku is a set of primitives that provides wallets with security and privacy. Kohaku’s core goals are : an SDK that exposes strong privacy/security primitives a power‑user-oriented reference implementation wallet that ships on top of that SDK to showcase these features; collaborations with other wallets to implement the SDK either in full or in parts that they care about To kickstart the effort, the project is focusing on privacy features and a browser extension that demonstrates the power of these features and targets power users. This reference implementation will not be a consumer oriented product. The browser extension is a fork of Ambire. Development on both the wallet and the SDK will be mainnet first, and progressively add support for Layer 2s. We will focus on layer 2s that are at least stage 1 and committed to reach stage 2 and add fast withdrawals. The reference implementation and the SDK will come with a plugin system that developers will enable themselves. This way wallet teams will be able to select the features they want to propose to their users. In the future new privacy protocols could be added to the plugin list. We will progressively enable more private interactions within DeFi protocols. Features In a first phase we will be working on a set of features enabling privacy and security improvements. Here is a non exhaustive list of features that we would like to achieve:
10/9/2025Special thanks to Tim Beiko, Yoav Weiss and Lightclient for feedback and review. Abstract EIP 7702 defines a mechanism to add code to an EOA. This proposal allows EOAs, the legacy ethereum accounts, to receive short-term functionality improvements, increasing the usability of applications. This is done by setting a pointer to already deployed code using a new transaction type: 4. This new transaction type introduces an authorization list. Each authorization tuple in the list is defined as [ chain_id, address, nonce, y_parity, r, s ] address is the delegation (already deployed bytecode that'll be used by the EOA)
4/23/2025This document outlines suggestions for creating a comprehensive, credibly neutral dashboard for all wallet solutions, à la L2Beat. “The primary challenge is making sure that all these projects are, collectively, building something that feels like one Ethereum ecosystem, and not 138 incompatible fiefdoms.” - [Vitalik Buterin](https://vitalik.eth. Software wallets (EOA), and smart wallets should be all under one dashboard. Hardware wallets should also be included (maybe in a different page as they're not the same) The Challenge of Being a Wallet Wallets are critical infrastructure and often the primary interface users have with the blockchain. For many, the wallet is the blockchain experience. Evaluating wallets can involve ranking them into stages based on specific criteria, similar to how Layer 2 solutions are assessed. I won't propose an implementation nor help with the execution (as I don't think that should be my role and also don't have the bandwith). But I'm happy to help the brainsorming of criteria and open my network of wallet people to make it happen ! Technical Alignment for Wallets
12/5/2024