Selected work / Ethereum / privacy
Quiet Pool
A Sepolia confidential prize-savings experiment built around Zama FHEVM.
The idea
Private inputs, an inspectable draw.
This selection keeps the opening, the position panel and the draw. The stills document the public interface as captured in September 2026.
The original makes privacy and prize-savings claims that this showcase does not certify. No funded flow was performed. Retained contract source is required for reconstruction.
Three selected moments
A closer look.
Move through the selected stills.
01 / Selected moment
The opening
The opening from the captured Quiet Pool interface.
Open full image ↗
02 / Selected moment
The position panel
The position panel from the captured Quiet Pool interface.
Open full image ↗
03 / Selected moment
The draw
The draw from the captured Quiet Pool interface.
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 Quiet Pool: A Sepolia confidential prize-savings experiment built around Zama FHEVM. Read the repository instructions and preserve existing work first. Reconstruct the idea from this selection; do not promise an exact recreation. Start with one complete useful flow.
02IngredientsPrepare sources and assets
Use the confidential-prize-savings repository, lockfile, contract tests, deployment configuration and documented Zama/OpenZeppelin interfaces. Keep private keys outside the package.
03InteractionBuild the core flow
Distinguish principal from sponsor-funded prizes. Implement pending, unavailable, rejected and settled states for deposit, draw, finalization, claim and withdrawal. Validate the complete flow on a test network before describing it as working.
04Verify & preserveLeave a working handoff
Check the real production route, keyboard operation, mobile layout, reduced motion, asset loading and failure states. Record what passed and what remains untested. Leave source, lockfiles, setup instructions, data provenance and unique selected assets in a compact package. Exclude secrets, dependencies and caches. Label reconstructed prompts honestly; a local package is not a NAS backup.