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/2025Many people showed up to discuss AA & 3074 during the Execution Layer Meeting 186 [2024-04-25] thus a breakout room has been decided to further discuss 3074. We propose to prepare the breakout in order to have a productive debate that focus on objective technical points rather than side meta-discussion about governance. It's not that those discussions are forbidden it's simply that a breakout room is not the venue for them. So we'd like to provide this framework, with the goal to produce an efficient debate, that people are free to follow. Preparing the breakroom with keeping in mind what is this breakroom for? Have a look at "The Hard Parts of Open Source" by Evan Czaplicki where he discusses intent communications in Open Source projects. And with this in mind I invite you to prepare your communications with the following structure : Intent: e.g understand 3074 AUTH Background: e.g I am a wallet dev for a software wallet dealing with EOAs and doing XYZ
5/3/2024