Merge branch 'main' into pnet

Author: seetadev

docs/gossipsub-1.2.rst

@@ -0,0 +1,196 @@
+GossipSub 1.2 Protocol Support
+==============================
+
+Overview
+--------
+
+Py-libp2p now supports the GossipSub 1.2 protocol specification, which introduces significant improvements for bandwidth efficiency and network performance. This document provides comprehensive information about the new features, configuration options, and best practices.
+
+What's New in GossipSub 1.2
+----------------------------
+
+GossipSub 1.2 introduces several key improvements over previous versions:
+
+* **IDONTWANT Control Messages**: A new mechanism to inform peers not to send specific messages, reducing unnecessary bandwidth usage
+* **Enhanced Protocol ID**: Uses `/meshsub/1.2.0` protocol identifier
+* **Backward Compatibility**: Maintains full compatibility with GossipSub 1.1 and earlier versions
+* **Improved Memory Management**: Better handling of message tracking and cleanup
+
+IDONTWANT Control Messages
+--------------------------
+
+The most significant feature in GossipSub 1.2 is the introduction of IDONTWANT control messages. These messages allow peers to inform each other about messages they have already received, preventing duplicate message transmission and improving overall network efficiency.
+
+How IDONTWANT Works
+~~~~~~~~~~~~~~~~~~~
+
+1. **Message Reception**: When a peer receives a message, it can send an IDONTWANT control message to its mesh peers
+2. **Bandwidth Optimization**: Mesh peers will avoid sending the same message to the peer that sent the IDONTWANT
+3. **Memory Management**: The system tracks IDONTWANT messages with configurable limits to prevent memory exhaustion
+
+Performance Benefits
+~~~~~~~~~~~~~~~~~~~~
+
+IDONTWANT messages provide the most benefit in scenarios with:
+
+* **Large Messages**: Significant bandwidth savings when preventing duplicate large message transmission
+* **High-Frequency Messaging**: Reduces network congestion in busy pubsub topics
+* **Mesh Networks**: Particularly effective in well-connected mesh topologies
+
+Configuration Options
+---------------------
+
+GossipSub 1.2 introduces new configuration parameters to control IDONTWANT behavior:
+
+max_idontwant_messages
+~~~~~~~~~~~~~~~~~~~~~~
+
+**Default Value**: 10
+
+**Purpose**: Limits the number of message IDs tracked per peer in IDONTWANT lists to prevent memory exhaustion from malicious or misbehaving peers.
+
+**DoS Prevention**: This parameter is crucial for preventing denial-of-service attacks where peers might send excessive IDONTWANT messages to consume memory resources.
+
+**Rationale for Default Value**: The default value of 10 was chosen based on:
+- Analysis of typical message patterns in pubsub networks
+- Balance between memory usage and bandwidth optimization
+- Protection against potential DoS attacks
+- Compatibility with existing network topologies
+
+**Performance Implications**:
+- **Small Messages**: IDONTWANT overhead may exceed benefits for very small messages
+- **Large Messages**: Significant bandwidth savings for messages larger than typical IDONTWANT control message size
+- **High-Frequency Scenarios**: Most beneficial when message frequency is high
+
+Memory Management
+-----------------
+
+GossipSub 1.2 implements aggressive cleanup of IDONTWANT entries during heartbeat intervals to prevent memory leaks.
+
+Current Approach
+~~~~~~~~~~~~~~~~
+
+The current implementation uses aggressive cleanup (clears all entries) which provides:
+
+* **Simplicity**: Easy to understand and maintain
+* **Memory Safety**: Strong guarantees against memory leaks
+* **Suitable for Regular Heartbeats**: Works well for applications with consistent heartbeat intervals
+
+Alternative Approaches
+~~~~~~~~~~~~~~~~~~~~~~
+
+The JavaScript implementation uses time-based expiration, which offers:
+
+* **More Sophisticated**: Tracks timestamps and only clears expired entries
+* **Better for Long-Running Applications**: More efficient for applications with infrequent heartbeats
+* **Future Enhancement**: Could be considered for GossipSub v1.3+ or as a separate optimization
+
+Usage Examples
+--------------
+
+Basic GossipSub 1.2 Setup
+~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+.. code-block:: python
+
+    from libp2p import new_node
+    from libp2p.pubsub.gossipsub import GossipSub
+    from libp2p.pubsub.pubsub import PubSub
+
+    # Create a new libp2p node
+    node = await new_node()
+
+    # Initialize GossipSub with default settings
+    gossipsub = GossipSub()
+
+    # Initialize PubSub with GossipSub
+    pubsub = PubSub(gossipsub)
+
+    # Start the node
+    await node.start()
+
+Custom Configuration
+~~~~~~~~~~~~~~~~~~~~
+
+.. code-block:: python
+
+    from libp2p.pubsub.gossipsub import GossipSub
+
+    # Configure GossipSub with custom IDONTWANT limits
+    gossipsub = GossipSub(
+        max_idontwant_messages=20,  # Allow more IDONTWANT messages per peer
+        # ... other parameters
+    )
+
+Protocol Compatibility
+----------------------
+
+GossipSub 1.2 maintains full backward compatibility:
+
+* **Protocol Negotiation**: Automatically negotiates the highest supported version
+* **Graceful Degradation**: Falls back to GossipSub 1.1 if peers don't support 1.2
+* **Mixed Networks**: Supports networks with both 1.1 and 1.2 peers
+
+Migration Guide
+---------------
+
+Upgrading from GossipSub 1.1 to 1.2 is straightforward:
+
+1. **No Code Changes Required**: Existing applications work without modification
+2. **Automatic Protocol Detection**: The system automatically uses 1.2 when available
+3. **Configuration Optional**: Default settings work for most use cases
+4. **Performance Benefits**: Immediate bandwidth improvements in compatible networks
+
+Best Practices
+--------------
+
+Configuration Recommendations
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+* **Default Settings**: Start with default configuration unless you have specific requirements
+* **Monitor Memory Usage**: Keep an eye on memory consumption in long-running applications
+* **Network Analysis**: Consider your message size and frequency patterns when tuning parameters
+* **Security Considerations**: Be aware of potential DoS vectors and configure limits appropriately
+
+Performance Optimization
+~~~~~~~~~~~~~~~~~~~~~~~~
+
+* **Message Size**: IDONTWANT is most beneficial for messages larger than ~1KB
+* **Network Topology**: Works best in well-connected mesh networks
+* **Heartbeat Frequency**: Regular heartbeats ensure proper cleanup of IDONTWANT entries
+* **Peer Management**: Monitor peer behavior for excessive IDONTWANT usage
+
+Troubleshooting
+---------------
+
+Common Issues
+~~~~~~~~~~~~~
+
+**High Memory Usage**
+- Check if `max_idontwant_messages` is set too high
+- Monitor for peers sending excessive IDONTWANT messages
+- Consider reducing the limit if memory usage is a concern
+
+**Network Performance**
+- Verify that peers support GossipSub 1.2
+- Check network topology and connectivity
+- Monitor message sizes and frequency patterns
+
+**Compatibility Issues**
+- Ensure all peers are using compatible libp2p versions
+- Check protocol negotiation logs
+- Verify network configuration and firewall settings
+
+Specification References
+------------------------
+
+* `GossipSub v1.2 Specification <https://github.com/libp2p/specs/blob/master/pubsub/gossipsub/gossipsub-v1.2.md>`_
+* `libp2p PubSub Specification <https://github.com/libp2p/specs/blob/master/pubsub/README.md>`_
+* `Py-libp2p GossipSub API Documentation <libp2p.pubsub.gossipsub>`_
+
+Related Documentation
+---------------------
+
+* :doc:`examples.pubsub` - Practical examples using GossipSub
+* :doc:`libp2p.pubsub` - Complete PubSub API documentation
+* :doc:`getting_started` - Getting started with Py-libp2p

