Selected work / Ethereum / privacy
Kohakool
A study of Kohaku, the Ethereum Foundation’s privacy-plugin standard for wallets, with a concept router and a separate Sepolia testnet wallet.
The idea
Several privacy protocols through one interface.
This selection keeps the concept router, the public protocol study and the next steps. It records the interface separately from wallet recovery and transaction execution.
The router uses mock pools. The original wallet targets Sepolia and alpha, unaudited SDKs. Transaction references are historical project records; wallet recovery, balances and private withdrawals were not verified for this selection.
Three selected moments
A closer look.
Move through the selected stills.
01 / Selected moment
The concept router
A mock-pool router demonstrates protocol selection through the Kohaku interface.
Open full image ↗
02 / Selected moment
The protocol study
The public About page records the project’s Sepolia transaction references and implementation limits.
Open full image ↗
03 / Selected moment
The next steps
The roadmap identifies standard conformance, withdrawal economics and a future live router as further work.
Open full image ↗Make something of your own
Build your own.
Take the idea into Codex and adapt it to your own subject, sources and audience.
Reconstructed recipe · Not the original prompts
An end-to-end recreation has not been tested.
01BriefDefine the experience
Build a new interpretation of Kohakool: a study of the Kohaku privacy-plugin interface, with a clearly labelled concept router and a separate Sepolia wallet boundary. Read repository instructions first. Treat these prompts as a reconstruction, not the original conversation or an exact restoration. Start with the public explanatory and concept-demo flow.
02IngredientsPrepare sources and assets
Preserve the engine, plugin-standard provenance, router, React/Vite interface, lockfile and selected public circuit/WASM assets. Record the exact SDK and circuit versions and their licenses. Keep the public transaction references as historical project evidence. Never include wallet mnemonics, private keys, browser storage or endpoint credentials in the project archive.
03InteractionBuild the core flow
Build a labelled mock-pool router with amount input, balanced/privacy-first ranking, protocol cards and a public-to-shielded visualization. Keep the real wallet in a separate flow. If restoring wallet functionality, constrain it to the documented test network, make recovery/export explicit, and distinguish relayed private withdrawal from the non-private ragequit exit. Do not claim that mock routing chooses routes for real funds.
04Verify & preserveLeave a working handoff
Verify the public demo, About and roadmap routes on desktop and mobile without opening a wallet. Record untested wallet, proving and transaction behavior honestly. Preserve the public runtime assets and upstream provenance with the source archive. Before retiring an original wallet origin, obtain owner confirmation that no wallet state requires preservation or that independent recovery is complete; a same-browser encrypted save and a source archive do not prove recovery.