This foundational milestone is dedicated to comprehensively understanding and aligning with the project’s requirements through detailed stakeholder engagement (including with the DDI project team to the degree that the two projects are time-synchronized at this stage) while outlining any recruitment needs for additional personnel resources and skills necessary for success. We will conduct in-depth analysis to clarify expectations for the architecture microservices UI and non-functional requirements going from coarse-grained to fine-grained and from the must-have requirements to the should- and could-have functionalities as laid out in the RFP and in our proposal. We will define the initial microservice suite (Deep Funding proposal portal Deep Funding voting portal and Blockchain Explorer including possible integration with Flipside Crypto or similar). This milestone is to establish an understanding and mapping of all the major functional interrelationships required for project success. This milestone’s budget will also support commencement of the subsequent milestone.

Project Requirements and Alignment Document that: - Encapsulates stakeholder inputs; - Details the state of and learnings from discussion with the DDI project team (to the degree that it is possible and that the two projects are time-synchronized at this stage); - Detail must-have requirements (as per RFP) and expectations; - Detail should-have requirements (as per RFP) and expectations; - Detail the selected potential could-have requirements (as per RFP) and expectations (to the degree/extent that is possible at this stage); - Detail the non-functional requirements (as per RFP) and expectations; - Demonstrates non-conflict between the individual requirements that are planned to be implemented; - Specification of the initial suite of microservices (Deep Funding proposal portal Deep Funding voting portal and Blockchain Explorer including possible integration with Flipside Crypto or similar) and their main expected functionalities; - Details a hiring plan; - Details a refined/adjusted/updated project roadmap as needed.

$40,000 USD

Success is achieved when the Project Requirements and Alignment Document receives approval from key stakeholders, verifying that at least all the must-have, should-have, and non-functional requirements are fully captured, and the could-haves to the degree possible at this stage. There is clarity and sufficient definition to the project plan that enables proceeding to the architectural design stage. The recruitment plan identifies any critical skills and a feasible recruitment schedule, aligned with the project timeline.

Establish the foundational system design and lay the groundwork for development. This includes refining the modular architecture setting up containerization strategies (e.g. WASM-based deployments) and drafting initial UI flows. By creating environment configurations and basic scaffolding the team ensures that microservices can be plugged in seamlessly later on. The key activities involve defining how standardized APIs will function ensuring future ZKP integration and implementing a user-consent framework at a conceptual and technical level. Early security considerations are introduced focusing on anonymization and pseudonymization where relevant. This milestone also includes creating mockups/wireframes to illustrate how data flows between microservices and the UI. Overall the objective is to move beyond just documentation by delivering a skeleton framework that can be tested and iterated upon in subsequent phases.

- Architecture Blueprint Document (with diagrams data flow and API definitions); - Containerization Templates (e.g. WASM or Docker files); - High-Level Security & Consent Model (outlining pseudonymization consent checks) (We will remain in communication with the DID team on this and if they are not ready on this we will issue recommendations/ make our best effort.); - Basic Code Repository Setup (showcasing initial environment configs scaffolding); - UI Mockups/Wireframes (showing proposed navigation configuration screens and envisioned blacklisting approach).

$30,000 USD

- A functioning “Hello World” style environment where containers can be built, deployed, and tested; - Confirmation that standardized I/O formats are agreed upon and partially implemented; - Verified basic security measures (e.g., pseudonymization hooks) exist in the architecture blueprint; - UI mockups/wireframes and architectural design demonstrates understanding and vision on the solution; - Clear alignment on how microservices will interact with the main system and each other.

Build out the essential functionalities of the three microservices—Deep Funding Proposal Portal Voting Portal and the Blockchain Explorer microservice—and integrate them into the previously established environment. Each microservice includes well-defined endpoints logic for data processing and basic privacy-enforcing methods. The team begins verifying fault isolation and error handling ensuring any failure in one service won’t disrupt the entire system. Load tests start here focusing on horizontal scalability. Microservices are containerized using the templates from Milestone 1 and adhere to standard API formats. Parallel efforts begin connecting these services to the UI confirming that the system design (e.g. APIs user-consent framework) holds up in practice. Updates to the architecture are made as necessary.

