The I2P Protocol: 13 weeks from prototype to fundable product.
I2P is not an accelerator. It is an engineering methodology. There are no pitch days in week two — only architecture reviews. Every phase has a binary go/no-go gate, and failing one gate resets the clock. We only advance what is technically ready.
Applications open quarterly. Cohort size is capped at 5 projects to ensure every team receives senior engineering attention throughout all four phases.
The Four Phases
Technical Desiccation
Strip the idea to its absolute minimum viable engine. No UI, no marketing copy, no investor deck — just: what is the core technical problem, and what is the simplest system that solves it? The output is a 10-page Technical Desiccation Report that defines what must exist for the product to function.
API-First Design
Design the API contract before writing the implementation. OpenAPI 3.0 specification, data models, authentication strategy, error handling, and versioning policy. This document becomes the legal scope of work for the freelancer team that will be assembled in Phase 4.
Crowdfunding Validation
Deploy a working prototype on Coderic Cloud — not a mockup. Real endpoints, real auth, real data. This prototype is listed on the OPM Engine for a 21-day community mini-round. If it doesn't reach 30% of its target, we return to Phase 1. The community is the final validation.
Production Hardening
Security audit (OWASP Top 10 baseline), load testing to 10x projected peak traffic, monitoring and alerting via Grafana stack, and automated CI/CD pipeline. The output is the handoff package for the full development team assembled via the Freelancers pillar — they take over at production quality, not prototype quality.
Application Requirements
- Working prototype or proof of concept — even a rough one. Ideas without any code are not eligible.
- LATAM market fit — the product must address a genuine problem in the Latin American market with clear enterprise or B2B revenue potential.
- Open-source commitment — the core engine must be open-sourceable within 24 months of launch.
- Founder technical ability — at least one founding team member must be a practicing engineer capable of participating in Phase 1 technical debates.