Contribo
ProgramsOrganizationsProjectsProposal StudioResourcesOrbit AIDashboard
Login
Login
Contribov1.0

Your premium companion for discovering, matching, and tracking paid open-source mentorship programs and verified starter issues.

Product

  • Programs Directory
  • Orbit AI
  • User Dashboard

Resources

  • Guides & Resources
  • Proposal Studio

Community

  • GitHub Repository
  • Code of Conduct

Legal

  • Privacy Policy
  • Terms & Conditions
  • Cookie Policy
  • Accessibility Statement

Made with love bySubhranshu Sekhar Dash

© 2026 Contribo. Built for the global open-source community.

PlatformProjects

Explore Projects

Find open source projects actively accepting contributors. Search repositories, filter by program milestones, difficulty tags, or tech stack.

Confused which project to choose or don't know which one you are most suitable to work on?

Use our Orbit AI Matcher to find out! Get instant matching scores based on your developer skills, preferred frameworks, and contribution experience.

Match with Orbit AI
Filters Clear
3179 Projects Found
Sort by

Project #2: Robotics Academy: consolidation of drone based exercises

advanced
JdeRobot•2022Varies

Ready to Apply?

Convert your selected open-source project into a winning GSoC, LFX, or Outreachy application using Proposal Studio.

Start Proposal
Proposal Status
0% ProgressNot Started
Accepted Proposals
3 SimilarView →
Proposal Guide
Tailored DocsOpen →
Checklist & Review
Readiness AuditCheck →
350h (Large)

Currently there are 11 drone exercises available, all as web-templates (RoboticsAcademy v3.2). The goal of this project is to consolidate the existing exercises, improving front-end appealing and extending drones back-end (PX4 and JdeRobot drone-wrapper) with new functionalities, such as adding support to new control methods or new sensors (IR sensors, depth cameras, etc) If time permits, the project may also explore the development of new drone exercises or extending support to real drones.. Work will be done with Docker, Gazebo-11 and ROS-noetic. Also, ROS2 use for these exercises will be explored. This work will possibly be done in the mentorship of Mr. Pedro Arias and Mr. Arkajyoti Basak. Deliverables Deliverable 1 Strengthening of current drone based exercises with bug crushing and optimised template (before Evaluation 1) Deliverable 2 Development of better and appealing frontend with broadened and extended drones backend through addition of support for new functionality like sensors and new control methods (by Evaluation 2) Deliverable 3 Pre development base for the new drone exercises & extension for support of real drones and exploration of ROS2 for these exercises (if time allows) (by the end of the coding period) Approach ● Creating an additional folder with several subfolders containing all the necessary scripts to beta test the optimised template. ● Running the exercises in search for details regarding existing bugs ● Improve the appeal of frontend through HTML document cleanup, optimising CSS performance, minifying CSS, Javascript & HTML ●Improving PX4 performance for multiple drones and additional HAL methods for controlling drone(s) through nosing around PX4, creating necessary scripts for packages. ● Adding new gazebo models for new sensors and interfacing them with the Robot’s brain with the HAL ● RADI (RoboticsAcademy Docker Image) launch shell script has to be updated additional requirements

pythonrosgazebo+2
Student: Prakarsh Kaushik
Code
Proposal

Generative-AI Assisted Testing of Complex Stacks of Spack Packages

advanced
CERN-HSF•2026Varies350h (Large)