- Essential functionalities of the three core microservices: Deep Funding Proposal Portal Deep Funding Voting Portal Blockchain Explorer (e.g. via Flipside Crypto); - API Documentation (request/response formats usage guides); - Pseudonymization Features (baseline integration with DID solutions like WaLT); - Basic Integration with the UI (test calls preliminary data display); - Initial Testing Reports (load testing fault isolation error handling) if possible at this stage (optional); - Updates to architecture as necessary (optional).

$30,000 USD

- Microservices run within the containerized environment; - Verified compliance with standardized I/O formats across services; - User consent checks or pseudonymization confirmed operational at the service level; - Successful early-stage load test results demonstrating baseline scalability; - Validation that UI can retrieve live data from each microservice in a development environment.

Build-out of the three microservices is complete. The user interface is complete or approaching completion to allow real-time interaction with all microservices and finalize how data is processed for reputation scoring. Users can configure which microservices to use adjust weighting from 0–100 manage blacklists and view aggregated reputation scores. A consent management dashboard ensures user-driven control over data usage. The system integrates each service’s outputs into a seamless interface providing transparency about data sources and enabling export to multiple formats. Testing and validation of the UI’s functionality including usability trials optionally occur in this milestone. The main result is an integrated platform where the modular design is visibly realized demonstrating the architecture’s ability to scale with future enhancements.

- Build-out and full functionality of the microservices complete; - Functional UI supporting: Microservice selection and weighting Reputation score calculation and display Blacklist management Consent management dashboard; - Export/Automation Capabilities (JSON CSV PDF additional APIs); - Documentation on UI flows configurations and user guides; - User Acceptance Testing (UAT) Feedback and Refinements (optional at this milestone).

$20,000 USD

- All microservices are accessible via the UI with good performance; - Users can customize configurations, apply weights, and view instantaneous score recalculations; - Blacklisting and consent features function as intended with clear feedback loops; - Successful UAT completion with minimal critical issues or UX blockers (optional at this milestone); - Demonstrated potential for additional microservices to be integrated without redesign.

Conduct thorough security testing and performance validation to ensure the system is ready for production. User acceptance testing (UAT) occurs (or is completed) here. penetration tests vulnerability scans and advanced load/stress tests gauge the resilience of both microservices and the UI. The user-consent framework is further tested to verify proper data protection. ZKP- or MPC-readiness is formally assessed ensuring cryptographic enhancements can be added later without major refactoring. Final documentation is compiled including detailed developer guides API references deployment instructions and user manuals. Warranty retainer conditions are determined. A production rollout plan is then confirmed concluding with a formal handover or training session to ensure smooth operation and future extensibility. Final fixes and touches to the architecture microservices and UI are done here as needed.

- UI is fully functional (if not previously completed); - Testing Reports (load testing fault isolation error handling) if not previously completed; - User Acceptance Testing (UAT) Feedback and Refinements completed; - Security & Vulnerability Test Reports (with mitigation actions); - Performance Test Reports (stress load scalability results); - Production Deployment Plan (orchestration guidelines environment configuration); - Warranty/retainer conditions specified and provided including assumptions pre-conditions in-scope vs. out-of-scope and dependencies; - Final Documentation Set: -- Developer Docs (code structure integration steps); -- Detailed API Reference (endpoints parameters error handling); -- User Guide (step-by-step usage of the UI and microservice interactions); -- Roadmap for ZKP Integration (If DID team is not ready with ZKP we will issue our best approximate recommendations).

$20,000 USD

- Microservices run within the containerized environment without conflict; - All microservices are accessible via the UI with consistent performance; - Successful UAT completion with minimal critical issues or UX blockers; - No high-severity vulnerabilities remain unaddressed after testing; - System reliably handles projected user load with minimal downtime; - Full documentation enabling new developers to maintain or enhance the platform; - Formal acceptance of production deployment plan by stakeholders; - Verification that ZKP or advanced cryptographic methods can be integrated without re-architecting; - Warranty/retainer conditions are specified.