Selected work / Ethereum / coordination
ETH Front Desk
A prototype for routing Ethereum founders to practical ecosystem support.
The idea
Turn a broad request into a useful next conversation.
This selection keeps the front desk, support categories and the flow preview. The stills document the public interface as captured in September 2026.
This is a prototype, not an operating support service. The source form is explicitly non-delivering; no requests or messages were sent.
Three selected moments
A closer look.
Move through the selected stills.
01 / Selected moment
The front desk
The front desk from the captured ETH Front Desk interface.
Open full image ↗
02 / Selected moment
Support categories
Support categories from the captured ETH Front Desk interface.
Open full image ↗
03 / Selected moment
The flow preview
The flow preview from the captured ETH Front Desk 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 ETH Front Desk: A prototype for routing Ethereum founders to practical ecosystem support. 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 support categories, eligibility and capacity rules supplied by an actual operator. Keep prototype contacts and routing examples clearly labeled; do not imply real people have agreed to help.
03InteractionBuild the core flow
Build structured intake and a visible routing/status flow. Keep the first version a non-delivering prototype. Add a real inbox or Telegram integration only after explicit operator authorization and delivery testing.
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.