Selected work / Ethereum / research
Ethereum Researchers
A public research-corpus explorer for people, papers, topics, institutions and source leads.
The idea
Start with a question, follow its sources.
This selection keeps the corpus opening, search and the data index. The stills document the public interface as captured in September 2026.
Counts and dates describe the captured corpus, not verified coverage. Source leads, inferred relationships and identity matches need individual review.
Three selected moments
A closer look.
Move through the selected stills.
01 / Selected moment
The corpus opening
The corpus opening from the captured Ethereum Researchers interface.
Open full image ↗
02 / Selected moment
Search
Search from the captured Ethereum Researchers interface.
Open full image ↗
03 / Selected moment
The data index
The data index from the captured Ethereum Researchers 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 Ethereum Researchers: A public research-corpus explorer for people, papers, topics, institutions and source leads. 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
Preserve source seeds, normalized researchers/works/topics, stable IDs, provenance, confidence and public dataset exports. Never import private address books or infer contact details.
03InteractionBuild the core flow
Build text search and source-linked dossiers before expensive graphs. Keep identity resolution conservative and disclose uncertain matches. Validate references and regenerate a small externally selected source set before claiming corpus completeness.
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.