The Problem: Spack’s combinatorial flexibility makes exhaustive CI testing computationally impossible. Current CI focuses almost exclusively on "leading-edge" configurations (latest packages with latest dependencies). This structurally excludes off-leading-edge scenarios where older packages meet newer, unbounded dependencies, leaving the ecosystem highly vulnerable to silent API/ABI breakages that users only discover in production. The Solution: This project introduces a Generative AI-assisted testing system to autonomously hunt for high-risk configuration breakages. The architecture treats configuration testing as a feedback-driven sequential decision-making pipeline. First, a data-driven heuristic risk model filters dependency pairs based on structural risk and historical failures. Next, an LLM acts as an iterative hypothesis generator to propose structurally diverse, high-risk abstract specs. Finally, a strict deterministic validation layer ensures mathematical correctness and bounds CI compute costs using Spack's Clingo ASP concretizer and semantic deduplication. Key Deliverables: Metadata Extraction Module: Parses package repositories to identify unbounded dependencies and analyze version gaps. Adaptive Risk Scoring Engine: Classifies package pairs into risk tiers using a multiplicative formula driven by structural signals and historical failure data. LLM Hypothesis Generator: An iterative prompt engine utilizing selective context retrieval and within-run adaptation to propose risky testing configurations. Validation Pipeline: A strict gating system utilizing spack.concretize_one() and 3-layered semantic deduplication to prevent redundant or hallucinated tests. State Management Registry: A unified SQLite database to map historical CI data, track tested configurations, and feed failure patterns back into the LLM context. Integration & Diagnostics: A working spack audit ai CLI subcommand and a heuristic log-triage pipeline.

pythonc/c++machine learning+6
Student: VaishnaviMishra
Code

Integrating Kmesh into Headlamp UI (2026 Term 2)

Intermediate
•Varies175h (Medium)

