Selected work / Ethereum / reading
Ethweekly
A weekly Ethereum reading experiment with source-linked issues and an archive.
The idea
A reading path into protocol work.
This selection keeps the opening, a historical issue and the archive. The stills document the public interface as captured in September 2026.
Captured issues are historical editorial artifacts. Headlines and protocol claims have not been independently revalidated. Rebuilding the workflow does not authorize publishing or emailing new issues.
Three selected moments
A closer look.
Move through the selected stills.
01 / Selected moment
The opening
The opening from the captured Ethweekly interface.
Open full image ↗
02 / Selected moment
A historical issue
A historical issue from the captured Ethweekly interface.
Open full image ↗
03 / Selected moment
The archive
The archive from the captured Ethweekly 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 Ethweekly: A weekly Ethereum reading experiment with source-linked issues and an archive. 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 published issue artifacts, citation URLs, source registries, dates and editorial revisions. Separate local crawling from public serving, and retain human review before publication.
03InteractionBuild the core flow
Build a readable issue page, topic sections, archive and RSS. Keep generated drafts separate from published issues. Test citation integrity, date windows and stale-source behavior; enable scheduling and email only with explicit operating authorization.
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.