How to Apply
Whether you're working on a specific project, or you're still exploring possibilities, you can connect with our team for guidance.
Secure and Decentralized Frontends
An RFP to design and implement systems that let decentralized applications serve frontends in a way that is verifiable, censorship resistant, and independent of centralized intermediaries such as DNS providers, gateways, and CDNs. The aim is client side verification of frontend assets with decentralized distribution and a user experience that works in real browsers and wallets. This initiative supports the long-term goal of making decentralized applications fully trustless from backend to frontend. Projects are expected to deliver practical, open implementations that can be adopted by wallets, browsers, and major dapps. See full details and proposal requirements in Resources.
Tags
- Privacy
- Security
Ecosystem Need
Most dapps still depend on centralized hosting and gateways, introducing risks such as provider compromise, DNS hijacking, single points of failure (e.g. through gateways), and censorship based on jurisdiction. These vulnerabilities contradict Ethereum’s neutrality and reduce the credibility of “decentralized” applications. To strengthen Ethereum’s resilience, frontends must be independently verifiable, resilient to tampering, distributed through peer to peer or content addressed networks, and easily integrated into common access points such as wallets and browsers. This RFP targets practical, deployable solutions that make decentralized frontend verification a default expectation across the ecosystem.
Hard Requirements
- Frontend assets must be cryptographically verifiable on client side, to eliminate current reliance on trusted intermediaries (e.g. gateways, CDNs, single providers). - Support for decentralized distribution (e.g. WebRTC, WebTransport, P2P mechanisms) with fallback options without central chokepoints. - Usable in at least one major browser without requiring extensions, or verifiable via wallet as fallback. - Deliver a proof of concept and a production ready implementation integrated with at least one major dapp and several smaller ones. - Provide an adoption plan for wallets and dapps, with milestones tied to real integrations. - All output must be open-source and designed as public goods.
Soft Requirements
- Developer tooling and documentation that make integration straightforward. - Roadmap and strategy for ecosystem integration (wallets, browsers, dApps). - Demonstrated alignment with existing standards (content addressing, IPFS, libp2p, etc.). - Performance, scalability, and usability testing on desktop and mobile.
Resources
Timeline
Opens: Oct 29, 2025
Closes: Dec 13, 2025
Estimated Project Duration: Up to 6 months.
