Selected work / Ethereum / modelling
curvETH
An educational payoff and exposure experiment for ETH-backed synthetic positions.
The idea
Read the curve before changing the assumptions.
This selection keeps the educational view, the simulator and the terminal. The stills document the public interface as captured in September 2026.
Research interface only. Parameters and costs are illustrative model assumptions, not prices, investment advice or a validated trading strategy.
Three selected moments
A closer look.
Move through the selected stills.
01 / Selected moment
The educational view
The educational view from the captured curvETH interface.
Open full image ↗
02 / Selected moment
The simulator
The simulator from the captured curvETH interface.
Open full image ↗
03 / Selected moment
The terminal
The terminal from the captured curvETH 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 curvETH: An educational payoff and exposure experiment for ETH-backed synthetic positions. 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 payoff formulas, strike/maturity/volatility units and dated market-data provenance. Separate terminal payoff identities from pricing estimates and transaction-cost assumptions.
03InteractionBuild the core flow
Build linked sliders, payoff curves and an exposure heatmap with educational and compact views. Independently test P plus N equals one ETH at terminal payoff, boundary cases and invalid inputs. Mark API history failures clearly rather than silently replacing market data.
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.