Selected work / Ethereum / privacy
Veil Protocol
A multi-vault interface study around one configured Sepolia confidential prize vault.
The idea
A directory around one real configuration.
This selection keeps the vault directory, the privacy boundary and the vault detail. The stills document the public interface as captured in September 2026.
The captured interface labels unavailable wallet data and planned multi-vault features. No transactions or privacy guarantees were independently verified.
Three selected moments
A closer look.
Move through the selected stills.
01 / Selected moment
The vault directory
The vault directory from the captured Veil Protocol interface.
Open full image ↗
02 / Selected moment
The privacy boundary
The privacy boundary from the captured Veil Protocol interface.
Open full image ↗
03 / Selected moment
The vault detail
The configured Sepolia vault detail, with the wallet disconnected.
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 Veil Protocol: A multi-vault interface study around one configured Sepolia confidential prize vault. 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
Start from the retained confidential-prize-savings source and lockfile. Document chain ID, vault addresses, token interfaces and which capabilities are implemented or planned. Use testnet only during reconstruction.
03InteractionBuild the core flow
Build one source-backed vault card, a detail view, a capability map and explicit unavailable states. Separate public contract reads from encrypted wallet state. Do not invent vaults, yields, balances or audit assurances.
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.