<p>[Headlamp](https://headlamp.dev) is an open-source, extensible Kubernetes web UI offering easy cluster management, multi-cluster support, RBAC, and a plugin system for adding custom functionality. Users who work with Kmesh today have to switch back and forth between Headlamp (for general Kubernetes resource management) and CLI tools / `kubectl` (for Kmesh-specific inspection), which creates a fragmented workflow and a poor user experience. There is currently no simple visual way to view Kmesh resources, inspect waypoints and related components, understand overall mesh status, or troubleshoot issues quickly from within an interface users already use. This project proposes building a Headlamp plugin for Kmesh that brings Kmesh resources directly into the Headlamp UI, providing lightweight visibility of Kmesh resources alongside other Kubernetes resources. The full-featured Kmesh dashboard remains the place for advanced operations; the Headlamp plugin focuses on reducing context switching and improving ease of use for day-to-day workflows.</p><p><br></p><p><br></p><p>Expected Outcome:</p><p><br></p><p>&nbsp;- A Headlamp plugin (TypeScript/React) that registers Kmesh CRDs and surfaces them as first-class resources in the Headlamp UI.</p><p><br></p><p>&nbsp;- List and detail views for core Kmesh resources (e.g., waypoints and eBPF map)</p><p><br></p><p>&nbsp;- Visual indicators of mesh status: per-resource health, readiness, and recent Events; cluster-level summary of Kmesh components.</p><p><br></p><p>&nbsp;- Inspection helpers: pretty-printed YAML, related-pod views, and quick links to associated workloads/services.</p><p><br></p><p>&nbsp;- Documentation (README, screenshots, install guide) and a published plugin (Helm/manifest or Headlamp plugin registry entry).</p><p><br></p><p>&nbsp;- Unit/component tests for the plugin and an end-to-end smoke test against a kind/minikube cluster running Kmesh.</p>

TBA
Proposal

Repository Service for TUF (RSTUF) 2026 Mentorship Project

Intermediate
•Varies175h (Medium)

<p><span style="background-color: transparent; color: rgb(0, 0, 0);">The purpose of this project is to enhance the (</span><a href="https://openssf.org/projects/repository-service-for-tuf/" rel="noopener noreferrer" target="_blank" style="background-color: transparent; color: rgb(17, 85, 204);">Repository Service for TUF RSTUF</a><span style="background-color: transparent; color: rgb(0, 0, 0);">) implementation by tackling critical areas that would significantly improve its functionality, scalability, and ease of adoption. RSTUF is designed to manage content distribution efficiently using the TUF (</span><a href="https://theupdateframework.io/" rel="noopener noreferrer" target="_blank" style="background-color: transparent; color: rgb(17, 85, 204);">The Update Framework</a><span style="background-color: transparent; color: rgb(0, 0, 0);">), but it currently has areas where improvements in delegation flexibility, performance, testing, and documentation are needed. This project will allow RSTUF to handle larger and more complex scenarios, while providing an improved experience for both developers and adopters.</span></p><p><br></p><h2><strong style="background-color: transparent; color: rgb(0, 0, 0);">Goal</strong></h2><p><br></p><p><strong style="background-color: transparent; color: rgb(0, 0, 0);">Add support for more signing schemes for hash-bin delegations under custom delegations: </strong><span style="background-color: rgb(255, 255, 255); color: rgb(0, 0, 0);">Enhance the flexibility of RSTUF’s delegation model to allow for more fine-grained delegation control</span></p><p><strong>TUF visualizer</strong>: Integration of a community-developed visualizer into RSTUF's deployment</p><p><strong style="background-color: transparent; color: rgb(0, 0, 0);">Improve documentation to facilitate easier adoption</strong><span style="background-color: transparent; color: rgb(0, 0, 0);">: Enhance the user-facing documentation to make it clearer, more comprehensive, and more accessible for new adopters, thus accelerating the onboarding process.</span></p>

TBA
Proposal

Add support for Fabric-X

Intermediate
•Varies175h (Medium)

<p>Hyperledger Fabric-X introduces a new architecture for Fabric, with decomposed services for ordering, endorsement, validation, and committing, but its current developer workflow is still centered around dedicated deployment scripts and Ansible-based setup.</p><p>Fablo, on the other hand, is widely used to start Hyperledger Fabric networks quickly from a single configuration file for local development, CI, and experimentation.</p><p>This project will explore and implement the best path to support a simple local Fabric-X network through the Fablo experience. We will evaluate architectural options such as a new engine, a separate repo, or an extension/wrapper approach, then build a minimal but practical MVP that can generate configuration, bootstrap the required components, and start/stop a working local Fabric-X network. The goal is to reduce setup friction for contributors and users, and provide a repeatable developer workflow, examples, and documentation that make Fabric-X easier to try, demo, and extend.</p><h3>Learning Objectives</h3><ul><li>Understand the architecture and deployment model of Hyperledger Fabric-X, including how it differs from classic Hyperledger Fabric.</li><li>Learn how to design contributor-facing tooling for distributed systems with evolving architecture.</li><li>Gain experience in open source development across CLI/tooling, configuration generation, testing, and documentation.</li><li>Develop practical skills in Docker-based environments, and debugging multi-component systems.</li></ul><h3>Expected Outcome and Deliverables</h3><ul><li>A design proposal describing the recommended integration path between Fablo and Fabric-X (for example: separate repo, pluggable engine, or wrapper-based approach).</li><li>An MVP implementation that can bootstrap a simple local Fabric-X network and manage its lifecycle.</li><li>Example configuration(s) and sample workflow for running Fabric-X through the proposed Fablo-based experience.</li><li>Automated tests and/or validation scripts covering the supported MVP scenario.</li><li>Contributor and user documentation explaining setup, architecture decisions, and next steps.</li></ul><p><br></p><p>Lean more at <a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/83" rel="noopener noreferrer" target="_blank">https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/83</a></p>

TBA
Proposal

Formal Methods for Comprehensive Testing of BGP Link-State (BGP-LS) Mentorship Project

Intermediate
•Varies175h (Medium)

<p>*THIS APPLICATION IS ONLY OPEN TO COLLEGE STUDENTS BASED IN CHINA*</p><p><br></p><p><strong>Problem Statement</strong></p><p><br></p><p>BGP Link State (BGP-LS) is a northbound information exchange protocol extension. It allows external clients to subscribe to and collect link-state data (topology, traffic engineering metrics, segment routing SIDs, etc.). Originally designed as an export mechanism, BGP-LS is being increasingly used as a critical feed-back component in the operation and management of cloud network infrastructures. For example, TE controllers may rely on such information to respond to real-time connectivity and traffic status. Thus, the accuracy and reliability of BGP-LS is of foundational importance.</p><p><br></p><p><br></p><p><strong>Mentorship Objectives</strong></p><p><br></p><p>The objective of this mentorship is to develop systematic tests and validations for the BGP-LS implementation. More specifically, it needs to address complexities at various levels to achieve high coverage of the implementation. For example, at the high level, the stateful nature of the protocol extension itself, as well as the dynamic, disaggregated changes in a router's internal states, require thorough exploration of the handling of diverse interaction scenarios and even inconsistent states. At the low level, data processing utilities, such as the parsing of internal routing data formats, also requires systematic testing to validate the handling of both normal and abnormal data.&nbsp;</p><p><br></p><p><br></p><p><strong>Expected Outcomes and Deliverables</strong></p><p><br></p><p>A set of formal models describing both the expected high-level interactions and low-level processing logics of BGP-LS.</p><p>Benchmarks containing diverse interaction sequences and input data, providing comprehensive behavior and code coverage.</p><p>Testing infrastructures to execute, evaluate, and refine these tests.</p><p><strong>*Program Term: Summer - Fall (May - November) 20 hours of work each week*</strong></p><p><br></p><p><br></p><p><strong>Recommended Qualifications</strong></p><p><br></p><ul><li>Proficiency in Python and C/C++</li><li>Basic knowledge of IP networking and routing</li><li>Basic understanding of distributed systems and concurrency</li><li>Ability to navigate and understand complex codebases</li></ul>

TBA
Proposal

Ensuring Behavioral Equivalence in SONiC’s RIB/FIB Architecture

Intermediate
•Varies175h (Medium)

<p><strong>*APPLICATION ONLY OPEN TO COLLEGE STUDENTS BASED IN CHINA*</strong></p><p><br></p><p><strong>Problem Statement</strong></p><p><br></p><p>Software refactoring and restructuring is common in the open-source development of SONiC. Existing code structure may limit the adoption of new usage scenarios or protocol features, necessitating its refactoring into a better logical structure. For example, the ongoing RIB/FIB project intends to separate the RIB and FIB maintenance code in Zebra and move the latter down to SONiC’s fpmsyncd component. Since fpmsyncd resides in SONiC code space, it allows FIB to construct SONiC specific forwarding chain, and handle route convergence based on SONiC’s requirements.</p><p><br></p><p><br></p><p><strong>Mentorship Objectives</strong></p><p><br></p><p>A central requirement in such refactoring is to ensure that behavior changes are exactly as expected. In the RIB/FIB example, it requires that normal executions must be equivalent before and after the refactor. The objective of this mentorship is to devise a systematic approach to validate behavioral equivalence during SONiC refactoring. More specifically, it involves applying formal methods to mathematically describe the intended behavior, compare two distinct setups, and generate comprehensive tests to ensure the consistency before and after the refactor. This will serve as an exemplar of the formal-methods-based correctness paradigm in production code development.</p><p><br></p><p><br></p><p><strong>Expected Outcomes and Deliverables</strong></p><p><br></p><ul><li>Abstract formal models describing expected behavior of the relevant RIB/FIB operations.</li><li>Testing infrastructure that supports parametrized testing of individual modules and execution sequences across modules.</li><li>A test generation framework and the resulting high-coverage benchmark to validate the correctness of the RIB/FIB implementation.</li><li>*<strong>Program Term: Summer / Fall Term (May - November) 20 hours of work each week*</strong></li></ul><p><br></p><p><br></p><p><strong>Recommended Qualifications</strong></p><p><br></p><ul><li>Familiarity with Python and C/C++</li><li>Basic understanding of network forwarding and routing</li><li>Comfort with hands-on systems work under technical guidance, including system setups, trouble shooting, etc.</li><li>Strong communication skills</li></ul>

TBA
Proposal

LFDT - Implementation of a ZK-SNARK Token Driver for Hyperledger Fabric using gnark Mentorship Project

Intermediate
•Varies175h (Medium)

<p>This project aims to implement a new privacy-preserving token driver for the Hyperledger Fabric Token SDK. The architecture will follow the blueprint established in the paper "Privacy-preserving auditable token payments in a permissioned blockchain system" (Androulaki et al.), which outlines a token management system tailored for enterprise networks that requires binding tokens to user identities while supporting fine-grained auditing functionalities for AML/KYC compliance.</p><p><br></p><p>While the original paper relies on specific zero-knowledge proofs and commitments, this mentorship project will adapt the cryptographic backend to utilize zk-SNARKs via gnark, a high-performance ZK-SNARK library written in Go by Consensys. The mentee will be responsible for designing the required ZK circuits for minting, transferring, and auditing tokens, and subsequently integrating these circuits into a fully functional token driver within the Fabric Token SDK framework.</p><p><br></p><h3>Learning Objectives</h3><ul><li>Gain a comprehensive understanding of the Hyperledger Fabric Token SDK architecture and the role of token drivers.</li><li>Develop practical expertise in Zero-Knowledge Proofs (zk-SNARKs) and circuit design using the gnark library.</li><li>​- Understand the cryptographic mechanisms behind privacy-preserving enterprise blockchains, including UTXO models, Pedersen commitments, and identity-bound token ownership.</li><li>Enhance skills in writing highly optimized, concurrent, and secure Go code for distributed systems.</li></ul><h3>Expected Outcome and Deliverables</h3><ul><li>Fully functional gnark circuits implementing the logic for token issuance, private transfers, and auditor revelation as described in the blueprint paper.</li><li>A new ZK-SNARK token driver completely integrated into the Hyperledger Fabric Token SDK.</li><li>A comprehensive test suite, including unit and integration tests for the driver and circuits.</li><li>​- Performance benchmarks evaluating proof generation times, verification times, and transaction throughput compared to existing FTS token drivers.</li><li>Technical documentation detailing the circuit design, driver architecture, and usage instructions.</li></ul><p><br></p><p>Lean more at <a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/67" rel="noopener noreferrer" target="_blank">https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/67</a></p>

TBA
Proposal

Using Formal Methods for Comprehensive Malformed Packet Handling in BGP Implementations Mentorship Project

Intermediate
•Varies175h (Medium)

<p><strong>*APPLICATION ONLY ACCEPTING US BASED COLLEGE STUDENTS*</strong></p><p><br></p><p><strong>Problem Statement</strong></p><p><br></p><p>As an Internet-facing networking protocol, BGP is one of the most critical components of cloud-scale networks. It enables routing information exchanges between a cloud network and the broad Internet, and incorrect behavior could devastate the connectivity of entire regions. Among many vulnerabilities, the proper handling of malformed packets is particularly important due to the propagation mechanisms of BGP. In real production network, a single mis-handling could result in cascading BGP message floodings across entire regions, degrading services or even causing network outages.</p><p><br></p><p><br></p><p><strong>Mentorship Objectives</strong></p><p><br></p><p>Currently, high-level BGP behaviors are well-defined through various RFCs. However, low-level details, such as the validation and handling of malformed packets, are often under-specified. Current testing relies on ad-hoc fuzzing or manual test cases, which may miss subtle state-machine interactions that require specific input combinations.</p><p><br></p><p>The objective of this mentorship is to apply formal methods to systematically validate the handling of malformed packets by concrete BGP software implementations. Unlike traditional approaches, formal methods use mathematical logic to systematically explore diverse behaviors triggered by different input combinations, providing comprehensive validation coverage.</p><p><br></p><p><br></p><p><strong>Expected Outcomes and Deliverables</strong></p><p><br></p><ul><li>A formal specification that describes high-level BGP interactions.</li><li>A set of implementation-agnostic safety invariants derived from the above high-level model. They ensure that invariant-abiding interactions will not cause cascading effects on neighboring BGP devices.</li><li>A reusable framework that applies off-the-shelf formal methods tools to systematically test concrete BGP implementations against the above invariants.</li><li>A benchmark suite of validated malformed packet scenarios with coverage metrics.</li><li><strong>SUMMER / FALL TERM (20~ HOURS OF WORK EACH WEEK)</strong></li></ul><p><br></p><p><br></p><p>Recommended Qualifications</p><p><br></p><ul><li>Familiarity with Python and C/C++</li><li>Basic understanding of networks and routing</li><li>Good analytical skills</li></ul><p><br></p>

TBA
Proposal

LFDT - Implement DKLs23 (threshold ECDSA) protocol Mentorship Project

Intermediate
•Varies175h (Medium)

<p>In standard cryptography, a single compromised key means total failure. Threshold Signing Schemes (TSS) mitigate this by distributing "shares" of a key across&nbsp;n&nbsp;participants, requiring a minimum threshold&nbsp;t&nbsp;participants to engage into the protocol to generate a signature. While the Lockness ecosystem already has a CGGMP24, a threshold ECDSA protocol, the&nbsp;<a href="https://eprint.iacr.org/2023/765.pdf" rel="noopener noreferrer" target="_blank" style="color: rgb(9, 105, 218);">DKLs23</a>&nbsp;protocol presents different features and performance, and unlocks new use-cases.</p><p><br></p><p>In this project, your goal is to transform a formal description of the protocol from the&nbsp;<a href="https://eprint.iacr.org/2023/765.pdf" rel="noopener noreferrer" target="_blank" style="color: rgb(9, 105, 218);">DKLs23 paper</a>&nbsp;into the code utilizing&nbsp;<code style="color: rgb(9, 105, 218); background-color: rgba(129, 139, 152, 0.12);"><a href="https://docs.rs/round-based/latest/round_based/" rel="noopener noreferrer" target="_blank">round-based</a></code>, a framework for TSS protocols, and&nbsp;<code style="color: rgb(9, 105, 218); background-color: rgba(129, 139, 152, 0.12);"><a href="https://docs.rs/generic-ec/latest/generic_ec/" rel="noopener noreferrer" target="_blank">generic-ec</a></code>, a type-safe library for elliptic-curve arithmetics.</p><p><br></p><h3>Learning Objectives</h3><ul><li>Deep Dive into MPC &amp; Threshold Primitives: Transition from theoretical knowledge of cryptography to implementing complex Multi-Party Computation (MPC) protocols, and gain a first-hand understanding of how&nbsp;t-out-of-n&nbsp;security is maintained mathematically.</li><li>Rust Development in the Lockness Ecosystem: Master high-performance, memory-safe programming by contributing to the Lockness ecosystem, specifically using the&nbsp;<code style="color: rgb(9, 105, 218); background-color: rgba(129, 139, 152, 0.12);"><a href="https://github.com/LFDT-Lockness/generic-ec" rel="noopener noreferrer" target="_blank">generic-ec</a></code>&nbsp;library for efficient and type-safe elliptic curve operations.</li><li>Modern Distributed Programming:&nbsp;Learn to write asynchronous code via the&nbsp;<code style="color: rgb(9, 105, 218); background-color: rgba(129, 139, 152, 0.12);"><a href="https://github.com/LFDT-Lockness/round-based" rel="noopener noreferrer" target="_blank">round-based</a></code>&nbsp;framework to manage complex network interactions.</li><li>From Paper to Production:&nbsp;Develop the ability to translate academic research into reliable, auditable, high-quality code, bridging the gap between "whitepaper math" and "real-world software".</li><li>Production-Grade Workflow:&nbsp;Experience a professional development lifecycle where cryptographic code is subject to rigorous peer reviews and testing to ensure maximum security. Learn the discipline required to build cryptographic libraries where every line of code must be verified for both correctness and security.</li></ul><p><br></p><h3>Expected Outcome and Deliverables</h3><p>A library that implements DKLs23 protocol.</p><p><br></p><p>Lean more at <a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/58" rel="noopener noreferrer" target="_blank">https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/58</a></p>

TBA
Proposal

Encrypted Portable Identity for AI Agents, Soul Protocol (Unpaid) Mentorship Project

Intermediate
•Varies175h (Medium)

<p>AI agents can't move between platforms. When a user switches runtimes, their agent's memory, personality, and learned behavior disappear, locked into whatever system created them. There's no open standard for encrypting and exporting an agent's cognitive state.</p><p><br></p><p>Soul Protocol defines a&nbsp;<code style="background-color: rgba(129, 139, 152, 0.12);">.soul</code>&nbsp;file format: an encrypted, portable container for agent identity and memory. It provides core primitives (create, read, write, export, import, encrypt, verify) without prescribing personality models, memory backends, or domain structures.</p><p><br></p><p>This project implements the encryption and portability layer: AES-256-GCM encrypted&nbsp;<code style="background-color: rgba(129, 139, 152, 0.12);">.soul</code>&nbsp;file export/import, machine-derived key management, digital signature verification on import, and a cross-runtime test suite that validates&nbsp;<code style="background-color: rgba(129, 139, 152, 0.12);">.soul</code>&nbsp;files across PocketPaw, LangChain, and CrewAI.</p><p><br></p><p>Reference implementation:&nbsp;<a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/github.com/pocketpaw/pocketpaw" rel="noopener noreferrer" target="_blank" style="color: rgb(9, 105, 218);">PocketPaw</a>, 533+ stars, 3,200+ PyPI downloads and growing, 31 contributors, 2,000+ tests, 7-layer security architecture with Guardian AI.</p><p>Academic context: "Everything is Context" (arXiv:2512.05470) formalizes context engineering for agents but treats them as stateless tools. Soul Protocol adds a persistent identity layer, portable, encrypted, and owned by the user.</p><p><br></p><h3>Learning Objectives</h3><ul><li>Understand encryption primitives for portable file formats (AES-256-GCM, PBKDF2 key derivation) and how they apply to identity systems</li><li>Study protocol design principles for thin open standards, looking at how MCP and W3C DID succeeded through minimal interfaces</li><li>Build cross-runtime compatibility layers in Python targeting multiple agent frameworks (PocketPaw, LangChain, CrewAI)</li><li>Practice test-driven development with 90%+ coverage on security-critical code</li><li>Write technical specifications and documentation for an open standard</li></ul><h3><br></h3><h3>Expected Outcome and Deliverables</h3><ul><li>Encrypted&nbsp;<code style="background-color: rgba(129, 139, 152, 0.12);">.soul</code>&nbsp;file format specification (AES-256-GCM, machine-derived PBKDF2 keys, Ed25519 signature verification)</li><li>Python SDK:&nbsp;<code style="background-color: rgba(129, 139, 152, 0.12);">soul.export(encrypted=True)</code>&nbsp;and&nbsp;<code style="background-color: rgba(129, 139, 152, 0.12);">soul.import(path, key)</code>&nbsp;with complete key management</li><li>Cross-runtime test suite validating&nbsp;<code style="background-color: rgba(129, 139, 152, 0.12);">.soul</code>&nbsp;portability across PocketPaw, LangChain, and CrewAI</li><li>Developer documentation, quickstart guide, and specification document</li><li>Blog post documenting the mentorship experience, technical decisions, and lessons learned</li></ul><p><br></p><p>Lean more at <a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/75 " rel="noopener noreferrer" target="_blank">https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/75</a></p>

TBA
Proposal
Showing 3169 - 3179 of 3179 Projects
131132133
Proposal