This milestone initiates the project by researching existing DDI solutions (e.g., Gitcoin Passport, Privado, Identus) and SNET ecosystem specs (WaLT, Voting Portal, Reputation System). It lays the groundwork for the NFTi hub by analyzing integration feasibility, privacy methods, and anti-Sybil needs over 1 month, ensuring a solid base for subsequent phases.

A detailed research report will outline findings on DDI solutions, their methods (e.g., ZKP, DID), and SNET component requirements. It will include a preliminary assessment of WaLT’s expansion potential, data collection from W3C and DIF sources, and initial notes on ZKP KYC frameworks (Hakata.io, Fractal.io), setting the stage for NFTi’s CW-721 spec.

$24,000 USD

Success is achieved if the report comprehensively covers at least 5 DDI solutions, maps their integration potential to SNET’s ecosystem, and identifies key privacy and Sybil resistance gaps. It must cite W3C, DIF, and SNET docs, providing a clear foundation for Milestone 2, validated by the team’s alignment with RFP must-haves.

This 1-month phase analyzes DDI solutions in depth—Gitcoin Passport, Privado, Identus—focusing on unique aspects (e.g., scoring, ZKPs) and defines the NFTi CW-721 spec. It explores WaLT’s hub expansion, sub-ID concepts, and ZKP integration, ensuring privacy and interoperability with SNET’s Voting, Deep Funding, and Reputation systems.

An analysis report and NFTi CW-721 specification will detail DDI integration feasibility, sub-ID design (e.g., “Vote2025”), and WaLT’s role as a hub. The spec will outline NFTi’s structure—metadata, ZKP proofs, $FET agent logic—aligned with W3C DIDs and OpenID4VC, providing a technical blueprint for the prototype phase and SNET ecosystem compatibility.

$24,000 USD

Success requires a report analyzing 5+ DDIs and a complete NFTi spec covering sub-IDs, ZKPs, and anti-Sybil methods. The spec must align with SNET’s must-haves (e.g., unique IDs, self-sovereign control) and integrate WaLT, validated by its feasibility for testnet implementation in Milestone 3 and peer review confirming RFP compliance.

Over 1 month, this phase builds a testnet prototype of NFTi and the WaLT DDI Hub on Fetch.ai’s Cosmwasm chain. It implements the CW-721 NFTi spec—minting tokens, linking wallets, and generating sub-IDs—using $FET agents for verification. The prototype will test core functionality, laying the groundwork for SNET ecosystem integration.

A functional testnet prototype of NFTi and WaLT hub will be delivered, including CW-721 token minting, wallet consolidation (e.g., fetch1abc, 0x123), and sub-ID generation (e.g., “X123”). It will feature $FET agent verification and basic ZKP proof storage in metadata, deployed on Fetch.ai’s testnet, ready for integration testing in the next phase.

$24,000 USD

The prototype is successful if it mints NFTi tokens, links at least 2 wallet types, and generates sub-IDs on testnet, with $FET agents verifying identities. It must store a ZKP proof (e.g., “owns $FET”) and run without crashes, validated by a demo showing WaLT hub functionality and alignment with SNET’s privacy-preserving goals.

This 0.5-month phase tests the NFTi prototype on Fetch.ai’s testnet, integrating DDI solutions like Gitcoin Passport and Privado. It validates scalability, privacy (via ZKPs), and SNET ecosystem compatibility—Voting Portal, Deep Funding—using sub-IDs and $FET agents. Results will refine the hub’s design and prep it for audit, ensuring robust performance.

A test report and updated prototype will document integration of 2+ DDIs (e.g., Gitcoin scores, Privado ZKPs) into NFTi, with sub-IDs enabling Voting and Deep Funding access. It will include testnet logs showing scalability (100+ NFTs) and privacy (ZKP proofs), plus API endpoints (/verify, /sub-id) for SNET components, finalized for security review

$24,000 USD

Success is met if the prototype integrates 2 DDIs, processes 100+ NFTi tokens without failure, and supports Voting/Deep Funding via sub-IDs. ZKP privacy must be functional (e.g., anonymized data queries), and APIs must return valid responses, validated by test logs and a demo showing SNET ecosystem compatibility per RFP must-haves.

In 0.25 months, this phase audits the NFTi prototype’s security and privacy on Fetch.ai’s testnet. It assesses ZKP implementation, $FET agent verification, and sub-ID access controls against vulnerabilities like spoofing or data leaks, ensuring compliance with GDPR/CCPA and SNET’s privacy goals before final reporting and RFP drafting.

An audit report will detail security/privacy findings—ZKP robustness, agent logic, sub-ID controls—identifying risks (e.g., spoofing) and fixes. The audited prototype, hardened against vulnerabilities, will be released on GitHub under MIT License, with CW-721 code and WaLT hub finalized, ready for SNET deployment and RFP development.

$12,000 USD

The audit succeeds if it confirms ZKP anonymity (no data leaks), agent verification reliability (no spoofing), and sub-ID security (restricted access). No critical vulnerabilities must remain, validated by a clean report and a testnet demo showing GDPR/CCPA compliance, ensuring the hub meets SNET’s privacy and security standards.

This 0.25-month phase compiles research findings into a paper and drafts 2-3 RFPs for NFTi development. The paper will summarize DDI analysis, prototype results, and KYC insights, while RFPs will outline a full DDI Hub and WaLT enhancements. All outputs will be open-sourced under MIT, concluding the 4-month effort with a roadmap for SNET.

A research paper will detail DDI findings, NFTi spec, test results, and KYC evaluations, citing W3C/DIF sources. Two RFPs will propose: 1) DDI Hub with Gitcoin/Privado/ZKP KYC, 2) WaLT with sub-ID and Reputation integration. Released on GitHub under MIT License, these deliverables will guide SNET’s next steps, fulfilling the RFP’s vision for a unified identity system.

$12,000 USD

Success is achieved if the paper covers all research (5+ DDIs, ZKP KYC, SNET integration) with citations, and 2 RFPs detail hub/WaLT development with clear budgets and timelines. Validation comes from alignment with RFP must-haves (unique IDs, privacy), community feedback on GitHub, and SNET’s acceptance of RFPs as viable next steps.