docs/index.rst

@@ -18,6 +18,7 @@ The Python implementation of the libp2p networking stack
 
     Examples <examples>
     API <libp2p>
+    GossipSub 1.2 <gossipsub-1.2>
 
 .. toctree::
     :maxdepth: 1

docs/introduction.rst

@@ -33,7 +33,7 @@ Current Capabilities
 Py-libp2p currently supports these core libp2p features:
 
 * **Transports**: TCP, QUIC (near completion, in final testing phase)
-* **Protocols**: Gossipsub v1.1, Identify, Ping
+* **Protocols**: Gossipsub v1.1 and v1.2, Identify, Ping
 * **Security**: Noise protocol framework
 * **Connection Management**: Connection multiplexing
 

docs/libp2p.pubsub.rst

@@ -1,6 +1,10 @@
 libp2p.pubsub package
 =====================
 
+Py-libp2p provides a comprehensive PubSub implementation with support for both FloodSub and GossipSub protocols, including the latest GossipSub 1.2 specification with IDONTWANT control messages for improved bandwidth efficiency.
+
+For detailed information about GossipSub 1.2 features and configuration, see :doc:`gossipsub-1.2`.
+
 Subpackages
 -----------
 

examples/doc-examples/README_mplex_timeouts.md

@@ -0,0 +1,80 @@
+# Mplex Stream Timeout and Deadline Example
+
+This example demonstrates the new timeout and deadline features in MplexStream, including deadline validation, timeout handling, and real-world timeout scenarios.
+
+## Features Demonstrated
+
+### 🔍 Deadline Validation
+
+- **Negative TTL values**: Returns `False` and doesn't modify deadlines
+- **Zero TTL values**: Returns `True` and sets immediate timeout
+- **Positive TTL values**: Returns `True` and sets timeout as expected
+
+### ⏰ Timeout Scenarios
+
+- **Normal operation**: Read/write with reasonable timeouts
+- **Short timeouts**: Demonstrates timeout behavior with very short deadlines
+- **Write timeouts**: Shows timeout handling for write operations
+- **Error handling**: Graceful handling of timeout exceptions
+
+### 🛠️ New Methods Demonstrated
+
+- `set_deadline(ttl)`: Sets both read and write deadlines
+- `set_read_deadline(ttl)`: Sets read deadline only
+- `set_write_deadline(ttl)`: Sets write deadline only
+- All methods now return `True`/`False` based on TTL validation
+
+## Usage
+
+The example requires a `--role` parameter to specify whether to run as server or client.
+
+**Note**: Running without parameters will show the help message with all available options.
+
+### 1. Start the Server
+
+```bash
+python example_mplex_timeouts.py --role server --port 8000
+```
+
+### 2. Start the Client
+
+```bash
+python example_mplex_timeouts.py --role client --destination /ip4/127.0.0.1/tcp/8000/p2p/QmServerPeerID
+```
+
+### 3. Run with Verbose Logging
+
+```bash
+python example_mplex_timeouts.py --role server --port 8000 --verbose
+```
+
+## What You'll See
+
+The demo will show:
+
+- ✅ Deadline validation results for different TTL values
+- ⏰ Timeout behavior with various deadline settings
+- 📤📥 Stream communication with timeout handling
+- 🔍 Error handling for invalid TTL values
+- 📊 Real-time demonstration of timeout features
+
+## Key Improvements
+
+This example showcases the refactored MplexStream implementation with:
+
+- **Input validation**: Proper handling of negative TTL values
+- **Meaningful return values**: Methods return `True`/`False` based on success
+- **Unified timeout handling**: Consistent timeout behavior across read/write operations
+- **Better error messages**: Descriptive timeout error messages
+- **Comprehensive testing**: Edge cases and real-world scenarios
+
+## Technical Details
+
+The example uses:
+
+- **Explicit mplex configuration**: `muxer_opt={MPLEX_PROTOCOL_ID: Mplex}`
+- **InsecureTransport**: Plaintext communication for demonstration purposes (not recommended for production)
+- **Trio async framework**: Non-blocking timeout operations
+- **Comprehensive logging**: Detailed output for understanding timeout behavior
+
+This demonstrates how the new timeout features make MplexStream more robust and easier to use in production applications.