Welcome to specs Discussions!

[seetadev]

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.

To get started, comment below with an introduction of yourself and tell us about what you do with this community.

[adarsh-7-satyam]

Hi @seetadev,

Thank you so much for the warm welcome and for sharing these resources! I am really excited about this project and would love to introduce myself and share what I have been working on.

About Me

I am Adarsh Satyam, a second-year B.Tech Computer Science student at IIT Bhilai. I have a strong background in Python, Java, and full-stack development, and I am deeply interested in open source infrastructure and distributed systems.

Open Source Experience

I participated in FOSS Overflow, an open source program by FOSS United, where I contributed production-grade features to a real-world placement portal. My contributions included designing a centralized Zod-based validation architecture eliminating mass-assignment vulnerabilities, migrating the frontend data layer to TanStack Query with caching and optimistic updates, and building a role-based public landing page improving onboarding and navigation consistency.

I was also selected as a FOSSEE Summer Intern at IIT Bombay where my screening task involved debugging Bash installer scripts on Ubuntu 25.04, giving me hands-on experience with low-level system tooling and open source workflows.

Pre-Contributions to This Project

After studying the repository deeply, I have already submitted four PRs to seetadev/specs:

• PR docs: add sequence diagrams for partial messages protocol flows #11 — Added four Mermaid sequence diagrams to partial-messages.md covering Extension Negotiation, Eager Push Flow, partsMetadata Exchange, and Heartbeat Gossip flows to help new implementers build a correct mental model of the protocol
• PR docs: add recommended metadata encodings for Partial Messages extension #13 — Added metadata-encodings.md documenting three recommended standard encoding approaches for partsMetadata — Bitmask, Range-based, and Bloom Filter — with concrete worked examples, wire format specifications, and an encoding selection guide
• PR docs: add security considerations and threat model for Partial Messages extension #15 — Added security-considerations.md providing a comprehensive threat model identifying six new attack vectors specific to the Partial Messages extension with concrete mitigations and an actionable implementation checklist
• PR docs: add Gossipsub v1.4 specification draft for large payload optimizations #17 — Added gossipsub-v1.4.md, a formal Working Draft specification for Gossipsub version 1.4 with protocol ID /meshsub/1.4.0, bundling Partial Messages, Batch Publishing, IDONTWANT on First Publish, and WFR Gossip into a single cohesive versioned protocol

My Idea for This Project

My approach is to tackle this project in four phases. The first phase focuses on refining the gossipsub-v1.4.md specification draft based on mentor feedback and submitting it as a formal RFC PR to the libp2p/specs repository. The second phase covers completing wire format documentation and encoding recommendations to ensure cross-implementation compatibility. The third phase involves building interoperability tests in Python using py-libp2p to validate large message propagation against nim-libp2p under real network conditions. The fourth phase covers documenting reproducible test reports and preparing the specification for Working Draft and Candidate Recommendation status progression.

I am also very excited about the py-ipfs-lite repository and the upcoming libp2p and IPFS meetup. I will definitely go through the py-libp2p documentation and explore the py-ipfs-lite discussions. Looking forward to collaborating with the community!